MLS-C01 Machine Learning Implementation and Operations Practice Test 23 — 15 Questions

Question 1

A team needs to automatically retrain a model every week using new data. Which SageMaker feature is designed to schedule and automate this workflow?

Accepted Answer

SageMaker Pipelines. SageMaker Pipelines is a purpose-built CI/CD service for machine learning that lets you define, schedule, and automate multi-step workflows including data preprocessing, training, evaluation, and model registration. You can trigger a pipeline on a weekly schedule using EventBridge or the Pipelines scheduling capability, making it the correct choice for automated weekly retraining.

Answer

SageMaker Automatic Model Tuning

Answer

SageMaker Model Monitor

Answer

SageMaker Data Wrangler

Question 2

A model deployed on a SageMaker endpoint is producing predictions that are consistently biased against a certain demographic. Which step should the team take FIRST to address this issue?

Accepted Answer

Use SageMaker Clarify to analyze bias in the training data and predictions. The first step is to analyze the data and model for bias. SageMaker Clarify can detect bias in training data and predictions, making option C the correct first step. Option A (SageMaker Model Monitor) tracks prediction quality but does not specifically analyze bias. Option B (switching algorithm) is a reactive change without understanding the bias source. Option D (retraining with balanced data) is a potential fix but should come after bias analysis.

Answer

Enable SageMaker Model Monitor to track prediction quality

Answer

Switch to a different algorithm that is less prone to bias

Answer

Retrain the model with balanced data

Question 3

A machine learning team is using SageMaker to train a model with a custom Docker container. The training script runs locally but fails on SageMaker with a 'Permission denied' error when writing to /opt/ml/model. What is the likely cause?

Accepted Answer

The container's user does not have write permission to /opt/ml/model. SageMaker mounts the model artifact directory at /opt/ml/model inside the training container and expects the training script to write model artifacts there. If the Docker container runs as a non-root user (e.g., USER appuser) and that user lacks write permissions on /opt/ml/model, the script will fail with 'Permission denied'. This is a common issue when custom containers are built with restrictive file ownership, since SageMaker does not automatically chown the mounted directories to the container's user.

Answer

The Docker image is too large

Answer

The training script is trying to read from /opt/ml/input/data instead of /opt/ml/input/data/training

Answer

The training data is not in the correct S3 bucket

Question 4

A company wants to monitor SageMaker endpoints for data drift. Which TWO services can be used together to detect and alert on drift?

Accepted Answer

SageMaker Model Monitor. SageMaker Model Monitor (option B) is the AWS service purpose-built to continuously monitor SageMaker endpoints for data drift, model quality, bias, and feature attribution drift; it captures endpoint traffic, compares it against a baseline, and emits metrics to CloudWatch. Amazon CloudWatch Alarms (option D) is then used to watch those Model Monitor metrics (e.g., the drift metric emitted to the AWS/SageMaker namespace) and trigger notifications or actions when drift exceeds a threshold, which is exactly the detect-and-alert workflow the company needs. SageMaker Data Wrangler (option A) is a data preparation and feature-engineering tool, not a runtime drift-detection service, so it does not monitor live endpoints. AWS CodePipeline (option C) is a CI/CD orchestration service and has no role in detecting data drift. Amazon CloudWatch Logs (option E) stores log data but does not itself detect drift or raise alerts, so it cannot fulfill the alerting requirement on its own.

Answer

SageMaker Data Wrangler

Answer

AWS CodePipeline

Answer

Amazon CloudWatch Logs

Question 5

A data scientist needs to deploy a model with a custom inference container. Which THREE requirements must the container meet for SageMaker hosting?

Accepted Answer

Implement a /ping endpoint for health checks. For SageMaker hosting with a custom inference container, the container must implement the required HTTP contract. Option C is correct because SageMaker sends GET requests to the /ping endpoint to verify the container is healthy and ready to serve traffic. Option D is correct because the container must listen for HTTP requests on port 8080, which is the port SageMaker expects for inference containers. Option E is correct because the /invocations endpoint is where SageMaker sends POST requests containing the input data and expects the model's predictions in response. Option A is incorrect because /opt/ml/input/data is a training data path convention, not a hosting requirement, and no training script is needed for inference. Option B is incorrect because the SageMaker Python SDK is a client-side tool for interacting with SageMaker; the container itself does not need to use it to load the model and can use any framework or library.

Answer

Provide a training script at /opt/ml/input/data

Answer

Use the SageMaker Python SDK to load the model

Question 6

A machine learning team is using SageMaker Pipelines to orchestrate a multi-step workflow. The pipeline fails with a 'ThrottlingException' when submitting a training job. Which TWO actions can reduce the likelihood of throttling?

Accepted Answer

