CPA Isc Quiz: Assess Data Quality And Integrity Controls

What this quiz covers

This quiz focuses on Assess Data Quality And Integrity Controls, giving you a quick way to practice the rules, question types, and explanations that matter most for CPA Isc.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

Question 1

1. Encryption of all vendor payment records.
2. Automated duplicate detection routines that compare key fields (vendor ID, invoice number, amount, date) and flag matches. (correct answer)
3. Requiring all accounts payable staff to attend data quality training.
4. Restricting accounts payable access to senior finance staff only.

Explanation: Automated duplicate detection analyzes key transaction fields to identify records that appear to be duplicates, directly addressing the risk of duplicate payments. Answer B is correct. Encryption (A), training (C), and access restriction (D) do not detect existing duplicate records.

Question 2

1. Data integrity violation caused by referential integrity failure.
2. Confidentiality breach exposing customer information.
3. Duplicate record or data consistency problem reducing data accuracy and reliability. (correct answer)
4. Normalization failure requiring database redesign.

Explanation: Multiple records for the same entity with inconsistent data is a duplicate/consistency problem - a classic data quality issue that can cause errors in reporting and customer communications. Answer C is correct. Referential integrity (A) concerns foreign key relationships, not duplicates. Confidentiality (B) is unrelated. Normalization (D) addresses redundancy in schema design, not record-level duplicates.

Question 3

1. Define and enforce data quality standards, resolve data issues, and manage the accuracy and consistency of data within their assigned domain. (correct answer)
2. Encrypt all data within their domain to prevent unauthorized access.
3. Back up all data within their domain on a daily basis.
4. Develop the database schema for their assigned data domain.

Explanation: A data steward is accountable for the quality, consistency, and fitness for use of data in their domain - defining standards, resolving issues, and coordinating with data owners and users. Answer A is correct. Encryption (B), backup (C), and schema development (D) are IT operational or technical functions, not data stewardship roles.

Question 4

1. Different font sizes used in reports generated by subsidiary systems.
2. Inconsistent account coding and chart of accounts structures across subsidiaries, making it impossible to accurately aggregate financial data. (correct answer)
3. Subsidiary systems operating in different time zones.
4. Varying numbers of decimal places used in local currency display.

Explanation: Inconsistent chart of accounts and account coding across subsidiaries is a major data consistency problem that directly prevents accurate financial consolidation - transactions may be miscategorized or unmappable. Answer B is correct. Font sizes (A) are formatting issues. Time zones (C) and decimal display (D) are manageable technical issues that do not inherently prevent consolidation.

Question 5

1. Completeness - ensuring all required data elements are present before a record is saved. (correct answer)
2. Timeliness - ensuring records are saved within a defined time window.
3. Consistency - ensuring the same data appears in multiple systems.
4. Confidentiality - ensuring only authorized users can view sales order data.

Explanation: Required field validation prevents records from being saved with missing mandatory data, directly enforcing data completeness. Answer A is correct. Timeliness (B) relates to currency of data. Consistency (C) relates to cross-system agreement. Confidentiality (D) is a security dimension, not a data quality dimension.

Question 6

1. Referential integrity - the journal entry references accounts that do not exist.
2. Processing controls - the system should reject or flag entries that do not balance before they are posted. (correct answer)
3. Encryption controls - journal entry amounts are not adequately protected.
4. Access controls - unauthorized users are posting journal entries.

Explanation: Accepting unbalanced journal entries is a processing control failure - the system should validate that debits equal credits before accepting any journal entry, a fundamental accounting data integrity rule. Answer B is correct. Referential integrity (A) concerns table relationships. Encryption (C) is a security control. Access controls (D) address authorization.

Question 7

1. Data confidentiality - ensuring sales data is not accessed by unauthorized parties.
2. Data security - protecting the interface file from tampering.
3. Data completeness and accuracy - verifying that all sales transactions were transferred completely and correctly between systems. (correct answer)
4. Data normalization - ensuring the interface file follows the correct schema.

Explanation: Reconciling record counts and amounts between systems verifies that all transactions were completely and accurately transferred - addressing completeness (no missing records) and accuracy (correct amounts). Answer C is correct. Confidentiality (A) and security (B) are not addressed by reconciliation. Normalization (D) is a schema design concept.

Question 8

1. Immediately grant all employees access to the new customer records.
2. Encrypt all imported records and store them in a separate database.
3. Validate, cleanse, and reconcile the imported data to ensure it meets quality standards before loading into the production system. (correct answer)
4. Archive the imported data for seven years without reviewing its contents.

Explanation: Before loading external data into a production system, organizations should validate format and completeness, cleanse errors, and reconcile record counts and totals to prevent introducing poor-quality data. Answer C is correct. Granting immediate access (A) bypasses data review. Encryption without validation (B) doesn't address quality. Archiving without review (D) defeats the purpose of the import.

Question 9

1. Increased network latency due to large volumes of low-quality data.
2. Higher costs for data storage and archival.
3. Reduced employee morale due to difficulty working with bad data.
4. Materially misstated financial statements resulting from inaccurate, incomplete, or inconsistent data. (correct answer)

Explanation: Poor data quality in financial systems directly risks producing inaccurate financial reports - potentially leading to material misstatements, regulatory violations, and loss of stakeholder confidence. Answer D is correct. Network latency (A), storage costs (B), and employee morale (C) are secondary or operational concerns, not the primary risk.

Question 10

1. Output control - the payroll reports fail to highlight zero-salary employees.
2. Access control - unauthorized users can enter zero-salary values.
3. Encryption control - salary amounts are not adequately protected.
4. Input validation control - the system should reject or flag implausible values such as zero salary for active employees. (correct answer)

