Knowledge + Practice

AWS Certified Machine Learning Engineer Associate MLA-C01 (MLA-C01) — Questions 676–750

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

Take a mock exam Exam hub

Page 10 of 12

676

MCQeasy

A machine learning team wants to monitor bias in a deployed model's predictions on an ongoing basis. Which AWS service should they use to schedule bias monitoring jobs and generate reports?

A.Amazon QuickSight with Athona queries

B.AWS CloudTrail for prediction logging

C.SageMaker Model Monitor with data quality monitoring

D.SageMaker Clarify with bias drift monitoring

AnswerD

Clarify offers bias monitoring after deployment, detecting shifts in fairness metrics.

Why this answer

SageMaker Clarify is the correct choice because it provides built-in bias drift monitoring capabilities that can be scheduled to run on a recurring basis. It evaluates predictions against pre-training and post-training bias metrics (e.g., DPL, DI, CDDL) and generates detailed reports, making it the only service designed specifically for ongoing bias monitoring in deployed models.

Exam trap

The trap here is that candidates confuse SageMaker Model Monitor (which handles data and model quality drift) with SageMaker Clarify (which handles bias and explainability drift), leading them to select Option C even though it does not support bias-specific monitoring.

How to eliminate wrong answers

Option A is wrong because Amazon QuickSight with Athena queries is a business intelligence and visualization service, not a bias monitoring tool; it lacks the ability to schedule bias detection jobs or compute bias metrics. Option B is wrong because AWS CloudTrail logs API calls for auditing and governance, not model predictions or bias metrics; it cannot schedule bias monitoring or generate bias reports. Option C is wrong because SageMaker Model Monitor with data quality monitoring focuses on detecting data drift (e.g., feature distribution changes) and model quality degradation (e.g., accuracy), not bias drift; it does not compute fairness metrics like disparate impact or equal opportunity.

Full explanation →

677

MCQmedium

A team is fine-tuning a Hugging Face BERT model for text classification using SageMaker. They want to use the Hugging Face estimator for convenience. Which parameter must be set to use a custom training script?

A.framework_version

B.instance_type

C.hyperparameters

D.entry_point

AnswerD

entry_point points to the custom training script.

Why this answer

The entry_point parameter specifies the path to the training script. The instance_type is for hardware selection. The hyperparameters dictionary passes parameters to the script.

The framework_version specifies the Hugging Face version.

Full explanation →

678

MCQmedium

A machine learning engineer is training a TensorFlow model using SageMaker with distributed training. They need to implement data parallelism across multiple GPUs. Which SageMaker feature should they use to distribute the training?

A.SageMaker Distributed Data Parallelism

B.SageMaker Automatic Model Tuning

C.SageMaker Debugger

D.SageMaker Model Parallelism

AnswerA

This library implements data parallelism for SageMaker training.

Why this answer

SageMaker's distributed data parallelism library handles splitting data across GPUs and synchronizing gradients, optimized for TensorFlow and PyTorch.

Full explanation →

679

MCQmedium

A data engineer needs to join two large datasets from Amazon S3: one containing customer demographics and another containing transaction history. The join key is `customer_id`. To minimize data shuffling and improve performance, the engineer decides to use Amazon SageMaker Processing with Spark. Which configuration should the engineer use?

A.Use a bucketed join with the same number of buckets

B.Broadcast join the larger dataset

C.Use a bucketed join with the same number of buckets and co-location

D.Use a repartition on the join key before join

AnswerC

Bucketing with co-location allows Spark to perform the join without shuffling.

Why this answer

Bucketed joins with the same number of buckets and co-location ensure that data with the same `customer_id` hash is physically stored together on the same nodes. This eliminates the need for expensive shuffles during the join, as Spark can perform the join locally within each executor, dramatically improving performance for large datasets in SageMaker Processing.

Exam trap

The trap here is that candidates assume bucketing alone (same number of buckets) is sufficient, but without co-location, Spark still performs a shuffle to align the data, so both conditions are required for a shuffle-free join.

How to eliminate wrong answers

Option A is wrong because bucketed joins require both datasets to have the same number of buckets AND co-location (data physically stored together); without co-location, Spark still shuffles data to align partitions, negating the performance benefit. Option B is wrong because broadcast join is only efficient when one dataset is small enough to fit in memory (typically <100 MB); the transaction history dataset is large, so broadcasting it would cause out-of-memory errors or severe performance degradation. Option D is wrong because repartitioning on the join key before the join adds an extra shuffle step, increasing overhead rather than reducing it; bucketing with co-location avoids shuffles entirely.

Full explanation →

680

Multi-Selecteasy

A data scientist is using SageMaker Autopilot to automatically build a model. Which TWO aspects does Autopilot handle? (Choose TWO.)

Select 2 answers

A.Data ingestion

B.Model deployment

C.Feature engineering

D.Data labeling

E.Hyperparameter tuning

AnswersC, E

Correct: Autopilot automatically explores different feature transformations.

Why this answer

SageMaker Autopilot automatically performs feature engineering, which includes data preprocessing, feature transformation, and selection of the most relevant features to improve model performance. This is a core capability of Autopilot, as it analyzes the dataset and applies techniques like one-hot encoding, scaling, and imputation without manual intervention.

Exam trap

The trap here is that candidates often confuse SageMaker Autopilot's automated capabilities with full MLOps automation, mistakenly thinking it handles data ingestion or deployment, when in fact it focuses solely on model building tasks like feature engineering and hyperparameter tuning.

Full explanation →

681

MCQhard

A data scientist is preparing data for a regression model. The target variable has a skewed distribution. The scientist wants to apply a log transformation to make it closer to normal. Which step should be taken before applying log transformation?

A.Standardize the data to zero mean and unit variance

B.Remove outliers using IQR

C.Ensure all values are positive

D.Center the data by subtracting the mean

AnswerC

Log is undefined for zero and negative values. If present, add a constant or use other transformations.

Why this answer

The log transformation is defined only for positive real numbers; applying it to zero or negative values results in undefined or complex outputs. Therefore, before applying a log transformation, you must ensure all values in the target variable are positive, typically by adding a constant (e.g., log(x + 1)) if zeros are present. This step is a fundamental data preparation requirement for log transformations in regression modeling.

Exam trap

AWS often tests the assumption that candidates will confuse data normalization or centering with the domain restriction of the log function, leading them to pick standardization or mean-centering as a preparatory step.

How to eliminate wrong answers

Option A is wrong because standardizing to zero mean and unit variance (z-score normalization) does not guarantee all values become positive; it centers data around zero, which can produce negative values, making log transformation invalid. Option B is wrong because removing outliers using IQR is not a prerequisite for log transformation; while outliers can affect model performance, the log transformation itself can help mitigate skewness and reduce the influence of outliers, and removing them beforehand is an optional, separate step. Option D is wrong because centering data by subtracting the mean shifts values to have a mean of zero, which inevitably introduces negative values, directly contradicting the requirement for positive inputs for log transformation.

Full explanation →

682

MCQmedium

A team is fine-tuning a large language model (LLM) using SageMaker and wants to reduce memory footprint during training. Which technique should they use?

A.Use LoRA (Low-Rank Adaptation) with fp32 precision

B.Use QLoRA (Quantized Low-Rank Adaptation) with 4-bit quantization

C.Use SageMaker Model Parallelism with tensor parallelism

D.Full fine-tuning on a p3.16xlarge instance

AnswerB

QLoRA uses 4-bit quantization to drastically lower memory usage while preserving performance.

Why this answer

QLoRA (Quantized Low-Rank Adaptation) combines 4-bit quantization with low-rank adapters, significantly reducing GPU memory usage while maintaining model quality.

Full explanation →

683

Multi-Selectmedium

Which TWO options are recommended best practices for monitoring model performance in production on SageMaker? (Choose 2.)

Select 2 answers

A.Retrain the model daily based on recent data without evaluation.

B.Use SageMaker Clarify for bias monitoring and feature importance drift.

C.Enable SageMaker Model Monitor to capture data drift and model quality metrics.

D.Set up a CloudWatch alarm on the endpoint's Invocations metric.

E.Manually compare prediction distributions weekly.

AnswersB, C

Clarify can monitor bias and explainability over time.

Why this answer

SageMaker Clarify is a recommended best practice for monitoring model performance because it provides automated bias detection and feature importance drift analysis, helping to identify when model predictions become unfair or when the relationships between features and predictions change over time. This is critical for maintaining model integrity and compliance in production.

Exam trap

The trap here is that candidates often confuse operational metrics (like invocation count or latency) with model performance monitoring, leading them to select CloudWatch alarms on Invocations instead of the specialized drift and bias detection tools.

Full explanation →

684

MCQeasy

A data scientist is using SageMaker Automatic Model Tuning to find the best hyperparameters for a model. They want to reduce the total tuning time for a given number of training jobs. Which tuning strategy should they choose?

A.Hyperband

B.Grid search

C.Random search

D.Bayesian optimization

AnswerA

Hyperband uses early stopping to prune bad trials, reducing total tuning time for the same number of jobs.

Why this answer

Hyperband is an early stopping strategy that allocates resources to promising configurations and stops poor performers early, reducing total tuning time compared to random search or Bayesian optimization without early stopping.

Full explanation →

685

MCQeasy

A data science team has trained a model using SageMaker and wants to deploy it to a production endpoint with automatic scaling based on request volume. Which SageMaker feature should they use to configure scaling?

A.SageMaker Endpoint Autoscaling

B.SageMaker Debugger

C.SageMaker Model Registry

D.SageMaker Pipelines

AnswerA

Endpoint Autoscaling automatically adjusts the number of instances based on demand.

Why this answer

SageMaker Endpoint Autoscaling is the correct feature because it automatically adjusts the number of instances behind a SageMaker hosted endpoint based on a target metric (e.g., requests per minute, CPU utilization) using Application Auto Scaling. This allows the endpoint to handle varying request volumes without manual intervention, ensuring cost efficiency and performance.

Exam trap

The trap here is that candidates may confuse SageMaker Debugger (a training debugger) or SageMaker Pipelines (a workflow tool) with scaling features, when only Endpoint Autoscaling directly manages production instance count based on request volume.

How to eliminate wrong answers

Option B (SageMaker Debugger) is wrong because it is a monitoring and debugging tool for training jobs, not for scaling production endpoints. Option C (SageMaker Model Registry) is wrong because it is a catalog for versioning and managing trained models, not a scaling mechanism. Option D (SageMaker Pipelines) is wrong because it is a workflow orchestration service for building and automating ML pipelines, not for configuring endpoint scaling.

Full explanation →

686

MCQmedium

A team uses MLflow on SageMaker for experiment tracking. They want to automate the retraining of a model when new training data arrives in an S3 bucket. Which combination of services should they use?

A.SageMaker Pipelines scheduled trigger every hour

B.EventBridge -> Lambda -> SageMaker Training Job

C.S3 Event Notifications -> SQS -> SageMaker Training Job

D.AWS Step Functions with S3 poller

AnswerB

EventBridge captures S3 events, Lambda initiates training, and MLflow can log the run.

Why this answer

EventBridge can detect S3 PutObject events and trigger a Lambda function that starts a SageMaker training job, possibly using MLflow for tracking.

Full explanation →

687

MCQmedium

