The AWS Certified Machine Learning Engineer - Associate (MLA-C01)

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.

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.

AWS documentation strongly recommends using columnar storage formats to optimize analytical query performance on large datasets stored in Amazon S3. Apache Parquet is a columnar, compressed, and splittable file format that significantly improves query speed and reduces I/O compared to row-based formats such as CSV.

By using AWS Glue to convert CSV files into Parquet format, the company can achieve faster query execution with minimal operational overhead. Glue is fully managed, serverless, and integrates natively with S3, Amazon Athena, and Amazon Redshift Spectrum.

Option A does not improve query efficiency; splitting files still leaves the data in an inefficient row-based format. Option B may reduce data size but does not address the fundamental inefficiency of CSV for analytics. Option D introduces significant operational overhead because Amazon EMR requires cluster provisioning, scaling, and maintenance.

Therefore, converting CSV files to Apache Parquet using AWS Glue ETL is the most efficient and low-maintenance solution.

The key requirements in this scenario are variable traffic patterns and cost efficiency. The workload has unpredictable spikes during evenings and weekends, followed by long periods of low or no usage. According to AWS Machine Learning documentation, Amazon SageMaker Serverless Inference is specifically designed for such use cases.

SageMaker Serverless Inference automatically provisions, scales, and shuts down compute resources based on incoming inference requests. Customers are billed only for the compute time used during inference, not for idle resources. This makes it highly cost-effective for workloads with intermittent or spiky traffic, such as real-time chat moderation in gaming environments.

Option A is incorrect because batch transform jobs are intended for offline, large-scale inference and require fixed capacity during job execution. They are not suitable for real-time NLP moderation.

Option C is also incorrect because reserving an EC2 GPU instance incurs continuous costs regardless of utilization. This would be inefficient given the long idle periods described in the scenario.

Option D, SageMaker Asynchronous Inference, is designed for workloads with long processing times or large payloads and still requires endpoint provisioning. While it can handle traffic spikes, it does not scale down to zero in the same cost-efficient manner as Serverless Inference.

Therefore, Amazon SageMaker Serverless Inference is the most cost-effective and operationally efficient solution for deploying an NLP moderation model with highly variable usage patterns.

Amazon MSK Serverless provides a fully managed Apache Kafka-compatible service that automatically handles provisioning, scaling, and capacity management. AWS documentation states that MSK Serverless is designed for customers who want Kafka functionality without managing infrastructure.

Option B requires capacity planning and scaling management. Option C uses proprietary technology rather than open source. Option D requires full infrastructure management.

MSK Serverless delivers near real-time streaming with minimal operational overhead while maintaining compatibility with open-source Kafka tooling.

Therefore, Option A is the correct solution.

Amazon SageMaker Data Wrangler provides a comprehensive solution for importing, consolidating, and preparing datasets for ML. It offers tools to handle missing values, duplicates, and outliers through its built-in cleansing and enrichment functionalities, allowing the ML engineer to efficiently prepare the data in a single environment with minimal manual effort.

Accuracy measures the proportion of correctly predicted labels (both positive and negative) out of the total predictions. It is the appropriate metric when the goal is to maximize the correct predictions of both positive and negative labels. However, it assumes that the classes are balanced; if the classes are imbalanced, other metrics like precision, recall, or specificity may be more relevant depending on the specific needs.

AWS Glue DataBrew is designed specifically for no-code and low-code data preparation, making it the fastest and lowest-overhead solution for resolving common data quality issues. DataBrew provides built-in transformations for deduplication, missing value imputation, and outlier handling while preserving data integrity.

Option A uses standard statistical techniques such as median imputation and value normalization, which are widely accepted and maintain the distribution of the data. DataBrew jobs are fully managed and do not require infrastructure setup or maintenance.

Option B deletes records, which can lead to data loss and does not preserve integrity. Option C introduces unnecessary infrastructure complexity and uses poor data imputation practices. Option D provides advanced capabilities but requires more configuration and ML expertise, increasing operational overhead.

AWS documentation clearly positions DataBrew as the preferred solution for quick, reliable data cleaning with minimal effort.

Therefore, Option A is the correct answer.

AWS recommends lifecycle configuration scripts as the simplest and most direct way to customize Amazon SageMaker Notebook Instances at creation time. Lifecycle configurations run automatically when a notebook instance is created or started, allowing scripts, packages, and system dependencies to be installed without manual intervention.

This approach is fully supported, requires no additional infrastructure, and integrates directly with the notebook creation workflow. The script can be reused across notebooks, ensuring consistency.

Options B, C, and D introduce unnecessary complexity, such as container management, private package repositories, or event-driven orchestration.

Therefore, lifecycle configuration scripts provide the least operational overhead solution.