Courseiva

AWS Certified Machine Learning Engineer Associate MLA-C01 (MLA-C01) — Questions 1–75

835 questions total · 12pages · All types, answers revealed

Take a mock examExam hub

Page 1 of 12

Page 2
1
MCQhard

A company uses AWS Glue to run ETL jobs that prepare data for machine learning. The source data in S3 has a schema that evolves over time (new columns are added occasionally). The Glue job schema is defined as a fixed schema in the job script. After an update to the source data, the Glue job fails with an error about mismatched schemas. How should the data engineer modify the data preparation process to handle schema evolution?

A.Modify the Glue job to use a dynamic frame and enable schema updates with a 'applyMapping' that includes new columns
B.Run a Glue crawler before each job to update the Data Catalog, but keep the fixed schema in the job
C.Store the schema definition in a separate file in S3 and read it at runtime
D.Manually update the Glue job script each time the schema changes
AnswerA

Dynamic frames with schema detection can adapt to schema changes.

Why this answer

AWS Glue DynamicFrames natively handle schema evolution by allowing you to apply a mapping that can include new columns. By using `applyMapping` with `resolveChoice`, you can define how to handle new fields (e.g., cast to a type or keep as a struct), preventing job failures when the source schema changes. This avoids the rigidity of a fixed schema in the job script.

Exam trap

The trap here is that candidates often assume updating the Data Catalog via a crawler is sufficient, but they miss that the job script's fixed schema must also be updated or made dynamic to avoid mismatches.

How to eliminate wrong answers

Option B is wrong because running a Glue crawler updates the Data Catalog but does not automatically adapt the fixed schema defined in the job script; the job will still fail if the script expects a specific schema. Option C is wrong because storing the schema in a separate S3 file and reading it at runtime still requires manual updates to that file when the schema changes, which does not provide dynamic adaptation. Option D is wrong because manually updating the job script each time the schema changes is error-prone, not scalable, and defeats the purpose of automated ETL processing.

Full explanation →
2
Multi-Selecthard

A company is building a CI/CD pipeline for ML models using AWS CodePipeline and SageMaker. The pipeline should include steps to automatically retrain, evaluate, and deploy models. Which THREE components are essential for this pipeline? (Choose three.)

Select 3 answers
A.SageMaker Pipelines to orchestrate training and evaluation steps.
B.Amazon S3 bucket to store training data and model artifacts.
C.Amazon CloudWatch to log API calls.
D.SageMaker Model Registry to store and version models.
E.AWS Lambda function to trigger evaluation.
AnswersA, B, D

Pipelines define the sequence of steps and conditional logic for retraining and evaluation.

Why this answer

SageMaker Pipelines is essential because it provides a native orchestration service to define, automate, and manage the end-to-end ML workflow, including training, evaluation, and conditional deployment steps. It integrates directly with other SageMaker components and CodePipeline, enabling a seamless CI/CD pipeline without requiring custom orchestration logic.

Exam trap

The trap here is that candidates often confuse monitoring services like CloudWatch with essential pipeline components, or assume that a serverless function like Lambda is required for evaluation when SageMaker Pipelines already provides native evaluation capabilities.

Full explanation →
3
MCQhard

A team needs to deploy a model that has compliance requirements to log all inference requests and responses for auditing. The model will be served using a real-time endpoint. How can they achieve this without custom code?

A.Enable SageMaker Data Capture on the endpoint
B.Add a custom Lambda function using a container
C.Use SageMaker Debugger to monitor inference
D.Enable CloudTrail for the endpoint
AnswerA

Data Capture logs requests and responses to S3 automatically.

Why this answer

SageMaker Data Capture is the native, no-code feature that automatically logs inference requests and responses for real-time endpoints. It captures payload data to an S3 bucket without requiring any custom code, directly meeting the compliance requirement for audit logging.

Exam trap

The trap here is that candidates often confuse CloudTrail (which logs API calls) with Data Capture (which logs payloads), or they assume Debugger can be repurposed for inference logging, but Debugger only works during training.

How to eliminate wrong answers

Option B is wrong because adding a custom Lambda function using a container introduces custom code, which the question explicitly states should be avoided. Option C is wrong because SageMaker Debugger is designed for monitoring training jobs and debugging model performance, not for capturing inference request/response logs for auditing. Option D is wrong because AWS CloudTrail logs API calls to the SageMaker endpoint (e.g., InvokeEndpoint actions) but does not capture the actual inference request and response payloads.

Full explanation →
4
MCQeasy

A data scientist is using Amazon SageMaker Data Wrangler to prepare a dataset for training. The dataset contains a column with missing values. Which built-in transform in Data Wrangler can be used to handle missing values by replacing them with the mean of the column?

A.Standardize data
B.Impute missing values
C.Balance data
D.Encode categorical
AnswerB

Data Wrangler's 'Handle missing values' transform can impute with mean.

Why this answer

SageMaker Data Wrangler provides a 'Handle missing values' transform that includes options to fill with mean, median, mode, or a custom value. The other options are separate transforms for different tasks.

Full explanation →
5
MCQhard

A machine learning engineer is using Amazon SageMaker Data Wrangler to prepare a dataset with a categorical feature that has over 5,000 distinct values (high cardinality). The engineer needs to transform this feature into a form suitable for a gradient boosting model while preserving as much information as possible. Which transform should be applied?

A.Label encoding
B.Target encoding with smoothing
C.One-hot encoding
D.Drop the feature
AnswerB

Target encoding replaces each category with the mean target value, optionally with smoothing to avoid overfitting. This is a standard technique for high-cardinality features in gradient boosting.

Why this answer

For high-cardinality categorical features in tree-based models like gradient boosting, target encoding (mean target per category) is effective because it captures the relationship with the target without exploding feature dimensions. One-hot encoding would create too many columns, and label encoding introduces ordinality issues.

Full explanation →
6
MCQmedium

A team used the above config to create an endpoint. However, the endpoint fails to invoke because of a "ModelError". What is the most likely cause?

A.The instance type is not available in the region.
B.The IAM role does not have permission to access the S3 bucket.
C.The model data URL points to a non-existent file.
D.The ECR image URI is incorrect for the region.
AnswerB

Without s3:GetObject, the endpoint cannot load the model artifact.

Why this answer

The most likely cause of a ModelError when invoking a SageMaker endpoint is that the IAM role associated with the endpoint does not have the necessary permissions to access the S3 bucket containing the model artifacts. SageMaker downloads the model data from S3 during endpoint creation, and if the role lacks s3:GetObject permission on the bucket, the model fails to load, resulting in a ModelError.

Exam trap

AWS often tests the distinction between errors that occur during model creation (e.g., invalid S3 URI, missing file) versus errors that occur at invocation time (ModelError), leading candidates to incorrectly choose Option C when the actual cause is a permissions issue that prevents the model from being loaded.

How to eliminate wrong answers

Option A is wrong because an unavailable instance type would cause an 'InsufficientInstanceCapacity' or 'ResourceLimitExceeded' error, not a ModelError. Option C is wrong because a non-existent model data file would cause a 'ModelError' only if the file path is syntactically valid but missing; however, the question states the endpoint fails to invoke, and a missing file typically raises a 'ValidationError' during model creation, not a runtime ModelError. Option D is wrong because an incorrect ECR image URI would cause an 'ImageNotFoundException' or 'AccessDeniedException' during model creation, not a ModelError at invocation time.

Full explanation →
7
Multi-Selecthard

An MLOps team is designing a SageMaker Pipeline to automate model retraining. The pipeline must: (1) run training only if new training data is available, (2) register the model in SageMaker Model Registry only if evaluation metrics exceed a threshold, (3) deploy the approved model to a staging endpoint automatically. Which THREE steps should they include? (Choose THREE.)

Select 3 answers
A.ConditionStep to check if evaluation metrics exceed the threshold
B.RegisterModel step to register the model in the Model Registry
C.TuningStep to perform hyperparameter optimization
D.TransformStep to deploy the model to a staging endpoint
E.ProcessingStep to check for new training data availability
AnswersA, B, E

A ConditionStep allows branching: if metrics exceed threshold, proceed to register; otherwise skip.

Why this answer

A ConditionStep evaluates a condition and routes to different branches. The RegisterModel step registers a model in the registry. A TransformStep (batch transform) runs inference, but for deployment a CreateModel and endpoint creation step is needed, though not listed; the correct deploy step is not a TransformStep.

A ProcessingStep can be used to check for new data. A TrainingStep trains the model. A TuningStep is for hyperparameter tuning.

Full explanation →
8
MCQmedium

A fraud detection model is being trained on imbalanced data. The team wants to ensure the model's precision is optimized. Which objective metric should be used in automatic model tuning?

A.F1
B.AUC
C.Precision
D.Recall
AnswerC
Full explanation →
9
MCQhard

A company uses SageMaker endpoint with production variants for canary deployments. The team wants to gradually shift traffic from the old model variant (variant A) to the new model variant (variant B) over a period of 10 minutes. After the shift, if the new variant's error rate increases by more than 5%, they want to roll back automatically. Which solution meets these requirements with minimal manual intervention?

A.Use AWS Cloud Map to register the new variant and perform a slow rollout.
B.Deploy variant B as a separate endpoint and use Route 53 weighted routing to shift traffic.
C.Use the SageMaker UpdateEndpoint API with a linear traffic shift from variant A to variant B over 10 minutes, and configure a CloudWatch alarm on the new variant's error rate that triggers a Lambda function to revert the traffic weights.
D.Use AWS CodeDeploy with a deployment group to shift traffic and automatically roll back if CloudWatch alarms trigger.
AnswerC

This approach automates both the gradual shift and the rollback based on error rates.

Why this answer

The SageMaker UpdateEndpoint API supports a linear traffic shift between production variants, allowing you to gradually route traffic from variant A to variant B over a specified time period (here, 10 minutes). By attaching a CloudWatch alarm on the new variant's error rate that triggers a Lambda function to revert the traffic weights, you achieve automatic rollback with minimal manual intervention when the error rate exceeds the 5% threshold.

Exam trap

The trap here is that candidates often assume AWS CodeDeploy (Option D) can manage SageMaker endpoints because it supports canary deployments for other services, but SageMaker has its own native traffic shifting and rollback mechanisms that are not integrated with CodeDeploy.

How to eliminate wrong answers

Option A is wrong because AWS Cloud Map is a service for service discovery and does not provide traffic shifting or canary deployment capabilities for SageMaker endpoints. Option B is wrong because deploying variant B as a separate endpoint and using Route 53 weighted routing would shift traffic at the DNS level, which introduces latency due to DNS caching and does not integrate with SageMaker's native variant monitoring or automatic rollback mechanisms. Option D is wrong because AWS CodeDeploy does not natively support SageMaker endpoints; it is designed for EC2, Lambda, and ECS deployments, and cannot directly manage traffic shifting or rollback for SageMaker production variants.

Full explanation →
10
MCQeasy

A data scientist wants to compare the performance of two model versions (V1 and V2) in production by splitting traffic between them. They want to gradually increase the percentage of traffic to the new version while monitoring metrics. Which SageMaker feature enables this?