A company uses SageMaker Inference Recommender to select the optimal endpoint configuration. After running the recommender, they receive a recommendation for a specific instance type and initial instance count. What should they do next to optimize costs over time?

A.Use the recommended configuration without changes, as it is already optimal

B.Purchase a Savings Plan for the recommended instance type to reduce hourly cost

C.Set up auto-scaling with a target tracking policy based on the recommended metric

D.Manually adjust the instance count daily based on observed traffic

AnswerC

Auto-scaling adjusts capacity to demand, minimizing cost while meeting performance.

Why this answer

SageMaker Inference Recommender provides a baseline configuration. To optimize costs, they should apply auto-scaling with a target tracking policy based on the recommended metric, such as invocation count or latency.

Full explanation →

688

MCQhard

A data scientist creates a feature group as shown in the exhibit. When ingesting data with an 'age' column of integer values, the ingestion fails. What is the most likely cause?

A.The role does not have permissions to write to the feature store.

B.The `age` feature type should be `Integral`, not `String`.

C.The `OnlineStoreConfig` must include a `SecurityConfig`.

D.The `EventTimeFeatureName` is incorrectly spelled.

AnswerB

The feature type must match the ingested data type.

Why this answer

The feature group definition specifies the 'age' column as a `String` type, but the ingested data contains integer values. Amazon SageMaker Feature Store requires that the data types of ingested records match the schema defined in the feature group. When a mismatch occurs, such as providing an integer for a string field, the ingestion fails with a type conversion error.

Exam trap

AWS often tests the distinction between schema definition and actual data types, trapping candidates who overlook that the feature group schema must exactly match the ingested data's types, not just the column names.

How to eliminate wrong answers

Option A is wrong because the question states the ingestion fails specifically due to a data type mismatch, not a permissions issue; a permissions error would typically occur at the API call level, not during data parsing. Option C is wrong because `SecurityConfig` is not a required field in `OnlineStoreConfig`; the online store configuration only requires an `EnableOnlineStore` boolean and optionally a `SecurityGroupIdList` and `SubnetIdList` for VPC settings. Option D is wrong because the `EventTimeFeatureName` is spelled correctly as 'EventTime' in the exhibit, and a misspelling would cause a different error (e.g., 'InvalidParameterValue') rather than a data type mismatch.

Full explanation →

689

MCQhard

A machine learning engineer is building a time-series forecasting model to predict daily sales for the next 30 days. The dataset spans two years of daily sales data. To evaluate model performance, the engineer needs to simulate a realistic forecasting scenario where the model is trained on past data and tested on future data without leakage. Which data splitting strategy should they use?

A.Hold-out validation using a random 80/20 split

B.Walk-forward validation with an expanding window

C.Stratified sampling based on sales volume

D.k-fold cross-validation with random shuffling

AnswerB

Walk-forward validation trains on all past data and evaluates on the next unobserved time step, mimicking real-world forecasting.

Why this answer

Walk-forward validation (also known as time-series cross-validation) is specifically designed for time-dependent data. It trains on an expanding window of historical data and tests on the next period, respecting temporal order.

Full explanation →

690

MCQeasy

A company uses SageMaker Studio for collaborative ML development. The security team requires that all SageMaker Studio notebooks run within a VPC and cannot access the public internet. Which configuration should the administrator set?

A.Enable VPC-only mode for the SageMaker Studio domain

B.Use SageMaker notebook instances instead of Studio

C.Apply an SCP that denies internet access for all IAM users

D.Set the SageMaker Studio domain to use a public subnet with a NAT Gateway

AnswerA

This restricts all traffic to the VPC, no internet access.

Why this answer

Enabling VPC-only mode for the SageMaker Studio domain ensures that all Studio notebooks and apps are launched within the specified VPC and cannot access the public internet. This mode enforces that all network traffic, including internet-bound traffic, is routed through the VPC, and it blocks direct internet access by default, meeting the security team's requirement.

Exam trap

The trap here is that candidates may confuse VPC-only mode with simply using a private subnet, but VPC-only mode is a specific SageMaker Studio domain setting that explicitly blocks all internet access, whereas a private subnet alone could still allow outbound traffic via a NAT Gateway or VPC endpoint.

How to eliminate wrong answers

Option B is wrong because using SageMaker notebook instances instead of Studio does not inherently enforce VPC-only internet restrictions; notebook instances can still be configured with public internet access unless explicitly blocked via VPC settings. Option C is wrong because an SCP that denies internet access for all IAM users is an organization-level policy that does not directly control the network configuration of SageMaker Studio notebooks; it would affect user permissions but not the VPC routing or internet access of the Studio environment. Option D is wrong because setting the SageMaker Studio domain to use a public subnet with a NAT Gateway would actually provide outbound internet access to the notebooks, which violates the requirement that notebooks cannot access the public internet.

Full explanation →

691

Multi-Selectmedium

A dataset for binary classification has a severe class imbalance (5% positive class). Which two data preparation techniques can help address this imbalance? (Choose two.)

Select 2 answers

A.Remove outliers from the minority class

B.Apply PCA to reduce dimensionality

C.Use stratified splitting for train/test sets

D.Undersample the majority class

E.Oversample the minority class using SMOTE

AnswersD, E

Reduces majority class size to balance with minority class.

Why this answer

Undersampling the majority class reduces the number of instances from the dominant class, helping to balance the dataset and prevent the model from being biased toward the majority class. This technique is straightforward and can be effective when the majority class has redundant or noisy samples, though it risks losing valuable information.

Exam trap

AWS often tests the distinction between techniques that change the dataset distribution (like undersampling and oversampling) versus those that only affect model training or evaluation (like stratified splitting), leading candidates to mistakenly select stratified splitting as a balancing technique.

Full explanation →

692

MCQhard

A team is using SageMaker Clarify to detect bias drift in a deployed model's predictions. They run weekly bias monitoring jobs. The team wants to be notified when the bias metric for a sensitive feature exceeds a threshold. What is the most efficient method to achieve this?

A.Configure the Clarify monitoring job to send results to an SNS topic directly

B.After each Clarify job, run a custom Lambda that parses the report and publishes a custom CloudWatch metric; create an alarm on that metric

C.Manually review the bias report in SageMaker Studio each week

D.Use SageMaker Model Monitor - Bias Drift Monitor which automatically creates CloudWatch metrics

AnswerB

This approach translates bias metrics into CloudWatch metrics for alarming.

Why this answer

SageMaker Clarify bias monitoring jobs output a JSON report to S3 but do not natively publish CloudWatch metrics. By using a custom Lambda to parse the report and publish a custom CloudWatch metric, you can then create a CloudWatch alarm that triggers notifications when the bias metric exceeds a threshold. This is the most efficient automated method because it leverages CloudWatch's native alarm and notification capabilities without manual intervention.

Exam trap

The trap here is that candidates may confuse SageMaker Clarify's bias monitoring with SageMaker Model Monitor's built-in bias drift capabilities, assuming that Clarify automatically creates CloudWatch metrics or integrates with SNS, when in fact it only outputs to S3 and requires a custom pipeline for metric extraction and alerting.

How to eliminate wrong answers

Option A is wrong because SageMaker Clarify monitoring jobs cannot directly send results to an SNS topic; they output reports to S3, and SNS integration would require an intermediary like Lambda. Option C is wrong because manually reviewing the bias report in SageMaker Studio each week is not efficient and does not provide automated notifications. Option D is wrong because SageMaker Model Monitor's Bias Drift Monitor is a separate feature for monitoring bias drift over time, but it does not automatically create CloudWatch metrics for Clarify's bias metrics; it uses its own built-in metrics and alerts, not the custom threshold-based approach described.

Full explanation →

693

MCQhard

An ML team uses SageMaker Pipelines to automate retraining. After a pipeline failure, they need to reprocess only the failed step without rerunning the entire pipeline. What should they do?

A.Create a new pipeline version for each run.

B.Use SageMaker Model Monitor to detect drift and trigger retraining.

C.Use SageMaker Pipelines Cache with step-level caching.

D.Manually rerun the pipeline with updated parameters.

AnswerC

Caching enables the pipeline to skip completed steps and resume from the failed step.

Why this answer

SageMaker Pipelines Cache with step-level caching allows you to reuse outputs from previous successful runs of unchanged steps. When a pipeline fails, only the failed step and any downstream steps that depend on it need to be re-executed, because cached results from prior successful steps are automatically retrieved. This avoids rerunning the entire pipeline, saving time and compute resources.

Exam trap

The trap here is that candidates confuse SageMaker Pipelines Cache with Model Monitor's drift detection, assuming that monitoring automatically handles retraining failures, when in fact caching is the correct mechanism for step-level reuse.

How to eliminate wrong answers

Option A is wrong because creating a new pipeline version for each run does not address step-level reuse; it creates an entirely new pipeline execution history, forcing a full rerun. Option B is wrong because SageMaker Model Monitor is designed for detecting data drift and model quality degradation, not for caching or resuming failed pipeline steps. Option D is wrong because manually rerunning the pipeline with updated parameters still executes all steps from scratch, ignoring any previously successful step outputs.

Full explanation →

694

Multi-Selectmedium

A data scientist is evaluating a binary classification model for loan default prediction. Which THREE metrics should they consider to thoroughly assess model performance, especially for imbalanced classes?

Select 3 answers

A.R²

B.Recall

C.RMSE

D.F1 score

E.AUC

AnswersB, D, E

Recall (true positive rate) is critical for default prediction to identify as many defaults as possible.

Why this answer

For imbalanced classification, accuracy can be misleading. AUC (Area under ROC curve) is robust to imbalance, F1 balances precision and recall, and recall (true positive rate) is important to catch defaults. RMSE and R² are for regression, NDCG is for ranking.

Full explanation →

695

Multi-Selecthard

A company needs to secure a SageMaker notebook instance that contains sensitive data. Which THREE of the following are effective security measures? (Select THREE.)

Select 3 answers

A.Use IAM policies to restrict who can access the notebook instance.

B.Disable direct internet access and use a VPC with a NAT gateway for outbound.

C.Attach a lifecycle configuration that runs a script to download data from a public S3 bucket.

D.Enable AWS CloudTrail to log all notebook API calls.

E.Encrypt the notebook instance's EBS volume using AWS KMS.

AnswersA, B, E

IAM policies can limit which users can create presigned URLs for the notebook.

Why this answer

IAM policies are the primary mechanism for controlling access to AWS resources, including SageMaker notebook instances, ensuring only authorized users can interact with the instance. Disabling direct internet access and using a VPC with a NAT gateway is a network security best practice that prevents exposure to the public internet while allowing controlled outbound traffic, which is critical for sensitive data. Encrypting the EBS volume with AWS KMS protects data at rest.

AWS CloudTrail is useful for auditing API calls, but it is a logging and monitoring tool, not a direct security measure that prevents unauthorized access or data exposure.

Exam trap

A common trap is to consider AWS CloudTrail as an effective security measure for protecting the notebook instance itself. While CloudTrail provides an audit trail, it does not prevent unauthorized access or data leakage. Direct security controls like IAM, VPC configuration, and encryption are more effective.

Full explanation →

696

MCQmedium

A company collects sensor data from IoT devices. The data arrives with missing timestamps due to network issues. For anomaly detection, the engineer needs to create features that capture rolling statistics over fixed windows. Which data preprocessing step is essential before feature generation?

