Amazon Web Services MLA-C01 Online Access

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.

Different data types require different encoding strategies. The Feedback column contains long, unstructured text responses. According to AWS ML documentation, text data must first be converted into tokens before it can be vectorized using techniques such as embeddings or bag-of-words. Tokenization is the correct preprocessing step for textual features.

The Satisfaction Level column is categorical but has a natural ordering (Low < Medium < High). AWS best practices recommend ordinal encoding for such ordered categorical variables because it preserves the inherent ranking information.

Option A is incorrect because one-hot encoding is not suitable for free-form text and would create an unmanageable number of features. Option B has the same issue for the Feedback column. Option C incorrectly applies label encoding to text and binary encoding to a three-class ordinal variable.

Therefore, tokenization for text data and ordinal encoding for satisfaction levels is the correct solution.

Amazon SageMaker supports direct file system access for training jobs through Amazon FSx. AWS documentation states that FSx for NetApp ONTAP file systems can be mounted directly to SageMaker training instances when they are located in the same VPC.

Mounting the FSx file system allows SageMaker to stream large datasets efficiently without copying data into Amazon S3. This is ideal for very large datasets such as 6 TB of image data and avoids unnecessary storage duplication.

Options involving SageMaker Data Wrangler are intended for data preparation and exploration, not large-scale training data access. Mountpoint for Amazon S3 is not required and introduces additional complexity.

Therefore, Option A is the correct and AWS-aligned solution.

For real-time video content moderation with minimal operational overhead, AWS documentation recommends using fully managed, purpose-built AI services. Amazon Rekognition provides real-time video analysis capabilities, including content moderation, unsafe content detection, and label recognition for live video streams.

By integrating Rekognition with AWS Lambda, the company can automatically process video frames, extract moderation metadata, and take immediate action (such as flagging or stopping a stream) without managing servers, models, or infrastructure. This serverless architecture scales automatically and minimizes operational complexity.

Option B introduces unnecessary complexity. While Amazon Bedrock LLMs are powerful, they are not required for image-based moderation tasks that Rekognition already handles natively.

Option C is incorrect because using Amazon SageMaker would require model training, endpoint management, and scaling, significantly increasing operational overhead.

Option D is incorrect because Amazon Transcribe and Amazon Comprehend are designed for audio and text analysis, not image or video frame moderation.

Therefore, Amazon Rekognition with AWS Lambda is the most efficient, scalable, and low-maintenance solution for real-time video moderation during live streaming events.