MLS-C01 · Question #370
A telecommunications company has deployed a machine learning model using Amazon SageMaker. The model identifies customers who are likely to cancel their contract when calling customer service. These…
The correct answer is A. Enable Amazon SageMaker Model Monitor data capture on the model endpoint. Create a. To effectively address concerns about a regionally trained model performing incorrectly when deployed globally to new regions, the company should enable Amazon SageMaker Model Monitor data capture on the model endpoint.
Question
A telecommunications company has deployed a machine learning model using Amazon SageMaker. The model identifies customers who are likely to cancel their contract when calling customer service. These customers are then directed to a specialist service team. The model has been trained on historical data from multiple years relating to customer contracts and customer service interactions in a single geographic region. The company is planning to launch a new global product that will use this model. Management is concerned that the model might incorrectly direct a large number of calls from customers in regions without historical data to the specialist service team. Which approach would MOST effectively address this issue?
Options
- AEnable Amazon SageMaker Model Monitor data capture on the model endpoint. Create a
- BEnable Amazon SageMaker Debugger on the model endpoint. Create a custom rule to measure
- CCapture all customer calls routed to the specialist service team in Amazon S3. Schedule a
- DEnable Amazon CloudWatch on the model endpoint. Capture metrics using Amazon CloudWatch
How the community answered
(34 responses)- A71% (24)
- B9% (3)
- C15% (5)
- D6% (2)
Why each option
To effectively address concerns about a regionally trained model performing incorrectly when deployed globally to new regions, the company should enable Amazon SageMaker Model Monitor data capture on the model endpoint.
Amazon SageMaker Model Monitor is specifically designed to detect data drift and model quality drift in production environments by capturing inference requests and responses from the model endpoint. By creating a baseline from the original training data and monitoring the model's performance on data from new regions, it can effectively identify when the model starts making incorrect predictions due to shifts in data distribution or model performance, directly addressing management's concerns.
Amazon SageMaker Debugger is primarily used during the model training phase to inspect and debug training jobs for issues like vanishing gradients or overfitting, not for monitoring data or model quality drift on a deployed inference endpoint.
While capturing data in Amazon S3 is a necessary step, simply storing the data and manually scheduling analysis is less effective and automated than using SageMaker Model Monitor, which provides built-in capabilities for baseline creation, drift detection, and alerting.
Amazon CloudWatch provides operational metrics like invocation counts and error rates for SageMaker endpoints, which are useful for monitoring endpoint health but do not inherently detect data drift or model quality degradation without significant custom metric and alarm configurations, which Model Monitor automates.
Concept tested: SageMaker Model Monitor for drift detection
Source: https://aws.amazon.com/sagemaker/model-monitor/
Topics
Community Discussion
No community discussion yet for this question.