A.Remove missing timestamps

B.Resample data to a fixed frequency

C.Sort data by device ID

D.Impute missing values with forward fill

AnswerB

Resampling ensures consistent time intervals, which is required for rolling windows.

Why this answer

Resampling the data to a fixed frequency is essential because rolling window statistics require a consistent time index to compute accurate aggregations over fixed windows. Without a uniform timestamp grid, the window boundaries become ambiguous and the resulting features will be misaligned or incomplete, undermining the anomaly detection model.

Exam trap

AWS often tests the distinction between handling missing values (imputation) and handling irregular timestamps (resampling), leading candidates to confuse forward-fill as a solution for time alignment when it only addresses missing data points, not the underlying time index irregularity.

How to eliminate wrong answers

Option A is wrong because simply removing missing timestamps discards valuable data and does not address the need for a consistent time index; the remaining timestamps remain irregularly spaced. Option C is wrong because sorting by device ID organizes data by device but does not fix the irregular timestamp spacing required for fixed-window rolling statistics. Option D is wrong because forward-fill imputation fills missing values but does not create a uniform time grid; the timestamps themselves remain irregular, so rolling windows cannot be applied consistently.

Full explanation →

697

MCQeasy

A startup is building a serverless inference API using AWS Lambda. They have a TensorFlow model that is 400 MB in size. They packaged the model and inference code into a Lambda function using a container image. When they test the function with a small input, it consistently times out after 3 seconds. The Lambda function has 512 MB of memory and a timeout of 30 seconds. The business requirement is that inference must complete in less than 5 seconds under normal conditions. What is the most likely cause of the slow performance, and which change should they make?

A.The function timeout is too low; increase the timeout to 60 seconds.

B.The function is experiencing a cold start; use provisioned concurrency to keep the container warm.

C.The Lambda function memory is insufficient for the model size; increase memory to 1024 MB or higher.

D.Use a Lambda function with a GPU container to accelerate inference.

AnswerC

Lambda allocates CPU proportionally to memory. More memory speeds up computation and reduces swapping.

Why this answer

The most likely cause is that the Lambda function's memory (512 MB) is insufficient to load the 400 MB TensorFlow model into memory, causing excessive swapping or out-of-memory errors that drastically slow inference. Increasing memory to 1024 MB or higher provides more CPU and memory resources, allowing the model to fit and inference to complete within the required 5 seconds.

Exam trap

The trap here is that candidates confuse cold start latency with runtime performance issues, assuming provisioned concurrency (Option B) fixes all slow Lambda functions, when in fact memory/CPU insufficiency is the root cause for large model inference.

How to eliminate wrong answers

Option A is wrong because the function already has a 30-second timeout, and the issue is not timeout-related—the function consistently times out after 3 seconds due to resource constraints, not because the timeout is too low. Option B is wrong because provisioned concurrency addresses cold starts (initialization latency), but the problem here is runtime performance after the function is already warm; the 3-second timeout occurs consistently, not just on first invocation. Option D is wrong because Lambda does not support GPU containers; GPU acceleration is not available in AWS Lambda, and the inference time is dominated by memory/CPU bottlenecks, not lack of GPU.

Full explanation →

698

MCQmedium

A data scientist is using SageMaker Automatic Model Tuning with Hyperband. They want to stop poorly performing trials early to save resources. Which strategy does Hyperband use?

A.Grid search

B.Random search

C.Successive Halving

D.Bayesian optimization

AnswerC

Hyperband uses Successive Halving to allocate more resources to promising trials.

Why this answer

Hyperband uses early stopping by allocating resources to promising configurations and stopping poorly performing ones. Bayesian optimization uses acquisition functions. Random search does not early stop.

Grid search exhaustively evaluates all combinations.

Full explanation →

699

MCQhard

Refer to the exhibit. A company configures a SageMaker Model Monitor Data Quality monitoring schedule as shown. The schedule runs every hour. However, the team notices that the monitoring job fails intermittently with an AccessDenied error when accessing the S3 bucket for output. The IAM role SageMakerMonitorRole has permissions to write to s3://my-bucket/monitor-output. What is the MOST likely cause of the failure?

A.The S3UploadMode is set to Continuous, which is only supported for batch transform jobs.

B.The monitoring job runs in a VPC that does not have an S3 VPC endpoint, and the bucket policy denies requests from outside the VPC.

C.The cron expression is invalid; it should use rate(1 hour) instead.

D.The baseline constraints and statistics files are missing from the S3 bucket.

AnswerB

VPC restrictions can cause AccessDenied even if the IAM role allows.

Why this answer

The intermittent AccessDenied error when SageMaker Model Monitor attempts to write to the S3 output bucket strongly indicates a network or policy restriction. If the monitoring job is configured to run inside a VPC (common for security compliance) and that VPC lacks an S3 VPC endpoint, traffic to S3 traverses the public internet. If the S3 bucket policy explicitly denies requests from outside the VPC (using a condition like `aws:SourceVpce` or `aws:SourceVpc`), then jobs running inside the VPC without an endpoint will be denied access intermittently, especially if the job's execution role is assumed from within the VPC.

Exam trap

AWS often tests the interaction between VPC networking and S3 bucket policies, where candidates overlook that a VPC without an S3 endpoint will cause AccessDenied errors even if the IAM role has full S3 permissions, because the bucket policy itself blocks non-VPC-endpoint traffic.

How to eliminate wrong answers

Option A is wrong because S3UploadMode is not a valid parameter for SageMaker Model Monitor; it is a concept for batch transform jobs, and the error is about access permissions, not upload mode. Option C is wrong because the cron expression `cron(0 * * * ? *)` is valid for hourly execution and is the correct format for SageMaker schedules; `rate(1 hour)` is used for EventBridge rules, not for SageMaker monitoring schedule expressions. Option D is wrong because missing baseline files would cause a different error (e.g., `NoSuchKey` or validation failure), not an intermittent AccessDenied error, and the error specifically points to S3 write access.

Full explanation →

700

MCQeasy

An organization wants to schedule a retraining pipeline to run every Sunday night. Which AWS service should they use to trigger the pipeline on a schedule?

A.AWS Lambda

B.AWS Step Functions

C.Amazon SQS

D.Amazon EventBridge

AnswerD

EventBridge provides scheduled events using cron or rate expressions.

Why this answer

Amazon EventBridge is the correct choice because it provides a scheduled event source using cron or rate expressions to trigger target services at specified times, such as every Sunday night. It can directly invoke an AWS Step Functions state machine or a Lambda function to start the retraining pipeline, making it the native scheduling service for event-driven workflows in AWS.

Exam trap

The trap here is that candidates often confuse AWS Lambda's ability to be triggered by a schedule with Lambda itself being a scheduling service, but Lambda is only the compute target, not the scheduler — EventBridge is the service that provides the scheduled trigger.

How to eliminate wrong answers

Option A is wrong because AWS Lambda is a compute service that runs code in response to triggers, but it does not natively provide scheduling capabilities; while you can use Lambda with EventBridge, Lambda alone cannot generate scheduled events. Option B is wrong because AWS Step Functions is a workflow orchestration service that coordinates multiple AWS services, but it does not have built-in scheduling; it requires an external trigger like EventBridge to start execution on a schedule. Option C is wrong because Amazon SQS is a message queue service for decoupling application components, not a scheduling service; it cannot trigger pipelines on a schedule and relies on consumers to poll or receive messages.

Full explanation →

701

Multi-Selecteasy

A data engineer is using AWS Glue to prepare a dataset for machine learning. The dataset has several columns with outliers. The engineer wants to detect and handle outliers in a scalable manner. Which TWO approaches should the engineer consider? (Select TWO.)

Select 2 answers

A.Manually remove outliers by inspecting the data in Amazon S3.

B.Train a neural network to identify anomalies and remove them.

C.Use pandas in a SageMaker notebook to calculate z-scores and filter outliers.

D.Use AWS Glue DynamicFrame with Apache Spark to compute interquartile range (IQR) and filter outliers.

E.Use Amazon SageMaker Data Wrangler to apply an outlier detection transform.

AnswersD, E

Spark can handle large-scale data and IQR is a standard method.

Why this answer

AWS Glue DynamicFrames, built on Apache Spark, provide a scalable, distributed computing environment to compute statistical measures like the interquartile range (IQR) across large datasets. This allows the engineer to programmatically filter outliers without manual intervention, leveraging Spark's parallel processing for efficient handling of data at scale.

Exam trap

The trap here is that candidates may assume that only a single AWS service can handle outlier detection at scale, but the question requires selecting two approaches, and both Glue DynamicFrames and SageMaker Data Wrangler are valid, scalable, and managed AWS solutions for this task.

Full explanation →

702

MCQmedium

An e-commerce company uses a machine learning model to predict customer churn. They notice that the model's performance degrades after a major marketing campaign changes customer behavior. Which approach is MOST effective to detect and respond to this type of concept drift?

A.Deploy an A/B test to compare the current model with a baseline.

B.Use SageMaker Model Monitor to track prediction distribution and trigger retraining.

C.Manually review model accuracy each month.

D.Set up a weekly batch transform job to compute accuracy against historical data.

E.Increase the number of instances for the endpoint.

AnswerB

Correct. Model Monitor continuously checks for drift and can initiate automated retraining.

Why this answer

SageMaker Model Monitor can automatically detect concept drift by tracking the distribution of predictions over time and comparing them against a baseline. When drift is detected, it can trigger a retraining pipeline, enabling the model to adapt to the new customer behavior caused by the marketing campaign without manual intervention.

Exam trap

The trap here is that candidates confuse operational scaling (Option E) or periodic evaluation (Option D) with automated drift detection, overlooking that SageMaker Model Monitor provides continuous, distribution-based monitoring and automated retraining triggers.

How to eliminate wrong answers

Option A is wrong because A/B testing compares model versions but does not proactively detect concept drift; it requires manual setup and interpretation, and does not provide continuous monitoring. Option C is wrong because manually reviewing accuracy each month is reactive, not proactive, and cannot detect drift in real time between reviews, leading to delayed response. Option D is wrong because weekly batch transform jobs compute accuracy against historical data, but this is a batch process that introduces latency and does not provide continuous, automated drift detection or triggering of retraining.

Option E is wrong because increasing endpoint instances improves throughput and latency but does not address model performance degradation caused by concept drift.

Full explanation →

703

MCQhard

An e-commerce company uses a multi-model endpoint on Amazon SageMaker to serve several deep learning models. After a new model version is deployed, the endpoint starts returning 503 errors for some models. Monitoring shows that the endpoint's memory utilization is near 100%. What should the team do to resolve this issue while minimizing operational overhead?

A.Increase the number of instances for the endpoint and configure an auto-scaling policy based on memory utilization.

B.Deploy each model on its own separate endpoint to isolate memory usage.

C.Use Amazon SageMaker Model Monitor to detect memory leaks and send alerts.

D.Use SageMaker's built-in model scaling feature to allocate more memory to the affected model.

AnswerA

Adds capacity and auto-scales.

Why this answer

Increasing the number of instances and configuring an auto-scaling policy based on memory utilization directly addresses the root cause (memory exhaustion) by distributing the load across more instances. SageMaker's auto-scaling can use custom CloudWatch metrics (like memory utilization) to dynamically adjust capacity, which minimizes operational overhead by automating scaling without manual intervention.

