Courseiva
Implementing AI Solutions →mediumMultiple Choice

AI0-001 Implementing AI Solutions Practice Question

A financial services firm is deploying a credit-scoring model built with Amazon SageMaker. Compliance requires that every prediction be explainable to a loan officer and to regulators. The model uses gradient boosting on 120 features. Which approach BEST satisfies the explainability requirement while keeping the production model unchanged?

⚠ Common exam trap

Watch out — candidates often confuse model monitoring for drift with per-prediction explainability, since both are described as making a model 'transparent'.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use SageMaker Clarify to generate SHAP-based feature attributions for each inference request through the Clarify explainer endpoint.

Explainability for regulated decisions requires per-prediction attributions tied to the actual model. SageMaker Clarify's SHAP explainer endpoint returns feature-level contributions for each request while the gradient boosting model remains in production, satisfying both accuracy and compliance. Monitoring tools track aggregate drift, simpler models change behavior, and manual reconstruction is not auditable, so only the Clarify-based approach meets the constraint of leaving the production model unchanged.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Log the raw feature vector for every request and have analysts manually reconstruct the decision using spreadsheet formulas.

    Why it's wrong here

    Manual reconstruction is neither scalable nor auditable for a production credit-scoring system and does not produce a defensible per-prediction explanation. It also introduces human error and cannot be reproduced consistently for regulators. The requirement is for a systematic, model-consistent explanation at inference time, which manual spreadsheet work cannot deliver reliably or at the required throughput.

  • ✗

    Enable SageMaker Model Monitor with a data quality baseline and publish the monitoring reports to the loan officers.

    Why it's wrong here

    SageMaker Model Monitor detects data drift, bias drift, and feature attribution drift over time, but it does not produce per-prediction explanations for individual loan decisions. Publishing drift reports does not tell a loan officer why a specific applicant was declined. This capability is a monitoring and observability tool, not an interpretability tool for individual inference requests, so it fails the stated compliance requirement.

  • ✗

    Replace the gradient boosting model with a single decision tree so that every prediction follows a human-readable path.

    Why it's wrong here

    A single decision tree is inherently interpretable, but swapping the model changes the prediction behavior the firm already validated and typically degrades scoring accuracy on 120 features. The scenario explicitly requires keeping the production model unchanged. This option addresses explainability by sacrificing model performance and violating the constraint, so it is not the correct approach for this deployment.

  • ✓

    Use SageMaker Clarify to generate SHAP-based feature attributions for each inference request through the Clarify explainer endpoint.

    Why this is correct

    SageMaker Clarify supports SHAP-based explanations and can be configured as an online explainer endpoint that returns per-request feature attributions alongside the prediction. This gives loan officers and regulators a ranked contribution of each feature for the individual decision without retraining or replacing the gradient boosting model, directly meeting the explainability requirement while leaving the production model untouched.

About these practice questions

Courseiva writes every AI0-001 question from scratch — 962 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official CompTIA exam blueprint

This AI0-001 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI0-001 exam.