PracticeISCFree practice exam

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.

The ruleMaster data describe persistent core business entities. Reference data supply controlled classification or validation values; transactional data record business events; metadata describe data's structure, meaning, or lineage.

Try one first

Company Z uses an integrated HR/ERP system. For data-governance and master-data-management purposes, classify each of the following items as Master data, Transactional data, Reference data, or Metadata. Assume these objects are used enterprise-wide and stored in the company's core systems. Items: 1. Employee profile record (employee ID, legal name, home address, hire date). 2. Payroll journal entries that record each pay run (employee ID, pay date, gross pay, taxes withheld). 3. Job-grade code table that maps grade codes (G1, G2, etc.) to compensation bands and benefit eligibility rules. 4. Database schema definitions and the data dictionary that document table/field names, data types, and allowed values.
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.

Sort it

Master data

Does it identify a persistent business entity or maintain its authoritative attributes for reuse across processes?

Reference data

Does it supply controlled codes or classification values that other records use?

Transactional data

Does it record an individual business event rather than describe the ongoing entity?

Metadata

Does it describe data's structure, meaning, or lineage rather than supply business records or codes?

ItemGoes 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.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

A manufacturer stores product records in separate sales, purchasing, and inventory applications. Because each area can edit product descriptions independently, reports often show inconsistent product names for the same item. Management is considering a master data management approach for product records. Assuming cost and system capacity are not the deciding constraints, which factor should primarily govern whether these records should be treated as master data?
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.

Question 3

Atlas Co. is integrating its purchasing, receiving, and accounts payable systems. Management wants a single source of truth so that a vendor address change is entered once and then used consistently in future transactions across all three systems. Which data item should Atlas treat as master data?
Hint

Focus on which option is the shared business record about an entity, not a transaction, log, or description of a field.

Question 4

Company X's data classification policy has three levels: Public, Internal, and Restricted. Restricted is defined as data that contains direct personally identifiable information (PII) (for example, legal name plus a full tax ID, or full financial account numbers) or any dataset that can reidentify an individual on its own. The company stores the following datasets in its cloud data warehouse. Assume the mapping (crosswalk) from surrogate customer reference IDs to identifying details is stored separately, encrypted, and accessible only to a small security team. Which single dataset below should be classified as Restricted?
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.

Question 5

Company Apex uses an ERP system. The 'Customer credit limit' field is stored in the central customer table and is maintained by the credit department (changes only after formal credit reviews). The value is used by order entry, collections, and finance across multiple transactions; a copy of the customer's credit limit is also snapshotted on each invoice for audit purposes and is searchable in the invoice archive. Under a standard data management taxonomy, how should the 'Customer credit limit' be classified?
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.

Question 6

Assume the entity's data governance program uses these standard definitions: master data describes core business entities the entity manages and reuses across processes; reference data consists of standardized allowable values used to classify, validate, or control other data and transactions; transaction data records business events; metadata describes the structure, meaning, lineage, or control attributes of data. As part of an ERP integration, the company creates one centrally governed dataset containing approved payment-term codes, tax-exemption reason codes, and order-status codes. The dataset is effective-dated, synchronized to multiple applications, and each transaction stores only the applicable code rather than the code definition. Under these definitions, how should this dataset be classified?
Hint

Focus on what the dataset fundamentally contains: core entity records, business events, data-about-data, or standardized allowable values used by other records.

Drill all 170 Data management questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Data management 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.