Exam trap

The trap here is that candidates may confuse SageMaker's built-in auto-scaling (which typically uses invocation-based metrics like request count) with the need for custom memory-based scaling, or mistakenly think Model Monitor can fix performance issues when it is only for monitoring data and model quality.

How to eliminate wrong answers

Option B is wrong because deploying each model on its own separate endpoint increases operational overhead (multiple endpoints to manage, monitor, and scale) and does not inherently resolve memory exhaustion if each endpoint still runs on under-provisioned instances. Option C is wrong because SageMaker Model Monitor detects data drift and model quality issues, not memory leaks; it cannot resolve high memory utilization or prevent 503 errors. Option D is wrong because SageMaker does not have a built-in 'model scaling feature' to allocate more memory to a specific model within a multi-model endpoint; memory allocation is per instance, not per model, and the only way to increase memory is to scale out or use larger instance types.

Full explanation →

704

MCQhard

A data science team uses SageMaker Studio with a VPC-only mode. They need to access a private S3 bucket in the same VPC to read training data. The SageMaker Studio domain is configured with VPC-only mode. Which configuration ensures the Studio notebook can access the S3 bucket without traversing the public internet?

A.Set the S3 bucket as public and restrict access by source IP

B.Configure a NAT Gateway in the public subnet and route Studio traffic through it

C.Use a SageMaker execution role with a policy that allows s3:GetObject from any network

D.Create an S3 Gateway Endpoint in the VPC and attach a bucket policy that allows access from the VPC

AnswerD

An S3 Gateway Endpoint allows private access to S3 without internet. The bucket policy must restrict access to the VPC endpoint.

Why this answer

An S3 Gateway Endpoint provides a private, VPC-only route to S3 without traversing the public internet. By attaching a bucket policy that restricts access to the VPC endpoint, the SageMaker Studio domain (configured with VPC-only mode) can securely read training data from the private S3 bucket using AWS PrivateLink.

Exam trap

The trap here is that candidates often confuse S3 Gateway Endpoints (which are free and route traffic privately within AWS) with VPC Interface Endpoints (which use PrivateLink and incur costs), or mistakenly think IAM policies alone control network path, ignoring the need for a VPC endpoint to avoid public internet traversal.

How to eliminate wrong answers

Option A is wrong because setting the S3 bucket as public exposes it to the internet, violating the VPC-only requirement and creating a security risk; source IP restrictions are not reliable in a VPC-only context. Option B is wrong because a NAT Gateway routes traffic to the public internet, which contradicts the VPC-only mode requirement and would cause the Studio notebook to traverse the public internet to reach S3. Option C is wrong because allowing s3:GetObject from any network in the execution role does not prevent the traffic from going over the public internet; the VPC-only mode requires a private network path, not just an IAM policy.

Full explanation →

705

MCQeasy

A data scientist is preparing a dataset for a binary classification model to predict customer churn. The dataset contains a timestamp column 'signup_date' that is not relevant for the prediction. What is the most appropriate action to handle this column?

A.Apply one-hot encoding to the year, month, and day components.

B.Convert the timestamp to a numeric feature (e.g., days since signup) and include it.

C.Use leave-one-out encoding based on the target variable.

D.Drop the 'signup_date' column from the dataset.

AnswerD

Irrelevant columns should be removed to prevent noise.

Why this answer

The 'signup_date' column is explicitly stated as not relevant for the prediction. In binary classification for customer churn, including an irrelevant timestamp can introduce noise, increase dimensionality, and potentially cause overfitting. Dropping the column is the most appropriate action to maintain model simplicity and focus on predictive features.

Exam trap

AWS often tests the misconception that all timestamp data must be transformed into numeric features, but the key is to first assess relevance—if the column is explicitly not relevant, dropping it is the correct action, not engineering features from it.

How to eliminate wrong answers

Option A is wrong because one-hot encoding the year, month, and day components would create multiple sparse features from an irrelevant column, adding unnecessary complexity and potentially misleading the model with temporal patterns that have no causal relationship with churn. Option B is wrong because converting the timestamp to a numeric feature like 'days since signup' would still retain irrelevant temporal information, which could introduce a spurious correlation or bias, especially if the dataset has a time-based split that leaks future information. Option C is wrong because leave-one-out encoding based on the target variable would leak target information into the feature, causing data leakage and overfitting, as the encoding uses the target value of other rows to encode the current row, which is inappropriate for an irrelevant column.

Full explanation →

706

Multi-Selecthard

A machine learning engineer is setting up model quality monitoring for a binary classification model. They have ground truth labels available in Amazon S3. Which TWO steps are required to configure model quality monitoring? (Choose two.)

Select 2 answers

A.Create a CloudWatch Alarm for accuracy degradation

B.Use Amazon SageMaker Clarify for bias detection

C.Create a schedule for the monitoring job to run at regular intervals

D.Create a baseline for model quality using training data and ground truth labels

E.Enable data capture on the endpoint to collect predictions

AnswersC, D

A schedule defines how often the monitoring job runs to compare predictions against ground truth.

Why this answer

A baseline must be computed from training data and ground truth, and a schedule for monitoring jobs must be defined. The monitoring job then compares production predictions against ground truth.

Full explanation →

707

MCQmedium

A team is monitoring a SageMaker endpoint and notices that the average latency (ModelLatency) is increasing over time, but the number of invocations is steady. They suspect that the model's inference code is becoming slower due to memory leaks. Which metric should they also examine to confirm this hypothesis?

A.Invocations metric

B.OverheadLatency metric

C.5XXError metric

D.MemoryUtilization metric (if custom)

AnswerD

Increasing memory usage suggests a leak, which can cause latency growth.

Why this answer

SageMaker publishes memory utilization metrics if the container emits them via CloudWatch. A memory leak would show increasing memory usage over time, correlating with increasing latency.

Full explanation →

708

Multi-Selectmedium

A data scientist is training a large language model using SageMaker and wants to reduce training costs. The training job is expected to run for several days. Which TWO actions should the data scientist take to minimize costs? (Choose TWO.)

Select 2 answers

A.Enable managed spot training

B.Use the most powerful GPU instance available to finish faster

C.Select ml.g5.xlarge instead of ml.p3.2xlarge

D.Increase the number of instances to reduce time

E.Disable checkpointing to save storage costs

AnswersA, C

Spot instances are much cheaper than on-demand; SageMaker managed spot automatically handles interruptions.

Why this answer

Using spot instances can save up to 90% compared to on-demand. Choosing a cheaper instance type like ml.g5 reduces cost. Managed spot training in SageMaker handles interruptions automatically.

GPU instances are not always necessary; the cheapest instance that meets requirements should be selected. Checkpointing is needed for spot instance resilience.

Full explanation →

709

MCQeasy

A data scientist uses SageMaker Experiments to track hyperparameters and metrics. Which component is used to organize related trials?

A.Experiment

B.Artifact

C.Trial component

D.Trial

AnswerA

An experiment contains multiple trials (runs) that share a common goal.

Full explanation →

710

Multi-Selecteasy

A company wants to implement cost monitoring and optimization for SageMaker endpoints. Which TWO actions should they take? (Select TWO)

Select 2 answers

A.Manually scale instances based on historical patterns

B.Enable detailed billing reports to track endpoint costs

C.Use SageMaker Savings Plans to get discounted rates in exchange for a commitment

D.Use SageMaker Model Monitor to reduce endpoint costs

E.Right-size endpoints using SageMaker Inference Recommender

AnswersC, E

Savings Plans provide lower costs for consistent usage.

Why this answer

SageMaker Savings Plans offer discounted compute rates (up to 64% off on-demand) in exchange for a 1- or 3-year commitment to a consistent amount of compute usage (measured in dollars per hour), directly reducing endpoint costs. This is a cost optimization mechanism, not a monitoring one, and aligns with the goal of reducing spend on SageMaker endpoints.

Exam trap

The trap here is that candidates confuse cost monitoring (Option B) with cost optimization, or assume that Model Monitor (Option D) directly reduces costs when it only monitors quality, not spend.

Full explanation →

711

Multi-Selectmedium

A company is using Amazon SageMaker Data Wrangler to prepare a dataset for training. They have created a data flow with multiple transforms. Which TWO actions can they take to operationalize the data preparation pipeline for production? (Choose 2)

Select 2 answers

A.Create a scheduled SageMaker Pipeline by directly converting the Data Wrangler flow

B.Convert the data flow directly to Amazon SageMaker Autopilot

C.Export the data flow to a SageMaker Processing job

D.Deploy the data flow as a real-time inference endpoint

E.Export the data flow as a standalone Python script

AnswersC, E

Data Wrangler can generate a processing script that runs as a SageMaker Processing job.

Why this answer

SageMaker Data Wrangler can export a data flow directly to a SageMaker Processing job. This allows the data preparation logic to be run as a managed, scalable batch job in production, integrating seamlessly with the SageMaker ecosystem for repeatable and scheduled processing.

Exam trap

The trap here is that candidates may confuse 'operationalizing for production' with real-time serving (Option D) or assume that Data Wrangler can directly feed into Autopilot (Option B), when in fact the correct approach is to export the flow to a batch processing job or standalone script.

Full explanation →

712

MCQmedium

A machine learning engineer needs to deploy a TensorFlow model that requires a custom inference environment with specific system libraries. The model will be used in a real-time application with variable traffic. They want to minimize cold start latency. Which SageMaker hosting option should they choose?

A.SageMaker real-time endpoint with a custom container

B.SageMaker Serverless Inference with a custom container

C.SageMaker Multi-Model Endpoint with a custom container

D.SageMaker Asynchronous Inference with a custom container

AnswerA

Real-time endpoints are always warm (no cold starts) and support custom containers.

Why this answer

SageMaker real-time endpoints with a custom container are the correct choice because they provide persistent, always-on infrastructure that eliminates cold start latency. By packaging the TensorFlow model with required system libraries in a custom Docker image, the engineer ensures the inference environment is ready immediately, and the endpoint can scale to handle variable traffic with minimal delay.

Exam trap

The trap here is that candidates often confuse 'minimizing cold start latency' with 'scaling to zero' and incorrectly choose Serverless Inference, failing to recognize that Serverless inherently introduces cold starts on first request after idle periods.

How to eliminate wrong answers

Option B is wrong because SageMaker Serverless Inference automatically scales to zero when idle, incurring cold start latency (typically 5–10 seconds) when traffic resumes, which contradicts the requirement to minimize cold start latency. Option C is wrong because SageMaker Multi-Model Endpoints are designed to host multiple models on a single container, but they still require a pre-configured inference environment; they do not inherently reduce cold start latency for a single custom model. Option D is wrong because SageMaker Asynchronous Inference is intended for non-real-time workloads with larger payloads and queuing, and it also experiences cold starts when scaling from zero, making it unsuitable for real-time applications with variable traffic.

Full explanation →

713

MCQeasy

A data scientist is preparing a dataset for binary classification using SageMaker. The dataset has 100 features and 10,000 rows, but the target variable is highly imbalanced (95% negative, 5% positive). Which technique should the data scientist apply during data preparation to address the imbalance?

A.Oversampling the minority class by duplicating examples

