Amazon Web Services Updated MLA-C01 Exam Questions and Answers by brooklyn

The described behavior indicates overfitting, where the model starts to memorize training data instead of generalizing.

Early stopping halts training when validation performance stops improving, preventing the model from overfitting further. AWS documentation recommends early stopping as a primary regularization technique.

Dropout randomly disables neurons during training, forcing the model to learn robust representations and reducing reliance on specific neurons. Increasing dropout is a well-established method for improving generalization.

Increasing layers or neurons increases model capacity and worsens overfitting. Model bias is unrelated to epoch-based degradation.

Therefore, Options A and B are correct.

This solution is the most efficient and involves the least operational overhead:

Amazon Kinesis data streams efficiently handle real-time ingestion of high-volume streaming data.

Amazon Managed Service for Apache Flink provides a fully managed environment for stream processing with built-in support for RANDOM_CUT_FOREST, an algorithm designed for anomaly detection in real-time streaming data.

This approach eliminates the need for deploying and managing additional infrastructure like SageMaker endpoints, Lambda functions, or external tools, making it the most scalable and operationally simple solution.

For near real-time inference with low latency and variable traffic, AWS recommends deploying models to managed SageMaker endpoints. By enabling auto scaling, the endpoint automatically adjusts the number of instances based on request volume, ensuring consistent performance while optimizing cost.

Amazon SageMaker Endpoints abstracts infrastructure management, health checks, scaling, and model deployment. This provides lower operational overhead than managing EC2 instances manually.

Batch transform is for offline inference. API Gateway with S3 cannot serve ML models. EC2-based deployments require manual scaling and monitoring.

Therefore, a SageMaker endpoint with auto scaling is the correct solution.

The correct answer is C. Use SageMaker Model Monitor to detect data drift. Use an AWS Lambda function to automate the re-training job.

Amazon SageMaker Model Monitor is the AWS-recommended solution for automatically detecting data drift in ML pipelines. Data drift occurs when the statistical properties of input features change over time, potentially reducing model accuracy. Model Monitor continuously analyzes incoming data and compares it to the baseline training dataset to identify deviations. It can track both feature distributions and prediction quality metrics.

Once Model Monitor detects data drift, it can trigger automated workflows using AWS Lambda or Amazon EventBridge. An AWS Lambda function can initiate a SageMaker training job to re-train the model using updated datasets, ensuring the ML model remains accurate and reliable. This setup fully automates the response to drift events, meeting the requirement of automatically initiating re-training.

Option A (AWS Glue) is designed for ETL processes but does not natively detect ML-specific data drift. Option B (Amazon Managed Service for Apache Flink) can process streaming data but does not provide native drift detection for ML pipelines. Option D (Amazon QuickSight anomaly detection) focuses on business intelligence and visual anomaly detection, not automated re-training workflows for ML models.

By integrating SageMaker Model Monitor with Lambda, the ML engineer can maintain model performance proactively, implement automated re-training, and align with AWS best practices for ML solution monitoring, maintenance, and security. This approach ensures continuous validation of model inputs and outputs, reduces operational overhead, and prevents degradation in production ML performance due to unseen data changes.