Implement retry logic with exponential backoff in the pipeline. Option B is correct because implementing retry logic with exponential backoff in the pipeline directly mitigates transient ThrottlingException errors from SageMaker API calls by spacing out retries and giving the service time to recover, which is the AWS-recommended pattern for handling throttling. Option D is correct because reducing the number of concurrent pipeline steps lowers the rate of simultaneous SageMaker API requests (for example, CreateTrainingJob calls), keeping request volume under the service's per-account throttling limits and thereby decreasing the chance of hitting ThrottlingException. Option A is not relevant because SageMaker Model Registry is for versioning and tracking models, not for controlling API request rates. Option C is incorrect because increasing parallel training jobs raises concurrent API call volume and would worsen throttling rather than reduce it. Option E is not the right fit here because a service quota increase addresses limits on resource counts (such as concurrent training jobs), whereas ThrottlingException is caused by exceeding API request-rate limits, which are not raised through the standard service quota increase process.

Answer

Use SageMaker Model Registry to version models

Answer

Increase the number of parallel training jobs

Answer

Request a service quota increase for training jobs

Question 7

A data scientist is training a deep learning model on Amazon SageMaker using the built-in Object Detection algorithm. The training job is failing with a 'ResourceLimitExceeded' error when trying to launch multiple GPU instances. Which of the following is the MOST likely cause?

Accepted Answer

The account has reached the limit for the number of GPU instances in the current AWS Region.. The 'ResourceLimitExceeded' error in SageMaker specifically indicates that the training job requested more instances (or a specific instance type) than the account's service quota allows in that AWS Region. GPU instances like ml.p3.2xlarge have default quotas that are often low for new accounts, and launching multiple instances can exceed the limit. The fix is to request a quota increase via Service Quotas.

Answer

The training script has a syntax error.

Answer

The dataset is too large for the selected instance type.

Answer

The S3 bucket containing the training data has insufficient permissions.

Question 8

A machine learning team is deploying a real-time inference endpoint on Amazon SageMaker for a model that requires low latency (<100 ms). The model is a PyTorch model with custom pre- and post-processing logic. The team uses a SageMaker Model with a custom inference container. After deployment, they observe that the endpoint takes over 500 ms for the first request, but subsequent requests are fast (~50 ms). What is the MOST likely cause?

Accepted Answer

The container has a cold start delay because the model needs to be loaded into memory from Amazon S3 on the first request.. The most likely cause is a cold start delay: the custom inference container must download the model artifacts from Amazon S3 and load them into memory on the first invocation. Subsequent requests reuse the loaded model, resulting in fast inference. This is a common pattern in SageMaker when the model is not pre-loaded or when the container lacks a warm-up mechanism.

Answer

The instance type is too small to handle the model size.

Answer

The model is too large and exceeds the instance memory.

Answer

The endpoint is not configured with auto-scaling.

Question 9

A data scientist is performing hyperparameter tuning using Amazon SageMaker Automatic Model Tuning (AMT). The job uses a random search strategy. After 20 training jobs, the best objective metric value has plateaued. The data scientist wants to explore more of the hyperparameter space. Which action should the data scientist take?

Accepted Answer

Change the tuning strategy from Random to Bayesian.. Changing the tuning strategy from Random to Bayesian allows the tuning job to use previous results to guide the search toward more promising hyperparameter regions, which can explore the space more efficiently after plateauing. Option B is incorrect because enabling early stopping terminates underperforming trials early but does not alter the search strategy itself; it may even reduce exploration. Option C is incorrect because decreasing the maximum number of training jobs reduces the total exploration of the hyperparameter space. Option D is incorrect because increasing the number of parallel training jobs only speeds up the process but still uses the same random search strategy, which is unlikely to escape the plateau.

Answer

Enable early stopping.

Answer

Decrease the maximum number of training jobs.

Answer

Increase the number of parallel training jobs.

Question 10

A machine learning engineer is deploying a model to an Amazon SageMaker endpoint. The model requires GPU for inference. Which instance type should be selected?

Accepted Answer

ml.p3.2xlarge. The ml.p3.2xlarge instance type is part of the Amazon SageMaker P3 family, which is specifically designed for GPU-accelerated computing. It includes NVIDIA Tesla V100 GPUs, making it suitable for deep learning inference that requires GPU. The other options are general-purpose (M5), compute-optimized (C5), and memory-optimized (R5) instances that do not have GPUs.

Answer

ml.m5.large

Answer

ml.c5.xlarge

Answer

ml.r5.large

Question 11

A data scientist is using Amazon SageMaker to train a model with a custom Docker container. The training script reads data from an S3 bucket and writes the model artifact to an S3 bucket. The training job fails with a 'NoSuchKey' error. What is the MOST likely cause?