B.Collect more data to match the number of samples in both classes

C.Random undersampling of the majority class

D.Apply SMOTE to generate synthetic samples for the minority class

AnswerD

SMOTE creates synthetic examples along the line segments of minority class nearest neighbors, addressing imbalance.

Why this answer

SMOTE (Synthetic Minority Oversampling Technique) is the most appropriate technique because it generates synthetic samples for the minority class by interpolating between existing minority instances, which avoids the overfitting risk of simple duplication (oversampling) and the information loss from undersampling. In SageMaker, SMOTE can be applied during data preparation using libraries like imbalanced-learn before training, or via SageMaker Data Wrangler's built-in transform, making it a robust choice for handling class imbalance without discarding data.

Exam trap

AWS often tests the distinction between oversampling by duplication and synthetic oversampling (SMOTE), where candidates mistakenly choose simple duplication (Option A) because they think 'more data is always better,' failing to recognize that SMOTE generates diverse synthetic samples to reduce overfitting.

How to eliminate wrong answers

Option A is wrong because oversampling the minority class by duplicating examples leads to overfitting, as the model sees the same exact data points repeatedly, which does not introduce new variance and can cause poor generalization. Option B is wrong because collecting more data to match the number of samples in both classes is often impractical, costly, or impossible in real-world scenarios, and the question specifically asks for a technique to apply during data preparation, not a data collection strategy. Option C is wrong because random undersampling of the majority class discards potentially valuable data, which can lead to loss of important patterns and reduce model performance, especially when the dataset is already limited to 10,000 rows.

Full explanation →

714

MCQeasy

An ML engineer wants to be notified when the average inference latency of a SageMaker endpoint exceeds 500 ms for 2 consecutive evaluation periods. Which AWS service combination should they use?

A.CloudWatch Alarm + SNS

B.SageMaker Model Monitor + SNS

C.EventBridge + Lambda

D.SageMaker Clarify + SNS

AnswerA

CloudWatch Alarm triggers on the Latency metric and publishes to SNS for notification.

Why this answer

CloudWatch collects the 'Latency' metric from SageMaker endpoints. A CloudWatch Alarm can be set on this metric with a threshold of 500 ms for 2 consecutive periods. SNS then sends notification (email, SMS, etc.).

Lambda is for automated remediation, not required for notification only.

Full explanation →

715

MCQhard

A model deployed on SageMaker uses custom inference code. The endpoint is showing intermittent 500 errors. CloudWatch logs reveal 'TimeoutError: Request timed out after 60 seconds'. The model takes on average 55 seconds to process. What is the most effective solution?

A.Increase the invocation timeout in the SageMaker API call.

B.Increase the SageMaker endpoint's model container timeout setting.

C.Optimize the inference code to reduce latency.

D.Increase the endpoint's instance count.

AnswerC

Reducing inference latency below the timeout threshold is the most direct and effective solution, as it addresses the root cause.

Why this answer

The model's average processing time of 55 seconds is dangerously close to the default SageMaker model container timeout of 60 seconds. Any transient spike in latency or resource contention can push the inference time beyond the timeout, causing intermittent 500 errors. Optimizing the inference code to reduce latency below the timeout threshold directly addresses the root cause by creating a safety margin, making the endpoint more resilient to normal variability.

Exam trap

The trap here is that candidates confuse the model container timeout (which applies to startup and health checks) with the per-request inference timeout, leading them to incorrectly choose Option B, while the real fix is to reduce latency through code optimization.

How to eliminate wrong answers

Option A is wrong because the SageMaker API invocation timeout is a client-side setting that controls how long the caller waits for a response; it does not affect the server-side timeout that the model container enforces. Option B is wrong because increasing the model container timeout setting (e.g., via the `ModelDataDownloadTimeoutInSeconds` or `ContainerStartupHealthCheckTimeoutInSeconds` parameters) applies to startup and health checks, not to the per-request inference timeout; the 60-second timeout is the default for the SageMaker InvokeEndpoint API's `MaxConcurrentTransforms` or the underlying HTTP server timeout, which is not directly configurable through the endpoint configuration. Option D is wrong because increasing the instance count adds more compute capacity to handle concurrent requests, but it does not reduce the per-request processing time; the same 55-second average latency will still risk hitting the 60-second timeout under load spikes.

Full explanation →

716

MCQhard

A team uses SageMaker Neo to compile a model for deployment on a target device. After compilation, they deploy the compiled model to a SageMaker endpoint using the Neo-optimized container. The endpoint fails to start with error "RuntimeError: Unable to load model". What could be the issue?

A.The compiled model was not uploaded to the correct S3 path.

B.The Neo compilation job failed silently.

C.The endpoint instance type does not support Neo.

D.The target device architecture during compilation does not match the endpoint instance architecture.

AnswerD

Neo models are compiled for specific architectures; mismatch causes load failure.

Why this answer

SageMaker Neo compiles a model for a specific target architecture (e.g., ARM, x86, GPU). When deploying the compiled model to a SageMaker endpoint, the endpoint instance type must have a CPU or accelerator architecture that matches the target device specified during compilation. If they do not match, the Neo-optimized runtime cannot load the compiled binary, resulting in a 'RuntimeError: Unable to load model'.

Exam trap

AWS often tests the misconception that Neo compilation is a generic optimization that works on any endpoint instance, when in fact the target architecture must exactly match the deployment instance's hardware.

How to eliminate wrong answers

Option A is wrong because if the compiled model were not uploaded to the correct S3 path, the endpoint would fail with an 'Unable to find model artifact' or S3 access error, not a runtime model loading error. Option B is wrong because if the Neo compilation job failed silently, no compiled model artifact would be produced, and the deployment would fail earlier with a missing artifact error, not a runtime load error. Option C is wrong because all SageMaker endpoint instance types support Neo-optimized containers; Neo does not restrict which instance types can host compiled models—the restriction is on the architecture match between the compilation target and the endpoint instance.

Full explanation →

717

MCQmedium

A company wants to use SageMaker Autopilot for a regression problem. They require an explainability report that shows feature importance globally. Which Autopilot feature should they enable?

A.AutoML candidate generation

B.Ensembling mode

C.Hyperparameter optimization

D.Explainability report generation

AnswerD

Autopilot can generate explainability reports including global feature importance.

Full explanation →

718

MCQeasy

A machine learning engineer needs to reduce costs when training a large model on SageMaker. They are willing to accept potential interruptions and have checkpointing enabled. Which instance purchasing option should they use?

A.Spot instances

B.Reserved instances

C.Dedicated hosts

D.On-demand instances

AnswerA

Spot instances offer large discounts but can be interrupted; with checkpointing, training can resume, saving costs.

Why this answer

Spot instances offer significant cost savings (up to 60-90%) compared to on-demand, but can be reclaimed by AWS with a 2-minute notice. Checkpointing allows resuming training from the last saved state, making spot instances suitable.

Full explanation →

719

MCQeasy

A company wants to deploy a model using a serverless inference endpoint that can automatically scale to zero when not in use and has a configurable maximum concurrency. Which SageMaker inference option meets these requirements?

A.Serverless inference

B.Real-time endpoint with auto-scaling

C.Batch transform

D.Asynchronous inference

AnswerA

Serverless inference scales to zero and has configurable max concurrency and memory.

Why this answer

SageMaker Serverless Inference is the correct choice because it automatically scales to zero when the endpoint is idle, eliminating costs during periods of no traffic, and it allows you to configure a maximum concurrency limit per endpoint to control throughput. This fully managed, pay-per-invoke option is designed for workloads with intermittent or unpredictable traffic patterns, meeting both requirements precisely.

Exam trap

The trap here is that candidates confuse 'auto-scaling' with 'scaling to zero' and incorrectly choose the real-time endpoint with auto-scaling, not realizing that auto-scaling maintains a minimum instance count and cannot reduce to zero.

How to eliminate wrong answers

Option B is wrong because a real-time endpoint with auto-scaling can scale down to a minimum number of instances (e.g., 1) but cannot scale to zero; it always keeps at least one instance running, incurring base costs. Option C is wrong because batch transform is not a real-time inference endpoint; it processes entire datasets offline and does not support automatic scaling to zero or configurable concurrency for live requests. Option D is wrong because asynchronous inference endpoints can scale to zero when idle, but they do not support a configurable maximum concurrency; concurrency is managed internally based on the payload size and queue depth, not directly set by the user.

Full explanation →

720

MCQeasy

A company wants to automate the deployment of a SageMaker model into production whenever a new model version is approved in the Model Registry. Which service can be used to trigger the deployment pipeline?

A.AWS Lambda

B.Amazon CloudWatch Events (EventBridge)

C.Amazon S3 Events

D.Amazon SNS

E.AWS Config

AnswerB

Correct. EventBridge can capture Model Registry events and trigger downstream actions like CodePipeline.

Why this answer

Amazon EventBridge (formerly CloudWatch Events) can detect state changes in SageMaker Model Registry, such as when a model version is approved. It can then trigger a target like AWS CodePipeline or a Lambda function to automate the deployment pipeline, making it the correct choice for event-driven automation of model deployment.

Exam trap

The trap here is that candidates often confuse the event source (SageMaker Model Registry) with the trigger mechanism (EventBridge), mistakenly selecting Lambda or SNS as the trigger service instead of recognizing EventBridge as the event bus that detects and routes the approval event.

How to eliminate wrong answers

Option A is wrong because AWS Lambda is a compute service that can be triggered by events, but it is not the service that detects or routes the Model Registry approval event; EventBridge is the native event bus service for this purpose. Option C is wrong because Amazon S3 Events are triggered by object-level operations in an S3 bucket (e.g., PUT, DELETE), not by SageMaker Model Registry approval state changes. Option D is wrong because Amazon SNS is a pub/sub messaging service used for sending notifications, not for triggering deployment pipelines directly from Model Registry events; it would require an intermediary like EventBridge to route the event.

Option E is wrong because AWS Config is a service for evaluating resource compliance and configuration history, not for triggering event-driven workflows based on Model Registry approvals.

Full explanation →

721

Multi-Selecthard

A machine learning engineer is evaluating a binary classification model that predicts customer churn. The model achieves 95% accuracy, but the engineer suspects class imbalance is causing a misleading metric. Which THREE evaluation steps should the engineer perform to properly assess the model? (Choose THREE.)

Select 3 answers

A.Calculate RMSE

B.Calculate precision, recall, and F1-score

C.Compute Mean Absolute Error (MAE)

D.Plot the ROC curve and compute AUC

E.Compute the confusion matrix

AnswersB, D, E

Precision, recall, and F1 are class-imbalance-aware metrics.

Why this answer

Accuracy is misleading for imbalanced datasets. Confusion matrix, precision/recall/F1, and AUC-ROC are robust metrics. RMSE is for regression.

MAE is also for regression.

Full explanation →

722

Multi-Selectmedium

A company is preparing data for a time-series forecasting model. The data is collected from IoT sensors at irregular intervals. Which TWO steps are necessary to prepare the data? (Choose 2.)

Select 2 answers

A.Normalize the data to a 0-1 range

B.Resample the data to a fixed frequency

C.Fill missing values using forward fill or interpolation

D.Remove outlier data points

E.Encode categorical features

AnswersB, C

Resampling creates regular time intervals required by most forecasting models.

