ISACA Advanced in AI Audit AAIA Practice Test 12
Question 110
In an audit of Privacy and Data Governance Programs, managers say this measure is live: Conduct purpose/compatibility and privacy impact review before reuse. They claim it corrected a material audit gap. What direct operating evidence would allow the auditor to substantiate that particular claim across a defensible sample?
- Updated processing register, legal assessment and approved purpose mapping
- Log pipeline samples, redaction tests and access reviews
- Verified processor list, hosting configuration and applicable transfer assessments
- Data source records, licensing terms and approval evidence for each training corpus
Explanation
Correct Answer
A:Correct. The proposed records—updated processing register, legal assessment and approved purpose mapping—are directly tied to the asserted safeguard and allow its actual operation to be corroborated. The gap being tested is secondary ai processing is not evaluated against the original lawful purpose.
Incorrect Answers
B:“Log pipeline samples, redaction tests and access reviews” would test observability logs bypass personal-data classification and handling controls, not the present safeguard against secondary AI processing is not evaluated against the original lawful purpose. The expected audit evidence is “Updated processing register, legal assessment and approved purpose mapping”.
C:“Verified processor list, hosting configuration and applicable transfer assessments” would test aI data transfers are missing location and processor transparency, not the present safeguard against secondary AI processing is not evaluated against the original lawful purpose. The expected audit evidence is “Updated processing register, legal assessment and approved purpose mapping”.
D:“Data source records, licensing terms and approval evidence for each training corpus” would test data provenance and lawful-use assurance are not established, not the present safeguard against secondary AI processing is not evaluated against the original lawful purpose. The expected audit evidence is “Updated processing register, legal assessment and approved purpose mapping”.
Question 111
In a review of Privacy and Data Governance Programs, investigators cannot establish the expected control proof: updated processing register, legal assessment and approved purpose mapping. The underlying event was that customer preference data collected for delivery scheduling is reused for credit scoring without a new assessment. Which control weakness is the MOST likely cause requiring focused audit work?
- Observability logs bypass personal-data classification and handling controls
- AI data transfers are missing location and processor transparency
- Data provenance and lawful-use assurance are not established
- Secondary AI processing is not evaluated against the original lawful purpose
Explanation
Correct Answer
D:Correct. The observed condition specifically indicates secondary ai processing is not evaluated against the original lawful purpose. A meaningful audit response is to verify this diagnosis and then recommend conduct purpose/compatibility and privacy impact review before reuse.
Incorrect Answers
A:“Observability logs bypass personal-data classification and handling controls” concerns a separate audit weakness, not the missing assurance described by secondary AI processing is not evaluated against the original lawful purpose. The correct cause is “Secondary AI processing is not evaluated against the original lawful purpose”.
B:“AI data transfers are missing location and processor transparency” concerns a separate audit weakness, not the missing assurance described by secondary AI processing is not evaluated against the original lawful purpose. The correct cause is “Secondary AI processing is not evaluated against the original lawful purpose”.
C:“Data provenance and lawful-use assurance are not established” concerns a separate audit weakness, not the missing assurance described by secondary AI processing is not evaluated against the original lawful purpose. The correct cause is “Secondary AI processing is not evaluated against the original lawful purpose”.
Question 112
Anonymized location data can be reidentified when combined with publicly accessible trip traces. From an AI audit perspective, which corrective action is the MOST direct response to the weakness described, rather than a useful control for some different AI risk?
- Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable
- Evaluate memorization, membership inference and release utility before sharing
- Perform linkage attacks and set release safeguards appropriate to residual identifiability
- Enforce least-privilege project entitlements and scoped deidentified training views
Explanation
Correct Answer
C:Correct. Perform linkage attacks and set release safeguards appropriate to residual identifiability is aimed at the actual failure: reidentification risk was not tested for the actual release context. The audit should subsequently obtain adversarial reidentification results, suppression thresholds and release decision to test execution, not merely the existence of a policy.
Incorrect Answers
A:“Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable” is a control for subject-rights workflow excludes derived AI data stores and vector copies, but the audit finding here is reidentification risk was not tested for the actual release context. The relevant measure is “Perform linkage attacks and set release safeguards appropriate to residual identifiability”.
B:“Evaluate memorization, membership inference and release utility before sharing” is a control for synthetic data was assumed private without membership-inference or disclosure tests, but the audit finding here is reidentification risk was not tested for the actual release context. The relevant measure is “Perform linkage attacks and set release safeguards appropriate to residual identifiability”.
D:“Enforce least-privilege project entitlements and scoped deidentified training views” is a control for dataset access is broad and lacks purpose-based authorization, but the audit finding here is reidentification risk was not tested for the actual release context. The relevant measure is “Perform linkage attacks and set release safeguards appropriate to residual identifiability”.
Question 113
In an audit of Privacy and Data Governance Programs, managers say this measure is live: Perform linkage attacks and set release safeguards appropriate to residual identifiability. They claim it corrected a material audit gap. What direct operating evidence would allow the auditor to substantiate that particular claim across a defensible sample?
- End-to-end deletion trace from source to vector index and exception ledger
- Adversarial reidentification results, suppression thresholds and release decision
- Attack evaluation reports, privacy thresholds and restricted release approvals
- Access grants, denied cross-project query tests and periodic privilege recertifications
Explanation
Correct Answer
B:Correct. The proposed records—adversarial reidentification results, suppression thresholds and release decision—are directly tied to the asserted safeguard and allow its actual operation to be corroborated. The gap being tested is reidentification risk was not tested for the actual release context.
Incorrect Answers
A:“End-to-end deletion trace from source to vector index and exception ledger” would test subject-rights workflow excludes derived AI data stores and vector copies, not the present safeguard against reidentification risk was not tested for the actual release context. The expected audit evidence is “Adversarial reidentification results, suppression thresholds and release decision”.
C:“Attack evaluation reports, privacy thresholds and restricted release approvals” would test synthetic data was assumed private without membership-inference or disclosure tests, not the present safeguard against reidentification risk was not tested for the actual release context. The expected audit evidence is “Adversarial reidentification results, suppression thresholds and release decision”.
D:“Access grants, denied cross-project query tests and periodic privilege recertifications” would test dataset access is broad and lacks purpose-based authorization, not the present safeguard against reidentification risk was not tested for the actual release context. The expected audit evidence is “Adversarial reidentification results, suppression thresholds and release decision”.
Question 114
In a review of Privacy and Data Governance Programs, investigators cannot establish the expected control proof: adversarial reidentification results, suppression thresholds and release decision. The underlying event was that anonymized location data can be reidentified when combined with publicly accessible trip traces. Which control weakness is the MOST likely cause requiring focused audit work?
- Reidentification risk was not tested for the actual release context
- Subject-rights workflow excludes derived AI data stores and vector copies
- Synthetic data was assumed private without membership-inference or disclosure tests
- Dataset access is broad and lacks purpose-based authorization
Explanation
Correct Answer
A:Correct. The observed condition specifically indicates reidentification risk was not tested for the actual release context. A meaningful audit response is to verify this diagnosis and then recommend perform linkage attacks and set release safeguards appropriate to residual identifiability.
Incorrect Answers
B:“Subject-rights workflow excludes derived AI data stores and vector copies” concerns a separate audit weakness, not the missing assurance described by reidentification risk was not tested for the actual release context. The correct cause is “Reidentification risk was not tested for the actual release context”.
C:“Synthetic data was assumed private without membership-inference or disclosure tests” concerns a separate audit weakness, not the missing assurance described by reidentification risk was not tested for the actual release context. The correct cause is “Reidentification risk was not tested for the actual release context”.
D:“Dataset access is broad and lacks purpose-based authorization” concerns a separate audit weakness, not the missing assurance described by reidentification risk was not tested for the actual release context. The correct cause is “Reidentification risk was not tested for the actual release context”.
Question 115
Engineers embed personal details in test prompts stored in external debugging dashboards. From an AI audit perspective, which corrective action is the MOST direct response to the weakness described, rather than a useful control for some different AI risk?
- Capture versioned transformation logic, imputation decisions and field-level lineage
- Test extraction risk and restrict sensitive content in model training and output handling
- Conduct purpose/compatibility and privacy impact review before reuse
- Sanitize and segregate prompt traces with restricted access and retention
Explanation
Correct Answer
D:Correct. Sanitize and segregate prompt traces with restricted access and retention is aimed at the actual failure: observability logs bypass personal-data classification and handling controls. The audit should subsequently obtain log pipeline samples, redaction tests and access reviews to test execution, not merely the existence of a policy.
Incorrect Answers
A:“Capture versioned transformation logic, imputation decisions and field-level lineage” is a control for lineage controls omit preprocessing operations essential to auditability, but the audit finding here is observability logs bypass personal-data classification and handling controls. The relevant measure is “Sanitize and segregate prompt traces with restricted access and retention”.
B:“Test extraction risk and restrict sensitive content in model training and output handling” is a control for training memorization and output disclosure controls were unassessed, but the audit finding here is observability logs bypass personal-data classification and handling controls. The relevant measure is “Sanitize and segregate prompt traces with restricted access and retention”.
C:“Conduct purpose/compatibility and privacy impact review before reuse” is a control for secondary AI processing is not evaluated against the original lawful purpose, but the audit finding here is observability logs bypass personal-data classification and handling controls. The relevant measure is “Sanitize and segregate prompt traces with restricted access and retention”.
Question 116
In an audit of Privacy and Data Governance Programs, managers say this measure is live: Sanitize and segregate prompt traces with restricted access and retention. They claim it corrected a material audit gap. What direct operating evidence would allow the auditor to substantiate that particular claim across a defensible sample?
- Reproducible pipeline manifests and source-to-feature trace samples
- Memorization probe results, content filters and reviewed training-data exclusions
- Log pipeline samples, redaction tests and access reviews
- Updated processing register, legal assessment and approved purpose mapping
Explanation
Correct Answer
C:Correct. The proposed records—log pipeline samples, redaction tests and access reviews—are directly tied to the asserted safeguard and allow its actual operation to be corroborated. The gap being tested is observability logs bypass personal-data classification and handling controls.
Incorrect Answers
A:“Reproducible pipeline manifests and source-to-feature trace samples” would test lineage controls omit preprocessing operations essential to auditability, not the present safeguard against observability logs bypass personal-data classification and handling controls. The expected audit evidence is “Log pipeline samples, redaction tests and access reviews”.
B:“Memorization probe results, content filters and reviewed training-data exclusions” would test training memorization and output disclosure controls were unassessed, not the present safeguard against observability logs bypass personal-data classification and handling controls. The expected audit evidence is “Log pipeline samples, redaction tests and access reviews”.
D:“Updated processing register, legal assessment and approved purpose mapping” would test secondary AI processing is not evaluated against the original lawful purpose, not the present safeguard against observability logs bypass personal-data classification and handling controls. The expected audit evidence is “Log pipeline samples, redaction tests and access reviews”.
Question 117
In a review of Privacy and Data Governance Programs, investigators cannot establish the expected control proof: log pipeline samples, redaction tests and access reviews. The underlying event was that engineers embed personal details in test prompts stored in external debugging dashboards. Which control weakness is the MOST likely cause requiring focused audit work?
- Lineage controls omit preprocessing operations essential to auditability
- Observability logs bypass personal-data classification and handling controls
- Training memorization and output disclosure controls were unassessed
- Secondary AI processing is not evaluated against the original lawful purpose
Explanation
Correct Answer
B:Correct. The observed condition specifically indicates observability logs bypass personal-data classification and handling controls. A meaningful audit response is to verify this diagnosis and then recommend sanitize and segregate prompt traces with restricted access and retention.
Incorrect Answers
A:“Lineage controls omit preprocessing operations essential to auditability” concerns a separate audit weakness, not the missing assurance described by observability logs bypass personal-data classification and handling controls. The correct cause is “Observability logs bypass personal-data classification and handling controls”.
C:“Training memorization and output disclosure controls were unassessed” concerns a separate audit weakness, not the missing assurance described by observability logs bypass personal-data classification and handling controls. The correct cause is “Observability logs bypass personal-data classification and handling controls”.
D:“Secondary AI processing is not evaluated against the original lawful purpose” concerns a separate audit weakness, not the missing assurance described by observability logs bypass personal-data classification and handling controls. The correct cause is “Observability logs bypass personal-data classification and handling controls”.
Question 118
A deletion request is completed in the CRM but old customer examples remain in retrieval indexes. From an AI audit perspective, which corrective action is the MOST direct response to the weakness described, rather than a useful control for some different AI risk?
- Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable
- Inventory processing locations, subprocessors and cross-border transfer safeguards
- Apply category-specific prompt retention limits, redaction and verified deletion paths
- Perform linkage attacks and set release safeguards appropriate to residual identifiability
Explanation
Correct Answer
A:Correct. Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable is aimed at the actual failure: subject-rights workflow excludes derived ai data stores and vector copies. The audit should subsequently obtain end-to-end deletion trace from source to vector index and exception ledger to test execution, not merely the existence of a policy.
Incorrect Answers
B:“Inventory processing locations, subprocessors and cross-border transfer safeguards” is a control for aI data transfers are missing location and processor transparency, but the audit finding here is subject-rights workflow excludes derived AI data stores and vector copies. The relevant measure is “Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable”.
C:“Apply category-specific prompt retention limits, redaction and verified deletion paths” is a control for retention defaults violate purpose limitation and approved data minimization, but the audit finding here is subject-rights workflow excludes derived AI data stores and vector copies. The relevant measure is “Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable”.
D:“Perform linkage attacks and set release safeguards appropriate to residual identifiability” is a control for reidentification risk was not tested for the actual release context, but the audit finding here is subject-rights workflow excludes derived AI data stores and vector copies. The relevant measure is “Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable”.
Question 119
In an audit of Privacy and Data Governance Programs, managers say this measure is live: Extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable. They claim it corrected a material audit gap. What direct operating evidence would allow the auditor to substantiate that particular claim across a defensible sample?
- Verified processor list, hosting configuration and applicable transfer assessments
- Configured TTL, deletion test logs and contractual retention commitments
- Adversarial reidentification results, suppression thresholds and release decision
- End-to-end deletion trace from source to vector index and exception ledger
Explanation
Correct Answer
D:Correct. The proposed records—end-to-end deletion trace from source to vector index and exception ledger—are directly tied to the asserted safeguard and allow its actual operation to be corroborated. The gap being tested is subject-rights workflow excludes derived ai data stores and vector copies.
Incorrect Answers
A:“Verified processor list, hosting configuration and applicable transfer assessments” would test aI data transfers are missing location and processor transparency, not the present safeguard against subject-rights workflow excludes derived AI data stores and vector copies. The expected audit evidence is “End-to-end deletion trace from source to vector index and exception ledger”.
B:“Configured TTL, deletion test logs and contractual retention commitments” would test retention defaults violate purpose limitation and approved data minimization, not the present safeguard against subject-rights workflow excludes derived AI data stores and vector copies. The expected audit evidence is “End-to-end deletion trace from source to vector index and exception ledger”.
C:“Adversarial reidentification results, suppression thresholds and release decision” would test reidentification risk was not tested for the actual release context, not the present safeguard against subject-rights workflow excludes derived AI data stores and vector copies. The expected audit evidence is “End-to-end deletion trace from source to vector index and exception ledger”.
Question 120
In a review of Privacy and Data Governance Programs, investigators cannot establish the expected control proof: end-to-end deletion trace from source to vector index and exception ledger. The underlying event was that a deletion request is completed in the CRM but old customer examples remain in retrieval indexes. Which control weakness is the MOST likely cause requiring focused audit work?
- AI data transfers are missing location and processor transparency
- Retention defaults violate purpose limitation and approved data minimization
- Subject-rights workflow excludes derived AI data stores and vector copies
- Reidentification risk was not tested for the actual release context
Explanation
Correct Answer
C:Correct. The observed condition specifically indicates subject-rights workflow excludes derived ai data stores and vector copies. A meaningful audit response is to verify this diagnosis and then recommend extend deletion propagation to indexes, caches, fine-tune stores and backups as applicable.
Incorrect Answers
A:“AI data transfers are missing location and processor transparency” concerns a separate audit weakness, not the missing assurance described by subject-rights workflow excludes derived AI data stores and vector copies. The correct cause is “Subject-rights workflow excludes derived AI data stores and vector copies”.
B:“Retention defaults violate purpose limitation and approved data minimization” concerns a separate audit weakness, not the missing assurance described by subject-rights workflow excludes derived AI data stores and vector copies. The correct cause is “Subject-rights workflow excludes derived AI data stores and vector copies”.
D:“Reidentification risk was not tested for the actual release context” concerns a separate audit weakness, not the missing assurance described by subject-rights workflow excludes derived AI data stores and vector copies. The correct cause is “Subject-rights workflow excludes derived AI data stores and vector copies”.