Accepted Answer

The training data path specified in the input data channel is incorrect.. The 'NoSuchKey' error indicates that the specified key (file path) does not exist within the S3 bucket, which occurs when the training data path provided in the input data channel is incorrect. Option A is wrong because, while a script compatibility issue could cause errors, it would not manifest as a 'NoSuchKey' S3 error; it would likely result in a failure during container execution. Option C is wrong because if the Docker image were not available in Amazon ECR, SageMaker would fail with an 'ImageNotFoundException' or similar ECR-related error, not a 'NoSuchKey' S3 error. Option D is wrong because insufficient S3 permissions (e.g., missing s3:GetObject) would result in an 'AccessDenied' error, not 'NoSuchKey'.

Answer

The training script is not compatible with the Docker image.

Answer

The Docker image is not available in Amazon ECR.

Answer

The SageMaker execution role does not have s3:GetObject permission.

Question 12

A company is using Amazon SageMaker to train a machine learning model. The training job is configured to use the File mode to download data from S3 to the training instances. The training data is stored in a single S3 bucket with multiple prefixes. Which TWO actions are required to ensure the training job can access the data? (Choose TWO.)

Accepted Answer

Grant the SageMaker execution role s3:GetObject permission for the data bucket.. Option A is correct because SageMaker training jobs access S3 using the execution role attached to the job, so that role must have s3:GetObject (and typically s3:ListBucket) permissions on the data bucket for File mode to download the objects. Option C is correct because each training input channel must point to the specific S3 prefix (or object) containing the data; with multiple prefixes, you define the appropriate S3 URI per channel so SageMaker knows what to download. Option B is incorrect because Pipe mode is an alternative streaming input mode, not a requirement for File mode access. Option D is incorrect because File mode downloads individual objects and does not require concatenating files into one. Option E is incorrect because RecordIO-protobuf is an optional data format for certain algorithms, not a prerequisite for S3 access.

Answer

Configure the training job to use Pipe mode.

Answer

Concatenate all data files into a single file.

Answer

Convert the data to RecordIO-protobuf format.

Question 13

A company is deploying a machine learning model using SageMaker. The model is a PyTorch model that requires GPU for inference. The company wants to minimize costs while ensuring low latency. Which instance type should be used for the SageMaker endpoint?

Accepted Answer

ml.g4dn.xlarge. Ml.g4dn.xlarge is a GPU instance with an NVIDIA T4, optimized for inference, and is more cost-effective than ml.p3.2xlarge while still providing low latency for PyTorch models. Option A (ml.m5.large) is wrong as it is a CPU instance without GPU support. Option B (ml.p3.2xlarge) is wrong because although it has a GPU, it is more expensive and not necessary for low-latency inference; ml.g4dn.xlarge offers similar performance at lower cost. Option C (ml.c5.2xlarge) is also a CPU instance and unsuitable.

Answer

ml.m5.large

Answer

ml.p3.2xlarge

Answer

ml.c5.2xlarge

Question 14

A company uses SageMaker to host a real-time inference endpoint. The endpoint is receiving a large number of requests, but the latency is higher than expected. The data scientist observes that the CPU utilization is low but memory utilization is high. Which action should be taken to reduce latency?

Accepted Answer

Switch to an instance type with more memory or optimize the model to reduce memory footprint.. High memory utilization with low CPU utilization indicates the instance is memory-bound, not CPU-bound. Adding more memory or reducing the model's memory footprint (e.g., quantization, pruning) will alleviate the bottleneck and reduce latency. Scaling out instances or adding vCPUs won't help because the constraint is memory per instance.

Answer

Enable VPC traffic mirroring to diagnose network issues.

Answer

Use an instance type with more vCPUs.

Answer

Increase the number of instances in the endpoint.

Question 15

A data scientist is using SageMaker Ground Truth to create a labeled dataset for object detection. After the labeling job completes, the scientist notices that the output manifest file contains incorrect labels. What is the most efficient way to correct these labels?

Accepted Answer

Create an incremental labeling job that includes only the mislabeled items.. SageMaker Ground Truth supports incremental labeling jobs that allow you to provide a new manifest with only mislabeled items, and the job will correct only those labels without re-labeling correctly labeled data. Option B is wrong because deleting and starting over is inefficient and loses all progress. Option C is wrong because the SageMaker console does not allow direct editing of manifest files; labels are fixed only through re-labeling. Option D is wrong because it would re-label the entire dataset, wasting time and resources.

Answer

Delete the labeling job and start over with a different set of workers.

Answer

Use the SageMaker console to edit the incorrect labels directly in the manifest file.

Answer

Create a new labeling job with the same dataset and manually verify all labels.