Why this answer

Time-series forecasting models require data at consistent time intervals to capture temporal patterns and seasonality. Resampling the irregular IoT sensor data to a fixed frequency (e.g., every 5 minutes) creates a uniform time index, which is essential for algorithms like ARIMA, Prophet, or LSTM. This step ensures the model can learn from a structured sequence rather than being confused by variable time gaps.

Exam trap

AWS often tests the misconception that data normalization or outlier removal is a universal first step, but for time-series with irregular intervals, the critical preparatory steps are resampling and handling missing values to create a regular time grid.

Full explanation →

723

MCQmedium

A company uses SageMaker Experiments to track training runs. They want to compare different hyperparameter configurations and identify the best run. Which SageMaker Experiments component should they use to organize related runs?

A.Trial

B.Experiment + Trial

C.Experiment

D.Trial Component

AnswerB

Full explanation →

724

Multi-Selectmedium

A company uses SageMaker Model Monitor for feature attribution drift monitoring with SHAP. Which THREE prerequisites must be in place before starting the monitoring schedule? (Select THREE)

Select 3 answers

A.A SageMaker Clarify processing job that computes SHAP values on the captured data

B.Ground truth labels for the inference data

C.Baseline constraints file for data quality

D.Real-time endpoint with data capture enabled

E.A baseline SHAP explainability file from training data

AnswersA, D, E

Clarify runs the SHAP analysis on the current data to compare with baseline.

Why this answer

SageMaker Model Monitor requires a Clarify processing job to compute SHAP values on the captured data as part of the feature attribution drift monitoring setup. This job generates the necessary SHAP explainability values that are compared against the baseline to detect drift.

Exam trap

The trap here is that candidates often confuse the prerequisites for feature attribution drift monitoring with those for data quality monitoring, mistakenly selecting the baseline constraints file (Option C) instead of the baseline SHAP explainability file (Option E).

Full explanation →

725

MCQmedium

A data science team uses Amazon SageMaker Model Monitor to detect data drift in production. They notice that the schema of incoming data (number of features) has changed compared to the training baseline. Which type of monitor is BEST suited to detect this issue?

A.Bias drift monitor

B.Feature attribution drift monitor

C.Data quality monitor

D.Model quality monitor

AnswerC

Data quality monitor checks for schema violations and statistical drift in input features.

Why this answer

The Data quality monitor in SageMaker Model Monitor is specifically designed to detect violations in the input data schema, such as changes in the number of features, feature types, or missing values, by comparing incoming data against a baseline computed from the training dataset. Since the issue is a structural change in the schema (number of features), the Data quality monitor is the correct choice.

Exam trap

The trap here is that candidates confuse 'data drift' (distribution shift) with 'schema change' and incorrectly choose Feature attribution drift monitor, thinking it covers all input changes, but it only tracks importance shifts, not structural feature count violations.

How to eliminate wrong answers

Option A is wrong because Bias drift monitor focuses on detecting bias in model predictions (e.g., demographic parity) and does not monitor input schema changes. Option B is wrong because Feature attribution drift monitor (SHAP-based) tracks changes in feature importance over time, not the number or presence of features. Option D is wrong because Model quality monitor evaluates degradation in prediction accuracy (e.g., AUC, F1) against ground truth, not input data structure.

Full explanation →

726

MCQmedium

An ML team is deploying a model using SageMaker. The model requires GPU inference and must be available in multiple AWS regions for low latency. The team has created a multi-model endpoint with GPU instances. After deployment, they notice high latency spikes when a new model is loaded. What is the most likely cause?

A.The team is using a multi-model endpoint, which loads models on demand; loading a model into GPU memory causes latency spikes.

B.The endpoint is configured with a single production variant, causing all traffic to overload one instance.

C.The endpoint is using the wrong instance type that lacks sufficient GPU memory.

D.The model is too large for the specified container memory, causing swap to disk.

AnswerA

Multi-model endpoints load and unload models from memory, causing latency spikes when a new model is accessed.

Why this answer

A multi-model endpoint (MME) loads models on demand from Amazon S3 into the instance's memory. When a new model is requested and not already cached, SageMaker must download the model artifacts and load them into GPU memory, which is a time-consuming operation that causes a latency spike for the first inference request. This cold-start behavior is inherent to MMEs and explains the observed spikes.

Exam trap

The trap here is that candidates may confuse multi-model endpoint cold-start latency with general endpoint misconfiguration (like instance type or variant count), but the key clue is the timing of the spikes—only when a new model is loaded—which directly points to the on-demand loading behavior of MMEs.

How to eliminate wrong answers

Option B is wrong because a single production variant does not inherently cause latency spikes when loading new models; it would cause consistent high latency under load, not spikes tied to model loading. Option C is wrong because the question states the team is using GPU instances, and insufficient GPU memory would cause out-of-memory errors or failures, not latency spikes. Option D is wrong because swap to disk would cause severe performance degradation for all inferences, not just when a new model is loaded, and SageMaker containers typically do not use swap for GPU memory.

Full explanation →

727

Multi-Selecthard

A financial services company must ensure that all data used by Amazon SageMaker training jobs is encrypted at rest. The company wants to use a customer-managed key (CMK) for the encryption. Which steps are necessary to achieve this? (Choose TWO.)

Select 2 answers

A.Enable SageMaker's default encryption for the training job by setting the EnableDefaultEncryption flag.

B.Create a CMK in AWS KMS and add the SageMaker service principal to the key policy to allow it to use the key.

C.Enable S3 default encryption using the CMK on all buckets containing training data.

D.Specify the CMK's ARN in the VolumeKmsKeyId parameter when creating the training job.

E.Use CloudWatch Logs encryption to protect the training logs.

AnswersB, D

SageMaker needs permission to use the CMK.

Why this answer

To use a customer-managed key (CMK) for encrypting SageMaker training job data, you must first create a CMK in AWS KMS and then add the SageMaker service principal (sagemaker.amazonaws.com) to the key policy. This grants SageMaker the necessary permissions to use the key for encrypting the ML storage volume (e.g., EBS volumes) attached to the training instances. Without this policy statement, SageMaker cannot access the CMK, and the encryption request will fail.

Exam trap

The trap here is that candidates often confuse encrypting data at rest in S3 (via S3 default encryption) with encrypting the SageMaker training job's local storage volumes, which are separate and require explicit configuration via the VolumeKmsKeyId parameter.

Full explanation →

728

MCQeasy

A team wants to automate the retraining and deployment of an ML model whenever new labeled data arrives in S3. The workflow includes data preprocessing, training, evaluation, and conditional deployment. Which AWS service is best suited for orchestrating this end-to-end pipeline?

A.AWS Step Functions with Lambda functions for each step.

B.AWS Glue workflows with triggers based on S3 events.

C.AWS CodePipeline with source from S3 and build from CodeBuild.

D.Amazon SageMaker Pipelines triggered by S3 events via EventBridge.

AnswerD

SageMaker Pipelines is designed for ML workflows and supports S3 event triggers.

Why this answer

Amazon SageMaker Pipelines is purpose-built for ML workflows, offering native integration with SageMaker for training, evaluation, and conditional deployment steps. Triggered by S3 events via Amazon EventBridge, it automates the end-to-end pipeline from data preprocessing to conditional model deployment without requiring custom orchestration code.

Exam trap

The trap here is that candidates often choose AWS Step Functions (Option A) because it is a general-purpose orchestrator, but they overlook that SageMaker Pipelines provides tighter integration with ML-specific steps and reduces custom code overhead.

How to eliminate wrong answers

Option A is wrong because AWS Step Functions with Lambda functions would require you to manually implement each ML step (e.g., training, evaluation) and manage SageMaker API calls, lacking native ML-specific features like built-in model evaluation and conditional deployment logic. Option B is wrong because AWS Glue workflows are designed for ETL and data preparation, not for orchestrating ML training, evaluation, and deployment steps; they lack native support for SageMaker training jobs or model endpoints. Option C is wrong because AWS CodePipeline is a CI/CD service for application code, not optimized for ML workflows; it does not natively handle model evaluation, conditional deployment, or SageMaker-specific resources like training jobs and endpoints.

Full explanation →

729

MCQhard

A large enterprise has multiple SageMaker endpoints serving models for different business units. Each endpoint uses a separate instance type and scaling policy. The enterprise wants to implement a unified monitoring and logging solution to track endpoint health, latency, and errors across all endpoints. They also want to set up alerts when the error rate exceeds 5% over a 5-minute period. The solution must be centralized and use AWS-native services. Which solution should the team implement?

A.Enable SageMaker Model Monitor data capture on each endpoint and stream captured data to Amazon Kinesis for analysis.

B.Use AWS CloudTrail to audit all API calls to SageMaker and set up alarms on error responses.

C.Use Amazon CloudWatch Logs to collect logs from each endpoint, and use a Lambda function to parse logs and calculate error rates, then publish custom metrics.

D.Use Amazon CloudWatch dashboards to aggregate metrics from all endpoints, and create a composite alarm based on the Sum of 5xx error counts across endpoints.

AnswerD

CloudWatch natively aggregates metrics and composite alarms can alert on the combined error rate.

Why this answer

Amazon CloudWatch can natively ingest SageMaker endpoint metrics (e.g., 5xx error counts, latency, invocation counts) without additional configuration. By creating a CloudWatch dashboard, you aggregate metrics from all endpoints into a single view, and a composite alarm using the Sum statistic across endpoints over a 5-minute period directly triggers when the error rate exceeds 5%. This approach is fully centralized, uses only AWS-native services, and requires no custom code or data streaming.

Exam trap

The trap here is that candidates confuse SageMaker Model Monitor (data quality) with endpoint monitoring (operational health), or assume CloudWatch Logs are required when SageMaker endpoints already emit rich metrics directly to CloudWatch.

How to eliminate wrong answers

Option A is wrong because SageMaker Model Monitor is designed for detecting data drift and quality issues in the input data, not for tracking endpoint health, latency, or error rates; it captures inference data to Amazon S3, not to Kinesis, and does not provide real-time error rate alerts. Option B is wrong because AWS CloudTrail records API calls (e.g., CreateEndpoint, InvokeEndpoint) but does not capture the actual inference request/response payloads or error rates; it cannot measure latency or 5xx errors per invocation. Option C is wrong because SageMaker endpoints do not natively emit logs to CloudWatch Logs for inference requests; they emit metrics directly to CloudWatch, so a Lambda function parsing logs would be unnecessary and would require custom instrumentation to generate logs, violating the 'AWS-native' requirement.

Full explanation →

730

MCQmedium

A data scientist is training an object detection model using SageMaker built-in Object Detection algorithm. They want to visualize the bounding boxes on validation images after training. Which approach should they use?

A.Use SageMaker Debugger to capture output tensors

B.Write a custom inference script that saves images with bounding boxes

C.Enable SageMaker Model Monitor

D.Use SageMaker Clarify

AnswerB

A custom script can run inference and save annotated images.

Full explanation →

731

MCQeasy

A data scientist wants to version control trained models and manage approvals for deployment. Which SageMaker feature should they use?

A.SageMaker Model Registry.

B.SageMaker Experiments.

C.SageMaker Feature Store.

D.SageMaker Ground Truth.

AnswerA

Model Registry provides version control for models and supports approval workflows for deployment.

