ISC · Information Systems and Data Management · 6 practice questions
Master Data vs Reference Data vs Transactional Data vs Metadata
Classify data by what it represents: business entities, events, controlled codes, or descriptions of data. Sort Apex's customer and billing datasets into these categories, then apply the rule in free practice questions.
Try one first
Hint
Decide for each item whether it (a) identifies a persistent entity, (b) records an event, (c) is a standardized code/value list used across processes, or (d) describes data structure/meaning.
Answer B. Employee profile records identify a persistent business entity (the employee) and its core attributes, so they are master data. Payroll journal entries capture discrete pay events and amounts and are therefore transactional data. A job-grade code table is a standardized list of domain values used across processes (reference data), while schema and data dictionaries describe the structure and meaning of data (metadata).
Why not A: This is tempting because job-grade codes relate to compensation and look like business information, but they are not records of an entity, they are a standardized value list used across systems (reference data). Likewise, schema/dictionaries document data meaning and structure (metadata), not domain value lists.
Why not C: This option misclassifies the employee profile as transactional. Although employee attributes can change over time, the profile describes a persistent entity and its attributes (master data); transactions record events such as pay runs.
Why not D: Payroll journal entries might be reused in reporting, but they record specific payment events and amounts, so they are transactional rather than reference data. The other classifications in this option are correct.
Sort it
Does it identify a persistent business entity or maintain its authoritative attributes for reuse across processes?
Does it supply controlled codes or classification values that other records use?
Does it record an individual business event rather than describe the ongoing entity?
Does it describe data's structure, meaning, or lineage rather than supply business records or codes?
| Item | Goes to |
|---|---|
| Apex's centrally approved pricing-tier table: tier code, description, and effective date, shared across billing and sales. | Reference dataThese are controlled classification values. Central governance and effective dates do not turn the list into entity records. |
| Apex's customer file: unique customer ID, legal name, billing address, and credit terms, authoritative across sales and billing. | Master dataEach row describes a persistent customer entity reused across business processes. |
| Apex's invoice archive: invoice ID, customer ID, invoice date, amount, and a snapshot of the customer's credit limit. | Transactional dataEach invoice records a billing event. Copying a master attribute onto it does not change the invoice's role. |
| Apex's data dictionary entry defining Customer_ID, including its meaning, data type, and permitted format. | MetadataThe entry describes a field; it does not identify an actual customer. |
| Apex's current credit-limit table: one row per customer, recalculated nightly and reused by sales, collections, and finance. | Master dataThe table maintains a current customer attribute. Frequent recalculation does not make it an event log. |
| Apex's payment records: payment ID, customer ID, receipt date, and amount received. | Transactional dataEach row captures a separate payment event, not the customer's ongoing identity or attributes. |
| Apex's approved two-letter state-code table used to validate customer addresses. | Reference dataThe table supplies allowable values for address entry rather than records of customers. |
| Apex's lineage documentation showing how customer credit-limit data move from the central table into billing. | MetadataIt describes the origin and movement of data rather than storing customer limits or billing events. |
| Apex's authoritative customer address records: customer ID, effective-dated billing and shipping addresses, and primary contact. | Master dataThese remain customer-level descriptive attributes. Effective dates alone do not turn entity records into transactions. |
| Apex's sales order lines: order ID, customer ID, quantity, and price at the time of sale. | Transactional dataThe rows capture individual sales activity. Referencing a customer ID does not make them customer master records. |
| Apex's database schema defining customer-table columns, data types, and relationships to invoice tables. | MetadataThe schema describes how data are structured and related, not the business entities or events themselves. |
| Apex's approved order-status codes and descriptions, synchronized across sales and billing applications. | Reference dataThe dataset defines allowable statuses. It does not record individual orders or changes to their status. |
Key points
- Remember: Classify what a record represents, not how often it changes or how widely it is shared.
- A customer ID on an invoice links an event to an entity; it does not make the invoice master data.
- MDM targets authoritative customer attributes, not every dataset containing a customer ID.
How the exam traps you
- Calling approved codes master data because they are centrally governed and shared. Look at their purpose: controlled classification values are reference data.
- Calling a nightly credit-limit update transactional data. One current value per customer remains an entity attribute, not a record of individual events.
- Treating a field definition and its lookup table as the same category. Field documentation is metadata. The actual controlled code list is reference data.
Question 2
Hint
Focus on what distinguishes master data from transaction data: think about how broadly the data is shared and what role it plays across the business.
Answer A. Master data is the relatively stable, core business information (for example, products, customers, vendors) that serves as an authoritative reference across functions and systems. In this scenario the same product information is used and edited in sales, purchasing, and inventory applications, producing inconsistencies, making enterprise-wide shared use the key factor for treating the records as master data. If the data is an authoritative, cross-system reference, implementing MDM is appropriate.
Why not B: High volume affects storage and processing considerations but does not define master data. Frequently created data is often transactional; master data is identified by being a shared, stable reference across systems rather than by its creation rate.
Why not C: If data primarily serves one department, it is less likely to be enterprise master data. Master data is typically important across multiple departments and processes, so single-department importance points away from an MDM classification.
Why not D: Whether data is temporary or retained is a lifecycle consideration, not the defining trait of master data. Data that is deleted after processing is usually transactional or temporary, whereas master data is maintained as an ongoing authoritative reference.
Question 3
Hint
Focus on which option is the shared business record about an entity, not a transaction, log, or description of a field.
Answer A. Master data is the core business data about entities (for example, customers, vendors, and products) that is used across multiple systems and transactions. The vendor record is the shared, relatively stable source of vendor information that purchasing, receiving, and accounts payable should all reference. Treating the vendor record as master data ensures consistency and reduces duplicate or conflicting updates.
Why not B: This is transaction data created for specific purchases; while POs may contain vendor address details, they are not the authoritative, reusable source of vendor information and updating POs does not create a single authoritative vendor record for future transactions.
Why not C: An audit log records change events and supports accountability, but it is not the business data itself. The log documents who made changes and when, rather than serving as the operational source of vendor address information.
Why not D: A data dictionary is metadata, it describes the structure, format, and rules for fields but does not contain the actual vendor values used in transactions. It helps with consistency but is not the master business record for vendor data.
Question 4
Hint
Ask whether the dataset itself contains full identifiers or can reidentify a person on its own; masked digits or surrogate IDs with a separate encrypted crosswalk generally do not qualify as Restricted.
Answer B. Option B is Restricted because it contains direct PII (legal name together with a full tax ID) and account/contact details that can identify an individual on their own, meeting the policy's definition of Restricted.
Why not A: Tempting because it contains detailed transaction history and a partial account value, but it uses a surrogate customer reference ID and only a masked last-four of an account number; without the encrypted crosswalk, these elements cannot reidentify an individual on their own, so this log is not Restricted.
Why not C: Tempting if one confuses sensitivity with identifiability, but aggregated totals lack PII or transaction-level detail and cannot reidentify individuals, so C does not meet the Restricted definition.
Why not D: Tempting only if focusing on business-critical data rather than PII; a product catalog contains no personal identifiers or account numbers tied to individuals, so it is not Restricted.
Question 5
Hint
Decide whether the value primarily describes the customer entity across systems (persistently maintained), is tied to a single transaction (a snapshot), is a controlled lookup list, or describes the data itself.
Answer B. The customer credit limit is an attribute of the customer entity, centrally maintained and reused across order entry, collections, and finance, characteristics of master data. The value stored on an invoice is a snapshot capturing the master-data state at transaction time; recording that snapshot does not convert the underlying attribute into transactional data.
Why not A: Tempting because a copy of the credit limit appears on each invoice and is stored with transaction records. It's wrong because transactional data represent the event (the invoice); the invoice field is a snapshot of the master attribute, not the canonical source of the customer credit limit.
Why not C: Tempting if candidates think of credit limits as constrained tiers or lookup values. It's wrong because reference data are controlled lists or codes shared across records; a customer's specific numeric credit limit is an entity attribute, not a reference list in the scenario described.
Why not D: Tempting because credit limits affect processes and are documented, which might sound like 'data about data.' It's wrong because metadata describe or document data (names, formats, provenance); the credit limit itself is business data about the customer.
Question 6
Hint
Focus on what the dataset fundamentally contains: core entity records, business events, data-about-data, or standardized allowable values used by other records.
Answer B. The dataset is reference data because it contains approved code sets (payment-term codes, tax-exempt reasons, order statuses) that other systems use to validate, classify, and control transactions. Being centrally governed and shared across applications does not make it master data, which represents core business entities like customers or products. It does not record business events (transaction data) nor primarily describe schema or lineage (metadata).
Why not A: This is tempting because the table is centrally governed and used across systems, but master data typically represents core entities (e.g., customers, vendors, items). A list of allowable codes is a reference list, not records of the core business entities themselves.
Why not C: Candidates may be distracted by the fact the table is effective-dated, but transaction data captures individual business events (orders, invoices, receipts). Updating or versioning a code table is an administrative change to reference data, not the recording of operational transactions.
Why not D: Although the codes may be accompanied by descriptive labels, metadata refers to data-about-data (field formats, lineage, owners, control attributes). The code values themselves are standardized allowable values used by transactions, which is the definition of reference data.
Common questions
What is the difference between master data and reference data?
Master data describe specific business entities, such as Apex's customers. Reference data supply controlled values used to classify or validate those entities, such as approved pricing-tier codes.
Is a customer credit limit master data or transactional data?
Apex's centrally maintained current credit limit is master data, even when recalculated nightly. An invoice containing a snapshot of that limit remains a transaction record.
Are allowed values reference data or metadata?
Apex's actual list of approved status codes is reference data. Documentation explaining the status field's meaning, format, and permitted values is metadata.
Watch it solved
A full CPA ISC task-based simulation on Data management, worked step by step.
Data Quality Defects & ETL Reconciliation | CPA ISC Simulation (TBS) 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 Data management
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.