Scenario: A claims automation system uses SageMaker AI, predicting claim approval based on vehicle damage severity and other features (age, mileage). The model must be continuously monitored for feature attribution drift in production (i.e., if the model starts prioritizing less relevant features like vehicle age over damage severity). Question- Which solution should be implemented? Options:

The core requirement is to continuously monitor for feature attribution drift in production. This means tracking changes in how the model weighs different input features when making predictions. The Amazon SageMaker ModelExplainabilityMonitor is the specific tool designed for this purpose. It uses explainability algorithms like SHAP (SHapley Additive exPlanations) to compute feature importance scores for real-time inferences. It then compares these scores against a pre-established baseline (generated from the training data) to detect significant drift, which directly addresses the scenario of the model incorrectly prioritizing features like vehicle age over damage severity over time.

B. ModelQualityMonitor tracks predictive performance metrics (e.g., accuracy, recall) by comparing predictions to ground truth. It measures what the model predicts, not why, and would not directly detect feature attribution drift.

C. This describes a manual, custom implementation for data or prediction drift monitoring. While possible, it is not the purpose-built, managed solution for feature attribution monitoring provided by SageMaker, making it less efficient and direct than option A.

D. SageMaker Clarify is the underlying technology, but this option incorrectly frames its use for a one-time analysis on the training dataset. The question requires continuous monitoring in production, which is the specific function of the ModelExplainabilityMonitor.

1. AWS SageMaker Developer Guide - Monitor model explainability: "You can also use Model Monitor to monitor for drift in feature attribution... Model Monitor detects drift by comparing the feature attributions for predictions that your model makes in production to the feature attributions from a baseline. Model Monitor uses SHAP values to explain the relative importance of each feature to the predictions that a model makes." This directly supports option A.

2. AWS SageMaker Developer Guide - How Model Explainability Monitoring Works: "The ModelExplainabilityMonitor class can inspect your model and generate a baseline for you... When you start a monitoring schedule, it launches a processing job that uses the baseline to analyze the predictions that your model makes on the data that it receives in production." This confirms the operational flow described in option A.

3. AWS SageMaker Developer Guide - Monitor model quality: "Model quality monitoring compares the predictions that your model makes with the actual ground truth labels that you store in Amazon S3... SageMaker compares the model's predictions to the ground truth labels to compute quality metrics." This confirms that ModelQualityMonitor (Option B) focuses on performance, not explainability.

4. AWS SageMaker Python SDK Documentation - sagemaker.modelmonitor.ModelExplainabilityMonitor: The documentation for this class explicitly states it "Handles Amazon SageMaker Model Monitor explainability monitoring jobs," confirming it as the correct tool for the task.