Why this answer

SageMaker Model Registry is the correct feature because it is specifically designed for versioning trained models, tracking their metadata (e.g., training job, metrics), and managing approval workflows for deployment stages (e.g., Pending, Approved, Rejected). This directly addresses the data scientist's need to version control models and manage deployment approvals.

Exam trap

The trap here is that candidates confuse SageMaker Experiments (which tracks training runs) with the Model Registry (which manages model versions and approvals), leading them to pick Experiments because they think 'version control' refers to experiment iterations rather than model artifacts.

How to eliminate wrong answers

Option B (SageMaker Experiments) is wrong because it is used for tracking and comparing machine learning training runs (experiments), not for versioning trained models or managing deployment approvals. Option C (SageMaker Feature Store) is wrong because it is a centralized repository for storing, sharing, and managing feature data for training and inference, not for model versioning or approval workflows. Option D (SageMaker Ground Truth) is wrong because it is a data labeling service for creating training datasets, not for model version control or deployment approvals.

Full explanation →

732

MCQmedium

A company has a batch transform job in Amazon SageMaker that processes large datasets every night. Recently, the job has been failing sporadically with an out-of-memory error. The data size has not increased. What is the MOST likely cause?

A.The custom inference code has a memory leak that gradually consumes available memory.

B.The data distribution has shifted, causing different memory usage patterns.

C.The instance type is not large enough to handle the dataset.

D.The batch transform input data has increased in size.

AnswerA

A memory leak can cause OOM even with same data size.

Why this answer

A memory leak in custom inference code would cause gradual memory consumption over time, eventually leading to out-of-memory errors even if the dataset size remains unchanged. SageMaker batch transform jobs run inference on each record independently, so a leak that accumulates across records (e.g., not releasing tensors or file handles) would cause sporadic failures as the job processes more data.

Exam trap

The trap here is that candidates assume out-of-memory errors always mean the instance is too small or data has grown, ignoring the possibility of a software defect like a memory leak that manifests over time without any change in data volume.

How to eliminate wrong answers

Option B is wrong because a data distribution shift would affect model accuracy or inference behavior, not directly cause out-of-memory errors; memory usage patterns are tied to data size and code efficiency, not distribution. Option C is wrong because the instance type has been sufficient historically and the data size has not increased, so the instance is not the root cause; the issue is a software defect, not capacity. Option D is wrong because the question explicitly states the data size has not increased, so input size growth cannot be the cause.

Full explanation →

733

MCQmedium

A data scientist is using Amazon SageMaker Studio to develop a model. The training job is taking longer than expected. The data scientist suspects that the data is being downloaded from Amazon S3 each time the training starts. What is the BEST way to reduce data loading time?

A.Use SageMaker Pipe Input mode to stream data directly from S3.

B.Enable S3 transfer acceleration and cache the data in S3.

C.Use a larger instance type with more network bandwidth.

D.Use Amazon FSx for Lustre to mount a high-performance file system.

AnswerA

Pipe mode streams data without downloading, reducing start time.

Why this answer

SageMaker Pipe input mode streams data directly from S3 into the training algorithm without first downloading it to the training instance's local storage. This eliminates the bottleneck of copying entire datasets, reducing startup time and disk usage. It is the most direct and efficient way to address the issue of repeated downloads from S3.

Exam trap

The trap here is that candidates often choose a 'bigger instance' (Option C) as a brute-force fix, overlooking that Pipe mode fundamentally changes the data access pattern to eliminate the download bottleneck entirely.

How to eliminate wrong answers

Option B is wrong because S3 Transfer Acceleration speeds up uploads to S3 over long distances, not downloads during training, and caching in S3 does not change the fact that data must still be transferred to the instance. Option C is wrong because while a larger instance with more network bandwidth may reduce transfer time, it does not eliminate the fundamental overhead of downloading the entire dataset to local storage before training begins. Option D is wrong because Amazon FSx for Lustre provides a high-performance file system that can be mounted to SageMaker, but it still requires data to be loaded from S3 into the file system (e.g., via `lustre` import), adding complexity and not directly solving the repeated download issue as efficiently as Pipe mode.

Full explanation →

734

Multi-Selectmedium

A company is deploying a SageMaker real-time endpoint and needs to monitor inference latency. Which THREE metrics are available from SageMaker for this purpose? (Choose THREE.)

Select 3 answers

A.OverheadLatency

B.Invocations

C.ModelLatency

D.MemoryUtilization

E.Latency

AnswersA, C, E

Time spent on SageMaker infrastructure overhead.

Why this answer

OverheadLatency is a SageMaker metric that measures the time taken by the SageMaker infrastructure to process the request before and after invoking the model, including network overhead and framework overhead. It is one of the three metrics specifically designed to monitor inference latency for real-time endpoints.

Exam trap

The trap here is that candidates often confuse Invocations (a request count metric) or MemoryUtilization (a resource utilization metric) with latency metrics, but SageMaker specifically provides three distinct latency-focused metrics: Latency, ModelLatency, and OverheadLatency.

Full explanation →

735

Multi-Selectmedium

A data scientist is using Amazon SageMaker Data Wrangler for data preparation. Which two tasks can be performed using Data Wrangler's built-in transforms? (Choose two.)

Select 2 answers

A.Running a SQL query on the data

B.Encoding categorical variables

C.Handling missing values

D.Creating an ensemble of models

E.Training a custom machine learning model

AnswersB, C

Built-in transform for one-hot encoding or label encoding.

Why this answer

Amazon SageMaker Data Wrangler includes a built-in transform for encoding categorical variables, such as one-hot encoding or ordinal encoding, directly within its visual interface. This allows data scientists to convert categorical data into numerical formats without writing custom code, streamlining the data preparation pipeline.

Exam trap

The trap here is that candidates may confuse Data Wrangler's capabilities with those of SageMaker Studio's other features, such as Athena for SQL queries or the built-in algorithms for model training, leading them to select options that are valid in SageMaker but not within Data Wrangler's scope.

Full explanation →

736

MCQeasy

A machine learning engineer wants to automatically trigger a retraining pipeline whenever new training data arrives in an S3 bucket. The pipeline uses SageMaker Pipelines. Which AWS service should be used to detect the S3 event and start the pipeline?

A.SageMaker Pipelines native S3 trigger

B.AWS Step Functions

C.Amazon CloudWatch Logs

D.Amazon EventBridge

AnswerD

EventBridge can react to S3 events and invoke a Lambda function that starts the SageMaker Pipeline execution.

Why this answer

Amazon EventBridge can be configured to listen for S3 events (e.g., PutObject) and then invoke a Lambda function that starts the SageMaker Pipeline execution. Step Functions could orchestrate the pipeline but is not needed to trigger on S3 events. SageMaker Pipelines does not natively listen to S3 events.

CloudWatch Events is the older name for EventBridge.

Full explanation →

737

Multi-Selectmedium

A data scientist wants to bring a custom PyTorch model to SageMaker. Which THREE methods are valid?

Select 3 answers

A.Use SageMaker Autopilot

B.Use the built-in Image Classification algorithm

C.Use Script mode with the PyTorch Estimator

D.Create a custom Docker container and use the BYOC framework

E.Use the PyTorch Estimator with a script

AnswersC, D, E

Full explanation →

738

Multi-Selecthard

An ML engineer is designing a SageMaker Pipeline for model training and registration. They need to ensure that the pipeline can be re-run with different datasets without manual intervention, and that the steps are only re-executed if inputs have changed. Which THREE features should they configure? (Select THREE.)

Select 3 answers

A.Add a Condition step to manually check for data changes

B.Enable step caching to reuse outputs when inputs are unchanged

C.Configure lineage tracking to record the origin of models

D.Use Parameterized execution to pass different values at runtime

E.Define pipeline parameters for dataset location and hyperparameters

AnswersB, D, E

Why this answer

Pipeline parameters allow passing different inputs. Step caching reuses step outputs when inputs are identical. Using Parameterized execution is synonymous with using parameters.

Lineage tracking is not for skipping steps. Condition steps are for branching, not caching. Model Registry is for versioning.

Full explanation →

739

MCQhard

Refer to the exhibit. A data scientist runs a SageMaker training job with the above configuration. The training completes but the model performance is poor. Which change to the hyperparameters is most likely to improve the model's AUC?

A.Increase max_depth to 10

B.Increase subsample to 1.0

C.Increase num_round to 200

D.Decrease eta to 0.1

AnswerD

A lower learning rate improves generalization by taking smaller steps, often yielding better AUC.

Why this answer

The training job uses XGBoost with default hyperparameters that likely cause overfitting or poor generalization. Decreasing eta (learning rate) to 0.1 slows down the learning process, allowing the model to converge more smoothly and reduce overfitting, which directly improves AUC on unseen data. This is a standard regularization technique in gradient boosting.

Exam trap

The MLA-C01 exam often tests the misconception that increasing model complexity (depth, rounds, or sample usage) always improves performance, when in fact regularization techniques like lowering the learning rate are more effective for fixing poor AUC caused by overfitting.

How to eliminate wrong answers

Option A is wrong because increasing max_depth to 10 makes trees deeper, which increases model complexity and risk of overfitting, likely worsening AUC on validation data. Option B is wrong because increasing subsample to 1.0 means using all training samples per tree, removing the regularization benefit of row subsampling and increasing overfitting risk. Option C is wrong because increasing num_round to 200 adds more boosting iterations without adjusting learning rate, which can lead to overfitting and degraded generalization, especially with default eta.

Full explanation →

740

MCQhard

An ML engineer is fine-tuning a large language model using LoRA on SageMaker. The training is converging slowly, and GPU utilization is low. The engineer suspects the bottleneck is data loading. Which action should the engineer take to improve GPU utilization?

A.Increase the batch size to maximize GPU memory usage

B.Enable checkpointing and use spot instances

C.Use SageMaker Pipe mode to stream data from S3 directly to the training instances

D.Reduce model parallelism to decrease communication overhead

AnswerC

Pipe mode reduces I/O latency by streaming data, which can improve GPU utilization.

Why this answer

Low GPU utilization during training is often due to a data pipeline bottleneck. Using SageMaker Pipe mode streams data directly from S3, reducing I/O wait times. Increasing batch size may improve utilization but can cause OOM.

Using spot instances and saving checkpoints helps with interruptions but not utilization. Reducing model parallelism may help if communication is the bottleneck, but the scenario suggests data loading.

Full explanation →

741

Multi-Selecthard

A data engineer is optimizing Amazon Athena queries on large datasets stored in S3 for machine learning data preparation. Which THREE practices improve query performance?

Select 3 answers

A.Partition the data by a frequently filtered column, such as date

B.Use uncompressed CSV files for simplicity

C.Partition the data by every column to maximize filtering

D.Store data in columnar formats like Parquet or ORC

E.Compress the data with Snappy or gzip

AnswersA, D, E

Partition pruning limits scanned data.

Why this answer

Partitioning by a frequently filtered column, such as date, allows Athena to use partition pruning. When a query includes a filter on the partition column, Athena can skip entire directories of data in S3, drastically reducing the amount of data scanned and improving query performance while also lowering cost.

Exam trap

AWS often tests the misconception that more partitions always improve performance, but in reality, over-partitioning leads to metastore overhead and small file problems that degrade query performance.

