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 3: AI Operations/Resilience / Part C - AI Controls Management
Q331 Defining how long AI decision logs are retained should PRIMARILY balance:
- A. Keeping logs forever by default, regardless of need, which is a minor but relevant consideration in most situations
- B. Deleting logs immediately after each inference call, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- C. Legal, regulatory, and investigative needs against data minimization and storage risk
- D. Whatever retention period requires the least storage cost, 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: C
Retention duration should balance real legal/investigative need against minimization principles, not default-forever, immediate deletion, or pure cost minimization. Per the AAIR Review Manual: "Data is retained primarily for business and regulatory purposes according to established schedules, archival rules, data formats, and the permissible means of storage, access, and security protocols (e.g., tokenization, encryption, and anonymization)."
Domain 3: AI Operations/Resilience / Part E - AI Supply Chain Risk Management
Q332 What should an enterprise prepare in advance for its critical AI vendor relationships?
- A. Create an exit plan only after a vendor signals they will discontinue service, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Treat exit planning as unnecessary for cloud-based AI services, 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. Assume vendor relationships will continue indefinitely without a transition plan, which is a minor but relevant consideration in most situations
- D. Develop exit/transition plans for critical AI vendor relationships to avoid lock-in and continuity risk
Answer: D
Exit/transition planning should be proactive for critical vendors, not assumed away, reactive, or skipped for cloud services. Per the AAIR Review Manual: "First, it is critical to understand the threats and shared responsibilities typical of vendor and supplier relationships."
Domain 3: AI Operations/Resilience / Part D - AI Risk Metrics, Monitoring, and Reporting
Q333 Having a documented policy for how outliers are handled during AI data preprocessing is valuable PRIMARILY because it:
- A. Replaces the need for a broader data quality monitoring process, which is a minor but relevant consideration in most situations
- B. Automatically removes all outliers regardless of context, 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. Ensures outlier treatment is consistent, defensible, and doesn't silently bias model training
- D. Is only necessary for financial data, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: C
A documented policy keeps outlier handling consistent and defensible; it doesn't mandate blanket removal, isn't domain-limited, or replace broader quality monitoring. Per the AAIR Review Manual: "Maintaining consistency between the data preprocessing during the training phase and the data preprocessing during the postproduction inference stage is essential for reliable and consistent model performance."
Domain 3: AI Operations/Resilience / Part F - AI Incident Response, BIA, Business Continuity, and Disaster Recovery
Q334 After an AI incident response concludes, what should happen to the lessons learned?
- A. Feed AI incident lessons learned back into risk assessments, controls, and training
- B. Close AI incidents without updating related risk assessments or controls, which is a minor but relevant consideration in most situations
- C. Share lessons learned only informally among the immediate response team, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- D. Document lessons learned but take no corrective action, 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: A
Lessons learned should formally update assessments, controls, and training, not stay informal or undocumented without action. Per the AAIR Review Manual: "• Incident response planning-Develop an incident response plan to address AI-related security incidents; this involves plan development, staff training, and testing of an Al-centric incident response plan."
Domain 2: AI Lifecycle / Part A - AI Design, Development/Procurement, and Documentation
Q335 Recording the random seed used during model training is valuable PRIMARILY because it:
- A. Supports reproducing the same training run later for audit or debugging purposes, which is a minor but relevant consideration in most situations
- B. Guarantees the model will never need retraining, 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 experiment tracking tools, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- D. Is only relevant for models trained on synthetic data
Answer: A
Recording the seed supports later reproduction for audit/debugging; it doesn't guarantee no retraining, isn't synthetic-data-specific, or replace broader experiment tracking. Per the AAIR Review Manual: "Therefore, ensuring a HITL is key to ensure the efficiency and efficacy of Al training and training sets. 2.7.2 Adversarial Training Adversarial training, or Al red tearning, 112 is a proactive method used during the Al model training phase to enhance the robustness and security of Al systems."
Domain 2: AI Lifecycle / Part A - AI Design, Development/Procurement, and Documentation
Q336 Documenting the hyperparameter tuning process used to develop an AI model is valuable PRIMARILY because it:
- A. Removes the need to document the final model architecture, which is a minor but relevant consideration in most situations
- B. Is only relevant for deep learning models, 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. Automatically prevents the model from overfitting, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- D. Supports reproducibility and helps reviewers understand how final model settings were chosen
Answer: D
Documentation supports reproducibility and informed review of settings choices; it isn't deep-learning-specific, doesn't prevent overfitting by itself, and doesn't replace architecture documentation. Per the AAIR Review Manual: "Validation dataset This small (typically 10% to 20%) dataset allows the organization to validate the performance of the model and make hyperparameter tuning tweaks to improve performance or help select the best model (if multiple models are being evaluated)."
Domain 3: AI Operations/Resilience / Part A - AI Risk Scenario Identification and Assessment
Q337 When building an AI risk scenario library, the enterprise should PRIMARILY include:
- A. Low-likelihood, high-impact scenarios in addition to common, everyday failure modes, which is a minor but relevant consideration in most situations
- B. Only scenarios that have already occurred at the enterprise
- C. Only scenarios with very low potential 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. Only scenarios identified by the model vendor, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: A
A complete scenario library covers tail/catastrophic risk alongside common failures; limiting to past, low-impact, or vendor-identified scenarios leaves gaps.
Domain 1: AI Governance / Part E - AI Regulatory Compliance and Legal Considerations
Q338 When a user withdraws consent for AI-driven personalization, the enterprise should PRIMARILY ensure:
- A. The user's entire account is immediately deleted, which is a minor but relevant consideration in most situations
- B. The request is forwarded to the AI vendor with no enterprise-side action
- C. Withdrawal requests are only honored once per calendar year, 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. Their data stops being used for that personalization going forward, consistent with the withdrawal, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: D
Honoring withdrawal means stopping that specific data use going forward; it doesn't require full account deletion, arbitrary frequency limits, or purely offloading action to the vendor.
Domain 1: AI Governance / Part F - AI Trustworthiness, Ethical, and Societal Implications
Q339 To properly manage human oversight for high-stakes AI decisions, an enterprise should PRIMARILY:
- A. Limit human oversight to a quarterly sample review
- B. Maintain meaningful human review for high-stakes automated AI decisions, 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. Allow human review only on customer request, which is a minor but relevant consideration in most situations
- D. Fully automate all high-stakes decisions without human review, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
Answer: B
High-stakes decisions require meaningful ongoing human oversight, not full automation or infrequent sampling alone. Per the AAIR Review Manual: "Organizations should aim to inventory all AI models or, at minimum, those classified as high risk or deployed in high-stakes settings."
Domain 3: AI Operations/Resilience / Part A - AI Risk Scenario Identification and Assessment
Q340 The GREATEST risk of a model extraction attack against a deployed AI API is that an attacker may:
- A. Slightly increase the API's average response latency, a factor that many practitioners tend to overlook even though it can meaningfully influence the final outcome
- B. Cause the vendor's invoice to be generated incorrectly, which is a minor but relevant consideration in most situations
- C. Reconstruct a functionally similar copy of the proprietary model through repeated queries
- D. Improve the model's accuracy through unintended feedback, 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: C
Extraction attacks let an attacker rebuild a functional copy via queries, which is the core IP/security risk, not latency, billing, or accuracy side effects. Per the AAIR Review Manual: "The attacker is then able to reconstruct a copy of the model."