Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Exam Questions

Answer : C

AWS recommends Amazon SageMaker Model Monitor as the native service for detecting data drift, model drift, and bias drift in deployed ML models. Model Monitor continuously compares incoming inference data against a baseline dataset captured during training.

When Model Monitor detects drift beyond configured thresholds, it can emit Amazon CloudWatch events. These events can trigger an AWS Lambda function, which is a common AWS-documented pattern for orchestrating automated workflows such as model retraining.

This Lambda function can then initiate a SageMaker Pipeline execution, starting a retraining job with updated data. This architecture aligns with AWS best practices for building automated, event-driven ML pipelines.

Option A is incorrect because AWS Glue is designed for data cataloging and ETL, not for ML-specific drift detection. Option B is unnecessary and overly complex for this use case. Option D is incorrect because Amazon QuickSight anomaly detection is intended for business intelligence analytics, not ML model monitoring.

AWS documentation explicitly positions SageMaker Model Monitor + Lambda automation as the recommended approach for continuous ML monitoring and retraining.

Therefore, Option C is the correct and AWS-verified answer.

Answer : C

AWS recommends shadow testing to evaluate a new model against a production model with minimal operational overhead. Using production variants on a single SageMaker endpoint allows traffic to be routed to multiple models without managing additional endpoints.

With a shadow variant, the new model receives a copy of live traffic but does not affect production responses. Performance metrics such as latency, accuracy, and error rates can be compared directly against the current model using Amazon CloudWatch metrics. This approach is natively supported by Amazon SageMaker Endpoints.

Options A, B, and D introduce unnecessary complexity by requiring additional endpoints, traffic routing infrastructure, or custom code.

Therefore, deploying the new model as a shadow variant on the same endpoint is the most efficient solution.

Answer : A

AWS Bedrock Knowledge Bases support multiple chunking strategies to optimize retrieval quality. Hierarchical chunking is specifically designed for structured documents such as PDFs with headings, sections, and subsections.

Hierarchical chunking allows fine-grained retrieval at the subsection level while automatically preserving parent section context. This ensures that when a small portion is retrieved, the surrounding section is also provided to the foundation model for better understanding.

Fixed-size and maximum-token chunking can split content arbitrarily, breaking semantic and structural boundaries. Semantic chunking focuses on meaning but does not guarantee structured context preservation without additional logic.

AWS documentation highlights hierarchical chunking as the preferred strategy when documents are structured and contextual integrity is required.

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

Answer : D

Answer : A

Managing permissions for multiple Amazon SageMaker notebook instances can become complex when handled individually. To centralize and streamline permission management, AWS recommends creating a single IAM role with the necessary permissions and attaching this role to each notebook instance used by the data science team.

Steps to Implement the Solution:

Create a Single IAM Role with Necessary Permissions:

Define an IAM role that encompasses all permissions required by the data scientists for their tasks. This includes permissions for SageMaker operations and any other AWS services they interact with.

AWS provides managed policies like AmazonSageMakerFullAccess that can be attached to the role to grant comprehensive SageMaker permissions.(IAM Policies for SageMaker)

Attach the IAM Role to Each Notebook Instance:

When creating or updating a SageMaker notebook instance, specify the IAM role created in the previous step. This ensures that all notebook instances operate under a consistent set of permissions.

In the SageMaker console, during the notebook instance setup, you can choose an existing IAM role to associate with the instance.(Creating SageMaker Workspaces)

Benefits of This Approach:

Centralized Permission Management:By using a single IAM role, you simplify the process of updating permissions. Changes to the role's policies automatically propagate to all associated notebook instances, ensuring consistent access control.

Adherence to Best Practices:AWS recommends using IAM roles to manage permissions for applications running on services like SageMaker. This approach avoids the need to manage individual user permissions separately.(IAM Best Practices for SageMaker)

Alternative Options and Their Drawbacks:

Option B: Creating a single IAM group and adding data scientists to it does not directly associate the group with notebook instances. IAM groups are used to manage user permissions, not to assign roles to AWS resources like notebook instances.

Option C: Using a single IAM user with the AdministratorAccess policy is not recommended due to security risks associated with granting broad permissions and the challenges in managing shared user credentials.

Option D: Associating an IAM group with a role and then with notebook instances is not a valid approach, as IAM groups cannot be directly associated with AWS resources.

Conclusion: Option A is the most effective solution to centralize and manage permissions for SageMaker notebook instances, aligning with AWS best practices for IAM role management.

AWS Documentation: IAM Policies for SageMaker

AWS Documentation: Creating SageMaker Workspaces

AWS Documentation: IAM Best Practices for SageMaker

Answer : A

Monitoring bias drift in deployed machine learning models is crucial to ensure fairness and accuracy over time. Amazon SageMaker Clarify provides tools to detect bias in ML models, both during training and after deployment. To monitor bias drift for models deployed to real-time endpoints, an effective approach involves orchestrating SageMaker Clarify jobs using AWS Lambda functions.

Implementation Steps:

Set Up Data Capture:

Enable data capture on the SageMaker endpoint to record input data and model predictions. This captured data serves as the basis for bias analysis.

Develop a Lambda Function:

Create an AWS Lambda function configured to initiate a SageMaker Clarify job. This function will process the captured data to assess bias metrics.

Schedule or Trigger the Lambda Function:

Configure the Lambda function to run on-demand or at scheduled intervals using Amazon CloudWatch Events or EventBridge. This setup allows for regular bias monitoring as per the application's requirements.

Analyze and Respond to Results:

After each Clarify job completes, review the generated bias reports. If bias drift is detected, take appropriate actions, such as retraining the model or adjusting data preprocessing steps.

Advantages of This Approach:

Automation: Utilizing AWS Lambda for orchestrating Clarify jobs enables automated and scalable bias monitoring without manual intervention.

Cost-Effectiveness: AWS Lambda's serverless nature ensures that you only pay for the compute time consumed during the execution of the function, optimizing resource usage.

Flexibility: The solution can be tailored to specific monitoring needs, allowing for adjustments in monitoring frequency and analysis parameters.

By implementing this solution, the company can effectively monitor bias drift in real-time, ensuring that the AI application maintains fairness and accuracy throughout its lifecycle.

Bias drift for models in production - Amazon SageMaker

Schedule Bias Drift Monitoring Jobs - Amazon SageMaker

Answer : B

The problem described is a patient segmentation use case, which is a classic example of unsupervised learning. The objective is to group patients with similar characteristics without predefined labels. AWS documentation clearly states that Amazon SageMaker k-means is designed specifically for clustering and segmentation tasks.

The SageMaker k-means algorithm groups data points into clusters based on feature similarity and requires the user to define the number of clusters using the k hyperparameter. This directly satisfies the requirement to ''determine the number of groups by using hyperparameters.'' AWS recommends k-means for applications such as customer segmentation, risk grouping, and pattern discovery in healthcare data.

Option A (XGBoost) is a supervised learning algorithm used for classification and regression. The max_depth hyperparameter controls tree complexity, not the number of groups, making it unsuitable for this task.

Option C (DeepAR) is a time-series forecasting algorithm optimized for predicting future values, not clustering patients.

Option D (Random Cut Forest) is an anomaly detection algorithm. While useful for identifying outliers or unusual patient behavior, it does not perform clustering or group segmentation.

AWS SageMaker documentation explicitly identifies k-means as the correct choice when the goal is to partition data into a predefined number of clusters using a tunable hyperparameter.

Therefore, Option B is the correct and AWS-verified answer.