ISC · Information Systems and Data Management · 7 practice questions
ERP Cores, Hybrid Architectures, and Best-of-Breed
A shared transactional platform integrating operations and accounting is an ERP, even with external payroll. Below, compare the primary system with the overall architecture to separate ERP cores, hybrid architectures, and best-of-breed systems.
Try one first
Hint
Decide whether a single system executes and records the core operational and financial transactions (look for a shared database and real‑time posting) or whether transaction authority is distributed or purely analytical.
Answer D. The environment matches an ERP: operational (sales, inventory, MRP, procurement) and financial (AP, AR, GL) modules are integrated on a single shared database with real‑time subledger‑to‑GL posting and automated cross‑module workflows. External SaaS for HR/CRM and a downstream analytics warehouse do not negate ERP status when core transaction processing is centralized in one system.
Why not A: Tempting since a downstream data warehouse is mentioned for reporting and analytics. It fails because a data warehouse aggregates data for analysis and is not the operational system that executes and posts daily transactions, the described environment performs those transactional activities.
Why not B: Tempting because the system includes GL, AP, and AR and performs accounting functions. It fails because an AIS implies a primarily accounting‑centric system; Apex's environment also centralizes operational modules (sales, inventory, MRP, procurement) on the same transactional platform, which is characteristic of an ERP.
Why not C: Tempting because HR/payroll and CRM are third‑party SaaS integrated via APIs, suggesting multiple vendors. It fails because best‑of‑breed implies distributed transactional authority; here the core operational and financial transactions originate and post within one integrated platform, so there is a centralized transactional system.
Side by side
| ERP with payroll inside the suite | ERP core with external payroll (hybrid architecture) | Best-of-breed without an ERP core | |
|---|---|---|---|
| Core operations and accounting | Native modules in one integrated suite. | Native modules in one integrated ERP core. | Separate specialist applications linked through interfaces. |
| Transactional database | One shared database includes payroll. | One shared core database; payroll has a separate database. | Separate application databases; no shared ERP core. |
| Operational posting to the general ledger | Core modules post immediately within the suite. | Core modules post immediately within the ERP. | Interfaces transfer transactions in real time or batches. |
| Where payroll is processed | Inside the suite. | By an external specialist provider. | In a separate specialist payroll application. |
| Payroll data flow | Native processing within the shared platform. | API or batch interface connects payroll to the ERP. | Interfaces connect payroll to separate accounting applications. |
| Shared chart of accounts or single sign-on | Consistent with ERP, but not sufficient proof. | Does not bring external payroll inside the core. | Can exist despite separate transactional databases. |
| What the question asks | Primary platform: ERP. Overall architecture: integrated suite. | Primary platform: ERP. Overall architecture: hybrid. | Overall processing environment: best-of-breed. |
| Deciding evidence | Shared transactional platform integrates operations, accounting, and payroll. | ERP core remains ERP; external payroll supports the hybrid architecture label. | Separate interfaced applications operate without an ERP core. |
Key points
- Remember: ERP describes the integrated core; hybrid can describe the broader architecture containing that same core.
- Read the answer's qualifiers: external payroll contradicts “all functions inside the suite,” not “ERP.”
- Real-time payroll interfaces do not put external payroll processing inside the ERP.
How the exam traps you
- Rejecting ERP solely because payroll is external. Classify the primary platform as ERP; use hybrid when describing the broader architecture.
- Calling separate applications an ERP because they share a chart of accounts or single sign-on. Look for a shared transactional database, not just shared codes or access.
- Calling an ERP core plus external payroll best-of-breed without considering the core. An integrated ERP core distinguishes hybrid architecture from best-of-breed without an ERP core.
Question 2
Hint
Focus on the feature that best distinguishes the system from a stand-alone sales or reporting application.
Answer B. The system updates multiple functional areas (inventory, receivables, production) from a single shared database, indicating enterprise-wide integration. That integration of core operational modules and shared data is the hallmark of an ERP system; while it performs transaction processing and reporting, its best overall classification is ERP.
Why not A: This is tempting because the system captures routine sales transactions, but TPS refers mainly to transaction capture and processing. The scenario describes cross-functional, integrated updates across modules, which goes beyond a TPS-only classification.
Why not C: Managers can generate routine reports (an MIS feature), but MIS emphasizes reporting and summary information for management. The presence of a shared database that updates inventory, receivables, and production points to an integrated enterprise system (ERP), not MIS-only.
Why not D: A DSS supports analytical, model-based, or 'what-if' decision making. The scenario describes routine operational processing and integrated modules rather than specialized analytical modeling, so DSS is not the best classification.
Question 3
Hint
Focus less on the number of source systems and more on the repository's refresh pattern, data volatility, and whether it supports operational action or long-term analytics.
Answer D. An operational data store integrates current data from multiple source systems for near-real-time operational reporting and monitoring. The frequent (15-minute) refreshes, emphasis on same-day operational decisions, limited recent history (~90 days), and routine overwrites when source data changes are all characteristic of an ODS rather than a historical analytics repository.
Why not A: A data lake stores large volumes of raw or lightly processed data in varied formats for flexible downstream use. The repository described stores structured, standardized data for purpose-built operational dashboards and is read-only with frequent refreshes, traits inconsistent with the typical raw, exploratory nature of a data lake.
Why not B: This is tempting because the repository integrates data from multiple systems and supports reporting. However, a data warehouse is designed for historical, relatively stable, analysis-oriented data and long-term trend reporting; the facts state multi-year analysis is done in a separate snapshot environment, which points away from an EDW.
Why not C: A data mart is typically an analytical store focused on a particular function or department. Although the repository supports a narrower operational purpose (fulfillment and collections), its near-real-time refreshes and volatile, routinely overwritten records make it an operational hub rather than an analytics-oriented departmental mart.
Question 4
Hint
Focus on whether the system is mainly for analysis, customer management, or integrated transaction processing across multiple business functions.
Answer B. An ERP system integrates multiple business functions through a common database and shared processing. The stem describes transactional integration, one system that records a sales order and automatically updates inventory, accounts receivable, and the general ledger, which is the defining feature of ERP. ERP systems enable cross-functional processes and shared data across operations and accounting.
Why not A: A DSS is designed to help managers analyze data and make decisions using models and reports; it supports analysis rather than performing live transactional processing that updates inventory, receivables, and the GL.
Why not C: A data warehouse is a consolidated repository optimized for reporting and analysis, typically populated from operational systems; it does not itself process live transactions to update operational records in real time.
Why not D: A CRM focuses on managing customer interactions and sales activities; while it may integrate with other systems, the stem describes broader operational and accounting integration that is characteristic of an ERP.
Question 5
Hint
Focus on what makes a system 'integrated' at the transaction-processing level: shared operational data and unified application design versus separate systems connected by interfaces.
Answer D. The applications are separate products from different vendors and are connected by middleware, synchronization routines, exception reports, and reconciliations. Those facts indicate multiple interfaced best-of-breed systems rather than a single fully integrated ERP that shares one common operational database. The separate data warehouse is used for reporting and analytics and does not serve as the operational transaction system of record.
Why not A: This is tempting because single sign-on, a shared chart of accounts, and automated flows resemble ERP behavior. However, the stem explicitly states the applications are separate vendor products with nonuniform field definitions and require reconciliations across interfaces, contradicting the presence of one shared operational database.
Why not B: Overnight synchronization and reconciliations might suggest some batch elements, but Mercury has multiple linked enterprise applications, automated middleware flows, and frequent (every 30 minutes) subledger postings, so the environment is more integrated than a minimal, stand-alone batch system.
Why not C: This distractor leverages the fact that reporting comes from a separate data warehouse, but a data warehouse is typically for analytics and reporting and is not the operational system of record for purchasing, inventory, payables, or GL transaction processing.
Question 6
Hint
Ask whether payroll runs in the same central database and whether its integration is immediate (real-time) or only periodic (batch).
Answer B. Most core finance and operational modules run in VendorOne's integrated ERP on a central real-time database, while payroll is handled by an external provider and only returns summarized results via nightly batch postings to the GL. That combination, core functions in an integrated ERP plus a separate specialist payroll system connected by periodic (batch) interfaces, is a hybrid architecture (integrated core + best-of-breed external systems).
Why not A: This is tempting because many core modules are on one integrated system with a real-time database. It fails because payroll is not processed inside that ERP and only posts summarized results via nightly batches, so the ERP does not handle payroll as part of a unified, real-time database.
Why not C: This distractor tempts because multiple vendors are present. It is incorrect because VendorOne provides the core modules as a single integrated suite (not separate specialist systems), and the payroll link is a nightly summary batch rather than the tight, near-real-time middleware integration characteristic of best-of-breed architectures.
Why not D: This can lure candidates who hear 'separate systems.' Two-tier refers specifically to separate ERP instances at different organizational tiers (corporate plus subsidiary/local ERPs). The scenario instead describes an external payroll service exchanging summarized batch results, not additional local ERP instances, so two-tier is incorrect.
Question 7
Hint
Determine whether the system is a single integrated operational package handling real‑time transactions and ledger postings across functions (ERP) or is primarily for analysis or composed of separate applications linked by middleware.
Answer C. The stem describes a single integrated application that centralizes master data across multiple functional areas, processes real-time transactions, generates automatic GL postings and subsidiary ledger updates, and supports intercompany eliminations and consolidation, core characteristics of an ERP with an integrated accounting/GL module. While the system also performs transaction processing and supports dashboards, those capabilities alone do not outweigh the cross-functional integration and consolidation features that identify it as ERP.
Why not A: This distractor plays on the mention of dashboards and historical analysis, but data warehouses/BI systems are for reporting and do not perform real-time transactional processing, post entries to subsidiary ledgers, or handle operational consolidations, the operational activities described occur in the primary system, not the warehouse.
Why not B: This is tempting because the system processes transactions and posts to the general ledger, which are TPS activities. It is incorrect because a TPS typically denotes a narrower, accounting-focused transactional application; the described single, cross-functional package with centralized master data and consolidation features fits ERP rather than a TPS limited to accounting tasks.
Why not D: While organizations sometimes use multiple best-of-breed apps linked by middleware, the stem explicitly specifies a single integrated enterprise application with centralized master data and automatic postings. That language indicates an ERP rather than multiple distinct point solutions connected by middleware.
Common questions
Is a system still an ERP if payroll is outsourced?
Yes. External payroll does not negate the ERP classification of an integrated operations-and-accounting platform. The overall architecture can also be described as hybrid.
What is the difference between hybrid ERP and best-of-breed?
Hybrid architecture combines an ERP core with external specialist applications. Best-of-breed without an ERP core relies on separate specialist applications linked through interfaces.
Do single sign-on and a shared chart of accounts mean a system is ERP?
No. Separate applications can share both while maintaining separate transactional databases. The deciding evidence is how operations and accounting process and share transactions.
Watch it solved
A full CPA ISC task-based simulation on Enterprise and accounting information systems, worked step by step.
ISC Simulation: Mapping Controls Through Order-to-Cash on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Enterprise and accounting information systems
- AP-to-GL Batch Recovery: Fix, Reprocess, and Reconcile
- ERP Revenue Recognition: Shipment vs. Invoice Date
- ERP Vendor Master Data Governance: One Controlled Source
- Auditing ERP Automated Controls: ITGCs and Data Conversion
- ERP Data Residency: When Local Laws Govern Deployment
All Enterprise and accounting information systems practice →
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.