This is not a replacement for the official study guide. Please read the official study guide first — use this exam prep only to reinforce or practice your understanding.
Free AAIR exam practice questions with answers and explanations, organized by domain and part.
Domain 1: AI Governance / Part A - AI Models, Frameworks, Strategies, and Use Cases
Q111 When addressing AI strategy use-case feasibility review, what is the BEST first step for an AI risk practitioner?
- A. Skip feasibility review for small-scale pilots, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Approve use cases based only on executive sponsorship, which is a minor but relevant consideration in most situations
- C. Conduct a feasibility review covering data availability, risk, and resourcing before approving a use case, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- D. Approve use cases once a vendor demo looks promising
Answer: C
Feasibility review of data, risk, and resourcing should precede use-case approval regardless of sponsorship or pilot size.
Domain 1: AI Governance / Part C - AI Ownership, Oversight, and Accountability
Q112 Tracking unsanctioned AI tool spending across business units (shadow IT) is valuable PRIMARILY because it:
- A. Guarantees that unauthorized tools will be more expensive, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Is only relevant for enterprises with a centralized finance function
- C. Automatically cancels any unauthorized subscriptions, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- D. Surfaces unapproved AI usage so it can be brought under governance and risk review, which is a minor but relevant consideration in most situations
Answer: D
Spend tracking surfaces unsanctioned usage for governance follow-up; it doesn't auto-cancel subscriptions, isn't limited to centralized-finance firms, or guarantee relative cost outcomes.
Domain 2: AI Lifecycle / Part A - AI Design, Development/Procurement, and Documentation
Q113 Requirements traceability for an AI system helps ensure:
- A. The system meets defined business and risk requirements, and gaps are identifiable
- B. The system is delivered on the originally planned schedule, which is a minor but relevant consideration in most situations
- C. Lower development costs only, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- D. Faster deployment regardless of requirements, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: A
Traceability links requirements to implementation so gaps are identifiable; it is not primarily about schedule adherence, speed, or cost. Per the AAIR Review Manual: "Performing checks for completeness and quality is essential to verify that the dataset covers the necessary scope and meets the requirements to fulfill the defined business case."
Domain 3: AI Operations/Resilience / Part A - AI Risk Scenario Identification and Assessment
Q114 AI-generated synthetic identities pose a GREATEST risk to the enterprise by enabling fraudsters to:
- A. Comply more easily with know-your-customer regulations
- B. Pass identity verification checks with fabricated but plausible-looking identity data, which is a minor but relevant consideration in most situations
- C. Improve the accuracy of fraud detection models, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- D. Reduce the cost of legitimate customer onboarding, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
Answer: B
Synthetic identities threaten by defeating identity verification with fabricated but plausible data, not by lowering onboarding cost, improving detection, or easing compliance.
Domain 1: AI Governance / Part C - AI Ownership, Oversight, and Accountability
Q115 The responsibility of the enterprise's governing body for AI oversight is BEST characterized as:
- A. Limited to financial objectives only, excluding ethics and culture
- B. Delegable to a third-party AI vendor once a service contract is signed, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- C. Non-delegable, extending beyond financial objectives to the culture, values, and ethics of the enterprise, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- D. Required only when an AI incident has already occurred, which is a minor but relevant consideration in most situations
Answer: C
The governing body's accountability for organizational activities, including AI adoption and its consequences, cannot be delegated and extends beyond financial goals to culture, values, and ethics. Per the AAIR Review Manual: "1.7 .1 Role of the Enterprise's Governing Body The responsibility of the governing body to establish goals in traditional contexts extends to both financial objectives and nonfinancial concerns, including the culture, values, and ethics of the enterprise."
Domain 3: AI Operations/Resilience / Part F - AI Incident Response, BIA, Business Continuity, and Disaster Recovery
Q116 Defining escalation service-level agreements (SLAs) by AI incident severity is valuable PRIMARILY because it:
- A. Removes the need to classify incidents at all, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Ensures response speed is matched to the actual business impact of the incident, which is a minor but relevant consideration in most situations
- C. Applies the same response time to every incident regardless of impact, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- D. Guarantees every incident will be fully resolved within the SLA window
Answer: B
Severity-based SLAs match response speed to actual impact; uniform timing, skipping classification, or guaranteed resolution windows don't achieve that. Per the AAIR Review Manual: "Defining and requiring a shared approach between entities will need to be addressed contractually with clearly defined expectations related to SLAs, incident response activities, and incident notification requirements."
Domain 1: AI Governance / Part B - AI Organizational Processes and Alignment
Q117 Requiring tiered approval thresholds for AI project spending is valuable PRIMARILY because it:
- A. Is only relevant to externally funded projects, which is a minor but relevant consideration in most situations
- B. Slows down every AI project equally regardless of size, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- C. Removes the need for a business case
- D. Ensures larger or riskier AI investments receive proportionate scrutiny, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: D
Tiered thresholds align scrutiny with investment size/risk; uniform delay or skipping business cases undermines that. Per the AAIR Review Manual: "This iterative process helps to reduce the overall risk of the project and ensures that the final AI solution is effective in addressing the identified problem."
Domain 3: AI Operations/Resilience / Part A - AI Risk Scenario Identification and Assessment
Q118 Regarding AI risk register maintenance, the BEST practice is to:
- A. Maintain the risk register only for regulator-visible systems, which is a minor but relevant consideration in most situations
- B. Update the risk register only during annual reviews, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- C. Create a risk register once and leave it static
- D. Maintain a living AI risk register that is updated as risks, controls, and context change, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
Answer: D
The AI risk register should be actively maintained and updated, not static, partial, or infrequently reviewed.
Domain 2: AI Lifecycle / Part D - AI Data and Asset Management
Q119 Minimizing personal data included in prompts sent to a generative AI system is valuable PRIMARILY because it:
- A. Improves the grammatical quality of the system's responses, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Removes the need for a data retention policy for prompts, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- C. Is only relevant when using an on-premises model
- D. Reduces the risk of unnecessary personal data exposure through logging, retention, or model output, which is a minor but relevant consideration in most situations
Answer: D
Minimizing personal data in prompts reduces exposure risk via logs/retention/output; it doesn't affect response grammar, isn't on-prem-only, and doesn't remove the need for a retention policy.
Domain 2: AI Lifecycle / Part C - AI Implementation, Maintenance, and Decommissioning
Q120 Formal sign-off before decommissioning an AI use case is valuable PRIMARILY because it:
- A. Confirms dependent processes and stakeholders have been identified and accounted for before shutdown, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Removes the need to communicate the decommissioning to affected users, an aspect that is often underestimated in real-world settings but can have a significant and lasting impact on both the process and its eventual results
- C. Is only necessary for use cases that were never profitable
- D. Automatically deletes all associated data immediately upon approval, which is a minor but relevant consideration in most situations
Answer: A
Sign-off confirms dependencies/stakeholders are accounted for before shutdown; it isn't profitability-gated, doesn't auto-trigger data deletion, or remove the need for user communication.