Explanation: Accepting zero salary for active employees without an alert is a failure of input validation - a reasonableness or logic check that should flag implausible entries. Answer D is correct. Output controls (A) detect errors after processing. Access controls (B) restrict who can enter data. Encryption (C) protects data confidentiality.

Question 11

1. Delete all records with null values in the customer segment field.
2. Replace all null values with the label 'Unknown' without investigating the cause.
3. Encrypt the customer segment field to prevent further null entries.
4. Investigate the root cause of the missing values, remediate the data, and implement validation controls to prevent future occurrences. (correct answer)

Explanation: The correct approach is to investigate why the values are missing (system error, process failure, data migration issue), fix the existing data, and implement controls to prevent recurrence. Answer D is correct. Deleting records (A) loses valid transaction data. Blanket replacement (B) masks the problem without fixing it. Encryption (C) does not address data completeness.

Question 12

1. Encrypting a data set to create a secure profile for audit purposes.
2. Creating user personas based on data collected from system users.
3. Analyzing a dataset's structure, content, and statistics (null rates, value distributions, format compliance) to assess its quality before processing. (correct answer)
4. Documenting data flows between systems in a data lineage diagram.

Explanation: Data profiling examines the characteristics of a dataset - completeness, format consistency, value ranges, null rates - to identify quality issues before the data is used in analytics or processing. Answer C is correct. Encryption (A), user personas (B), and data lineage (D) are unrelated to data profiling.

Question 13

1. The speed at which data is processed and transmitted across a network.
2. The degree to which data is accurate, complete, consistent, timely, and fit for its intended use. (correct answer)
3. The level of encryption applied to data stored in a database.
4. The number of data fields contained in a database record.

Explanation: Data quality encompasses multiple dimensions - accuracy, completeness, consistency, timeliness, and fitness for purpose - that collectively determine whether data can be relied upon for decision-making and reporting. Answer B is correct. Processing speed (A) is a performance metric. Encryption (C) is a security control. Field count (D) is a structural attribute.

Question 14

1. All data fields are encrypted using the strongest available algorithm.
2. Duplicate records cannot exist in any database table.
3. Data is backed up to a secondary location in real time.
4. A foreign key value in one table must match an existing primary key value in the related table, preventing orphaned records. (correct answer)

Explanation: Referential integrity enforces valid relationships between tables - a record in a child table must reference an existing record in the parent table, preventing broken links (orphaned records). Answer D is correct. Encryption (A) is a security control. Duplicate prevention (B) is uniqueness/entity integrity. Backup (C) is a recovery control.

Question 15

1. Data masking to protect sensitive fields during processing.
2. Record counts and control totals that are compared before and after processing. (correct answer)
3. Role-based access controls limiting who can process batches.
4. Encrypting batch files during transmission.

Explanation: Record counts and hash/control totals established before processing are compared to post-processing results to verify that all records were processed correctly and none were added or lost. Answer B is correct. Data masking (A) protects confidentiality. Access controls (C) restrict authorization. Encryption (D) protects data in transit.

Question 16

1. Establishing a single authoritative source (golden record) for customer data that all systems reference to ensure consistency. (correct answer)
2. Encrypting all master data tables in the production database.
3. Backing up master data to an offsite location on a daily basis.
4. Restricting access to master data to senior management only.

Explanation: MDM creates a single, trusted version of key business data (customers, products, vendors) that all systems reference, eliminating inconsistencies that arise from maintaining duplicate master records in multiple systems. Answer A is correct. Encryption (B), backup (C), and access restriction (D) are important controls but do not define MDM.

Question 17

1. Ensuring that each table has a unique primary key.
2. Ensuring that foreign key values match primary key values in related tables.
3. Ensuring that data values in a column fall within a defined set of acceptable values or meet specified constraints. (correct answer)
4. Ensuring that the database schema follows third normal form.

Explanation: Domain integrity enforces constraints on the values that can be entered in a column - data type, range, format, allowed values - ensuring each value is valid for its domain. Answer C is correct. Unique primary keys (A) describe entity integrity. Foreign key matching (B) describes referential integrity. Normal form compliance (D) describes normalization.

Question 18

1. That all processed records were encrypted before storage.
2. That the payroll manager has reviewed each individual transaction.
3. That the record count and total payroll amount after processing match the pre-processing control totals. (correct answer)
4. That each employee's record was accessed at least once during processing.

Explanation: Comparing post-processing record counts and financial totals to pre-processing control totals verifies that all transactions were processed completely and accurately - a run-to-run control total check. Answer C is correct. Encryption verification (A) addresses security. Individual review (B) is impractical for 10,000 records. Access logging (D) does not verify processing accuracy.

Question 19

1. All required data fields are populated with values and no mandatory information is missing. (correct answer)
2. Data is stored in a secure location protected from unauthorized access.
3. All data in the system reflects the most recent available information.
4. Data from different systems produces the same results when used in calculations.

Explanation: Data completeness means all required data elements are present - no mandatory fields are null, no required records are missing. Answer A is correct. Data security (B) is a confidentiality concern. Most recent information (C) describes timeliness. Consistent results across systems (D) describes consistency.

Question 20

1. Role-based access controls on the source system.
2. Data masking applied to sensitive fields before transfer.
3. Hash totals or checksums that verify data integrity before and after transmission. (correct answer)
4. Data retention policies governing how long transferred records are kept.

Explanation: Hash totals or checksums generate a unique value from the data content; if the value changes after transmission, data corruption occurred during transfer. This is a key data integrity control for system-to-system data transfers. Answer C is correct. Access controls (A) restrict who can initiate transfers. Data masking (B) protects confidentiality. Retention policies (D) govern storage duration.