A.SageMaker production variants with traffic splitting
B.SageMaker shadow testing
C.SageMaker blue/green deployment
D.SageMaker canary deployment
AnswerA

Production variants allow splitting traffic between model versions for A/B testing and gradual rollout.

Why this answer

Production variants with traffic splitting allow routing a percentage of inference requests to different model versions. By updating the initial variant weights, the data scientist can gradually shift traffic from V1 to V2. Shadow testing mirrors traffic but does not affect real responses.

Blue/green is a deployment pattern but not a SageMaker feature for gradual traffic splitting. Canary deployments are a pattern but SageMaker implements it via production variants.

Full explanation →
11
MCQmedium

A team is training a PyTorch model using SageMaker. They have a custom training script that requires specific Python packages not included in the SageMaker default PyTorch container. Which approach should they use?

A.Use the built-in PyTorch estimator and specify a requirements.txt in the source directory
B.Build a custom Docker container from scratch and push it to Amazon ECR
C.Use the SageMaker XGBoost estimator and modify the script to use PyTorch
D.Use SageMaker Autopilot to automatically handle dependencies
AnswerA

SageMaker automatically installs packages listed in requirements.txt in the source directory.

Why this answer

Using a SageMaker PyTorch estimator with a requirements.txt file allows installing additional packages on top of the official container. This is simpler than building a custom container.

Full explanation →
12
MCQeasy

A data scientist needs to deploy a single ML model that will serve real-time predictions with low latency (under 10 ms) for a high-traffic web application. The model fits in memory and requires GPU acceleration. Which SageMaker inference option is MOST suitable?

A.Real-time endpoint on ml.m5 instances
B.Batch Transform
C.Real-time endpoint on ml.g4dn instances
D.Serverless Inference
AnswerC

ml.g4dn instances offer GPU acceleration and are designed for low-latency, real-time inference.

Why this answer

Real-time endpoints on GPU instances (ml.g4dn) provide low latency and GPU acceleration, ideal for high-traffic, latency-sensitive workloads.

Full explanation →
13
MCQeasy

A team is building a machine learning model for natural language processing using SageMaker BlazingText. The data preparation step must format the training data correctly. What format does BlazingText require for supervised text classification?

A.One-hot encoded feature vectors stored in CSV
B.JSON lines with a 'text' and 'label' field
C.Tokenized words separated by spaces, with text and labels combined in a single line (e.g., '__label__positive great product')
D.TFRecord files with sequence features
AnswerC

BlazingText expects this format for supervised learning.

Why this answer

BlazingText for supervised text classification expects the training data in a specific format where each line contains the text and its labels, with labels prefixed by '__label__'. This format allows BlazingText to efficiently parse and process the data for training the word2vec or classification model without additional preprocessing. Option C correctly describes this format, where the label and text are space-separated on a single line.

Exam trap

The trap here is that candidates often confuse the JSON lines format (used by other SageMaker algorithms like BlazingText for Word2Vec or built-in Text Classification) with the specific '__label__' prefix format required for BlazingText's supervised text classification, leading them to select option B.

How to eliminate wrong answers

Option A is wrong because BlazingText does not accept one-hot encoded feature vectors in CSV; it requires raw text with inline labels for supervised classification. Option B is wrong because while JSON lines are common in other SageMaker built-in algorithms (e.g., BlazingText for Word2Vec or Text Classification using JSON lines), BlazingText's supervised text classification specifically requires the '__label__' prefix format, not JSON. Option D is wrong because TFRecord files are used by TensorFlow-based algorithms, not by BlazingText, which expects plain text files with the label-prefixed format.

Full explanation →
14
MCQhard

During a blue/green deployment of a SageMaker endpoint, the team notices that traffic is not being fully shifted to the new variant after the update. The endpoint has two variants with equal initial weights (50% each). The team wants to shift 100% traffic to the new variant. What is the most likely cause?

A.The new variant is using a different instance type that is not supported in the same endpoint
B.The new variant's model container is failing health checks, so traffic is not routed to it
C.The new variant's weight was set to 100 but the maximum weight per variant is 50
D.The endpoint's load balancer is misconfigured and not forwarding traffic to the new variant
AnswerB

SageMaker performs health checks; if the new variant fails, it stays in 'Creating' state and no traffic is routed.

Why this answer

SageMaker endpoints route traffic only to variants that pass health checks. If the new variant's model container fails health checks (e.g., due to a misconfigured inference script or incompatible dependencies), SageMaker will not send any traffic to it, regardless of the weight setting. This explains why traffic remains stuck at 50% on the old variant despite the intended shift to 100%.

Exam trap

The trap here is that candidates assume weight settings alone control traffic distribution, overlooking that SageMaker enforces health checks as a prerequisite for routing traffic to any variant.

How to eliminate wrong answers

Option A is wrong because SageMaker endpoints support multiple instance types across variants; a different instance type does not prevent traffic routing. Option C is wrong because SageMaker allows a single variant's weight to be set to 100 (the maximum is 100, not 50), so this would not block the shift. Option D is wrong because SageMaker endpoints use an internal application load balancer managed by the service; there is no customer-accessible load balancer to misconfigure.

Full explanation →
15
MCQhard

A machine learning team is preparing numerical features for a linear regression model. Feature 'A' ranges from 0 to 1000, feature 'B' ranges from 0 to 1, and feature 'C' ranges from -10000 to 10000. The team wants to ensure that feature scales do not affect the model's coefficients and that the features are bounded between 0 and 1. Which transformation should they apply?

A.RobustScaler (based on median and IQR)
B.Log transformation
C.StandardScaler (z-score normalization)
D.MinMaxScaler
AnswerD

MinMaxScaler scales to a given range (default 0 to 1), exactly as required.

Why this answer

MinMaxScaler scales each feature to a fixed range (default 0 to 1) by subtracting the minimum and dividing by the range. This ensures all features are within [0,1] and eliminates scale differences.

Full explanation →
16
MCQmedium

A company wants to implement a retraining pipeline that automatically triggers when SageMaker Model Monitor detects data drift. The retraining job should use the latest approved pipeline version in SageMaker Pipelines. Which approach meets these requirements?

A.Use a scheduled EventBridge rule to run the pipeline every day
B.Use SageMaker Model Monitor to update the model registry and trigger a deployment
C.Configure SageMaker Model Monitor to directly invoke a Lambda function on violation
D.Create an EventBridge rule that listens for SageMaker Model Monitor violation events and triggers a Lambda function that starts the pipeline
AnswerD

Model Monitor violations are captured as CloudWatch events; EventBridge can route those events to a Lambda function that starts the retraining pipeline.

Why this answer

It uses an EventBridge rule to listen for SageMaker Model Monitor violation events (e.g., `aws.sagemaker.model-monitoring-violation`), which then triggers a Lambda function that starts the latest approved pipeline version in SageMaker Pipelines. This creates an automated, event-driven retraining pipeline without manual intervention or scheduled polling.

Exam trap

The trap here is that candidates may think SageMaker Model Monitor can directly invoke Lambda or update the model registry, but in reality, it only emits events to EventBridge, and the integration requires an intermediate Lambda function to orchestrate the pipeline execution.

How to eliminate wrong answers

Option A is wrong because a scheduled EventBridge rule runs the pipeline daily regardless of whether data drift has occurred, leading to unnecessary retraining and resource waste. Option B is wrong because SageMaker Model Monitor does not directly update the model registry or trigger a deployment; it only publishes violation events and metrics. Option C is wrong because SageMaker Model Monitor cannot directly invoke a Lambda function; it emits events to EventBridge, which can then trigger Lambda, but the direct invocation is not supported.

Full explanation →
17
MCQhard

A company uses AWS Glue ETL jobs to transform data for machine learning. They have a dataset with a column 'income' that is heavily right-skewed. Which transformation should be applied to make the distribution more Gaussian-like?

A.Log transformation (natural log)
B.Standardization (z-score)
C.Min-max scaling to [0,1]
D.Equal-width binning
AnswerA

Reduces right skewness, makes distribution more symmetric.

Why this answer

A log transformation is appropriate for heavily right-skewed data because it compresses the long tail by applying a concave function, pulling extreme values closer to the mean and making the distribution more symmetric. In AWS Glue ETL, you can apply this using Spark SQL's `LOG` function or a Python UDF with `numpy.log`, which directly addresses the skewness to better approximate a Gaussian distribution for downstream ML models.

Exam trap

The trap here is that candidates confuse scaling (standardization or min-max) with shape-changing transformations, assuming any normalization makes data Gaussian, when in fact only non-linear transformations like log or Box-Cox address skewness.

How to eliminate wrong answers

Option B is wrong because standardization (z-score) centers and scales data to have mean 0 and standard deviation 1, but it does not change the shape of the distribution—it only rescales, so right-skewness remains. Option C is wrong because min-max scaling to [0,1] linearly compresses the data into a fixed range, which preserves the relative distances and does not alter skewness or make the distribution Gaussian-like. Option D is wrong because equal-width binning discretizes the continuous 'income' column into fixed intervals, which loses granularity and does not transform the distribution toward Gaussian—it creates a categorical or ordinal feature instead.

Full explanation →
18
MCQmedium

A data scientist is using SageMaker Autopilot to automatically build a binary classification model on a balanced dataset. They want to understand the relationship between the input features and the model predictions. Which feature in SageMaker Autopilot should they use?

A.Explainability reports
B.Data visualizations
C.Model tuning results
D.Model candidate definitions
AnswerA

Explainability reports provide feature importance and SHAP values, showing how features impact predictions.

Why this answer

SageMaker Autopilot generates explainability reports, including feature importance and model insights, via the 'Explainability' feature. This provides the relationship between features and predictions.

Full explanation →
19
MCQhard

A machine learning engineer deploys a model to an Amazon SageMaker endpoint with data capture enabled. The endpoint uses a production variant with initial instance count of 2. After a week, they notice that the captured data is not being sent to the specified Amazon S3 bucket. The IAM role used by the endpoint has the following policy attached. What is the MOST likely reason for the failure?

A.The S3 bucket does not exist.
B.The S3 bucket uses AWS KMS encryption and the role lacks kms:Decrypt permission.
C.The IAM role does not have permission to write to the correct S3 prefix.
D.The IAM role does not have s3:ListBucket permission.
AnswerC

The policy restricts writes to 'captures/' prefix, but the endpoint may use a different prefix.

Why this answer

