Auditing · Topic 7
Digital Auditing and CAATs Quiz
Work through 25 multiple-choice questions, one at a time. Submit each answer for feedback. At the end, review your score and see which concepts to revisit.
Your quiz report
Question-by-question review
Show the answer key
- Exception analytics A flagged item is a lead that requires investigation.
- Data completeness Analytics cannot support the planned conclusion until the population is validated.
- Logical access control The account can expose the system to unauthorized use.
- Test data Boundary and rejection cases show how the configured rule behaves.
- Change management Uncontrolled changes may undermine reliance on automated calculations.
- Inspect source documents before deciding whether flagged entries are duplicates A flagged item is a lead that requires investigation.
- Reconcile the extracted data to authoritative control totals before testing it Analytics cannot support the planned conclusion until the population is validated.
- Review the offboarding process and inspect activity after termination The account can expose the system to unauthorized use.
- Compare expected rule outcomes with recorded system results Boundary and rejection cases show how the configured rule behaves.
- Inspect privileges and test approval and deployment records Uncontrolled changes may undermine reliance on automated calculations.
- Invoices, bank payments and matched transaction records Inspect source documents before deciding whether flagged entries are duplicates.
- Source-system counts and totals with extraction filters documented Reconcile the extracted data to authoritative control totals before testing it.
- HR exit list, access export and activity logs Review the offboarding process and inspect activity after termination.
- Documented input cases, expected outputs and captured results Compare expected rule outcomes with recorded system results.
- Version history, change tickets and migration logs Inspect privileges and test approval and deployment records.
- A flagged item is a lead that requires investigation Invoices, bank payments and matched transaction records would support this assessment.
- Analytics cannot support the planned conclusion until the population is validated Source-system counts and totals with extraction filters documented would support this assessment.
- The account can expose the system to unauthorized use HR exit list, access export and activity logs would support this assessment.
- Boundary and rejection cases show how the configured rule behaves Documented input cases, expected outputs and captured results would support this assessment.
- Uncontrolled changes may undermine reliance on automated calculations Version history, change tickets and migration logs would support this assessment.
- Treating every match as confirmed fraud A flagged item is a lead that requires investigation.
- Ignoring missing rows because the script runs successfully Analytics cannot support the planned conclusion until the population is validated.
- Assuming an inactive-looking account cannot be used The account can expose the system to unauthorized use.
- Inserting dummy transactions into the live ledger without authorization Boundary and rejection cases show how the configured rule behaves.
- Assuming automation is consistently correct regardless of program changes Uncontrolled changes may undermine reliance on automated calculations.
These cases use general auditing principles. Apply the relevant local law and professional standards when evaluating a real engagement. Reference: IAASB standards and pronouncements.