Full explanation →

742

MCQeasy

Refer to the exhibit. A user has the above IAM policy attached but cannot access files in SageMaker Studio. What additional permission is most likely needed?

A.sagemaker:ListApps

B.s3:GetObject on the relevant S3 buckets

C.sagemaker:DescribeUserProfile

D.kms:Decrypt

AnswerB

To read files in Studio, the user must have S3 access permissions.

Why this answer

The IAM policy shown likely grants permissions for SageMaker API actions (e.g., CreateApp, DescribeDomain) but does not include S3 data plane permissions. SageMaker Studio notebooks and experiments read training data, scripts, and model artifacts from S3 buckets. Without s3:GetObject on the relevant S3 buckets, the user can launch the Studio environment but cannot load or save any files, resulting in access failures.

Exam trap

The MLA-C01 exam often tests the distinction between SageMaker control plane permissions (e.g., CreateApp, DescribeUserProfile) and data plane permissions (e.g., S3 GetObject), leading candidates to focus on SageMaker-specific actions when the real blocker is S3 access.

How to eliminate wrong answers

Option A is wrong because sagemaker:ListApps is a read-only API used to list apps within a domain, but it does not grant access to file contents in Studio; the inability to access files is a data plane issue, not a listing issue. Option C is wrong because sagemaker:DescribeUserProfile returns metadata about the user profile (e.g., domain ARN, status) but does not authorize reading or writing files in the Studio file system or S3. Option D is wrong because kms:Decrypt is needed only if the S3 buckets or Studio EFS volumes use customer-managed KMS keys; the question does not indicate encryption at rest with a custom key, so this is not the most likely missing permission.

Full explanation →

743

MCQeasy

A machine learning engineer needs to deploy a TensorFlow model to Amazon SageMaker and wants to use the built-in TensorFlow Serving container. What should the engineer provide in the model archive?

A.A frozen graph of the TensorFlow model.

B.A tar.gz file containing the TensorFlow SavedModel.

C.Model artifacts and a Python inference script.

D.A Dockerfile and model artifacts.

AnswerB

SageMaker's TensorFlow serving container expects a SavedModel packaged as tar.gz.

Why this answer

The built-in TensorFlow Serving container in Amazon SageMaker expects a TensorFlow SavedModel packaged in a tar.gz archive. This is because TensorFlow Serving natively loads models from the SavedModel format, which includes the model's computational graph, weights, and assets in a standardized directory structure. Providing a tar.gz of the SavedModel ensures compatibility with the container's default serving stack without requiring custom inference code.

Exam trap

AWS often tests the misconception that a frozen graph (Option A) is sufficient for TensorFlow Serving, but the exam expects candidates to know that TensorFlow Serving specifically requires the SavedModel format with its directory structure, not just a single protobuf file.

How to eliminate wrong answers

Option A is wrong because a frozen graph (typically a .pb file) is a legacy TensorFlow format that lacks the full SavedModel structure (e.g., variables and assets), and TensorFlow Serving does not natively support frozen graphs as a direct input; it requires the SavedModel format. Option C is wrong because a Python inference script is unnecessary when using the built-in TensorFlow Serving container, which handles inference automatically via the SavedModel; custom scripts are only needed for bring-your-own-container scenarios. Option D is wrong because a Dockerfile is not part of the model archive; SageMaker's built-in containers are pre-built, and providing a Dockerfile would indicate a custom container approach, which contradicts the requirement to use the built-in TensorFlow Serving container.

Full explanation →

744

MCQhard

A financial services company is building a fraud detection model using transactional data stored in Amazon S3. The data includes transaction_id, timestamp, amount, merchant_category, and fraud_label (0/1). The data is collected from multiple sources and has inconsistencies: timestamps are in different timezones (UTC and EST), merchant categories are sometimes misspelled (e.g., 'RESTAURANT', 'Restaurant', 'restaurant'), and the fraud_label is missing for about 5% of records. The data science team uses AWS Glue for ETL. They need to prepare a clean dataset for training. The final dataset must have consistent timestamps in UTC, standardized merchant categories, and no missing fraud labels. The team also wants to minimize data loss. Which set of actions should the team take?

A.Use AWS Glue to convert all timestamps to UTC, apply a mapping function to correct merchant category misspellings to a standard list, and drop records with missing fraud_label.

B.Use AWS Glue to convert timestamps to UTC, use a fuzzy matching algorithm to standardize merchant categories, and replace missing fraud_label with the mean value (0.05).

C.Use AWS Glue to convert timestamps to UTC, correct merchant categories by mapping known misspellings to correct names, and drop records with missing fraud_label.

D.Use AWS Glue to convert timestamps to UTC, use a mapping table to group similar merchant categories (e.g., all restaurant variants to 'Restaurant'), and impute missing fraud_label using mode (most frequent value).

AnswerD

Mode imputation preserves the majority class and avoids data loss, while timestamp conversion and category mapping clean the data correctly.

Why this answer

It preserves data by imputing missing fraud labels using the mode (most frequent value), which is appropriate for a binary classification label where the majority class is likely 0. It also standardizes timestamps to UTC and uses a mapping table to group merchant category variants, ensuring consistency without data loss. Dropping records (as in A and C) would reduce the dataset size, and imputing with the mean (as in B) is invalid for a categorical label.

Exam trap

The trap here is that candidates often choose to drop missing values (options A and C) to avoid imputation complexity, not realizing that minimizing data loss is explicitly stated as a requirement, and that mode imputation is a standard technique for categorical labels in ML pipelines.

How to eliminate wrong answers

Option A is wrong because dropping records with missing fraud_label causes unnecessary data loss (5% of records) when imputation is feasible, and the mapping function for merchant categories is vague and not standardized. Option B is wrong because replacing missing fraud_label with the mean (0.05) is inappropriate for a binary categorical variable; mean imputation can introduce fractional values that are meaningless for classification. Option C is wrong because dropping records with missing fraud_label again causes data loss, and correcting merchant categories by mapping known misspellings is less robust than using a mapping table to group all variants, which better handles unseen misspellings.

Full explanation →

745

Multi-Selecteasy

A company wants to deploy its trained model to edge devices such as cameras and IoT devices. The model must run efficiently with low latency and minimal memory footprint. Which THREE actions should the company take to prepare the model for edge deployment? (Choose THREE.)

Select 3 answers

A.Use SageMaker Edge Manager to package and manage the model on devices.

B.Quantize the model to reduce precision and memory footprint.

C.Increase the model's complexity to improve accuracy on edge devices.

D.Use SageMaker Neo to compile the model for the target edge hardware.

E.Deploy the model directly as a SageMaker endpoint and have the edge devices call it over the internet.

AnswersA, B, D

Edge Manager provides tools for model packaging, deployment, and monitoring on edge.

Why this answer

SageMaker Edge Manager is purpose-built to package, optimize, and manage machine learning models on edge devices. It provides model packaging, runtime monitoring, and over-the-air updates, ensuring the model runs efficiently with low latency and minimal memory footprint on resource-constrained hardware like cameras and IoT devices.

Exam trap

AWS often tests the misconception that edge deployment can rely on cloud endpoints for inference, but the correct approach is to optimize and run the model locally on the device to achieve low latency and offline operation.

Full explanation →

746

MCQhard

A machine learning practitioner is building a binary classifier with severe class imbalance (1:1000). They want to use SMOTE for oversampling. What is a potential drawback of applying SMOTE on the entire dataset before splitting into training and test sets?

A.SMOTE increases the risk of overfitting to the minority class

B.SMOTE cannot be applied to categorical features

C.It causes data leakage, making validation metrics overly optimistic

D.SMOTE generates synthetic samples that may not be realistic

AnswerC

Generating synthetic samples before splitting leaks information from the test set into the training set.

Why this answer

Applying SMOTE before splitting causes data leakage because synthetic samples are generated using information from both training and test sets, leading to overly optimistic performance estimates.

Full explanation →

747

MCQmedium

A team is training a large language model and needs to split the model layers across multiple GPUs due to memory constraints. Which distributed training strategy should they use?

A.Data parallelism

B.Hyperparameter tuning

C.Autopilot

D.Model parallelism

AnswerD

Full explanation →

748

MCQmedium

A data scientist is training a linear learner model using SageMaker and notices that the loss is not decreasing. They suspect the issue is exploding gradients. Which SageMaker Debugger rule should they enable to monitor this?

A.LossNotDecreasing

B.ExplodingGradients

C.VanishingGradients

D.Overfit

AnswerB

Monitors for gradients that become excessively large.

Why this answer

The ExplodingGradients rule tracks gradient values and alerts if they exceed a threshold, which is the correct detection for exploding gradients.

Full explanation →

749

Multi-Selectmedium

A team is migrating their ML infrastructure to AWS and wants to use infrastructure as code to manage SageMaker Studio domains, user profiles, and associated resources. Which services can they use for this purpose? (Select THREE.)

Select 3 answers

A.AWS CDK (Cloud Development Kit)

B.SageMaker Python SDK

C.Boto3

D.Terraform by HashiCorp

E.AWS CloudFormation

AnswersA, D, E

CDK allows defining infrastructure using programming languages and synthesizes CloudFormation templates.

Why this answer

AWS CDK (Cloud Development Kit) is correct because it allows you to define AWS infrastructure, including SageMaker Studio domains and user profiles, using familiar programming languages like Python or TypeScript. CDK synthesizes these definitions into CloudFormation templates, enabling infrastructure as code (IaC) for SageMaker resources. This approach provides type safety and high-level abstractions, making it suitable for managing complex ML environments.

Exam trap

The trap here is that candidates often confuse the SageMaker Python SDK (used for ML workflows) or Boto3 (used for general AWS API calls) with infrastructure as code tools, but neither provides declarative, state-managed provisioning of SageMaker Studio resources like CloudFormation, CDK, or Terraform do.

Full explanation →

750

Multi-Selectmedium

A team is training a deep learning model on Amazon SageMaker using a custom Docker container. Which three practices should they follow to optimize training performance? (Choose three.)

Select 3 answers

A.Store training data in Amazon S3 in a shuffled and compressed format

B.Use the largest instance type available

C.Increase the number of layers in the model to improve accuracy

D.Use SageMaker Managed Spot Training with checkpointing

E.Use Pipe mode to stream data instead of File mode

AnswersA, D, E

Shuffling prevents bias and compression reduces transfer time, improving training performance.

Why this answer

Storing training data in Amazon S3 in a shuffled and compressed format (Option A) optimizes training performance because shuffling prevents biased gradient updates during stochastic gradient descent, while compression reduces I/O overhead and network transfer time. SageMaker's Pipe mode can then stream this compressed data directly to the training algorithm without intermediate disk writes, further accelerating throughput.

Exam trap

AWS often tests the misconception that bigger instances always mean faster training, but the real optimization lies in data pipeline efficiency (e.g., Pipe mode, compression, and shuffling) and cost management (e.g., Managed Spot Training with checkpointing).

Full explanation →

Page 10 of 12

All pages

1 2 3 4 5 6 7 8 9 10 11 12

Practice MLA-C01 by domain

Target a specific domain to shore up weak areas.

ML Model Development Data Preparation for Machine Learning Deployment and Orchestration of ML Workflows ML Solution Monitoring, Maintenance, and Security

See all domains with question counts →