The IAM role attached to the SageMaker endpoint must have write permissions to the exact S3 prefix where data capture is configured. The policy shown likely grants access to a broader bucket or a different prefix, but not the specific path (e.g., s3://bucket-name/prefix/) that the endpoint's DataCaptureConfig specifies. Without s3:PutObject on that exact prefix, the captured data fails to upload silently.

Exam trap

The trap here is that candidates often assume any S3 write permission on the bucket is sufficient, but SageMaker data capture requires explicit permission on the exact prefix path, not just the bucket or a wildcard that doesn't match the configured prefix.

How to eliminate wrong answers

Option A is wrong because if the S3 bucket did not exist, SageMaker would fail at endpoint creation or deployment time, not after a week of operation. Option B is wrong because the question does not mention KMS encryption being enabled on the bucket, and the policy shown does not include kms:Decrypt; if KMS were used, the role would need kms:GenerateDataKey and kms:Decrypt, but the absence of those is not the issue here. Option D is wrong because s3:ListBucket is not required for writing captured data; SageMaker only needs s3:PutObject on the specific prefix, not ListBucket on the bucket.

Full explanation →
20
Multi-Selectmedium

A data scientist is using Amazon SageMaker Feature Store to manage features for a fraud detection model. The model needs to be updated hourly with new features from streaming data, and historical features must be available for training. Which THREE actions are necessary to set up this pipeline? (Choose THREE.)

Select 3 answers
A.Use point-in-time queries from the offline store to retrieve historical feature values for training
B.Use Amazon Kinesis Data Streams to ingest streaming data and write to the feature group
C.Use Amazon SageMaker Data Wrangler to continuously ingest streaming data into the feature group
D.Use Amazon SageMaker Ground Truth to label incoming streaming data
E.Create a feature group with both online and offline store enabled
AnswersA, B, E

Point-in-time queries allow reconstructing feature values as they were at a specific time.

Why this answer

To ingest streaming features, use Kinesis Data Streams/Firehose. To store them, create a feature group with both online and offline stores. To retrieve historical data, use point-in-time queries from the offline store.

The online store alone cannot serve historical queries. Ground Truth is for labeling, not feature ingestion. Data Wrangler is for preparation, not ingestion.

Full explanation →
21
MCQeasy

A company has a model that receives low traffic but needs to handle sudden spikes. Which deployment option is most cost-effective?

A.SageMaker Serverless Inference
B.SageMaker Real-Time Endpoint with Auto Scaling
C.SageMaker Multi-Model Endpoint
D.SageMaker Batch Transform
AnswerA

Serverless scales to zero during idle periods and handles spikes, minimizing cost.

Why this answer

SageMaker Serverless Inference is the most cost-effective option for low-traffic models with sudden spikes because it automatically scales to zero when not in use and scales up instantly to handle bursts, charging only for the compute time consumed per inference request. This eliminates the cost of idle provisioned infrastructure, making it ideal for unpredictable or intermittent traffic patterns.

Exam trap

AWS often tests the misconception that auto-scaling (Option B) is the most cost-effective for spikes, but the trap is that auto-scaling still requires a baseline of provisioned instances that incur cost even when idle, whereas serverless inference scales to zero and charges only for active compute time.

How to eliminate wrong answers

Option B (SageMaker Real-Time Endpoint with Auto Scaling) is wrong because it requires always-on provisioned instances, incurring costs even during idle periods, and auto-scaling has a lag that may not handle sudden spikes as quickly as serverless. Option C (SageMaker Multi-Model Endpoint) is wrong because it still uses provisioned instances that run continuously, and while it shares resources across models, it does not scale to zero or handle sudden spikes without pre-provisioned capacity. Option D (SageMaker Batch Transform) is wrong because it is designed for offline, asynchronous batch processing on a complete dataset, not for real-time inference with low latency or handling live traffic spikes.

Full explanation →
22
MCQmedium

A data engineer needs to ingest streaming clickstream data from a website into an S3 data lake for ML training, with the ability to run real-time aggregations before storage. Which combination of AWS services meets these requirements?

A.Amazon Kinesis Data Streams → Kinesis Data Analytics → Kinesis Data Firehose → S3
B.Amazon Kinesis Data Streams → Amazon SageMaker Data Wrangler → S3
C.Amazon Kinesis Data Firehose → AWS Glue ETL → S3
D.Amazon SQS → AWS Lambda → S3
AnswerA

Correct flow for real-time streaming, aggregations, and delivery to S3.

Why this answer

It provides a complete pipeline for both real-time aggregation and durable storage. Kinesis Data Streams ingests the streaming clickstream data, Kinesis Data Analytics performs real-time SQL or Apache Flink-based aggregations on the stream, and Kinesis Data Firehose delivers the aggregated results to S3 with optional data transformation and buffering, meeting the requirements for ML training.

Exam trap

The trap here is that candidates may confuse Kinesis Data Firehose's ability to invoke Lambda for simple transformations with the need for real-time aggregations, overlooking that Kinesis Data Analytics is the only service that provides continuous, stateful stream processing required for real-time aggregations before storage.

How to eliminate wrong answers

Option B is wrong because Amazon SageMaker Data Wrangler is a tool for data preparation and feature engineering in batch mode, not for real-time streaming ingestion or aggregations; it cannot process a live Kinesis stream directly. Option C is wrong because Kinesis Data Firehose can ingest streaming data but lacks native real-time analytics capabilities—it can only buffer and deliver data, and AWS Glue ETL is a batch-oriented service, not suitable for real-time aggregations. Option D is wrong because Amazon SQS is a message queue for decoupling components, not designed for high-throughput streaming data, and AWS Lambda has a maximum execution time of 15 minutes and is not optimized for continuous real-time aggregations on clickstream data.

Full explanation →
23
MCQhard

A machine learning team is training a large natural language processing model on Amazon SageMaker using the SageMaker Hugging Face container. The training job runs on multiple instances and uses Managed Spot Training to reduce costs. However, the job frequently gets interrupted by Spot interruptions, causing long training times. What should the team do to mitigate this issue?

A.Use a reserved capacity with Savings Plans
B.Use a larger instance type to finish faster
C.Enable checkpointing and increase the number of save intervals
D.Disable Managed Spot Training and use On-Demand instances
AnswerC

Checkpointing saves model state so training can resume after a Spot interruption; more frequent saves reduce the amount of work lost.

Why this answer

Enabling checkpointing and saving intermediate model states at appropriate intervals allows the training job to resume from the last checkpoint after a Spot interruption, significantly reducing wasted time. Increasing save intervals means more frequent saving, which reduces work lost. Reserved capacity does not help with interruptions; using larger instances doesn't prevent interruptions; disabling Spot increases cost.

Full explanation →
24
MCQhard

A data engineer is processing a large dataset in Amazon S3 with AWS Glue ETL. The dataset contains timestamps in multiple time zones. The engineer needs to create a feature for hour-of-day consistent across all records. Which approach ensures correctness?

A.Convert all timestamps to UTC in the ETL script using Spark's from_utc_timestamp
B.Use AWS Glue's built-in transform to parse timestamps with timezone offsets
C.Use Python's datetime.strptime with tzlocal
D.Convert all timestamps to UTC during the ETL process, then extract hour
AnswerD

Normalizing to UTC before extracting hour guarantees consistency across time zones.

Why this answer

Converting all timestamps to UTC during the ETL process ensures a consistent time zone reference before extracting the hour-of-day feature. This avoids ambiguity from mixed time zones and aligns with best practices for machine learning feature engineering. AWS Glue ETL with Apache Spark provides built-in functions like `to_utc_timestamp()` to perform this conversion reliably.

Exam trap

AWS often tests the confusion between `from_utc_timestamp` and `to_utc_timestamp` in Spark, where candidates mistakenly choose the function that converts away from UTC instead of to UTC, leading to incorrect hour-of-day features.

How to eliminate wrong answers

Option A is wrong because `from_utc_timestamp` in Spark converts a UTC timestamp to a specified time zone, not to UTC, which would introduce inconsistency. Option B is wrong because AWS Glue's built-in transforms (e.g., `ResolveChoice`) do not provide a dedicated transform to parse timestamps with timezone offsets and normalize them to a single time zone; they only handle schema resolution. Option C is wrong because Python's `datetime.strptime` with `tzlocal` relies on the local system time zone, which is not deterministic in a distributed ETL environment like AWS Glue and can vary across workers, leading to incorrect hour extraction.

Full explanation →
25
MCQeasy

A data scientist notices that a SageMaker endpoint is returning HTTP 5XX errors under high load. The endpoint uses a single ml.m5.large instance. The team wants to reduce these errors without changing the instance type. What is the most cost-effective step?

A.Increase the endpoint's invocation timeout to 120 seconds
B.Deploy the model on a SageMaker batch transform job
C.Configure auto-scaling for the endpoint with a target tracking policy
D.Create a new endpoint with multiple instances and use weighted routing
AnswerC

Auto-scaling adds instances during high load and removes them when traffic subsides, reducing errors cost-effectively.

Why this answer

Configuring auto-scaling with a target tracking policy allows the endpoint to dynamically add more instances under high load, distributing the traffic and reducing HTTP 5XX errors. Since the team cannot change the instance type, scaling out is the most cost-effective way to handle increased demand, as it only adds capacity when needed and avoids over-provisioning.

Exam trap

The trap here is that candidates may think increasing the timeout (Option A) or using batch transform (Option B) can solve real-time load issues, but these options do not address the fundamental need for horizontal scaling under high concurrency.

How to eliminate wrong answers

Option A is wrong because increasing the invocation timeout to 120 seconds does not address the root cause of 5XX errors under high load; it merely extends the time the endpoint has to respond, which can lead to increased latency and potential timeouts, but does not prevent the endpoint from being overwhelmed. Option B is wrong because deploying the model on a SageMaker batch transform job is for offline, asynchronous inference on a static dataset, not for real-time serving; it cannot replace a real-time endpoint that needs to handle live traffic. Option D is wrong because creating a new endpoint with multiple instances and weighted routing adds cost by requiring manual management and does not automatically scale based on load; it is less cost-effective than auto-scaling, which adjusts capacity dynamically.

Full explanation →
26
MCQhard

A company uses SageMaker Model Monitor for data quality. They notice that monitoring jobs are failing intermittently with constraint violations. Upon review, they see that some features have different data types in production compared to the baseline (e.g., string instead of integer). Which type of drift is this?

A.Schema drift
B.Concept drift
C.Statistical drift
D.Bias drift
AnswerA

Schema drift involves changes in the schema, such as data type mismatches, new or missing columns.

Why this answer

Schema drift occurs when the structure or data types of features in production data differ from the baseline used during model training. In this scenario, a feature that was an integer in the baseline is now a string in production, which is a classic example of schema drift. SageMaker Model Monitor detects this by comparing the inferred schema of production data against the baseline schema, flagging any type mismatches as constraint violations.

Exam trap

The trap here is that candidates may confuse schema drift with statistical drift, thinking any change in feature values qualifies as statistical drift, but the key differentiator is that schema drift specifically involves changes in data type or structure, not just distributional shifts.

How to eliminate wrong answers

Option B is wrong because concept drift refers to changes in the underlying relationship between features and the target variable, not changes in data types or schema. Option C is wrong because statistical drift (e.g., distribution shift) involves changes in the statistical properties of features (like mean or variance) while data types remain consistent. Option D is wrong because bias drift relates to changes in model fairness metrics over time, such as disparate impact, not to data type mismatches.

Full explanation →
27
MCQmedium

A company uses SageMaker Clarify to detect bias during training. They want to ensure that the trained model does not rely on a sensitive attribute like gender. Which Clarify feature should they configure?

A.Clarify bias config with post-training bias metrics
B.Clarify with SageMaker Model Monitor
C.SHAP analysis
D.Clarify processing job with pre-training bias metrics
E.Bias report generation
AnswerA

Post-training bias metrics can be configured to check for bias in model predictions.

Full explanation →
28
MCQhard

Refer to the exhibit. A SageMaker Pipeline fails with 'Invalid output reference' at the TrainingStep. What is the most likely cause?

A.The TuningStep output name is misspelled
B.The pipeline role lacks permissions
C.The TrainingStep expects a single artifact but TuningStep produces multiple
D.The instance type is incompatible
AnswerC

Tuning step outputs multiple models; directly passing to training step causes ambiguity.

Why this answer

In SageMaker Pipelines, a `TrainingStep` that expects a single artifact as input will fail with 'Invalid output reference' if the preceding `TuningStep` produces multiple artifacts (e.g., from multiple training jobs). The pipeline cannot resolve which specific artifact to pass, causing the error.

Exam trap

AWS often tests the subtle distinction between output reference errors caused by naming mismatches versus those caused by cardinality mismatches, where candidates mistakenly focus on permissions or spelling instead of the pipeline's inability to handle multiple artifacts.

How to eliminate wrong answers

Option A is wrong because a misspelled output name would cause a different error (e.g., 'Property not found'), not 'Invalid output reference', and the pipeline would fail at the step referencing the name, not at the TrainingStep. Option B is wrong because insufficient pipeline role permissions typically result in an 'AccessDenied' or 'UnauthorizedOperation' error, not 'Invalid output reference'. Option D is wrong because an incompatible instance type causes an 'InsufficientInstanceCapacity' or 'ResourceLimitExceeded' error during step execution, not an output reference validation error.

Full explanation →
29
MCQmedium

A team is training a PyTorch model using SageMaker with a custom training script. They want to track hyperparameters and metrics across multiple experiments. Which service should they use?

A.SageMaker Clarify
B.SageMaker Experiments
C.SageMaker Model Monitor
D.SageMaker Debugger
AnswerB

Experiments is designed to track and compare machine learning runs.

Why this answer

SageMaker Experiments is the native service for tracking machine learning experiments, including hyperparameters and metrics. SageMaker Debugger is for debugging training jobs. SageMaker Model Monitor is for inference monitoring.

SageMaker Clarify is for bias analysis.

Full explanation →
30
Multi-Selecthard

A machine learning engineer is deploying a custom PyTorch model to a SageMaker endpoint for real-time inference. The model requires GPU acceleration. The engineer wants to minimize latency and cost. Which THREE actions should the engineer take? (Select THREE.)

Select 3 answers
A.Use an ml.c5.2xlarge instance with CPU only
B.Use SageMaker Batch Transform for inference
C.Compile the model with SageMaker Neo
D.Use SageMaker Elastic Inference (EI) instead of a full GPU instance
E.Use an ml.p3.2xlarge instance for the endpoint
AnswersC, D, E

Neo optimizes the model for faster inference on target hardware.

Why this answer

SageMaker Neo compiles the PyTorch model into an optimized runtime binary that is specifically tuned for the target hardware (e.g., GPU instances like ml.p3). This reduces inference latency by applying graph-level optimizations, operator fusion, and memory layout transformations without changing the model's accuracy, while also lowering compute resource usage and cost.

Exam trap

AWS often tests the distinction between real-time vs. batch inference and the trade-off between full GPU instances and lighter acceleration options like Elastic Inference, expecting candidates to recognize that Batch Transform is not suitable for low-latency endpoints and that CPU-only instances cannot meet GPU requirements.

Full explanation →
31
MCQeasy

A data scientist wants to track the lineage of models, datasets, and training jobs in SageMaker. Which SageMaker feature should they use to capture these relationships as artifacts and actions?

A.SageMaker Model Registry
B.SageMaker Experiments
C.SageMaker ML Lineage Tracking
D.SageMaker Feature Store
AnswerC

Lineage Tracking explicitly models artifacts, actions, and contexts to provide end-to-end reproducibility.

Why this answer

SageMaker ML Lineage Tracking creates a graph of artifacts (datasets, models) and actions (training jobs, endpoints) to track the provenance of ML workflows.

Full explanation →
32
MCQmedium

A machine learning engineer sees the above error in Amazon CloudWatch Logs for a SageMaker endpoint. What is the most likely cause?

A.The model file is corrupted during deployment.
B.The data capture configuration is incorrectly set to capture only the response body.
C.The inference code in the Docker container outputs a different response format than expected by the endpoint.
D.The endpoint is overloaded and dropping requests.
AnswerC

The inference script (e.g., in a SageMaker inference container) must output the exact JSON structure the endpoint expects. This error shows a mismatch.

Why this answer

The error in CloudWatch Logs indicates that the SageMaker endpoint received a response from the inference container that does not match the expected format. SageMaker endpoints require the container to output a response body in a specific format (e.g., JSON or CSV) as defined by the model's Accept header or the endpoint's serialization configuration. If the inference code returns a malformed or unexpected response (e.g., raw bytes, incorrect JSON structure, or missing fields), the endpoint will fail to parse it and log an error.

This is the most direct cause of the observed error.

Exam trap

The trap here is that candidates often confuse data capture configuration (which only logs payloads) with the actual response format validation performed by the SageMaker endpoint proxy, leading them to incorrectly select Option B.

How to eliminate wrong answers

Option A is wrong because a corrupted model file during deployment would typically cause a model loading failure or a 500 error during invocation, not a response format mismatch error in CloudWatch Logs. Option B is wrong because data capture configuration only affects whether request/response payloads are stored in S3, not the format of the response returned by the container to the endpoint. Option D is wrong because an overloaded endpoint would result in throttling errors (HTTP 429) or increased latency, not a response format parsing error.

Full explanation →
33
Multi-Selectmedium

A data engineer is preparing a dataset for a classification model. The dataset contains duplicate rows. Which TWO approaches are appropriate to handle duplicates in AWS? (Choose 2.)

Select 2 answers
A.Use the RemoveDuplicates built-in feature in Amazon QuickSight
B.Use the DistinctRows transform in Amazon SageMaker Data Wrangler
C.Use the DropDuplicates transform in AWS Glue
D.Use a SQL query with SELECT DISTINCT in Amazon Athena to create a deduplicated table
E.Use the pandas drop_duplicates() method in a SageMaker notebook
AnswersC, D

Glue's DropDuplicates removes duplicate rows in a distributed manner.

Why this answer

AWS Glue provides a DropDuplicates transform within its DynamicFrame API, which is designed for ETL operations on large-scale datasets. This transform efficiently removes duplicate rows by comparing all columns or a specified subset, making it a native and scalable solution for deduplication in AWS.

Exam trap

The trap here is that candidates confuse the existence of a feature name (e.g., 'DistinctRows' in Data Wrangler) with the actual available transform, or they incorrectly assume that any Python code in a SageMaker notebook qualifies as an 'AWS approach' rather than a custom script.

Full explanation →
34
MCQeasy

A data scientist needs to label a large dataset of product images for a classification model. They want to reduce labeling costs by prioritizing uncertain samples. Which Amazon SageMaker Ground Truth feature should they use?

A.Pre-built worker templates
B.Active learning
C.Consolidated labeling
D.Automated data labeling
AnswerB

Active learning selects the most informative samples for labeling.

Why this answer

Active learning in Amazon SageMaker Ground Truth automatically selects the most uncertain or informative samples from the unlabeled dataset and sends them to human annotators. This prioritization reduces labeling costs by focusing budget on the samples that will most improve model performance, rather than labeling all data indiscriminately.

Exam trap

The trap here is confusing 'active learning' with 'automated data labeling' — candidates often think automated labeling reduces costs by skipping humans entirely, but active learning specifically reduces costs by selectively using humans only on uncertain samples.

How to eliminate wrong answers

Option A is wrong because pre-built worker templates are UI frameworks for custom labeling workflows, not a mechanism to prioritize uncertain samples. Option C is wrong because consolidated labeling refers to merging multiple annotations for the same data point to produce a ground truth label, not selecting which samples to label. Option D is wrong because automated data labeling uses a trained model to label data without human review, which does not involve prioritizing uncertain samples for human annotation.

Full explanation →
35
Multi-Selecteasy

A data science team wants to automate the retraining of a model when data drift is detected. Which TWO AWS services should they use in combination to achieve this? (Choose TWO)

Select 2 answers
A.AWS Cloud9
B.Amazon DynamoDB
C.SageMaker Model Monitor
D.AWS Lambda
E.Amazon Kinesis Data Analytics
AnswersC, D

Detects drift and publishes metrics for alarms.

Why this answer

SageMaker Model Monitor detects data drift and can publish to CloudWatch Metrics. CloudWatch Alarms can trigger an SNS topic, which invokes a Lambda function that starts a SageMaker Pipeline for retraining.

Full explanation →
36
Multi-Selectmedium

A team wants to deploy a new model using a canary deployment strategy on SageMaker. Which TWO configurations are necessary? (Choose two.)

Select 2 answers
A.Create a CloudWatch alarm to automatically rollback
B.Set the initial traffic distribution (e.g., 90% old, 10% new)
C.Enable data capture on the endpoint
D.Create a new endpoint configuration with two production variants, each pointing to a different model
E.Use SageMaker Model Registry to approve the new model
AnswersB, D

Initial weights define the canary traffic percentage.

Why this answer

A canary deployment requires two production variants (old and new) with traffic distribution. Gradual traffic shifting can be achieved by updating the endpoint's variant weights over time.

Full explanation →
37
MCQeasy

A data scientist needs to split a time-series dataset into training and testing sets while avoiding data leakage from future values. Which splitting technique should the data scientist use?

A.Random shuffle followed by a 80/20 split
B.K-fold cross-validation with shuffled folds
C.Stratified sampling based on the target variable
D.Time-series split (walk-forward validation)
AnswerD

Respects temporal order: trains on past, tests on future.

Why this answer

Time-series split (walk-forward validation) ensures that the training set only contains past data relative to the test set, preventing leakage. Stratified sampling and random shuffle are not appropriate for time series because they ignore temporal order. K-fold cross-validation without adjustments will also leak future information.

Full explanation →
38
Multi-Selectmedium

A machine learning team is preparing a dataset for a text classification model. The dataset contains customer reviews. The team wants to convert the text into numerical features while reducing the impact of common words and capturing word importance. Which THREE techniques should the team apply? (Select THREE.)

Select 3 answers
A.Tokenization
B.TF-IDF
C.Word embeddings
D.One-hot encoding
E.Stop-word removal
AnswersA, B, E

Splits text into tokens (words or phrases) for further processing.

Why this answer

Tokenization, stop-word removal, and TF-IDF are standard preprocessing steps for text classification. Word embeddings are an alternative to TF-IDF but not a combination; one-hot encoding is not suitable for text.

Full explanation →
39
Multi-Selecteasy

A company is adopting Amazon SageMaker Pipelines to automate their ML workflow. They want to choose three key benefits that SageMaker Pipelines provides over traditional manual scripts and ad-hoc steps. Which THREE benefits are correct?

Select 3 answers
A.Model lineage tracking from raw data to trained model artifacts.
B.Automated deployment of models to endpoints upon pipeline completion.
C.Event-driven execution when new data arrives in S3.
D.Automatic scaling of compute resources based on data volume.
E.Reproducible execution through a directed acyclic graph (DAG) of steps with re-run capabilities.
AnswersA, C, E

Pipelines automatically capture lineage metadata.

Why this answer

SageMaker Pipelines automatically captures and tracks the lineage of every artifact, including datasets, processing jobs, training jobs, and model versions. This lineage is stored in SageMaker's metadata store, enabling full traceability from raw data to the final model artifact, which is critical for auditability and compliance in ML workflows.

Exam trap

AWS often tests the distinction between orchestration features (like SageMaker Pipelines) and infrastructure management features (like auto-scaling), leading candidates to confuse pipeline benefits with SageMaker's broader managed service capabilities.

Full explanation →
40
MCQmedium

A company is using SageMaker Model Registry to manage model versions. They want to automatically deploy the latest approved model to production after retraining. Which approach is best?

A.Manually deploy the approved model using the SageMaker console
B.Use AWS Lambda to update the endpoint whenever a new model version is created
C.Create a SageMaker Pipeline that includes a model approval step and deployment step
D.Schedule a CloudWatch Event to invoke a SageMaker update endpoint API daily
AnswerC

SageMaker Pipelines can model the entire workflow including conditional deployment based on approval.

Why this answer

A SageMaker Pipeline can orchestrate the entire workflow from retraining to deployment, including a model approval step that gates deployment to production only when the model is approved. This automates the process end-to-end, ensuring that only approved models are deployed, which aligns with the requirement to automatically deploy the latest approved model after retraining.

Exam trap

The trap here is that candidates may choose Option B because it sounds automated, but they overlook the critical requirement for model approval before deployment, which Lambda alone cannot enforce without additional logic.

How to eliminate wrong answers

Option A is wrong because manual deployment via the SageMaker console does not automate the process and violates the requirement for automatic deployment after retraining. Option B is wrong because using AWS Lambda to update the endpoint whenever a new model version is created would deploy models without waiting for approval, bypassing the model approval step and potentially deploying unapproved models. Option D is wrong because scheduling a CloudWatch Event to invoke a SageMaker update endpoint API daily does not tie deployment to model approval or retraining events; it deploys on a fixed schedule regardless of model status.

Full explanation →
41
MCQmedium

A data scientist needs to ensure that the same train/test split is used across multiple experiments for reproducibility in SageMaker. Which approach should they take?

A.Use the same SageMaker instance type
B.Use the same hyperparameter values
C.Use the same dataset version
D.Set a random seed in the training script
AnswerD

Correct: Setting a random seed ensures reproducibility of random operations like data splits.

Why this answer

Setting a random seed in the training script ensures that the pseudo-random number generator used for splitting the dataset produces the same sequence of random indices across runs. This guarantees an identical train/test split regardless of instance type, hyperparameters, or dataset version, which is essential for reproducibility in SageMaker experiments.

Exam trap

The trap here is that candidates often confuse environmental consistency (instance type, dataset version) with algorithmic determinism, overlooking that reproducibility of data splits requires explicit control of the random seed in code.

How to eliminate wrong answers

Option A is wrong because the SageMaker instance type affects compute performance and memory, not the randomness of data splits; using the same instance type does not control the random seed. Option B is wrong because hyperparameter values influence model training behavior, not the deterministic splitting of data; they do not ensure the same train/test split. Option C is wrong because using the same dataset version ensures the data is identical, but without a fixed random seed, the split can still vary across runs due to different random number generator states.

Full explanation →
42
Multi-Selecthard

A company is using an AWS Step Functions state machine to orchestrate a multi-step ML deployment. The workflow includes: training a model, evaluating it, registering the model, and deploying to a staging endpoint. They need to implement an approval gate before deploying to production. Which THREE components are necessary to achieve this? (Choose three.)

Select 3 answers
A.An AWS CodePipeline pipeline with approval stage
B.A task in the state machine that pauses and waits for manual approval via SNS or Lambda
C.Model Registry to store the approved model version after evaluation
D.An Amazon SNS topic for notification of approval status
E.An API call to SageMaker to create or update the production endpoint
AnswersB, C, E

Step Functions can use 'Wait for Task Token' to implement human approval.

Why this answer

Step Functions can use a task with a callback pattern (`.waitForTaskToken`) to pause the workflow and wait for external manual approval. When combined with an SNS topic or Lambda function that sends a task success or failure signal back to Step Functions, this creates a reliable approval gate. This pattern allows the state machine to halt execution until a human approves or rejects the deployment, which is essential for production deployment control.

Exam trap

AWS often tests the distinction between a notification-only service (like SNS) and a service that can actively pause and resume a workflow (like Step Functions with task tokens), leading candidates to mistakenly select SNS as a sufficient approval gate component.

Full explanation →
43
MCQeasy

A company stores its model training data in Amazon S3. To meet compliance requirements, all data in transit between the S3 bucket and SageMaker must be encrypted. What should the company enforce?

A.Enable S3 versioning
B.Enable S3 access logging
C.Enforce HTTPS for all S3 access
D.Use S3 server-side encryption (SSE-S3)
AnswerC

HTTPS provides encryption in transit.

Why this answer

Enforcing HTTPS for all S3 access ensures that data in transit between the S3 bucket and SageMaker is encrypted using TLS. This meets the compliance requirement for encrypting data in transit, as HTTPS uses TLS to protect data as it travels over the network.

Exam trap

The trap here is that candidates often confuse encryption at rest (SSE-S3) with encryption in transit (HTTPS/TLS), leading them to select Option D when the question explicitly asks about data in transit.

How to eliminate wrong answers

Option A is wrong because S3 versioning is a data protection feature that preserves, retrieves, and restores every version of an object stored in a bucket; it does not encrypt data in transit. Option B is wrong because S3 access logging provides detailed records of requests made to a bucket for auditing purposes, but it does not enforce or provide encryption for data in transit. Option D is wrong because S3 server-side encryption (SSE-S3) encrypts data at rest within S3, not data in transit between S3 and SageMaker.

Full explanation →
44
MCQhard

A company is running multiple SageMaker endpoints for different models, each serving a separate business unit. The total cost is growing rapidly. The ML engineering team wants to reduce costs without sacrificing performance or isolation. They are considering either consolidating models into a Multi-Model Endpoint (MME) or onto a Multi-Container Endpoint (MCE). The models vary in size from 100 MB to 5 GB, and traffic patterns are unpredictable. Which recommendation is MOST appropriate?

A.Use a Multi-Model Endpoint with a single large instance type to host all models, and enable SageMaker inference pipelines if pre-processing is needed.
B.Use Multi-Container Endpoints to deploy multiple models on a single instance.
C.Migrate all models to AWS Lambda functions for serverless inference.
D.Keep individual endpoints but switch to Graviton-based instances for cost savings.
AnswerA

Multi-Model Endpoints load models on demand, allowing many small models to share an instance, reducing cost. They support isolation through model directories and can be combined with inference pipelines.

Why this answer

A Multi-Model Endpoint (MME) is the most appropriate choice because it allows hosting multiple models on a single instance while keeping them isolated in separate memory spaces, which reduces cost by sharing the underlying infrastructure. MME dynamically loads and unloads models based on traffic, making it ideal for unpredictable patterns and model sizes ranging from 100 MB to 5 GB. Inference pipelines can be added for pre-processing without breaking the multi-model architecture, preserving performance and isolation.

Exam trap

The trap here is that candidates confuse Multi-Model Endpoints with Multi-Container Endpoints, assuming both provide similar isolation and cost benefits, but MCE is designed for microservices-like architectures where all containers must be active, not for dynamic model loading based on traffic.

How to eliminate wrong answers

Option B is wrong because Multi-Container Endpoints (MCE) run multiple containers on the same instance but all containers are always active, which does not optimize for unpredictable traffic and can lead to higher memory usage and cost. Option C is wrong because AWS Lambda has a maximum deployment package size of 250 MB (unzipped, including layers) and a 15-minute timeout, making it unsuitable for models up to 5 GB and real-time inference with unpredictable latency. Option D is wrong because keeping individual endpoints, even with Graviton instances, does not address the core issue of cost from multiple endpoints; it only reduces per-instance cost marginally, while consolidation is needed for significant savings.

Full explanation →
45
MCQhard

A company uses SageMaker Autopilot to build a binary classification model. The generated leaderboard shows an ensemble model as the best candidate. The team needs a model that can be deployed for real-time inference with latency < 10ms. What should they do?

A.Use SageMaker Inference Recommender to profile the ensemble model and optimize it
B.Deploy the ensemble model as a SageMaker endpoint; ensemble models are optimized for low latency
C.Retrain the ensemble model with fewer base estimators using a custom container
D.Select the best single model from the leaderboard (non-ensemble candidate) and deploy it
AnswerD

Single models usually have lower latency; evaluate if it meets the latency requirement.

Why this answer

Autopilot ensemble models may have high latency due to combining multiple models. The team should evaluate non-ensemble candidates (single model) from the leaderboard to meet latency requirements.

Full explanation →
46
MCQhard

In SageMaker Data Wrangler, you have a flow that imports data from Amazon S3 and needs to join it with a table from Amazon Redshift. The data volumes are large (hundreds of GB). Which approach is most efficient within Data Wrangler?

A.Use Amazon Athena federated query to join in place and import the result
B.Export the Redshift table to S3 as Parquet, then import both datasets into Data Wrangler and join
C.Use AWS Glue to join the datasets and output to S3, then import the joined result into Data Wrangler
D.Import the Redshift table directly using a Data Wrangler source step and apply a join transform
AnswerD

Data Wrangler can connect to Redshift natively and perform joins efficiently.

Why this answer

SageMaker Data Wrangler natively supports Amazon Redshift as a source via a direct connection, allowing you to import the Redshift table as a source step and then apply a join transform within the same visual flow. This approach avoids unnecessary data movement or intermediate exports, which is critical for hundreds of GB of data, as it leverages Data Wrangler's optimized in-memory and Spark-based processing to perform the join efficiently.

Exam trap

The trap here is that candidates assume large-scale joins must be offloaded to external services like AWS Glue or Athena, but Data Wrangler's native Redshift source and join transform are designed for this exact use case, making the direct approach the most efficient.

How to eliminate wrong answers

Option A is wrong because Amazon Athena federated query is designed for querying across data sources, but it does not integrate directly as a join step within Data Wrangler; you would need to export the result to S3 and re-import, adding latency and complexity. Option B is wrong because exporting the Redshift table to S3 as Parquet introduces an extra data movement step that is inefficient for large volumes, and Data Wrangler can directly import from Redshift without this intermediate export. Option C is wrong because using AWS Glue to join the datasets and output to S3 adds an unnecessary orchestration layer and data duplication, whereas Data Wrangler can perform the join natively without external services.

Full explanation →
47
MCQmedium

A machine learning team is building a fraud detection model. They have a dataset with a categorical feature 'merchant_id' that has over 10,000 unique values. Which feature engineering technique should they apply to 'merchant_id' to reduce dimensionality while retaining predictive power?

A.One-hot encoding
B.Target encoding
C.Ordinal encoding
D.Label encoding
AnswerB

Encodes based on target mean, compact and predictive for high-cardinality features.

Why this answer

Target encoding replaces each category with the mean target value, effectively encoding high-cardinality features into a single numeric column while preserving correlation with the target. One-hot encoding would explode dimensionality; label encoding imposes ordinality; ordinal encoding assumes order.

Full explanation →
48
MCQeasy

A company wants to automate remediation when a SageMaker endpoint's latency exceeds a threshold for more than 5 minutes. The team needs to be notified and a Lambda function should be invoked to scale up the endpoint. Which combination of services should be used?

A.CloudWatch Alarm → SNS topic → Lambda function
B.EventBridge rule to trigger Lambda
C.CloudWatch Logs subscription filter → Lambda function
D.SageMaker Model Monitor → Lambda function
AnswerA

CloudWatch Alarms can publish to an SNS topic which can invoke a Lambda function for automated scaling.

Why this answer

CloudWatch Alarms monitor metrics and trigger actions. SNS can notify and invoke Lambda for automated remediation. EventBridge is used for scheduled events, not direct alarm actions.

Full explanation →
49
MCQhard

A data scientist is preparing text data for a sentiment analysis model. The dataset contains customer reviews with a high proportion of misspellings, slang, and emojis. The scientist wants to preprocess the text to reduce noise while preserving semantic meaning. Which combination of preprocessing steps is MOST effective?

A.Removing emojis, applying lemmatization, and converting to uppercase.
B.Lowercasing, removing punctuation and stop words, and applying stemming.
C.Tokenization, removing stop words, and applying word embeddings trained on general text.
D.Lowercasing, removing punctuation, and applying TF-IDF vectorization.
AnswerD

Lowercasing and punctuation removal reduce noise; TF-IDF vectorization captures word importance and handles variability without over-normalizing.

Why this answer

Converting to lowercase, removing punctuation, and applying TF-IDF (which includes tokenization) is a standard approach that handles noise while preserving meaning. Stemming may over-normalize, and removing stop words is useful but not essential. The correct combination balances noise reduction and meaning preservation.

Full explanation →
50
MCQhard

A data scientist is preparing a large dataset (50 GB) for training a TensorFlow model on SageMaker. The dataset consists of many small CSV files. Training is slow due to I/O bottlenecks. Which data preparation strategy most effectively accelerates training?

A.Convert the dataset to TFRecord format and use tf.data pipeline with prefetching
B.Convert the dataset to Parquet format and use Apache Arrow for loading
C.Compress the CSV files and decompress during data loading
D.Use a larger instance type with more vCPUs
AnswerA

TFRecord combines many records into a few large files, and prefetching improves data pipeline efficiency.

Why this answer

TFRecord format stores data in a binary, row-oriented format that TensorFlow's tf.data API can read efficiently, especially with prefetching to overlap data loading with model computation. This eliminates the per-file open/parse overhead of many small CSV files, which is the primary cause of I/O bottlenecks in this scenario.

Exam trap

The trap here is that candidates often choose larger instances (Option D) as a brute-force fix, failing to recognize that the root cause is the small-file I/O pattern, which requires a format change (TFRecord) rather than more compute resources.

How to eliminate wrong answers

Option B is wrong because Parquet is a columnar storage format optimized for analytical queries and selective column reads, not for sequential row-by-row training loops typical in deep learning; Apache Arrow adds overhead without solving the small-file problem. Option C is wrong because compressing CSV files reduces storage size but increases CPU load during decompression, often worsening I/O bottlenecks due to the many small files still requiring individual decompression. Option D is wrong because increasing vCPUs does not fix the fundamental I/O bottleneck caused by many small files; it may even exacerbate contention on shared storage without addressing the file access pattern.

Full explanation →
51
Multi-Selectmedium

A data scientist is using SageMaker Autopilot for a regression problem. They want to see which data preprocessing steps Autopilot applied. Which TWO sources can they use to find this information?

Select 2 answers
A.Candidate definition notebook
B.Model leaderboard
C.Autopilot job description in AWS CloudTrail
D.Data exploration report
E.Explainability report
AnswersA, D

Contains the generated code for data preprocessing and model training, showing the exact steps Autopilot applied.

Why this answer

The two sources that show the data preprocessing steps applied by SageMaker Autopilot are the candidate definition notebook and the data exploration report. The candidate definition notebook contains the generated Python code for the entire pipeline, including all preprocessing transformations. The data exploration report provides a summary of the data and includes information about the transformations that were automatically applied.

The model leaderboard only lists the performance metrics of the trials, not the preprocessing steps. The Autopilot job description in AWS CloudTrail logs the API calls made, but does not capture the preprocessing steps. The explainability report shows feature importance values, not the preprocessing steps.

Full explanation →
52
MCQhard

A data scientist is using SageMaker built-in Image Classification algorithm on a dataset with 1000 classes. The training is very slow. They want to speed it up without sacrificing accuracy. Which instance type and training configuration is MOST appropriate?

A.Use ml.trn1.32xlarge instances with data parallelism
B.Use ml.m5.24xlarge instances with data parallelism
C.Use ml.c5.18xlarge instances with model parallelism
D.Use ml.p3.16xlarge instances with data parallelism
AnswerD

ml.p3.16xlarge has powerful GPUs and data parallelism can speed up training.

Why this answer

For image classification, GPU instances like ml.p3 or ml.g4dn are suitable. ml.p3.16xlarge provides 8 V100 GPUs. ml.m5 is CPU only. ml.c5 is CPU. ml.trn1 is for training, but for this built-in algorithm, GPU instances are standard.

Full explanation →
53
MCQeasy

A data scientist wants to version and manage trained models, require approval before deployment, and enable cross-account deployment. Which SageMaker feature provides these capabilities?

A.SageMaker Neo
B.SageMaker Pipelines
C.Amazon Elastic Inference
D.SageMaker Model Registry
AnswerD

Why this answer

SageMaker Model Registry is the correct choice because it provides a centralized catalog for versioning trained models, supports approval workflows (e.g., pending, approved, rejected) to gate deployment, and enables cross-account deployment by sharing model package ARNs across AWS accounts via AWS Resource Access Manager (RAM) or cross-account IAM roles. This directly satisfies all three requirements: versioning, approval before deployment, and cross-account deployment.

Exam trap

The trap here is that candidates may confuse SageMaker Pipelines (which orchestrates the ML workflow) with Model Registry (which manages model versions and approvals), but Pipelines lacks native versioning and approval gatekeeping, while Model Registry is specifically designed for those governance tasks.

How to eliminate wrong answers

Option A is wrong because SageMaker Neo is a model optimization and compilation service that converts trained models into efficient runtime code for target hardware (e.g., ARM, Intel, NVIDIA), but it does not provide model versioning, approval workflows, or cross-account deployment capabilities. Option B is wrong because SageMaker Pipelines is a CI/CD orchestration service for building, training, and deploying ML pipelines, but it does not natively include a model registry with approval gates or cross-account deployment features; while it can integrate with Model Registry, Pipelines itself does not offer versioning or approval management. Option C is wrong because Amazon Elastic Inference is a service that attaches low-cost GPU-powered inference acceleration to SageMaker endpoints, but it has no role in model versioning, approval workflows, or cross-account deployment.

Full explanation →
54
MCQhard

A company uses SageMaker Pipelines to orchestrate their ML workflow. They notice that if a pipeline step fails due to a transient error (e.g., a brief network issue), the entire pipeline fails and they must manually rerun from the beginning. They want to automatically retry failed steps a few times before failing. What should they do?

A.Use a Lambda function to catch step failures and re-invoke the step
B.Use the CreatePipelineExecution API with a flag to ignore failures
C.Configure a RetryPolicy in the pipeline step definition to specify the number of retry attempts and backoff
D.Use AWS Step Functions to orchestrate the workflow instead of SageMaker Pipelines
AnswerC

SageMaker Pipelines supports RetryPolicy to automatically retry steps on failure.

Why this answer

SageMaker Pipelines supports retry policies for steps. By setting a RetryPolicy in the step definition with a maximum number of retry attempts, the pipeline will automatically retry the step on failure. The other options do not achieve automatic retry within the pipeline: Step Functions would require rebuilding the pipeline, Lambda cannot retry pipeline steps, and CreatePipelineExecution does not handle retries.

Full explanation →
55
MCQmedium

A team is training a large language model on SageMaker using PyTorch with data parallelism. The model is too large to fit on a single GPU. Which distributed training strategy should they use to split the model across multiple GPUs?

A.Model parallelism
B.Tensor parallelism
C.Data parallelism
D.Pipeline parallelism
AnswerA

Model parallelism partitions the model across GPUs, allowing training of models that exceed single GPU memory.

Why this answer

Model parallelism splits the model itself across devices, which is necessary when the model is too large for one GPU. SageMaker's model parallelism library supports this.

Full explanation →
56
MCQmedium

A team is fine-tuning a foundation model using LoRA. They want to reduce memory usage during training. Which technique should they combine LoRA with to further reduce memory?

A.Instruction tuning
B.Pruning
C.RLHF
D.QLoRA
AnswerD

QLoRA quantizes the base model to 4-bit, reducing memory further.

Why this answer

QLoRA combines LoRA with quantization (e.g., 4-bit) to drastically reduce memory. Instruction tuning is a method, not a memory reduction technique. RLHF is a training process.

Pruning reduces model size but is not typically combined with LoRA in this context.

Full explanation →
57
MCQeasy

A data engineer needs to prepare a large dataset for machine learning. The data is stored in an Amazon RDS MySQL database and needs to be transformed and moved to an S3 bucket in Parquet format for use with SageMaker. Which AWS service is most suitable for this extraction, transformation, and loading (ETL) task?

A.Use AWS Glue ETL jobs with PySpark to read from RDS, apply transformations, and write to S3 as Parquet.
B.Use Amazon Athena CTAS statements to copy data from RDS to S3.
C.Use SageMaker Data Wrangler to connect to RDS and export transformed data to S3.
D.Use Amazon EMR with Spark to read from RDS, transform, and write to S3.
AnswerA

Glue is purpose-built for this workload.

Why this answer

AWS Glue ETL jobs with PySpark are the most suitable service for this task because Glue is a fully managed, serverless ETL service that can natively connect to Amazon RDS MySQL via JDBC, apply transformations using PySpark, and write the output directly to S3 in Parquet format. This aligns perfectly with the requirement to extract, transform, and load a large dataset into a machine-learning-ready format without managing infrastructure.

Exam trap

The trap here is that candidates may confuse SageMaker Data Wrangler's ability to connect to RDS and export data with a full ETL capability, overlooking that it is an interactive tool for data preparation within SageMaker Studio rather than a serverless batch ETL service like AWS Glue.

How to eliminate wrong answers

Option B is wrong because Amazon Athena CTAS statements cannot read directly from Amazon RDS; Athena only queries data already in S3 or other data sources via federated queries, but CTAS itself requires the source to be in S3 or a cataloged table, not a live RDS database. Option C is wrong because SageMaker Data Wrangler is designed for interactive data preparation and feature engineering within SageMaker Studio, not for running serverless ETL jobs at scale; it can import data from RDS but lacks the native ability to schedule or run large-scale batch transformations and write to S3 as Parquet without additional infrastructure. Option D is wrong because while Amazon EMR with Spark can technically perform this task, it requires provisioning and managing a cluster, which adds operational overhead; AWS Glue is more suitable as a serverless, cost-effective alternative for this specific ETL workload without the need to manage EC2 instances or cluster lifecycle.

Full explanation →
58
Multi-Selecteasy

A machine learning engineer wants to set up a retraining pipeline that triggers when model quality degrades. Which TWO components are essential for this automated retraining pipeline? (Select TWO)

Select 2 answers
A.CloudWatch Alarm on model quality metric
B.SNS topic to send notification to a Lambda function
C.SageMaker Ground Truth to collect new labels
D.SageMaker Data Wrangler to preprocess data
E.EventBridge rule to schedule retraining weekly
AnswersA, B

The alarm detects when model quality drops below a threshold.

Full explanation →
59
MCQmedium

A company uses Amazon SageMaker Pipelines for automated retraining. The pipeline includes a processing step that runs a Python script. The script uses the boto3 library to call an AWS service, but the calls are being throttled. What is the MOST effective way to address this within the pipeline?

A.Increase the instance count for the processing step to distribute the API calls.
B.Modify the Python script to include retry with exponential backoff when receiving throttling exceptions.
C.Request a service quota increase for the throttling limit.
D.Add a wait step in the pipeline before the processing step.
AnswerB

Standard best practice for handling API throttling.

Why this answer

Implementing retry with exponential backoff directly in the Python script is the most effective way to handle transient throttling exceptions from AWS service API calls. This approach is a best practice for managing service limits within a SageMaker Pipeline processing step, as it allows the script to automatically recover from throttling without modifying the pipeline structure or requiring manual intervention.

Exam trap

The trap here is that candidates often confuse infrastructure-level scaling (increasing instance count) with application-level retry logic, assuming more instances will reduce API call frequency, when in fact each instance independently makes the same number of calls and can still be throttled.

How to eliminate wrong answers

Option A is wrong because increasing the instance count for the processing step distributes the compute load, not the API calls made by the boto3 script; each instance still makes independent API calls to the same service endpoint, so throttling persists. Option C is wrong because requesting a service quota increase is a long-term, manual process that does not address immediate throttling within the pipeline and may not be necessary if the throttling is due to burst limits rather than hard quotas. Option D is wrong because adding a wait step before the processing step introduces a fixed delay that does not adapt to the actual throttling response; it cannot dynamically retry after a throttling exception occurs during the script execution.

Full explanation →
60
MCQeasy

A machine learning engineer wants to monitor a deployed model for data drift. Which SageMaker feature should they use to automatically detect drift in the input data distribution compared to the training data baseline?

A.SageMaker Pipelines
B.SageMaker Model Monitor
C.SageMaker Debugger
D.SageMaker Clarify
AnswerB

SageMaker Model Monitor provides data quality monitoring to detect drift in input data distributions.

Why this answer

SageMaker Model Monitor can be configured to run monitoring jobs that compare live inference data against a baseline created from training data to detect data drift.

Full explanation →
61
MCQhard

A team uses SageMaker Pipelines for CI/CD. The training step fails due to insufficient memory. How to fix without rewriting code?

A.Modify the training algorithm to use less memory
B.Reduce the batch size in the training script
C.Increase the instance type in the pipeline step configuration
D.Enable managed spot training
AnswerC

Changing instance type is a configuration change, not a code change.

Why this answer

SageMaker Pipelines allows you to specify the instance type for each training step in the pipeline definition. By increasing the instance type (e.g., from ml.m5.large to ml.m5.xlarge or a memory-optimized instance like ml.r5.large), you allocate more memory to the training container without modifying the training script or algorithm. This directly resolves the out-of-memory error while preserving the existing code.

Exam trap

AWS often tests the distinction between infrastructure-level fixes (changing instance type in pipeline config) and code-level fixes (modifying script or algorithm), trapping candidates who think reducing batch size or enabling spot instances solves memory issues without considering the 'no code rewrite' constraint.

How to eliminate wrong answers

Option A is wrong because modifying the training algorithm to use less memory requires rewriting code, which violates the constraint of fixing the issue without rewriting code. Option B is wrong because reducing the batch size in the training script also requires modifying the training code, and while it may reduce memory usage, it does not meet the 'without rewriting code' condition. Option D is wrong because enabling managed spot training does not increase memory; it only reduces cost by using spare EC2 capacity and can cause interruptions, but it does not address insufficient memory for the training step.

Full explanation →
62
MCQeasy

A data science team needs to deploy a frequently updated PyTorch model for real-time inference. The model is retrained weekly and versioned using SageMaker Model Registry. Which deployment strategy minimizes downtime and allows easy rollback?

A.Deploy the model on an EC2 instance behind an Application Load Balancer and manually update the instance with the new model version.
B.Deploy the model using AWS Lambda with a container image and trigger via API Gateway.
C.Configure SageMaker endpoints with multiple production variants and use canary deployment to shift traffic gradually.
D.Use SageMaker hosting with a single production variant and update the endpoint with a new model configuration each week.
AnswerC

Canary deployment allows gradual traffic shift, minimizing downtime and enabling rollback.

Why this answer

SageMaker endpoints with multiple production variants enable canary deployment, which shifts traffic gradually from the old model to the new one. This minimizes downtime by keeping both variants active during the transition and allows easy rollback by simply redirecting all traffic back to the previous variant if issues arise.

Exam trap

The trap here is that candidates often assume a single production variant with endpoint updates is sufficient, overlooking the downtime and rollback limitations, while the canary deployment pattern with multiple variants directly addresses the requirements for minimal downtime and easy rollback.

How to eliminate wrong answers

Option A is wrong because manually updating an EC2 instance behind an ALB introduces downtime during the update process and lacks automated rollback capabilities, making it unsuitable for a frequently updated model requiring minimal downtime. Option B is wrong because AWS Lambda has a maximum invocation duration of 15 minutes and is designed for stateless, short-lived functions, not for hosting real-time inference workloads that require persistent, low-latency serving. Option D is wrong because using a single production variant and updating the endpoint configuration each week requires a full endpoint update, which causes downtime during the deployment and does not support gradual traffic shifting or easy rollback without redeploying the previous version.

Full explanation →
63
MCQeasy

A company uses an Amazon SageMaker endpoint for real-time inference. The security team requires that all traffic between the endpoint and the client application be encrypted in transit. Which configuration ensures this?

A.Deploy the endpoint in a VPC and use VPC Endpoints.
B.Use AWS Key Management Service (KMS) to encrypt the data in transit.
C.The endpoint is automatically served over HTTPS; no additional configuration is needed.
D.Attach an AWS Certificate Manager (ACM) certificate to the endpoint.
AnswerC

SageMaker endpoints use HTTPS by default.

Why this answer

Amazon SageMaker endpoints are automatically served over HTTPS, which encrypts all data in transit between the client application and the endpoint. This is a default behavior of SageMaker real-time inference endpoints, so no additional configuration is required to meet the encryption-in-transit requirement.

Exam trap

The trap here is that candidates often overthink security requirements and assume additional configuration (like VPC endpoints or ACM certificates) is needed, when in fact SageMaker endpoints are inherently encrypted in transit via HTTPS by default.

How to eliminate wrong answers

Option A is wrong because deploying the endpoint in a VPC and using VPC Endpoints controls network traffic routing and provides private connectivity, but does not inherently enforce encryption in transit; the traffic could still be unencrypted if not using HTTPS. Option B is wrong because AWS KMS is used for encrypting data at rest (e.g., model artifacts, endpoint storage), not for encrypting data in transit; TLS/SSL handles in-transit encryption. Option D is wrong because attaching an ACM certificate to the endpoint is not a supported configuration for SageMaker endpoints; SageMaker automatically provisions and manages the TLS certificate for HTTPS, so manual certificate attachment is unnecessary and not possible.

Full explanation →
64
Multi-Selectmedium

A company is deploying a machine learning model using SageMaker hosting. They need to support multiple versions of the model for A/B testing. Which TWO actions are required to set up the A/B test? (Choose two.)

Select 2 answers
A.Enable shadow variants to capture traffic for the new model without affecting users
B.Set up a batch transform job to compare performance offline
C.Configure the endpoint to route a percentage of traffic to each variant using initial variant weight
D.Register both models in SageMaker Model Registry
E.Create an endpoint with two production variants, each serving a different model version
AnswersC, E

Traffic splitting is achieved via variant weights.

Why this answer

SageMaker endpoints use `initial variant weight` to distribute traffic among production variants. By setting this weight, you can route a specific percentage of inference requests to each model version, enabling A/B testing without changing the endpoint configuration.

Exam trap

The trap here is that candidates confuse shadow variants (which are for passive monitoring) with production variants (which are for active traffic splitting), leading them to select Option A instead of understanding that A/B testing requires explicit traffic routing via variant weights.

Full explanation →
65
MCQeasy

A company is using Amazon SageMaker Ground Truth to create a labeled dataset for object detection in images. The team wants to minimize labeling costs while maintaining high accuracy. Which feature should they use to achieve this?

A.Use a private workforce of internal employees
B.Enable automated data labeling with active learning
C.Use a larger initial training set with pre-labeled public datasets
D.Reduce the number of label categories
AnswerB

Active learning reduces costs by focusing human effort on the most valuable samples.

Why this answer

Active learning in Ground Truth automatically selects the most uncertain or informative samples from the unlabeled pool and sends them to human labelers, reducing the total number of images that need manual labeling.

Full explanation →
66
Multi-Selectmedium

A data scientist wants to use SageMaker Clarify to analyze bias during training of a binary classification model. Which TWO types of bias metrics can SageMaker Clarify compute? (Select TWO.)

Select 2 answers
A.Feature importance
B.Post-training bias metrics (e.g., Difference in Positive Proportions, AD)
C.SHAP values
D.Pre-training bias metrics (e.g., Class Imbalance, DPL)
E.Confusion matrix
AnswersB, D

These metrics are computed on model predictions.

Why this answer

SageMaker Clarify computes pre-training bias (e.g., class imbalance) and post-training bias (e.g., difference in positive proportions across groups).

Full explanation →
67
MCQhard

A healthcare company is deploying a model for predicting patient outcomes. The model must be deployed across multiple AWS accounts to meet compliance requirements. Each account has its own Amazon SageMaker endpoint. The company wants to centralize monitoring of model performance without exposing data across accounts. Which solution should the company use?

A.Establish VPC peering between accounts and call the endpoints from a central monitoring service.
B.Replicate the inference data to a central S3 bucket in the management account using cross-account replication, then run Model Monitor centrally.
C.Use SageMaker Model Monitor in each account and publish custom metrics to a central CloudWatch account using cross-account observability.
D.Create a shared SageMaker Model Registry across accounts and aggregate monitoring.
AnswerC

This allows centralized monitoring without moving data across accounts.

Why this answer

It uses SageMaker Model Monitor in each account to detect data drift and model degradation locally, then publishes custom metrics to a central CloudWatch account via cross-account observability. This approach centralizes monitoring without moving raw inference data across accounts, satisfying the compliance requirement of not exposing data.

Exam trap

The trap here is confusing data replication (which exposes raw data) with metric aggregation (which exposes only statistical summaries), leading candidates to pick Option B despite its compliance violation.

How to eliminate wrong answers

Option A is wrong because VPC peering enables network connectivity but does not provide a mechanism to centralize monitoring metrics or avoid exposing inference data across accounts; it would require direct data transfer to a central service, violating compliance. Option B is wrong because replicating inference data to a central S3 bucket using cross-account replication exposes raw data across accounts, which directly violates the requirement to not expose data. Option D is wrong because a shared SageMaker Model Registry aggregates model metadata and versions, not real-time monitoring metrics or data drift detection; it does not provide centralized performance monitoring.

Full explanation →
68
MCQhard

A machine learning engineer is setting up automated retraining for a model using SageMaker Pipelines. The pipeline should trigger when a data drift alert is received from Model Monitor. Which event source should the engineer use to initiate the pipeline?

A.Amazon CloudWatch Events (Amazon EventBridge) rule that captures Model Monitor outcome.
B.AWS Lambda function that polls CloudWatch logs.
C.S3 event notification on the monitoring output bucket.
D.SageMaker model monitor webhook.
AnswerA

Model Monitor publishes violation events to EventBridge, which can trigger a pipeline execution reliably.

Why this answer

Amazon EventBridge (formerly CloudWatch Events) is the native AWS service for reacting to state changes in AWS resources. SageMaker Model Monitor publishes data drift alerts as events to EventBridge, so a rule can be configured to match those specific events and trigger the SageMaker Pipeline execution as a target. This provides a fully managed, event-driven architecture without polling or custom integrations.

Exam trap

The trap here is that candidates confuse S3 event notifications (which are for object-level events) with the structured, high-level alerts emitted by Model Monitor, leading them to choose Option C instead of the correct EventBridge integration.

How to eliminate wrong answers

Option B is wrong because polling CloudWatch Logs with a Lambda function introduces unnecessary latency, complexity, and cost; AWS best practice is to use EventBridge for event-driven triggers rather than polling. Option C is wrong because S3 event notifications on the monitoring output bucket would fire on every object write, not specifically on a data drift alert, leading to false triggers and wasted compute. Option D is wrong because SageMaker Model Monitor does not expose a webhook; it integrates with EventBridge for event delivery, not with external HTTP callbacks.

Full explanation →
69
MCQmedium

An ML engineer needs to orchestrate a multi-step workflow that includes data preprocessing on Spark, model training on SageMaker, and deployment to a production endpoint. They require tight integration with other AWS services and the ability to add custom logic. Which AWS service should they use alongside SageMaker?

A.AWS Step Functions
B.AWS CloudFormation
C.SageMaker Pipelines
D.Amazon EventBridge
AnswerA

Why this answer

AWS Step Functions is the correct choice because it provides a serverless workflow orchestration service that can coordinate multi-step ML pipelines involving Spark on AWS Glue or EMR, SageMaker training jobs, and endpoint deployments. It offers tight integration with over 200 AWS services via direct SDK integrations, supports custom logic through Lambda functions, and includes built-in error handling, retries, and parallel execution — making it ideal for complex, heterogeneous ML workflows that extend beyond SageMaker's native capabilities.

Exam trap

The trap here is that candidates confuse SageMaker Pipelines (a SageMaker-native orchestrator) with a general-purpose orchestrator, overlooking the requirement for tight integration with non-SageMaker services like Spark and custom logic — Step Functions is the correct choice for heterogeneous, multi-service ML workflows.

How to eliminate wrong answers

Option B (AWS CloudFormation) is wrong because it is an Infrastructure as Code (IaC) service for provisioning and managing AWS resources declaratively, not a workflow orchestrator — it cannot sequence steps like 'run Spark job, then train model, then deploy endpoint' with conditional logic or dynamic state management. Option C (SageMaker Pipelines) is wrong because while it can orchestrate SageMaker-native steps (training, tuning, batch transform), it lacks direct integration with external services like Spark on EMR or Glue and cannot easily incorporate custom logic outside the SageMaker ecosystem — the question explicitly requires tight integration with other AWS services and custom logic beyond SageMaker. Option D (Amazon EventBridge) is wrong because it is an event bus service for routing events between services based on rules, not a workflow orchestrator — it cannot manage sequential dependencies, retries, or stateful execution of a multi-step pipeline.

Full explanation →
70
Multi-Selecthard

A company is training a deep learning model for object detection using SageMaker. The training is very slow and the GPU memory is insufficient for the batch size. The team wants to scale across multiple GPUs efficiently. Which THREE actions should they take? (Choose THREE.)

Select 3 answers
A.Use SageMaker distributed model parallelism
B.Use SageMaker distributed data parallelism
C.Use managed spot instances
D.Use a SageMaker distributed training configuration with the SageMaker SDK
E.Enable SageMaker Debugger to identify bottlenecks
AnswersA, B, D

Model parallelism partitions the model across GPUs if the model is too large for one GPU.

Why this answer

Distributed data parallelism replicates the model and splits batches across GPUs. SageMaker distributed library optimizes this. Model parallelism splits the model when memory is insufficient.

Spot instances reduce cost but not speed or memory. Debugger does not speed up training.

Full explanation →
71
Multi-Selectmedium

An ML engineer is using Amazon SageMaker Feature Store to manage features for a fraud detection model. The team needs to retrieve point-in-time feature values for training, ensuring no future data leaks. Which THREE configurations are required? (Choose 3)

Select 3 answers
A.Use the GetRecord API with an as-of timestamp
B.Enable the online store for the feature group
C.Enable the offline store for the feature group
D.Configure the feature group with a record identifier and event time feature
E.Store the feature group in the offline store with a record identifier and event time
AnswersC, D, E

Offline store records historical feature values with timestamps, enabling point-in-time queries.

Why this answer

Point-in-time queries require recording timestamps, using the offline store (which supports historical queries), and enabling the feature group with the correct configuration. The online store is for real-time, not historical. As-of timestamp is a parameter for queries but not a configuration.

Record identifier is for record keys.

Full explanation →
72
Multi-Selectmedium

A data scientist is using SageMaker to train a custom PyTorch model for image classification. They want to use SageMaker Debugger to detect training issues. Which TWO built-in rules are most relevant for detecting common training problems? (Select TWO.)

Select 2 answers
A.DataDistribution
B.Overfit
C.ExplodingGradients
D.ImageQuality
E.ConfusionMatrix
AnswersB, C

The Overfit rule in SageMaker Debugger monitors the validation loss relative to the training loss; if validation loss begins to increase while training loss continues to decrease, the rule emits a warning. This directly addresses the image classification scenario, where a custom PyTorch model can easily memorise training data rather than generalising, satisfying the stem’s requirement to detect common training problems.

Why this answer

ExplodingGradients detects gradients becoming too large, and Overfit detects when validation loss diverges from training loss. Both are common issues.

Full explanation →
73
MCQhard

A machine learning engineer is using Amazon SageMaker Debugger to monitor a training job for a deep neural network. They receive a rule alert indicating 'exploding gradients'. Which action should they take to address this issue?

A.Use a smaller batch size
B.Reduce the learning rate
C.Increase the number of layers to absorb gradients
D.Increase the learning rate
AnswerB

Reducing the learning rate decreases the size of weight updates, helping to prevent gradients from exploding.

Why this answer

Exploding gradients occur when gradients become too large, causing instability. Reducing the learning rate mitigates this. Increasing batch size can also help by smoothing gradients, but reducing learning rate is a direct solution.

Full explanation →
74
Multi-Selectmedium

A data scientist is training a deep learning model using SageMaker and wants to use distributed training across multiple GPUs to reduce training time. Which TWO actions should the scientist take to configure distributed training? (Select TWO.)

Select 2 answers
A.Reduce the number of epochs to match the number of GPUs
B.Use the SageMaker distributed data parallelism library
C.Manually split the training data into shards and upload to S3
D.Configure the SageMaker estimator with a distribution parameter
E.Set the instance count to 1 with a multi-GPU instance
AnswersB, D

The library automatically distributes data across GPUs.

Why this answer

The SageMaker distributed data parallelism library (option B) automatically partitions training data and synchronizes gradients across multiple GPUs, reducing training time without manual data splitting. Configuring the SageMaker estimator with a distribution parameter (option D) enables this library by specifying the distribution strategy (e.g., 'torch_distributed' or 'tensorflow_distributed'), which is required to activate distributed training.

Exam trap

The trap here is that candidates confuse single-instance multi-GPU training (option E) with true distributed training across multiple instances, or assume manual data sharding (option C) is required when SageMaker automates it.

Full explanation →
75
MCQmedium

A machine learning engineer is configuring auto-scaling for a SageMaker real-time endpoint. The endpoint is expected to have steady traffic during business hours and low traffic at night. The engineer wants to minimize costs by scaling in during low traffic, but the model container has a long start-up time (about 5 minutes). Which scaling policy should the engineer use to prevent request drops during sudden traffic spikes?

A.Use a step scaling policy based on invocations per minute with a step that adds two instances at a time.
B.Use a target tracking scaling policy based on average invocations per minute with a warm-up of 300 seconds.
C.Use a scheduled scaling action to add instances before business hours and remove them after.
D.Use a simple scaling policy based on average CPU utilization with a cooldown period of 5 minutes.
AnswerB

Target tracking with a warm-up period ensures that newly launched instances are not included in the metric until they are ready, preventing traffic loss.

Why this answer

Target tracking scaling policies in SageMaker automatically adjust capacity to maintain a target metric value, and the warm-up time of 300 seconds accounts for the 5-minute container start-up latency. This prevents request drops during sudden traffic spikes by ensuring new instances are fully initialized before they receive traffic, while still allowing the endpoint to scale in during low traffic to minimize costs.

Exam trap

The trap here is that candidates often choose a step scaling policy (Option A) because they think adding multiple instances at once handles spikes faster, but they overlook the critical need for a warm-up period to account for container start-up latency, which target tracking with warm-up explicitly addresses.

How to eliminate wrong answers

Option A is wrong because step scaling policies add instances in fixed increments (e.g., two at a time) without considering the long start-up time; this can lead to over-provisioning or under-provisioning during sudden spikes, and the lack of a warm-up period means new instances may not be ready to handle incoming requests, causing drops. Option C is wrong because scheduled scaling actions only handle predictable traffic patterns (e.g., business hours) and cannot react to sudden, unplanned traffic spikes, leaving the endpoint vulnerable to request drops. Option D is wrong because simple scaling policies based on average CPU utilization with a cooldown period of 5 minutes do not account for the model container's start-up latency; the cooldown prevents further scaling actions during the start-up period, but the policy itself cannot pre-warm instances, so traffic spikes during the cooldown can still cause request drops.

Full explanation →

Page 1 of 12

Page 2

All pages

123456789101112

Practice MLA-C01 by domain

Target a specific domain to shore up weak areas.

ML Model DevelopmentData Preparation for Machine LearningDeployment and Orchestration of ML WorkflowsML Solution Monitoring, Maintenance, and Security
See all domains with question counts →