Knowledge + Practice

AWS Certified Machine Learning Engineer Associate MLA-C01 (MLA-C01) — Questions 751–825

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

Take a mock exam Exam hub

Page 11 of 12

751

MCQmedium

A company uses SageMaker Model Monitor to detect bias drift in their real-time inference endpoint. They have collected ground truth labels and want to monitor for bias across different demographic groups. Which type of monitoring should they configure?

A.SageMaker Model Monitor – Feature Attribution Drift Monitoring

B.SageMaker Clarify – Bias Drift Monitoring

C.SageMaker Model Monitor – Model Quality Monitoring

D.SageMaker Model Monitor – Data Quality Monitoring

AnswerB

Clarify's bias drift monitoring uses ground truth labels to compute bias metrics for demographic groups.

Why this answer

SageMaker Clarify offers post-deployment bias monitoring that uses ground truth labels to compute bias metrics (e.g., difference in positive outcome rates) over time.

Full explanation →

752

MCQmedium

An ML team is preparing time-series data for a demand forecasting model. They want to evaluate model performance over time without leaking future information into past training windows. Which data splitting strategy is MOST appropriate?

A.Random k-fold cross-validation

B.Single hold-out set with random selection

C.Stratified sampling based on the target variable

D.Walk-forward validation with an expanding window

AnswerD

Walk-forward validation trains on past data and tests on immediate future data, respecting temporal dependencies.

Why this answer

Walk-forward validation with an expanding window is the most appropriate strategy because it respects the temporal order of the data, ensuring that each training window contains only past observations and each validation window contains only future observations. This prevents data leakage and provides a realistic evaluation of how the model will perform on unseen future time steps, which is critical for demand forecasting.

Exam trap

The trap here is that candidates often default to random k-fold cross-validation (Option A) because it is a standard technique for i.i.d. data, forgetting that time-series data requires strict temporal ordering to avoid data leakage.

How to eliminate wrong answers

Option A is wrong because random k-fold cross-validation shuffles the data before splitting, which can place future observations in the training set and past observations in the validation set, causing temporal data leakage and invalidating the time-series evaluation. Option B is wrong because a single hold-out set with random selection also ignores the temporal order, potentially mixing future data into the training set and leading to overly optimistic performance estimates. Option C is wrong because stratified sampling based on the target variable does not account for the sequential dependency in time-series data; it preserves the distribution of the target but can still break the temporal ordering, allowing future information to leak into past training windows.

Full explanation →

753

Multi-Selecthard

An ML engineer is designing a SageMaker Pipeline for a computer vision model. The pipeline includes steps for data processing, training, evaluation, and registration. The engineer wants to enable caching to avoid reprocessing when step inputs have not changed. For which steps is caching supported? (Select TWO.)

Select 2 answers

A.Processing step

B.Transform step

C.Condition step

D.Lambda step

E.RegisterModel step

AnswersA, B

Processing steps support caching.

Why this answer

Caching is supported for the following step types: Processing, Training, Tuning, Transform, and AutoML. Condition steps and Lambda steps do not support caching because they are control flow steps.

Full explanation →

754

MCQeasy

A data scientist is preparing a dataset for training a binary classification model. The dataset has 100,000 rows and 50 features. The target variable is imbalanced, with only 5% positive cases. Which technique should the data scientist apply to address the class imbalance BEFORE training?

A.Principal Component Analysis (PCA) dimensionality reduction

B.Random oversampling of the minority class

C.Standard scaling of numerical features

D.One-hot encoding of categorical variables

AnswerB

Random oversampling is a valid technique to balance classes by replicating minority samples.

Why this answer

Random oversampling of the minority class (Option B) directly addresses the class imbalance by duplicating examples from the positive class until the class distribution is more balanced. This prevents the binary classification model from being biased toward the majority class, which is critical when only 5% of the 100,000 rows are positive cases. Oversampling is applied before training to ensure the model sees sufficient minority examples during learning.

Exam trap

AWS often tests whether candidates confuse data preprocessing techniques (scaling, encoding, dimensionality reduction) with methods that directly modify the class distribution, leading them to pick a plausible but irrelevant option like PCA or scaling.

How to eliminate wrong answers

Option A is wrong because PCA dimensionality reduction reduces the number of features but does not alter the class distribution; it would not fix the 5% imbalance and could even discard variance useful for separating the minority class. Option C is wrong because standard scaling normalizes numerical feature ranges but has no effect on the ratio of positive to negative samples; it addresses feature magnitude, not class imbalance. Option D is wrong because one-hot encoding converts categorical variables into binary columns but does not change the target variable's distribution; it is a preprocessing step for feature representation, not for balancing classes.

Full explanation →

755

MCQhard

During deployment of a Hugging Face model, the endpoint logs show this error. Which step was likely missed?

A.The inference container does not include the transformers library; the team should use a pre-built Hugging Face container.

B.The IAM role does not have permissions to download additional libraries.

C.The model artifact was not packaged correctly; the inference script is missing.

D.The endpoint configuration specifies the wrong instance type.

AnswerA

Hugging Face containers are pre-built with transformers and other dependencies.

Why this answer

The error indicates that the inference container cannot find the `transformers` library, which is required to load and run the Hugging Face model. By using a pre-built Hugging Face container from AWS, the team ensures that all necessary dependencies (like `transformers`, `tokenizers`, and `torch`) are pre-installed and compatible with the SageMaker inference environment. Option A is correct because the most likely missed step was selecting a generic container instead of the purpose-built Hugging Face container.

Exam trap

The trap here is that candidates confuse runtime dependency issues (missing Python libraries) with infrastructure or configuration problems (IAM permissions, instance types, or packaging), leading them to select a plausible-sounding but incorrect option like B or C.

How to eliminate wrong answers

Option B is wrong because IAM role permissions control access to AWS services (e.g., S3, ECR) and cannot prevent the container from downloading Python libraries at runtime; missing libraries are a container image issue, not an IAM issue. Option C is wrong because the error message specifically mentions a missing Python module (`transformers`), not a missing inference script or packaging error; if the inference script were missing, the error would be about a missing entry point or handler function. Option D is wrong because the instance type affects compute capacity and pricing, not the availability of Python libraries inside the container; an incorrect instance type would cause resource errors (e.g., memory or GPU), not an `ImportError`.

Full explanation →

756

MCQmedium

A company is training a deep learning model on Amazon SageMaker. The training job started but has been stuck in 'InProgress' state for an unusually long time with low CPU utilization. The data scientist suspects a bottleneck. What should be the first troubleshooting step?

A.Switch the training job to use Spot instances to reduce cost and potentially improve throughput.

B.Increase the number of training instances to parallelize data loading.

C.Stop and restart the training job with a different instance type.

D.Review CloudWatch Logs for the training container to identify errors or warnings.

AnswerD

Logs often show the exact cause of hanging, such as waiting for data or resource constraints.

Why this answer

When a SageMaker training job is stuck in 'InProgress' with low CPU utilization, the most common cause is a bottleneck in data loading or preprocessing within the training container. Reviewing CloudWatch Logs for the training container is the first troubleshooting step because it provides direct visibility into container-level errors, warnings, or stalls (e.g., hanging on a file read, waiting for a dependency, or a misconfigured data channel) that would not be visible from instance-level metrics alone.

Exam trap

The trap here is that candidates often jump to scaling or instance changes (Options B and C) without first checking logs, assuming a performance issue is hardware-related when it is almost always a software or configuration issue inside the container.

How to eliminate wrong answers

Option A is wrong because switching to Spot instances does not address a bottleneck causing low CPU utilization; Spot instances can be interrupted and may introduce additional latency, not resolve a stuck training job. Option B is wrong because increasing the number of training instances does not fix a bottleneck within a single container (e.g., a stuck data loader) and may even compound the issue by adding coordination overhead. Option C is wrong because stopping and restarting with a different instance type is a premature escalation; it does not diagnose the root cause and may waste time if the issue is software-related (e.g., a bug in the training script) rather than hardware-related.

Full explanation →

757

MCQmedium

A team notices that inference requests to their SageMaker endpoint are failing with '504 Gateway Timeout' for large payloads. What change should be made?

A.Enable data capture on the endpoint

B.Increase the endpoint's invocation timeout

C.Deploy a shadow endpoint for testing

D.Switch to a multi-model endpoint

AnswerB

Increasing the invocation timeout allows more time for large payloads to be processed.

Why this answer

A 504 Gateway Timeout indicates that the SageMaker endpoint's invocation timeout (default 60 seconds) was exceeded while processing a large payload. Increasing the invocation timeout allows the endpoint more time to complete inference for large payloads, resolving the timeout error.

Exam trap

The trap here is that candidates confuse a 504 timeout with a 413 payload too large error, leading them to incorrectly consider multi-model endpoints or data capture instead of adjusting the invocation timeout.

How to eliminate wrong answers

Option A is wrong because enabling data capture logs inference requests and responses but does not affect the endpoint's timeout behavior or ability to handle large payloads. Option C is wrong because deploying a shadow endpoint is used for A/B testing or canary deployments, not for resolving timeout issues on the existing endpoint. Option D is wrong because switching to a multi-model endpoint improves resource utilization for multiple models but does not change the per-invocation timeout limit.

Full explanation →

758

MCQmedium

A machine learning engineer needs to prepare a dataset containing customer transactions for training a fraud detection model. The dataset includes features such as transaction amount, timestamp, merchant category, and customer ID. The engineer wants to create a feature representing the average transaction amount per customer over the last 7 days. Which approach should be used in Amazon SageMaker Data Wrangler?

A.Write a custom PySpark SQL query in a SQL transform that uses the `AVG` window function partitioned by customer ID and ordered by timestamp with a range between 7 days preceding and current row

B.Export the data to Amazon SageMaker Feature Store and use point-in-time queries with a 7-day lookback

C.Use the built-in 'Aggregate' transform with a group-by on customer ID and average of transaction amount

D.Use the 'Handle Missing' transform to fill missing values with the mean transaction amount

AnswerA

This computes the exact rolling average per customer over a 7-day window, which is the requirement.

Why this answer

SageMaker Data Wrangler supports custom SQL queries via PySpark SQL, which can compute windowed aggregations like a rolling average partitioned by customer ID over a time window. This is the most direct and scalable approach.

Full explanation →

759

MCQhard

A financial services company is deploying a fraud detection model on SageMaker. To comply with regulations, they must ensure that the model's predictions are not biased against protected groups. They plan to monitor bias drift post-deployment using SageMaker Clarify. Which data inputs are required to configure Clarify's bias drift monitoring?

A.Only the inference data with predictions

B.Only the ground truth labels for recent predictions

C.Only the training data with feature attributions

D.Baseline training data with ground truth labels and inference data with predictions

AnswerD

Clarify bias monitoring requires a baseline dataset (training data with labels) and current inference data (with predictions and ground truth when available) to compute bias metrics over time.

Why this answer

SageMaker Clarify's bias drift monitoring requires a baseline—specifically, the training data with ground truth labels—to establish the original bias metrics, and the inference data with predictions to compute post-deployment bias metrics. By comparing these two datasets, Clarify detects statistically significant shifts in bias over time, which is essential for regulatory compliance in fraud detection models.

Exam trap

The trap here is that candidates often assume only inference data is needed for monitoring, overlooking the critical requirement of a baseline training dataset with ground truth labels to measure drift against.

How to eliminate wrong answers

Option A is wrong because inference data with predictions alone lacks a baseline for comparison, making it impossible to measure drift from the original model behavior. Option B is wrong because ground truth labels for recent predictions, without a baseline training dataset, cannot establish the initial bias metrics needed for drift detection. Option C is wrong because training data with feature attributions, while useful for explainability, does not include the inference data with predictions required to compute post-deployment bias metrics.

Full explanation →

760

MCQmedium

A company deploys a model on Amazon SageMaker for real-time inference. The inference latency is too high. The model is a large deep learning model. The company wants to reduce latency without significantly impacting accuracy. Which approach should the company consider?

A.Increase the batch size for inference.

B.Use a smaller instance type to reduce inference time.

C.Use SageMaker Inference Recommender to test different instance types and optimizations.

D.Enable SageMaker Model Monitor to detect performance issues.

AnswerC

Inference Recommender helps find the optimal configuration for low latency.

Why this answer

SageMaker Inference Recommender is designed specifically to automate load testing and benchmarking across various instance types and model optimizations (e.g., Elastic Inference, GPU acceleration, serialization formats). It provides latency and throughput metrics to identify the optimal configuration for reducing inference latency while maintaining accuracy, making it the correct choice for a large deep learning model with high latency.

Exam trap

AWS often tests the misconception that reducing instance size or increasing batch size directly reduces latency, when in fact these actions typically increase latency or degrade throughput for real-time inference.

How to eliminate wrong answers

Option A is wrong because increasing batch size typically increases throughput but also increases per-request latency, as the model must process more data before returning results, which is counterproductive for real-time inference. Option B is wrong because using a smaller instance type generally reduces computational capacity, leading to longer inference times and higher latency, not lower. Option D is wrong because SageMaker Model Monitor is for detecting data drift, model quality degradation, and bias over time, not for optimizing inference performance or reducing latency.

Full explanation →

761

Multi-Selecthard

A data scientist is cleaning a text dataset for natural language processing. The raw data contains HTML tags, URLs, and special characters. Which THREE steps should be taken to preprocess the text data? (Choose 3.)

Select 3 answers

A.Convert all text to lowercase

B.Encode the text using one-hot encoding

C.Remove HTML tags using a regular expression

D.Perform stemming or lemmatization

E.Remove stop words

AnswersA, C, D

Lowercasing standardizes text and reduces vocabulary size.

Why this answer

Converting all text to lowercase (Option A) is a standard text normalization step in NLP preprocessing. It reduces the vocabulary size by treating words like 'Apple' and 'apple' as the same token, which helps downstream models avoid treating case variations as distinct features. This is typically done early in the pipeline before tokenization or vectorization.

Exam trap

AWS often tests the distinction between preprocessing steps that clean raw data (like removing HTML tags and normalizing case) versus later feature engineering steps (like encoding or stop word removal), causing candidates to mistakenly select stop word removal as a cleaning step when it is actually a filtering step applied after tokenization.

Full explanation →

762

Multi-Selecthard

A data scientist is building a text classification model using Amazon SageMaker. The dataset is stored as a CSV file in Amazon S3. The scientist wants to use the SageMaker built-in BlazingText algorithm. Which of the following steps are required to prepare the data for training? (Choose TWO.)

Select 2 answers

A.Convert the text to one-hot encoded vectors.

B.Tokenize and remove stop words from the text.

C.Convert the CSV file to the format of a single file with one instance per line.

D.Upload the data to an Amazon SageMaker notebook instance.

E.Ensure each line in the training file contains a single text instance with the label prefixed by '__label__'.

AnswersC, E

BlazingText expects a single file with one instance per line.

Why this answer

BlazingText expects input data in a single file where each line represents one training instance. This is a specific requirement of the algorithm's input format, not a general SageMaker practice. The CSV file must be converted to this line-per-instance format for BlazingText to process it correctly.

Exam trap

The trap here is that candidates assume general NLP preprocessing (like tokenization or stop word removal) is always required, but BlazingText is designed to handle raw text and expects a specific line format, not preprocessed vectors.

Full explanation →

763

MCQeasy

A company wants to reduce costs for a SageMaker real-time endpoint that receives predictable traffic patterns: high during business hours and low at night. The model is a small PyTorch model. Which cost-saving strategy is most suitable?

A.Use a single large instance to handle peak load

B.Use a multi-model endpoint with multiple models

C.Configure auto-scaling with a scheduled scaling policy to add instances during business hours and reduce at night

D.Switch to batch transform jobs and run nightly

AnswerC

Matches capacity to predictable demand, minimizing cost.

Why this answer

Auto-scaling with a schedule can adjust instance count based on time, matching capacity to demand. This is more efficient than manual scaling or using a larger instance.

Full explanation →

764

MCQmedium

A machine learning engineer needs to ingest streaming data from thousands of IoT devices into Amazon S3 for batch training. The data should be available in S3 within minutes of arrival. Which combination of services should the engineer use?

A.Amazon Kinesis Data Streams and Amazon Kinesis Data Firehose

B.AWS IoT Core and Amazon DynamoDB Streams

C.Amazon SQS and AWS Lambda

D.Amazon Kinesis Data Analytics and AWS Glue ETL

AnswerA

Kinesis Data Streams ingests high-throughput data; Kinesis Data Firehose buffers and delivers data to S3 within minutes.

Why this answer

Amazon Kinesis Data Streams ingests and stores streaming data from thousands of IoT devices durably, while Amazon Kinesis Data Firehose automatically delivers that data to Amazon S3 with near-real-time latency (typically 60–90 seconds). This combination provides the required buffering, scaling, and direct S3 integration without custom code, meeting the 'within minutes' requirement for batch training data.

Exam trap

The trap here is that candidates often choose AWS IoT Core (Option B) because it seems IoT-specific, but they overlook that IoT Core does not natively stream data into S3 with low latency—it requires an additional integration like Kinesis or Lambda, making the direct Kinesis Data Streams + Firehose pipeline the correct and simpler choice.

How to eliminate wrong answers

Option B is wrong because AWS IoT Core and DynamoDB Streams are designed for device connectivity and change-data-capture on DynamoDB tables, not for high-throughput streaming ingestion into S3; DynamoDB Streams has a 24-hour retention limit and cannot directly write to S3. Option C is wrong because Amazon SQS with AWS Lambda would require custom code to buffer and batch records into S3, and SQS does not natively support the partitioning or compression needed for efficient S3 writes at scale. Option D is wrong because Amazon Kinesis Data Analytics is for real-time SQL or Flink-based analytics on streams, not for ingestion, and AWS Glue ETL is a batch processing service that cannot directly consume streaming data without an intermediate streaming source.

Full explanation →

765

MCQeasy

Which technique is commonly used to handle missing values in a categorical feature?

A.One-hot encoding

B.Mean imputation

C.Mode imputation

D.Standard scaling

AnswerC

Mode imputation replaces missing categorical values with the most frequent category, a common practice.

Why this answer

Mode imputation is the standard technique for handling missing values in categorical features because it replaces missing entries with the most frequent category, preserving the feature's distribution without introducing artificial values. Unlike numerical imputation methods, mode imputation respects the non-numeric nature of categorical data and maintains the integrity of the original categories.

Exam trap

The MLA-C01 exam often tests the distinction between data preprocessing techniques (imputation) and feature engineering techniques (encoding, scaling), leading candidates to mistakenly select one-hot encoding as a missing-value handler because it is commonly associated with categorical data.

How to eliminate wrong answers

Option A is wrong because one-hot encoding is a technique for converting categorical variables into a binary matrix representation, not a method for handling missing values; applying it to missing data would create spurious dummy columns. Option B is wrong because mean imputation is designed for numerical features and would produce non-integer, non-categorical values that are invalid for a categorical feature, distorting the data type. Option D is wrong because standard scaling is a normalization technique for numerical features that centers and scales data to zero mean and unit variance, which is meaningless and inapplicable to categorical data.

Full explanation →

766

MCQhard

An MLOps engineer is building an automated retraining pipeline for a fraud detection model. The model must be retrained weekly, and the new model should only be promoted to production if it meets predefined performance thresholds compared to the current model. Which combination of SageMaker capabilities should the engineer use?

A.Amazon SageMaker Debugger and Amazon SageMaker Clarify

B.Amazon SageMaker Model Monitor and Amazon SageMaker Ground Truth

C.Amazon SageMaker Autopilot and Amazon SageMaker Experiments

D.Amazon SageMaker Pipelines and Amazon SageMaker Model Registry

AnswerD

Pipelines orchestrate the workflow, Model Registry manages model versions and approvals.

Why this answer

Amazon SageMaker Pipelines provides the orchestration for the automated retraining workflow (including weekly scheduling and conditional logic), while SageMaker Model Registry enables versioning, approval, and promotion of models based on performance thresholds. Together, they allow the engineer to define a pipeline that trains a new model, evaluates it against the current production model, and only registers it for deployment if it meets the predefined criteria.

Exam trap

AWS often tests the distinction between monitoring tools (Model Monitor, Debugger) and orchestration/registry services (Pipelines, Model Registry), so the trap here is that candidates may confuse Model Monitor's drift detection with the need for a retraining pipeline, overlooking that the question specifically requires automated retraining and conditional promotion.

How to eliminate wrong answers

Option A is wrong because SageMaker Debugger monitors training metrics and detects anomalies (e.g., vanishing gradients), but it does not orchestrate retraining pipelines or manage model promotion. SageMaker Clarify is used for bias detection and feature importance, not for automated retraining workflows. Option B is wrong because SageMaker Model Monitor detects data drift in production, not for retraining orchestration, and SageMaker Ground Truth is a labeling service for creating training datasets, not for pipeline automation or model promotion.

Option C is wrong because SageMaker Autopilot automates model building (feature engineering, algorithm selection) but does not provide pipeline orchestration or model registry capabilities for conditional promotion; SageMaker Experiments tracks trial runs but lacks the workflow automation and approval gates needed for this use case.

Full explanation →

767

Multi-Selecthard

A machine learning team is building a product recommendation system. They have a dataset with millions of users and thousands of products. The team wants to reduce the dimensionality of the user-product interaction matrix while preserving as much variance as possible. Which THREE techniques are appropriate for dimensionality reduction? (Choose THREE.)

Select 3 answers

A.Lasso regularization

B.Mutual information feature selection

C.Principal Component Analysis (PCA)

D.t-Distributed Stochastic Neighbor Embedding (t-SNE)

E.Singular Value Decomposition (SVD)

AnswersC, D, E

PCA reduces dimensions by projecting onto principal components that capture maximum variance.

Why this answer

PCA, SVD, and t-SNE are common dimensionality reduction techniques. PCA and SVD are linear methods that maximize variance. t-SNE is non-linear and good for visualization. Lasso is for feature selection, not matrix factorization.

Mutual information is for feature selection, not reduction.

Full explanation →

768

MCQmedium

A data scientist is training an XGBoost model on a large dataset using a SageMaker Training Job. They want to minimize costs without sacrificing model performance. Which instance type and training strategy should they choose?

A.Use a single ml.g4dn.xlarge Spot instance with no distributed training

B.Use a single ml.m5.large On-Demand instance with model parallelism

C.Use multiple ml.trn1.2xlarge On-Demand instances with data parallelism

D.Use a single ml.p3.2xlarge On-Demand instance with data parallelism

AnswerA

Spot instances drastically reduce cost; single instance avoids parallelism overhead for XGBoost.

Why this answer

Using Spot instances with Managed Spot Training can reduce costs by up to 90% compared to On-Demand, and SageMaker automatically handles interruptions. For single-instance training, a single ml.g4dn.xlarge provides sufficient compute for moderate-sized datasets.

Full explanation →

769

MCQmedium

A team has deployed a real-time inference endpoint and wants to automatically scale based on CPU utilization. Which scaling policy type should they use with Application Auto Scaling for SageMaker endpoints?

A.Target tracking scaling

B.Step scaling

C.Predictive scaling

D.Simple scaling

AnswerA

Target tracking scaling automatically maintains a target metric value, such as average CPU utilization.

Why this answer

Target tracking scaling adjusts the number of instances based on a target metric value (e.g., CPU utilization at 50%). Step scaling uses step adjustments, and simple scaling is deprecated. Predictive scaling is not supported for SageMaker endpoints.

Full explanation →

770

MCQmedium

A company uses Amazon SageMaker to train and deploy a machine learning model. After deployment, they notice that the model's accuracy drops significantly over time due to changes in the underlying data distribution. Which monitoring solution should they implement to detect this issue automatically?

A.Set up Amazon SageMaker Model Monitor with data quality monitoring.

B.Configure AWS Config rules to check the model accuracy metric.

C.Use AWS CloudTrail to monitor changes to the model's S3 bucket.

D.Enable Amazon CloudWatch Logs on the endpoint and set alarms on inference latency.

AnswerA

SageMaker Model Monitor automatically detects drift in data quality and model quality.

Why this answer

Amazon SageMaker Model Monitor with data quality monitoring is the correct solution because it automatically detects deviations in the input data distribution compared to a baseline, which directly addresses the problem of model accuracy degradation due to data drift. It continuously monitors the statistical properties of inference requests and alerts when drift is detected, enabling proactive retraining.

Exam trap

The trap here is confusing operational monitoring (latency, logs, API activity) with data quality monitoring, leading candidates to pick options that track infrastructure or performance rather than the underlying data distribution that causes model decay.

How to eliminate wrong answers

Option B is wrong because AWS Config rules are designed for compliance and resource configuration auditing (e.g., checking if encryption is enabled), not for monitoring real-time model performance metrics like accuracy. Option C is wrong because AWS CloudTrail tracks API calls and user activity, not data distribution changes; monitoring S3 bucket changes would not detect shifts in the data distribution of inference requests. Option D is wrong because CloudWatch Logs and alarms on inference latency measure performance (e.g., response time), not data quality or model accuracy; latency issues are unrelated to data drift.

Full explanation →

771

MCQeasy

A team uses SageMaker for training. They need to monitor training progress and view metrics like loss and accuracy. Which SageMaker feature should they use?

A.SageMaker Ground Truth

B.SageMaker Debugger

C.SageMaker Model Monitor

D.SageMaker Experiments

AnswerB

Debugger can output tensors and metrics during training for real-time monitoring.

Why this answer

SageMaker Debugger is the correct feature because it provides real-time monitoring of training metrics such as loss and accuracy, along with the ability to set alerts and capture tensors for debugging. It integrates directly with the SageMaker training loop, allowing users to visualize metrics via the SageMaker Studio UI or retrieve them programmatically without additional infrastructure.

Exam trap

The trap here is that candidates confuse SageMaker Experiments (which tracks and compares runs) with real-time monitoring, but Experiments is post-hoc analysis, not live metric streaming during training.

How to eliminate wrong answers

Option A is wrong because SageMaker Ground Truth is a data labeling service for creating training datasets, not for monitoring training progress or metrics. Option C is wrong because SageMaker Model Monitor is designed for detecting drift in deployed model endpoints (e.g., feature or prediction drift), not for monitoring live training metrics like loss and accuracy. Option D is wrong because SageMaker Experiments is used for tracking and comparing multiple training runs, hyperparameters, and results, but it does not provide real-time monitoring of metrics during training; it focuses on experiment organization and analysis after runs complete.

Full explanation →

772

MCQeasy

A data scientist is preparing a dataset for a binary classification model. The dataset has 10,000 records with 100 features. The target variable is imbalanced, with 95% negative class and 5% positive class. Which data preparation step should the data scientist take to address the imbalance before training?

A.Normalize all features to a 0-1 range

B.Use cross-validation to handle imbalance

C.Remove enough instances of the negative class to achieve balance

D.Apply SMOTE to oversample the positive class

AnswerD

SMOTE generates synthetic samples for the minority class, effectively balancing the dataset.

Why this answer

SMOTE (Synthetic Minority Oversampling Technique) generates synthetic samples for the minority class (positive class, 5%) by interpolating between existing minority instances. This addresses the severe class imbalance (95:5) without discarding data, allowing the model to learn decision boundaries for the minority class more effectively than simple duplication.

Exam trap

AWS often tests the misconception that any data preprocessing step (like normalization or cross-validation) can fix class imbalance, when in fact only resampling techniques (oversampling, undersampling, or synthetic generation) directly alter the class distribution.

How to eliminate wrong answers

Option A is wrong because normalizing features to a 0-1 range addresses feature scaling, not class imbalance; it does not change the class distribution. Option B is wrong because cross-validation is a model evaluation technique that helps assess performance but does not modify the training data to correct imbalance; it would still train on the imbalanced dataset. Option C is wrong because removing instances of the negative class (random undersampling) discards potentially valuable data, which can lead to loss of information and reduced model performance, especially when the negative class represents 95% of the data.

Full explanation →

773

MCQmedium

A team has 200 small ML models that need to be served via HTTPS endpoints. Each model is used infrequently, and the team wants to minimize hosting costs. Which SageMaker deployment approach is MOST cost-effective?

A.Use SageMaker Serverless Inference for each model

B.Deploy each model on a separate real-time endpoint

C.Use Batch Transform for all models

D.Use a single multi-model endpoint (MME)

AnswerD

MME dynamically loads models from Amazon S3 onto shared instances, minimizing cost for many infrequently used models.

Why this answer

Multi-model endpoints (MME) allow hosting multiple models on a single endpoint, sharing instances and reducing costs, especially for infrequently used models.

Full explanation →

774

MCQmedium

A machine learning team uses SageMaker Pipelines to automate retraining. They want to avoid re-running data processing steps if the data has not changed since the last successful pipeline run. Which built-in feature should they enable?

A.Pipeline caching

B.Model lineage tracking

C.Parameterized pipeline executions

D.Step parallelism

AnswerA

Caching reuses step outputs when inputs and configuration haven't changed, avoiding redundant processing.

Why this answer

Pipeline caching is the correct choice because SageMaker Pipelines can cache the outputs of each step based on a hash of the step's input parameters, configuration, and code. If the hash matches a previous successful run, the cached output is reused, avoiding redundant execution of data processing steps when the underlying data hasn't changed.

Exam trap

The trap here is that candidates confuse lineage tracking (Option B) with caching, assuming that tracking data versions automatically prevents re-execution, when in fact lineage only records history without affecting pipeline execution behavior.

How to eliminate wrong answers

Option B is wrong because model lineage tracking (via SageMaker ML Lineage Tracking) records the relationships between data, models, and training jobs, but it does not prevent re-running steps; it only provides auditability and provenance. Option C is wrong because parameterized pipeline executions allow you to pass different input values at runtime, but they do not automatically skip unchanged steps—caching is required for that. Option D is wrong because step parallelism controls the concurrency of step execution within a pipeline, not the reuse of previous outputs.

Full explanation →

775

Multi-Selectmedium

A company uses SageMaker Model Monitor to detect data drift. They want to receive alerts when drift is detected and automatically trigger a retraining pipeline. Which TWO steps should they implement? (Select TWO.)

Select 2 answers

A.Configure Model Monitor to directly invoke a SageMaker Pipeline when drift is detected

B.Configure a SageMaker Processing job to run periodically and check drift

C.Set up an SNS subscription that triggers a Lambda function to start the SageMaker Pipeline

D.Create a CloudWatch Alarm on the data quality violation metric that publishes to an SNS topic

E.Create an EventBridge rule that triggers on Model Monitor drift events to start the pipeline

AnswersC, D

Lambda function subscribed to SNS can start the pipeline programmatically.

Why this answer

Amazon SNS can be used to publish a notification when Model Monitor detects data drift, and a Lambda function subscribed to that SNS topic can invoke the SageMaker Pipeline to trigger retraining. This decouples the monitoring from the pipeline execution, allowing for flexible, event-driven automation. Option D is correct because Model Monitor emits CloudWatch metrics for data quality violations, and you can create a CloudWatch Alarm on those metrics to publish to an SNS topic, which can then trigger a retraining pipeline via Lambda or other integrations.

Exam trap

The trap here is that candidates may think Model Monitor can directly trigger pipelines or emit EventBridge events, but in reality it relies on CloudWatch metrics and SNS for downstream automation.

Full explanation →

776

MCQmedium

A model deployed on a SageMaker endpoint is returning predictions. The team wants to log all predictions to an S3 bucket for auditing. What is the most efficient way to achieve this?

A.Enable SageMaker endpoint data capture to the S3 bucket.

B.Configure CloudWatch Logs to export to S3.

C.Modify the inference code to write logs to S3.

D.Use Amazon Kinesis Data Firehose to stream predictions to S3.

AnswerA

Data capture is built-in and efficient.

Why this answer

SageMaker endpoint data capture is the native, most efficient way to log predictions to S3 because it automatically captures input payloads and output predictions for all requests to the endpoint, storing them directly in the specified S3 bucket without any custom code or additional infrastructure. This feature is designed specifically for auditing and monitoring, requiring only a DataCaptureConfig to be set on the endpoint.

Exam trap

The trap here is that candidates overcomplicate the solution by choosing a streaming or custom logging approach (like Kinesis or code modification), not realizing that SageMaker provides a built-in, zero-code feature (Data Capture) specifically designed for this auditing requirement.

How to eliminate wrong answers

Option B is wrong because CloudWatch Logs export to S3 is a batch process (e.g., via ExportTask) that exports logs after they are generated, not a real-time or efficient solution for capturing individual predictions; it also adds latency and cost for log storage and export. Option C is wrong because modifying inference code to write logs to S3 introduces unnecessary complexity, potential performance overhead from S3 PUT operations per request, and violates the principle of using managed services; it also requires custom error handling and retry logic. Option D is wrong because Amazon Kinesis Data Firehose is an over-engineered solution for this use case—it adds a streaming layer, additional cost, and latency, whereas SageMaker data capture directly writes to S3 with minimal overhead and is purpose-built for this exact scenario.

Full explanation →

777

MCQhard

A data scientist observes that a linear regression model has many irrelevant features. They want to perform feature selection to improve generalization. Which method combines feature selection with model training using a penalty that can shrink coefficients to zero?

A.Ridge regression

B.Lasso regression

C.Recursive Feature Elimination (RFE)

D.Principal Component Analysis (PCA)

AnswerB

Lasso's L1 penalty forces some coefficients to exactly zero, enabling feature selection.

Why this answer

Lasso regression uses L1 regularization to shrink coefficients to zero, effectively performing feature selection.

Full explanation →

778

MCQhard

An AWS IAM policy is attached to a role used by a CI/CD pipeline to deploy SageMaker endpoints. The policy includes: - An Allow statement for sagemaker:CreateEndpointConfig on all resources. - A Deny statement for sagemaker:CreateEndpoint on all resources with a condition that the VPC subnet must not equal subnet-0123456789abcdef0 (StringNotEquals on ec2:Subnet). The pipeline attempts to create an endpoint configuration with a VPC subnet that is not subnet-0123456789abcdef0. What will happen when the pipeline tries to create the endpoint configuration?

A.The action will be denied because the Deny statement explicitly blocks CreateEndpointConfig when the subnet does not match.

B.The action will be allowed because the CreateEndpoint statement allows all endpoints.

C.The action will be allowed only if the endpoint configuration uses a VPC with multiple subnets.

D.The action will be allowed because the policy lacks a Deny on the subnet condition for the endpoint resource.

AnswerD

Without an explicit Deny on the specific subnet condition for CreateEndpointConfig, the action is allowed if an Allow statement exists. The default IAM behavior is to deny, but if there is an Allow without a restricting condition that fails, the action is permitted. The policy lacks a Deny, so the request is allowed.

Why this answer

The policy has an explicit Allow for sagemaker:CreateEndpointConfig without any conditions, so the action is allowed. The Deny statement applies only to sagemaker:CreateEndpoint, not to CreateEndpointConfig. Therefore, even if the subnet does not match, the CreateEndpointConfig request is allowed.

Option D is correct because the policy lacks a Deny on the subnet condition for the endpoint configuration resource.

Exam trap

Candidates may mistakenly think the Deny statement applies to all SageMaker actions, but it explicitly targets CreateEndpoint. The subnet condition only affects CreateEndpoint, leaving CreateEndpointConfig unrestricted.

How to eliminate wrong answers

Option B is wrong because the policy contains a Deny statement that explicitly restricts the subnet condition for `CreateEndpointConfig`, so the Allow on `CreateEndpoint` does not override the Deny; IAM Deny statements always take precedence. Option C is wrong because the policy does not grant any special permission for multiple subnets; the Deny condition applies regardless of the number of subnets used. Option D is wrong because the policy does include a Deny on the subnet condition for the `sagemaker:CreateEndpointConfig` action, not for the endpoint resource, so the action is blocked.

Full explanation →

779

MCQmedium

A team is training a large deep learning model on SageMaker using a single ml.p3.16xlarge instance. Training is taking too long. They want to reduce time by distributing across multiple GPUs but are constrained by model size that does not fit in a single GPU memory. Which distributed training strategy should they use?

A.Data parallelism using SageMaker distributed data parallelism

B.Switch to a smaller instance type and use horizontal scaling

C.Use multiple training jobs with hyperparameter tuning

D.Model parallelism using SageMaker distributed model parallelism

AnswerD

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

Why this answer

Model parallelism splits the model across multiple GPUs, which is needed when the model does not fit in a single GPU. Data parallelism replicates the model on each GPU and splits data, which requires the model to fit in each GPU's memory.

Full explanation →

780

MCQhard

A machine learning team is processing a large dataset in Amazon SageMaker using a processing job. The data is stored in S3 in CSV format. The team wants to split the data into training, validation, and test sets (70/20/10) while ensuring that the distribution of a categorical feature 'region' is preserved across splits. Which SageMaker SDK method should they use to write the output?

A.Use sagemaker.sklearn.processing.SKLearnProcessor with a script that uses sklearn's StratifiedShuffleSplit

B.Use sagemaker.xgboost.processing.XGBoostProcessor with a script that uses random split

C.Use sagemaker.processing.Processor.run() with a custom script that uses train_test_split

D.Use sagemaker.processing.FrameworkProcessor with a script that uses pandas.sample

AnswerA

StratifiedShuffleSplit ensures the 'region' distribution is maintained across splits.

Why this answer

`SKLearnProcessor` allows you to run a custom Python script that uses `sklearn.model_selection.StratifiedShuffleSplit`, which preserves the distribution of the categorical 'region' feature across the training, validation, and test splits. This is the only option that directly supports stratified splitting within a SageMaker processing job, ensuring the 70/20/10 ratio while maintaining class balance.

Exam trap

The trap here is that candidates often confuse generic processing methods (like `Processor.run()` or `FrameworkProcessor`) with the specific processor that supports stratified splitting, or they assume `train_test_split` with a random state is sufficient for preserving categorical distributions, ignoring the need for stratification.

How to eliminate wrong answers

Option B is wrong because `XGBoostProcessor` is designed for XGBoost-specific preprocessing (e.g., converting CSV to libsvm) and does not natively support stratified splitting or custom scripts for data partitioning. Option C is wrong because `Processor.run()` is a generic method that executes a processing job, but it does not provide built-in stratified splitting; using `train_test_split` alone would perform a random split, not preserving the 'region' distribution. Option D is wrong because `FrameworkProcessor` is a generic base class for custom frameworks, and `pandas.sample` performs random sampling without stratification, failing to maintain the categorical feature distribution across splits.

Full explanation →

781

MCQmedium

A healthcare company is building a model to predict patient readmission rates. The dataset contains a mix of numeric features (age, blood pressure, lab test results) and categorical features (gender, diagnosis code, hospital department). The dataset has 2 million rows. The data is stored in an Amazon S3 bucket, and they use AWS Glue to catalog and preprocess the data. The data scientist notices that the 'diagnosis_code' column has 10,000 unique codes, and 20% of the rows have missing values for 'blood_pressure'. They plan to use a SageMaker built-in XGBoost model. For optimal model performance, which preprocessing steps should they apply using AWS Glue ETL?

A.Impute missing 'blood_pressure' with the mean, and apply label encoding to 'diagnosis_code'.

B.Impute missing 'blood_pressure' with median, and apply integer encoding to 'diagnosis_code'.

C.Replace missing 'blood_pressure' with -1 and apply one-hot encoding to 'diagnosis_code' after grouping rare codes into 'other'.

D.Apply one-hot encoding to 'diagnosis_code' and drop rows with missing 'blood_pressure'.

AnswerB

Median is robust; integer encoding is sufficient for tree-based models like XGBoost.

Why this answer

XGBoost handles missing values natively, so median imputation for 'blood_pressure' is robust to outliers and preserves data distribution, while integer encoding (label encoding) for 'diagnosis_code' with 10,000 unique values is efficient and avoids the dimensionality explosion of one-hot encoding. AWS Glue ETL can apply these transformations using built-in functions like `Imputer` and `StringIndexer` without excessive memory overhead.

Exam trap

The trap here is that candidates overestimate the need for one-hot encoding with high-cardinality categorical features, forgetting that tree-based models like XGBoost can effectively use integer encoding, and they may also default to mean imputation without considering outlier sensitivity.

How to eliminate wrong answers

Option A is wrong because mean imputation for 'blood_pressure' is sensitive to outliers, which can skew the model, and label encoding is a form of integer encoding but the term 'label encoding' often implies ordinal mapping that may introduce unintended ordinal relationships; however, the primary flaw is the mean imputation choice. Option C is wrong because replacing missing 'blood_pressure' with -1 introduces an arbitrary value that XGBoost may misinterpret as a valid numeric pattern, and one-hot encoding 'diagnosis_code' with 10,000 categories (even after grouping rare codes) still creates a very high-dimensional sparse matrix that degrades performance and increases memory usage in Glue ETL. Option D is wrong because dropping 20% of rows with missing 'blood_pressure' leads to significant data loss and potential bias, and one-hot encoding 'diagnosis_code' with 10,000 categories is computationally prohibitive and unnecessary for tree-based models like XGBoost.

Full explanation →

782

Multi-Selectmedium

A company deploys a model on SageMaker that serves predictions to a web application. The model's performance degrades over time due to data drift. The company wants to set up continuous monitoring. Which TWO actions should the company take to monitor and retrain the model effectively? (Choose TWO.)

Select 2 answers

A.Manually review model performance monthly and retrain if necessary.

B.Configure an Amazon EventBridge rule to start a retraining pipeline when the Model Monitor detects violations.

C.Enable SageMaker Model Monitor to capture inference data and run monitoring schedules.

D.Use Amazon CloudWatch Logs Insights to query inference logs for anomalies.

E.Deploy the model on multiple endpoints with A/B testing to compare performance.

AnswersB, C

EventBridge can react to Model Monitor violation events to trigger automatic retraining.

Why this answer

Amazon EventBridge can be configured to trigger a retraining pipeline automatically when SageMaker Model Monitor detects data drift or other violations, enabling a closed-loop monitoring and retraining system. Option C is correct because SageMaker Model Monitor must first be enabled to capture inference data and run monitoring schedules, which is the prerequisite for detecting drift and triggering automated actions.

Exam trap

The trap here is that candidates may confuse general monitoring tools like CloudWatch Logs Insights with the specialized, model-aware monitoring capabilities of SageMaker Model Monitor, or they may overlook that EventBridge automation requires Model Monitor to be enabled first.

Full explanation →

783

Multi-Selectmedium

A company is using AWS Step Functions to orchestrate their ML retraining pipeline. They want to trigger retraining when new data arrives, but only if the model's performance has degraded below a threshold. Which THREE AWS services should they use together to achieve this? (Choose three.)

Select 3 answers

A.AWS Step Functions

B.AWS Lambda

C.Amazon EventBridge

D.Amazon CloudWatch Logs

E.SageMaker Model Registry

AnswersA, B, C

Step Functions orchestrates the retraining pipeline.

Why this answer

A solution: Amazon EventBridge detects S3 events (new data), invokes a Lambda function that checks model performance (e.g., via SageMaker Model Monitor or custom metrics), and then starts a Step Functions workflow if degradation is detected. The other services: SageMaker Pipelines could replace Step Functions but is not listed as an option; SageMaker Model Monitor can track performance but is not an event source; CloudWatch Logs is not directly involved in the trigger logic.

Full explanation →

784

MCQmedium

Your company uses SageMaker batch transform to process a large dataset (5 TB) of customer transactions every night. The batch transform job uses a single ml.c5.4xlarge instance and takes about 6 hours to complete. However, the job recently started failing with an error message: 'Timed out waiting for transformation to complete. The maximum job duration is 3600 seconds.' You check the input data and notice that one of the input files is a single large JSON file of 50 GB, while the rest are smaller files. The job is configured with a batch strategy of 'MultiRecord' and a maximum payload size of 6 MB. What is the most likely cause of the timeout and which fix should you apply?

A.Set the batch strategy to 'SingleRecord' so that each record is processed individually.

B.Split the large JSON file into smaller files (e.g., 100 MB each) before feeding to the batch transform job.

C.Increase the job timeout to 7200 seconds.

D.Increase the number of instances to 5 in the batch transform job.

AnswerB

SageMaker batch transform splits input on file boundaries; small files allow parallel processing and stay within time limits.

Why this answer

The batch transform job is timing out because the single 50 GB JSON file cannot be processed within the default 3600-second (1-hour) timeout. With a 'MultiRecord' batch strategy and a 6 MB maximum payload size, SageMaker must split the large file into many small batches, but the job still tries to read the entire file sequentially, causing excessive processing time. Splitting the large file into smaller files (e.g., 100 MB each) allows SageMaker to parallelize and complete the transform within the timeout.

Exam trap

AWS often tests the misconception that increasing instances or timeout alone can solve performance bottlenecks caused by a single large input file, when in fact SageMaker batch transform processes each file on a single instance and requires file-level splitting for parallelism.

How to eliminate wrong answers

Option A is wrong because setting the batch strategy to 'SingleRecord' would process each record individually, which would increase the number of API calls and likely worsen the timeout issue, not resolve it. Option C is wrong because increasing the job timeout to 7200 seconds only masks the underlying problem of the oversized file; the job may still fail due to resource constraints or eventually hit other limits. Option D is wrong because increasing the number of instances does not help when a single massive file cannot be split across instances—SageMaker batch transform assigns each file to a single instance, so the 50 GB file would still be processed by one instance, causing the same timeout.

Full explanation →

785

MCQmedium

A company is deploying a large number of small models (each < 100 MB) for different customers. They want to minimize costs and management overhead while serving traffic that varies significantly. Which SageMaker endpoint type should they choose?

A.A batch transform job

B.A multi-model endpoint on a GPU instance

C.A multi-variant endpoint to route traffic to different model versions

D.A serverless endpoint

AnswerB

MME allows hosting many models on one instance, reducing costs.

Why this answer

A multi-model endpoint (MME) on a GPU instance is the best choice because it allows you to host multiple small models (< 100 MB each) on a single endpoint, sharing the underlying GPU instance to reduce costs. SageMaker MME dynamically loads and unloads models based on traffic, which minimizes management overhead and handles variable traffic patterns efficiently without provisioning separate endpoints per model.

Exam trap

The trap here is that candidates confuse 'multi-model endpoint' (hosting many models on one endpoint) with 'multi-variant endpoint' (routing traffic to different versions of the same model), leading them to select option C incorrectly.

How to eliminate wrong answers

Option A is wrong because batch transform jobs are designed for offline, asynchronous inference on large datasets, not for serving real-time traffic that varies significantly. Option C is wrong because a multi-variant endpoint is used to route traffic between different versions (variants) of the same model for A/B testing or gradual rollouts, not to host multiple distinct models per customer. Option D is wrong because serverless endpoints automatically scale to zero but have a maximum payload size of 6 MB and a maximum invocation duration of 60 seconds, making them unsuitable for GPU-accelerated inference or models that require GPU instances.

Full explanation →

786

Multi-Selecthard

Which TWO tools are specifically designed for debugging and analyzing training jobs in SageMaker?

Select 2 answers

A.SageMaker Autopilot

B.SageMaker Experiments

C.SageMaker Debugger

D.SageMaker Clarify

E.SageMaker Model Monitor

AnswersB, C

Experiments organizes training runs for analysis and comparison.

Why this answer

SageMaker Debugger is specifically designed to monitor and debug training jobs by capturing tensors, gradients, and other metrics in real time, while SageMaker Experiments tracks and analyzes training job parameters, metrics, and artifacts for comparison and reproducibility. Both tools directly address debugging and analysis of training jobs, unlike the other options which focus on automation, bias detection, or inference monitoring.

Exam trap

The MLA-C01 exam often tests the distinction between tools that operate during training (Debugger, Experiments) versus those for inference (Model Monitor) or automation (Autopilot), leading candidates to mistakenly select Clarify for debugging when it is actually for bias and explainability.

Full explanation →

787

MCQhard

A data scientist is using Amazon SageMaker Debugger to monitor training metrics. They want to stop training automatically if the model is overfitting. Which action should they take?

A.Define a Debugger rule that monitors the loss plateau

B.Configure a custom rule that triggers a STOP training action when validation loss stops decreasing

C.Create a SageMaker Training Compiler

D.Use a built-in rule that checks for vanishing gradients

AnswerB

A custom rule can monitor validation loss and stop training when it plateaus or increases, indicating overfitting.

Why this answer

SageMaker Debugger allows you to define custom rules that can invoke a STOP training action when a specified condition is met, such as validation loss ceasing to decrease. This enables automatic termination of a training job to prevent overfitting, as the model is no longer improving on unseen data.

Exam trap

The trap here is that candidates confuse monitoring for overfitting with monitoring for convergence or training stability, leading them to select a built-in rule (like vanishing gradients or loss plateau) that does not directly trigger a STOP action for overfitting.

How to eliminate wrong answers

Option A is wrong because monitoring a loss plateau (e.g., training loss flattening) does not specifically detect overfitting; it could indicate convergence, and Debugger's built-in loss plateau rule does not trigger a STOP action by default. Option C is wrong because SageMaker Training Compiler is designed to accelerate training through optimized graph compilation and memory management, not to monitor or stop training based on overfitting. Option D is wrong because the built-in rule for vanishing gradients checks for gradient explosion or vanishing, which is a training stability issue, not a direct indicator of overfitting.

Full explanation →

788

MCQeasy

Which SageMaker feature provides AutoML capabilities, including automatic data preprocessing, model selection, and hyperparameter tuning?

A.SageMaker Data Wrangler

B.SageMaker Automatic Model Tuning

C.SageMaker Autopilot

D.SageMaker Experiments

AnswerC

Autopilot automates the entire ML workflow.

Why this answer

SageMaker Autopilot automates the ML pipeline from data to model, including preprocessing, algorithm selection, and tuning.

Full explanation →

789

Multi-Selectmedium

A company uses SageMaker Pipelines to automate their ML workflow. They need to add model versioning and approval workflow. Which THREE steps should they include in their pipeline to achieve this? (Choose THREE.)

Select 3 answers

A.RegisterModel step

B.Training step

C.Condition step

D.Processing step for evaluation

E.Transform step

AnswersA, C, D

This step creates a new model version in the Model Registry.

Why this answer

The RegisterModel step is correct because it creates a model package in SageMaker Model Registry, which enables versioning and approval workflows. This step registers the trained model artifact along with metadata, allowing the pipeline to track model versions and trigger approval processes for deployment.

Exam trap

The trap here is that candidates may think the Training step alone suffices for versioning, but AWS explicitly separates model training from model registration, requiring the RegisterModel step for registry integration.

Full explanation →

790

MCQeasy

A data engineer notices that an AWS Glue ETL job is failing with an Out of Memory error when processing a large dataset. The dataset is 500 GB in size, and the worker type is G.1X. Which change is MOST likely to resolve the issue?

A.Partition the input data into smaller files

B.Use a Spark DataFrame instead of RDD

C.Increase the number of workers

D.Use a larger worker type like G.2X

AnswerD

G.2X provides double the memory of G.1X, resolving the OOM.

Why this answer

The G.1X worker type provides 16 GB of memory per worker. A 500 GB dataset requires sufficient aggregate memory across workers for processing. Increasing the worker type to G.2X (which doubles memory to 32 GB per worker) increases the memory per executor, allowing each task to handle larger data partitions without running out of memory.

This directly addresses the Out of Memory error by providing more heap space for Spark operations.

Exam trap

The trap here is that candidates often assume adding more workers (scaling out) always solves memory issues, but the real bottleneck is per-executor memory, which is only addressed by using a larger worker type (scaling up).

How to eliminate wrong answers

Option A is wrong because partitioning input data into smaller files does not increase the available memory per worker; it only changes how data is read and may reduce parallelism but does not resolve an OOM caused by insufficient executor memory. Option B is wrong because using a Spark DataFrame instead of RDD does not inherently reduce memory usage; DataFrames use Catalyst optimizer and Tungsten execution for better performance, but they still operate within the same memory constraints and will OOM if memory per worker is insufficient. Option C is wrong because increasing the number of workers distributes the data across more executors but does not increase the memory per executor; if each executor still has only 16 GB, a single large partition or shuffle operation can still cause OOM on an individual executor.

Full explanation →

791

Multi-Selectmedium

Which THREE components are required to set up automated model retraining in response to performance degradation using Amazon SageMaker? (Select THREE.)

Select 3 answers

A.An Amazon SNS topic with a subscription to send a manual approval email.

B.A CloudWatch alarm that triggers when a quality metric falls below a threshold.

C.A SageMaker Model Monitor schedule to capture inference data and compute quality metrics.

D.An AWS Lambda function that starts a SageMaker training job or pipeline execution.

E.A production variant with a canary traffic shift configuration.

AnswersB, C, D

The alarm detects degradation and triggers the retraining.

Why this answer

A CloudWatch alarm can monitor a SageMaker Model Monitor quality metric (e.g., accuracy, precision) and trigger an alarm when the metric falls below a defined threshold. This alarm acts as the event source to initiate automated retraining, forming the monitoring and alerting backbone of the retraining pipeline.

Exam trap

The trap here is that candidates often confuse the monitoring and alerting components (CloudWatch alarm and Model Monitor) with deployment or notification mechanisms, mistakenly selecting manual approval (SNS) or traffic shifting (canary) as part of the automated retraining workflow.

Full explanation →

792

MCQhard

A financial services company deploys a fraud detection model with a SageMaker endpoint. They need to ensure that all data sent to the endpoint is encrypted in transit and at rest, and that the endpoint cannot be accessed from the public internet. Which combination of settings should they use?

A.Use endpoint data encryption with an AWS managed key and enable public endpoint access

B.Enable inter-container traffic encryption and disable VPC-only mode

C.Enable VPC-only mode, inter-container traffic encryption, and use a KMS key for endpoint encryption

D.Deploy the endpoint in a private subnet without SageMaker VPC-only mode

AnswerC

VPC-only isolates the endpoint; inter-container encryption secures traffic; KMS encrypts data at rest.

Why this answer

VPC-only mode ensures the endpoint is private. Inter-container traffic encryption is needed for data in transit between containers in multi-model endpoints. KMS encryption secures data at rest on the instance storage.

Full explanation →

793

MCQmedium

A data science team has trained a PyTorch model using Amazon SageMaker and wants to deploy it with a custom inference container that includes a pre-processing step. The team needs to minimize latency and ensure the pre-processing runs only once per request. Which SageMaker real-time inference option should they use?

A.Deploy the model on a multi-model endpoint and include pre-processing in the model code.

B.Use a batch transform job with a pre-processing script.

C.Package pre-processing and inference in a single container with a custom entry point.

D.Create a SageMaker inference pipeline with two containers: one for pre-processing and one for inference.

AnswerD

An inference pipeline chains containers sequentially, allowing pre-processing to run once per request with low latency.

Why this answer

A SageMaker inference pipeline allows you to chain two containers in a single endpoint, where the first container handles pre-processing and the second runs inference. This ensures that pre-processing runs exactly once per request, minimizing latency by avoiding redundant processing and keeping the request within the same HTTP connection.

Exam trap

AWS often tests the distinction between a single-container approach (Option C) and a multi-container pipeline (Option D), where candidates mistakenly think a single custom container is simpler and sufficient, but the pipeline is required to guarantee that pre-processing runs exactly once per request and to allow independent scaling or updates of the pre-processing logic.

How to eliminate wrong answers

Option A is wrong because a multi-model endpoint hosts multiple models on the same container, but it does not support a separate pre-processing step; any pre-processing would be embedded in the model code and run per model load, not once per request, and it cannot guarantee a separate container for pre-processing. Option B is wrong because a batch transform job is designed for asynchronous, offline processing of large datasets, not for real-time inference with low latency requirements. Option C is wrong because packaging pre-processing and inference in a single container with a custom entry point runs both steps sequentially per request, but it does not leverage SageMaker's built-in pipeline orchestration, and if the pre-processing logic changes, the entire container must be rebuilt, whereas a pipeline allows independent updates.

Full explanation →

794

MCQmedium

A data scientist is building a regression model to predict house prices. The dataset contains a feature 'neighborhood' with 500 distinct values, and most neighborhoods have fewer than 10 samples. Which approach is MOST appropriate for handling this high-cardinality categorical feature?

A.Drop the neighborhood feature entirely

B.Apply frequency encoding, replacing each neighborhood with its count in the training set

C.One-hot encode the feature and use L1 regularization

D.Use target encoding with proper cross-validation to avoid data leakage

AnswerD

Target encoding effectively captures the relationship between categories and target, and cross-validation prevents overfitting.

Why this answer

Target encoding replaces each category with the mean target value, which is effective for high-cardinality features while maintaining predictive power. One-hot encoding would create too many sparse columns, and label encoding would impose an arbitrary ordinal relationship.

Full explanation →

795

MCQeasy

A company has 50 small PyTorch models that are used infrequently for inference. They want to minimize costs while maintaining the ability to serve all models from a single endpoint. Which SageMaker feature should they use?

A.Multi-container endpoint

B.Batch transform job

C.Real-time endpoint with 50 production variants

D.Multi-model endpoint

AnswerD

MME hosts many models on one endpoint, loading each model on demand. Ideal for many small, infrequently used models.

Why this answer

Multi-model endpoints (MME) allow hosting multiple models on a single endpoint, loading models dynamically based on the target model in the request. This reduces cost for many small, infrequently used models by sharing the underlying instance.

Full explanation →

796

MCQmedium

A machine learning engineer needs to select features for a regression model. The dataset contains 50 numeric features, and the target variable is continuous. The engineer wants to reduce dimensionality by selecting features that have the strongest linear relationship with the target. Which feature selection method is MOST appropriate?

A.Lasso regularization

B.Correlation analysis

C.Mutual information

D.Recursive feature elimination (RFE)

AnswerB

Correlation analysis directly measures linear correlation (e.g., Pearson's r) between each feature and the target, making it ideal for selecting linearly related features.

Why this answer

Correlation analysis (e.g., Pearson correlation) measures the linear relationship between each feature and the target. Features with high absolute correlation can be selected. Mutual information captures non-linear relationships but is more appropriate when non-linear relationships are expected.

Recursive feature elimination and Lasso are valid but more computationally expensive for initial screening.

Full explanation →

797

MCQeasy

Which SageMaker built-in algorithm is designed for time series forecasting?

A.Linear Learner

B.Factorisation Machines

C.DeepAR

D.BlazingText

AnswerC

Full explanation →

798

Multi-Selectmedium

A data scientist is evaluating a binary classification model. They have the confusion matrix and want to assess the model's performance comprehensively. Which THREE metrics should they consider? (Select THREE.)

Select 3 answers

A.Precision

B.RMSE

C.Recall

D.F1 score

E.R²

AnswersA, C, D

Precision measures the accuracy of positive predictions.

Full explanation →

799

Multi-Selecthard

A team is using Amazon SageMaker Ground Truth to build a labeled dataset for a multi-class classification task. They have a small budget and want to reduce labeling costs. Which THREE features or strategies should they use? (Select THREE.)

Select 3 answers

A.Enable active learning to select the most informative samples

B.Use a pre-built annotation workflow for image classification

C.Use a private workforce with domain expertise

D.Use a public workforce (Mechanical Turk) for all labeling

E.Label all data manually without automation

AnswersA, B, C

Active learning reduces the number of samples needed for labeling.

Why this answer

Active learning in SageMaker Ground Truth automatically selects the most informative or uncertain samples from the unlabeled dataset to be sent for human labeling. By focusing labeling effort on these high-value data points, the team can achieve a high-quality model with significantly fewer labeled examples, directly reducing labeling costs.

Exam trap

The trap here is that candidates often assume using a public workforce (Mechanical Turk) is always cheaper, but the question specifically asks for cost-reduction strategies, and a private workforce with domain expertise reduces rework and per-label costs, while active learning and pre-built workflows directly minimize the number of labels needed.

Full explanation →

800

Multi-Selecteasy

A data science team is deploying a model on Amazon SageMaker and wants to protect the endpoint from unauthorized access. Which TWO methods can the team use to secure the endpoint? (Choose TWO.)

Select 2 answers

A.Configure the endpoint to be deployed within a VPC and control traffic using security groups and network ACLs.

B.Use a resource-based IAM policy on the endpoint to restrict invocation.

C.Place an Amazon API Gateway in front of the endpoint with AWS WAF.

D.Attach a security group directly to the SageMaker endpoint.

E.Use an IAM policy that requires authentication for the sagemaker:InvokeEndpoint action.

AnswersA, E

Deploying inside a VPC allows network-level access control.

Why this answer

Deploying a SageMaker endpoint within a VPC allows you to control inbound and outbound traffic using security groups and network ACLs, effectively restricting network-level access to the endpoint. This is a fundamental network security measure that prevents unauthorized network traffic from reaching the endpoint.

Exam trap

The trap here is that candidates often confuse resource-based IAM policies (which are not supported for SageMaker endpoints) with identity-based policies, or they assume that attaching a security group directly to an endpoint is possible without deploying it in a VPC.

Full explanation →

801

MCQmedium

A machine learning engineer is training a model using SageMaker and wants to set up monitoring to detect if gradients become too large, which could destabilize training. Which SageMaker Debugger built-in rule should they enable?

A.DeadRelu

B.LossNotDecreasing

C.Overfit

D.ExplodingGradients

AnswerD

ExplodingGradients rule detects when gradients become too large.

Why this answer

Debugger's built-in rule 'ExplodingGradients' monitors gradient norms and alerts if they exceed a threshold, helping to stabilize training.

Full explanation →

802

MCQmedium

A company is using Amazon SageMaker to train a large deep learning model. The training job is taking a very long time. The data scientist suspects that the GPU utilization is low due to inefficient data loading. Which action should the data scientist take to diagnose and address this issue?

A.Switch to a CPU-only instance to reduce overhead.

B.Check GPU utilization using Amazon CloudWatch metrics, and if low, optimize the data loading pipeline by using Pipe mode or faster data formats.

C.Reduce the batch size to speed up training.

D.Increase the number of GPUs in the training instance.

AnswerB

Monitoring GPU utilization and optimizing data loading addresses the bottleneck.

Why this answer

Low GPU utilization during deep learning training often indicates a data loading bottleneck, where the GPU spends cycles waiting for data. Amazon CloudWatch provides GPU utilization metrics for SageMaker training jobs, and if utilization is low, optimizing the data pipeline with Pipe mode (streaming data directly from Amazon S3) or using faster data formats like RecordIO or TFRecord can reduce I/O overhead and keep the GPU busy.

Exam trap

The trap here is that candidates often assume adding more GPUs or reducing batch size will speed up training, but without addressing the data pipeline bottleneck, these changes can actually worsen GPU utilization and training time.

How to eliminate wrong answers

Option A is wrong because switching to a CPU-only instance would eliminate GPU acceleration entirely, making training even slower, and does not address the root cause of inefficient data loading. Option C is wrong because reducing the batch size typically decreases GPU utilization further, as the GPU processes fewer samples per step, increasing the relative overhead of data loading and model synchronization. Option D is wrong because increasing the number of GPUs does not fix a data loading bottleneck; it can actually exacerbate the issue by requiring even more data to be fed to multiple GPUs, potentially lowering per-GPU utilization further.

Full explanation →

803

MCQhard

A financial services company needs to deploy a SageMaker endpoint that only accepts inference requests from within a specific VPC and denies all public traffic. The endpoint must also encrypt data in transit between containers. How should the endpoint be configured?

A.Deploy the endpoint in a public subnet and restrict security group ingress to the VPC CIDR

B.Enable VPC-only mode for the endpoint and disable public access

C.Use a privateLink endpoint and enable data encryption at rest

D.Configure the endpoint with network isolation mode and enable inter-container traffic encryption

AnswerD

Network isolation blocks public internet access; inter-container traffic encryption secures data in transit between containers.

Why this answer

Enabling network isolation mode ensures the SageMaker endpoint is deployed within a VPC and cannot be accessed from the public internet, satisfying the requirement to deny all public traffic. Additionally, enabling inter-container traffic encryption (using TLS) encrypts data in transit between the containers hosting the model, meeting the encryption requirement. This configuration is specific to SageMaker endpoints and directly addresses both constraints.

Exam trap

The trap here is that candidates confuse 'network isolation mode' with simply deploying in a VPC, or they mistakenly think that a PrivateLink endpoint or security group rules alone can block all public traffic, when in fact network isolation is the only way to ensure the endpoint has no public endpoint URL.

How to eliminate wrong answers

Option A is wrong because deploying the endpoint in a public subnet does not prevent public traffic; security group ingress rules alone cannot block all public access since the endpoint would still have a public endpoint URL. Option B is wrong because 'VPC-only mode' is not a valid SageMaker endpoint configuration; SageMaker endpoints are either publicly accessible or deployed in a VPC with network isolation, but there is no toggle for 'VPC-only mode' that disables public access. Option C is wrong because using a PrivateLink endpoint (AWS PrivateLink) is for accessing the endpoint from other VPCs or on-premises networks, not for restricting public traffic, and enabling data encryption at rest does not address encryption of data in transit between containers.

Full explanation →

804

MCQmedium

Refer to the exhibit. A team observes that their SageMaker endpoint scales out quickly when load increases, but scales in very slowly when load decreases, causing over-provisioning. What is the most likely cause?

A.TargetValue is too high

B.ScaleOutCooldown is too low

C.ScaleInCooldown is too high

D.Wrong predefined metric selected

AnswerC

A high ScaleInCooldown delays scale-in responses.

Why this answer

A high ScaleInCooldown value causes the SageMaker endpoint to wait too long before initiating a scale-in event after load decreases. This delay prevents the endpoint from releasing resources promptly, leading to over-provisioning. In contrast, the scaling out behavior is unaffected by this cooldown, which explains why the endpoint scales out quickly but scales in slowly.

Exam trap

The trap here is that candidates often confuse cooldown periods with scaling thresholds, assuming that slow scale-in is caused by a high TargetValue or wrong metric, rather than recognizing that cooldown timers directly control the delay between scaling actions.

How to eliminate wrong answers

Option A is wrong because a TargetValue that is too high would cause the endpoint to scale out less aggressively and scale in more readily, not the observed slow scale-in. Option B is wrong because a ScaleOutCooldown that is too low would make scaling out even faster, but the issue is with scaling in, not scaling out. Option D is wrong because selecting the wrong predefined metric would affect both scaling directions or cause incorrect scaling decisions, not specifically slow scale-in while maintaining fast scale-out.

Full explanation →

805

Multi-Selectmedium

A machine learning team needs to automatically retrain a model when concept drift is detected in the deployed endpoint's predictions. Which TWO steps should they take? (Choose TWO.)

Select 2 answers

A.Schedule retraining with Amazon EventBridge on a fixed schedule

B.Create a CloudWatch alarm on a model quality metric (e.g., accuracy) and trigger a Lambda function to start a retraining job

C.Set up SageMaker Model Monitor - Model Quality Monitor to compute prediction quality metrics against ground truth

D.Configure SageMaker Model Monitor - Data Quality Monitor to detect input drift

E.Use SageMaker Clarify to monitor bias drift

AnswersB, C

Alarm triggers retraining pipeline when quality drops.

Why this answer

Model Quality Monitor compares predictions with ground truth to detect concept drift. When an alarm triggers, a Lambda function can start a retraining pipeline. Data Quality Monitor is for data drift, not concept drift.

Full explanation →

806

Multi-Selectmedium

A machine learning engineer is preparing a dataset for a multiclass classification task. The dataset has 10 features and 100,000 rows. Which TWO techniques should the engineer use to reduce the risk of overfitting during data preparation?

Select 2 answers

A.Data augmentation (e.g., adding noise)

B.SMOTE to balance classes

C.One-hot encoding of all categorical features

D.Log transformation of skewed features

E.Feature selection using correlation analysis

AnswersA, E

Increases training data diversity, reducing overfitting.

Why this answer

Data augmentation (A) is correct because it artificially increases the diversity of the training set by adding noise or transformations, which helps the model generalize better and reduces overfitting. Feature selection using correlation analysis (E) is correct because it removes redundant or highly correlated features, simplifying the model and minimizing the risk of learning noise from irrelevant predictors.

Exam trap

AWS often tests the distinction between techniques that address overfitting versus those that handle other data issues like imbalance or skewness, leading candidates to confuse SMOTE or log transforms as overfitting remedies.

Full explanation →

807

MCQmedium

An e-commerce company is building a recommendation system using user interaction data stored in Amazon DynamoDB. The data includes user_id, product_id, timestamp, event_type (click, add_to_cart, purchase), and session_id. The data science team exports the data to Amazon S3 as JSON files. During preprocessing, they discover that the 'event_type' field contains inconsistent values due to logging errors: 'Click', 'click', 'CLICK', and 'clck' all appear. Also, there are duplicate records where the same user_id, product_id, and timestamp appear multiple times with the same event_type. The team wants to use AWS Glue to clean the data for training a sequence-based recommendation model. Which set of actions should they perform?

A.Use AWS Glue to group records by session_id and aggregate event_types into a list per session. Then apply a mapping function to standardize event_type names.

B.Use AWS Glue to drop exact duplicate rows (all columns identical). Then apply a mapping function to standardize event_type to a controlled vocabulary (e.g., 'click', 'add_to_cart', 'purchase').

C.Use AWS Glue to drop duplicate records based on all columns. Then drop the event_type column and use only numeric features for training.

D.Use AWS Glue to impute event_type with the mode for records with inconsistent values. Then drop duplicate records based on user_id, product_id, and timestamp.

AnswerB

Deduplication removes redundant records, and mapping standardizes event_type, both essential for clean sequence data.

Why this answer

It addresses both data quality issues: first, dropping exact duplicate rows (all columns identical) removes redundant records that would bias the sequence model; second, standardizing event_type to a controlled vocabulary ensures consistent categorical input for ML training. AWS Glue's DynamicFrame with DropDuplicates and Map transformations are the appropriate tools for this ETL task.

Exam trap

The trap here is that candidates may think grouping by session_id is necessary for sequence modeling, but the question asks for cleaning steps, not feature engineering—duplicate removal and standardization must come first to avoid propagating errors into the sequence aggregation.

How to eliminate wrong answers

Option A is wrong because grouping by session_id and aggregating event_types into a list per session loses the individual event timestamps and ordering, which are critical for sequence-based recommendation models. Option C is wrong because dropping the event_type column removes the target label for the recommendation model, and using only numeric features would discard the core behavioral signal. Option D is wrong because imputing event_type with the mode is inappropriate for categorical data with logging errors (e.g., 'clck' should be mapped to 'click', not replaced by the most frequent value), and dropping duplicates only on user_id, product_id, and timestamp may remove legitimate distinct events that differ in event_type.

Full explanation →

808

Multi-Selectmedium

A machine learning engineer is building an ML pipeline using Amazon SageMaker. The engineer needs to prepare the data, detect bias in the dataset, and then create features for training. Which TWO AWS services or features should the engineer use? (Choose TWO.)

Select 2 answers

A.AWS Glue DataBrew

B.Amazon SageMaker Model Monitor

C.Amazon SageMaker Clarify

D.Amazon SageMaker Data Wrangler

E.Amazon SageMaker Feature Store

AnswersC, D

Clarify is used for bias detection and model explainability, and can be invoked from Data Wrangler.

Why this answer

Amazon SageMaker Data Wrangler is the visual data preparation tool that also integrates with Clarify for bias detection. SageMaker Clarify provides bias detection and explainability. Together they cover data preparation and bias detection in the same workflow.

Full explanation →

809

MCQmedium

A machine learning engineer is developing a text classification model using Amazon SageMaker. The dataset consists of 1 million customer reviews, with labels indicating sentiment (positive, negative, neutral). The engineer uses a pre-trained BERT model from the Hugging Face Model Hub and fine-tunes it on the dataset using SageMaker's Hugging Face estimator with a ml.p3.2xlarge instance. After 2 hours of training, the training job fails with a 'ResourceExhaustedError: CUDA out of memory' error. The error occurs during the forward pass of the first epoch. The engineer confirms that the batch size is set to 32, the maximum sequence length is 512 tokens, and the dataset is stored in a S3 bucket in the same AWS region. The engineer needs to complete fine-tuning without increasing instance costs. Which course of action should the engineer take?

A.Reduce the batch size to 8 and enable gradient accumulation with 4 steps to maintain effective batch size.

B.Enable SageMaker Managed Spot Training to reduce costs and use the savings to upgrade to a ml.p3.8xlarge instance.

C.Switch to a CPU-based instance like ml.c5.2xlarge to avoid GPU memory constraints.

D.Reduce the maximum sequence length to 128 tokens to lower memory consumption.

AnswerA

Reducing batch size lowers GPU memory usage, and gradient accumulation allows the model to see the same number of samples per update without increasing memory.

Why this answer

Reducing the batch size to 8 directly lowers GPU memory usage per forward pass, and enabling gradient accumulation with 4 steps allows the model to simulate the original effective batch size of 32 (8 × 4 = 32) without increasing memory footprint. This approach resolves the CUDA out-of-memory error while keeping the same instance type (ml.p3.2xlarge) and without incurring additional costs.

Exam trap

The trap here is that candidates may think reducing sequence length (Option D) is the simplest fix, but they overlook that it can severely impact model performance for sentiment analysis on long reviews, while gradient accumulation (Option A) is the standard technique to handle GPU memory limits without sacrificing batch size or accuracy.

How to eliminate wrong answers

Option B is wrong because upgrading to a ml.p3.8xlarge instance increases costs (it has 4× the GPU memory and is more expensive per hour), and Managed Spot Training only reduces cost but does not change the instance type; the engineer explicitly needs to avoid increasing instance costs. Option C is wrong because switching to a CPU-based instance (ml.c5.2xlarge) would dramatically increase training time for a BERT model (which relies on GPU parallelism) and may still run out of memory for sequence length 512, while also violating the requirement to complete fine-tuning efficiently. Option D is wrong because reducing the maximum sequence length to 128 tokens would truncate input texts, potentially losing critical context in customer reviews and degrading model accuracy; the engineer needs to maintain model quality while fixing the memory error.

Full explanation →

810

MCQeasy

A company wants to reduce costs for a production SageMaker endpoint that has predictable traffic patterns. They have purchased a Savings Plan. What additional step can they take to further optimize costs while maintaining performance?

A.Use SageMaker Inference Recommender to right-size the endpoint

B.Reduce the number of instances to one, regardless of load

C.Switch from real-time to batch inference

D.Disable auto-scaling

AnswerA

Inference Recommender tests different instance types and configurations to find the most cost-effective option for the workload.

Why this answer

SageMaker Inference Recommender provides instance type and configuration recommendations to right-size endpoints, balancing cost and performance. It is the appropriate tool for cost optimization beyond a Savings Plan.

Full explanation →

811

MCQmedium

A company wants to allow a SageMaker model in one AWS account to be accessed by a different AWS account for inference. They need to maintain security and compliance. Which approach meets the requirement?

A.Use AWS PrivateLink to expose the SageMaker endpoint privately and grant access via security groups

B.Attach a resource-based policy to the SageMaker endpoint that grants the other account's IAM role invoke permissions

C.Create an IAM role in the source account and share the role ARN with the target account

D.Share the model artifacts via an S3 bucket with cross-account bucket policies and let the other account deploy independently

AnswerB

Resource-based policies allow cross-account access to the endpoint. The other account's IAM role must have sts:AssumeRole or be allowed by the policy.

Why this answer

Cross-account access can be achieved by using resource-based policies on the SageMaker model or endpoint, combined with appropriate IAM roles in the consuming account.

Full explanation →

812

MCQhard

A team is using AWS Glue to process streaming data from Amazon Kinesis. The streaming data contains both structured and semi-structured fields. The team needs to flatten the semi-structured fields into columns for downstream ML training. Which Glue feature is BEST suited?

A.Relationalize transform

B.Spigot transform

C.ResolveChoice transform

D.ApplyMapping transform

AnswerA

Relationalize recursively flattens nested data into separate tables or columns.

Why this answer

The Relationalize transform is specifically designed to flatten nested JSON or semi-structured fields into a relational structure, making it ideal for converting complex streaming data from Kinesis into flat columns for ML training. It automatically handles arrays and structs by creating separate tables or columns, which is exactly what the team needs for downstream processing.

Exam trap

The trap here is that candidates confuse 'flattening semi-structured data' with simple schema operations like type resolution or column mapping, leading them to choose ResolveChoice or ApplyMapping instead of the specialized Relationalize transform.

How to eliminate wrong answers

Option B is wrong because the Spigot transform is used to sample or write a subset of data to a specified location for debugging or testing, not for flattening semi-structured fields. Option C is wrong because the ResolveChoice transform resolves ambiguity when a column has multiple data types (e.g., string vs. int) by casting to a chosen type, but it does not flatten nested structures. Option D is wrong because the ApplyMapping transform renames, casts, or drops columns based on a mapping specification, but it cannot flatten nested JSON or semi-structured data into separate columns.

Full explanation →

813

Multi-Selectmedium

A machine learning team needs to deploy a PyTorch model that has been compiled with SageMaker Neo to improve inference performance on edge devices. Which TWO statements about SageMaker Neo are correct? (Select TWO.)

Select 2 answers

A.Neo reduces model inference latency through optimization techniques

B.Neo requires the model to be trained on SageMaker

C.Neo compiles models for a specific hardware target, such as Intel or ARM

D.Neo can only compile models trained with SageMaker built-in algorithms

E.Neo automatically scales SageMaker endpoints based on demand

AnswersA, C

Why this answer

SageMaker Neo optimizes models for specific hardware targets (e.g., ARM, Intel, NVIDIA) and reduces latency. It does not require training frameworks; it compiles trained models. It does not automatically scale endpoints.

It is not limited to built-in algorithms.

Full explanation →

814

MCQhard

A company uses SageMaker endpoints with auto-scaling based on CPU utilization. During a flash sale, latency increases despite low CPU. What should be done?

A.Use a custom metric such as memory utilization or request count for auto-scaling

B.Increase the instance size

C.Disable auto-scaling and use a larger instance

D.Switch to GPU instances

AnswerA

Custom metrics can better capture the actual load and scale appropriately.

Why this answer

CPU utilization is a poor scaling metric for inference workloads that are I/O or memory-bound. During a flash sale, increased request concurrency can cause queuing and latency spikes even when CPU is low. Using a custom metric like request count per instance or memory utilization directly reflects the load on the inference endpoint, enabling the Application Auto Scaling target tracking policy to scale out proactively before latency degrades.

Exam trap

The trap here is that candidates assume CPU utilization is always the best scaling metric for compute-bound workloads, but the MLA-C01 exam specifically tests the understanding that inference endpoints can be I/O-bound, making request count or memory utilization more appropriate for auto-scaling.

How to eliminate wrong answers

Option B is wrong because increasing the instance size does not address the root cause—auto-scaling is not triggering due to an inappropriate metric; it merely shifts the bottleneck to a larger instance without solving the scaling policy issue. Option C is wrong because disabling auto-scaling removes elasticity entirely, which is counterproductive for handling unpredictable traffic spikes like a flash sale; a static larger instance will either be over-provisioned or still suffer latency under extreme load. Option D is wrong because GPU instances are designed for compute-heavy workloads like deep learning inference, not for resolving latency caused by request queuing or I/O bottlenecks; they add cost without fixing the scaling metric problem.

Full explanation →

815

MCQmedium

A data science team has trained a model using SageMaker and wants to deploy it for real-time inference with automatic scaling based on request latency. The deployment must handle unpredictable traffic spikes without manual intervention. Which combination of SageMaker features should the team use?

A.Create a SageMaker endpoint with an Application Auto Scaling target tracking policy based on the SageMakerVariantInvocationsPerInstance metric

B.Deploy the model on a multi-model endpoint and manually adjust the number of instances via the AWS Management Console

C.Deploy the model on an Elastic Inference accelerator and use AWS Auto Scaling with a scheduled policy

D.Create a batch transform job with a scheduled Lambda function to trigger scaling

AnswerA

Correct. This combination provides automatic scaling based on invocations per instance, which correlates with latency and handles spikes without manual intervention.

Why this answer

It uses a SageMaker endpoint with an Application Auto Scaling target tracking policy based on the SageMakerVariantInvocationsPerInstance metric. While this metric measures invocations per instance rather than latency directly, it serves as a proxy: high invocations per instance often lead to increased latency, so scaling on this metric helps maintain low latency by distributing load. This approach handles unpredictable traffic spikes automatically, meeting the requirement for latency-aware scaling better than any other option, which lack automatic or latency-based scaling.

Exam trap

Candidates may expect a metric that directly measures latency (e.g., SageMakerVariantLatency), but such a metric is not available as a built-in target tracking metric. The SageMakerVariantInvocationsPerInstance metric is the standard choice for latency scaling and is designed to maintain performance under variable load.

How to eliminate wrong answers

Option B is wrong because manually adjusting instances via the AWS Management Console does not provide automatic scaling, which is required to handle unpredictable traffic spikes without manual intervention. Option C is wrong because Elastic Inference accelerators are used to reduce the cost of deep learning inference by attaching a fraction of GPU power to an instance, not for scaling based on latency; AWS Auto Scaling with a scheduled policy is not suitable for unpredictable spikes as it relies on predefined schedules. Option D is wrong because a batch transform job is designed for offline, asynchronous inference on large datasets, not for real-time inference, and a scheduled Lambda function cannot dynamically scale based on real-time latency metrics.

Full explanation →

816

MCQmedium

A company uses SageMaker for training and inference. They have a model that retrains weekly. After each retraining, the model is evaluated on a held-out test set. If the evaluation metrics meet a threshold, the model is registered as 'Approved' in the SageMaker Model Registry. The team manually deploys the approved model to a production endpoint. They want to automate this deployment process to reduce manual errors. However, the deployment should only proceed if the new model passes a canary test in a staging environment. Which combination of AWS services should the team use to achieve this?

A.AWS CodeDeploy with a blue/green deployment strategy.

B.SageMaker Pipelines with a conditional deployment step that includes a canary test.

C.AWS Lambda to deploy to staging, then automatically promote to production if staging tests pass.

D.Amazon EKS with a custom inference container and use ArgoCD for automated deployments.

AnswerB

Pipelines natively support conditional logic, canary deployments via weighted endpoints, and automatic rollback.

Why this answer

SageMaker Pipelines natively supports conditional execution steps, allowing you to add a canary test step that evaluates the new model in a staging environment before automatically promoting it to production. This directly addresses the requirement for automated deployment gated by a canary test, without needing external orchestration services.

Exam trap

The trap here is that candidates may overthink the solution and choose a generic CI/CD tool like CodeDeploy or Lambda, missing that SageMaker Pipelines already provides a fully managed, ML-specific orchestration with conditional deployment and canary testing capabilities.

How to eliminate wrong answers

Option A is wrong because AWS CodeDeploy with blue/green deployment is a general-purpose deployment service for EC2, Lambda, or ECS, not integrated with SageMaker Model Registry or SageMaker endpoints, and lacks native canary testing for ML models. Option C is wrong because using AWS Lambda to deploy to staging and then promote to production would require custom code to manage the canary test logic, state tracking, and rollback, which is less reliable and maintainable than SageMaker Pipelines' built-in conditional steps. Option D is wrong because Amazon EKS with ArgoCD is designed for Kubernetes container orchestration, not for managing SageMaker endpoints or Model Registry, and introduces unnecessary complexity for a SageMaker-native workflow.

Full explanation →

817

MCQmedium

A data scientist runs the exhibit AWS Glue ETL job. The job fails with a Spark stage failure error. What is the most likely cause?

A.The output path is missing.

B.The S3 bucket does not exist.

C.The job does not have enough memory.

D.The data type mapping in ApplyMapping is incorrect; "value" column contains non-numeric strings that cannot be cast to double.

AnswerD

Casting string to double fails on non-numeric data, causing task failure.

Why this answer

The Spark stage failure error in an AWS Glue ETL job is most likely caused by a data type mismatch during the ApplyMapping transformation. When the 'value' column contains non-numeric strings that cannot be cast to double, Spark throws a stage failure because it cannot complete the required type conversion, leading to task failures and job termination.

Exam trap

The trap here is that candidates often attribute Spark stage failures to resource issues (memory or missing paths) rather than recognizing that data type casting errors during transformations are a primary cause of stage-level failures in Glue ETL jobs.

How to eliminate wrong answers

Option A is wrong because a missing output path would cause a different error, such as 'Path does not exist' or 'FileNotFoundException', not a Spark stage failure. Option B is wrong because a non-existent S3 bucket would result in an 'AccessDenied' or 'NoSuchBucket' error at the job start, not during a Spark stage. Option C is wrong because insufficient memory typically manifests as an 'OutOfMemoryError' or 'Container killed by YARN' error, not a generic stage failure; stage failures are more commonly tied to data processing errors like type casting issues.

Full explanation →

818

MCQmedium

A data scientist needs to evaluate a binary classification model. The dataset is highly imbalanced (5% positive class). Which metric is MOST appropriate for assessing model performance?

A.Precision

B.Accuracy

C.Recall

D.AUC

AnswerD

AUC measures ranking quality and is insensitive to class imbalance.

Why this answer

AUC (Area Under the ROC Curve) is robust to class imbalance as it evaluates the model's ability to rank positive vs negative examples. Precision, recall, and F1 can be misleading if not threshold-optimized.

Full explanation →

819

MCQeasy

A company wants to track the lineage of their ML models, including the training dataset, hyperparameters, and training job used to produce each model version. Which AWS service should they use?

A.SageMaker ML Lineage Tracking

B.Amazon DynamoDB

C.AWS Glue Data Catalog

D.Amazon S3 object tagging

AnswerA

ML Lineage Tracking tracks artifacts, actions, and contexts for full model lineage.

Why this answer

SageMaker ML Lineage Tracking is the correct choice because it is purpose-built to record and query the provenance of ML models, capturing relationships between datasets, training jobs, hyperparameters, and model versions. It creates a directed acyclic graph (DAG) of entities (e.g., artifacts, actions, contexts) that allows you to trace how a specific model version was produced, which directly meets the requirement for lineage tracking.

Exam trap

The trap here is that candidates may confuse general-purpose data storage or cataloging services (like DynamoDB or Glue Data Catalog) with the specialized ML lineage tracking service, overlooking that SageMaker ML Lineage Tracking is the only AWS service designed to model the directed relationships between ML artifacts, actions, and contexts.

How to eliminate wrong answers

Option B (Amazon DynamoDB) is wrong because it is a NoSQL key-value and document database designed for low-latency, scalable data storage, not for tracking ML lineage or modeling the complex relationships between training datasets, hyperparameters, and model versions. Option C (AWS Glue Data Catalog) is wrong because it is a metadata repository for data assets (e.g., tables, schemas, partitions) used in ETL and data cataloging, not for capturing the lineage of ML model training runs or hyperparameters. Option D (Amazon S3 object tagging) is wrong because while tags can label S3 objects with metadata like version or dataset name, they cannot capture the relational graph of lineage (e.g., which training job produced which model from which dataset) and lack query capabilities for tracing provenance across multiple artifacts.

Full explanation →

820

MCQeasy

A data scientist wants to use SageMaker Autopilot to automatically build a regression model. The dataset contains 200 features and 50,000 rows. Which output does SageMaker Autopilot provide?

A.Only the best model without any metrics

B.A leaderboard of candidate models with metrics and explainability reports

C.A single optimal model with no further tuning

D.A Python script for manual training

AnswerB

Autopilot generates a leaderboard and can produce explainability reports.

Why this answer

SageMaker Autopilot automatically explores various algorithms and preprocessing steps, then provides a leaderboard of candidate models with metrics.

Full explanation →

821

MCQhard

A company has a SageMaker endpoint running a model that provides real-time recommendations. Recently, the model's accuracy has degraded due to data drift. The team wants to automatically retrain the model when a drift metric exceeds a threshold and deploy the new model without downtime. Which architecture should the team implement?

A.Use SageMaker Model Monitor to collect drift metrics, and have a data scientist manually analyze the metrics and trigger retraining via the SageMaker console

B.Use SageMaker Model Monitor to trigger an Amazon EventBridge event that starts a SageMaker Pipeline, which retrains the model, registers it in the Model Registry, and then updates the existing endpoint with a new production variant

C.Schedule a daily SageMaker Pipeline that retrains the model and deploys it using a new endpoint, then updates the application to point to the new endpoint

D.Use SageMaker Model Monitor to publish drift metrics to Amazon CloudWatch, and create a CloudWatch alarm that triggers an AWS Lambda function to retrain and deploy the model

AnswerB

EventBridge triggers pipeline on drift; pipeline retrains, registers, and uses production variant to shift traffic gradually with no downtime.

Why this answer

It uses SageMaker Model Monitor to detect data drift and emit an EventBridge event, which triggers a SageMaker Pipeline to retrain the model, register it in the Model Registry, and then update the existing endpoint with a new production variant. This architecture enables automatic retraining and zero-downtime deployment by leveraging the endpoint's production variants for a blue/green deployment.

Exam trap

AWS often tests the distinction between automatic drift-triggered retraining with zero-downtime deployment (Option B) versus scheduled retraining or manual intervention, and candidates may overlook the need to update the existing endpoint rather than creating a new one.

How to eliminate wrong answers

Option A is wrong because it relies on manual analysis and triggering, which does not meet the requirement for automatic retraining. Option C is wrong because scheduling a daily pipeline ignores the data drift trigger and deploys a new endpoint instead of updating the existing one, causing downtime or requiring application changes to point to the new endpoint. Option D is wrong because while it uses CloudWatch alarms and Lambda for automation, it lacks the integration with SageMaker Model Registry and the ability to update the existing endpoint with a new production variant, potentially causing downtime or manual intervention.

Full explanation →

822

MCQeasy

A data scientist is preparing a dataset for binary classification. The dataset has a target variable with 90% of samples belonging to class 0 and 10% to class 1. Which data splitting strategy should the scientist use to ensure that the training and test sets maintain the same class proportion as the original dataset?

A.Time-series split

B.Simple random split

C.k-fold cross-validation

D.Stratified sampling

AnswerD

Preserves class proportions in each split by sampling within each class.

Why this answer

Stratified sampling ensures that each class is proportionally represented in the splits. Random splitting may not preserve the ratio; k-fold CV and time-series split are not appropriate for this requirement.

Full explanation →

823

MCQmedium

A data scientist is exploring data stored in an Amazon Redshift cluster. The data includes timestamp columns with different formats. The scientist wants to create a new column that standardizes the timestamp format to UTC. Which approach is MOST efficient?

A.Use AWS Glue to read the Redshift table and apply a custom transform

B.Use a SELECT with CONVERT_TIMEZONE in Redshift and export to S3

C.Use a SageMaker notebook to query Redshift and transform

D.Use Amazon QuickSight to transform the timestamp

AnswerB

CONVERT_TIMEZONE is a built-in Redshift function that efficiently converts timestamps.

Why this answer

`CONVERT_TIMEZONE` in Amazon Redshift is a native SQL function that directly converts timestamps to UTC without moving data outside the cluster. This approach avoids the overhead of external services, leverages Redshift's massively parallel processing (MPP) engine, and is the most efficient for in-database transformations.

Exam trap

The trap here is that candidates assume external ETL tools (Glue, SageMaker) are always necessary for complex transforms, overlooking Redshift's powerful built-in SQL functions that can perform the same task with zero data egress.

How to eliminate wrong answers

Option A is wrong because AWS Glue would require reading the entire Redshift table into a separate Spark environment, adding network latency and compute costs, which is far less efficient than a native SQL transform. Option C is wrong because a SageMaker notebook would need to query Redshift via a JDBC/ODBC connection, pulling data into the notebook's memory for transformation, introducing unnecessary data movement and serialization overhead. Option D is wrong because Amazon QuickSight is a visualization and dashboarding service, not a data transformation engine; it cannot create new columns or modify schemas in Redshift.

Full explanation →

824

MCQmedium

A healthcare company deploys a model that predicts patient readmission risk. The model is deployed using a SageMaker real-time endpoint with data capture enabled. The compliance team requires that all inference data be encrypted at rest in S3 using AWS KMS with a customer managed key. The team has configured the endpoint to use an IAM role that includes the necessary KMS permissions. However, after deployment, the captured data is not being written to the S3 bucket. The team checks the CloudWatch logs for the endpoint and finds no errors. The S3 bucket policy is as follows: { "Version": "2012-10-17", "Statement": [ { "Effect": "Deny", "Principal": "*", "Action": "s3:PutObject", "Resource": "arn:aws:s3:::my-bucket/*", "Condition": { "Bool": { "aws:SecureTransport": "false" } } } ] } The bucket also has a default KMS key. What is the MOST likely reason that the captured data is not being written?

A.The bucket policy includes an explicit deny that overrides any allow.

B.The bucket policy denies all PutObject requests because aws:SecureTransport is false.

C.The KMS key policy does not grant the SageMaker execution role the kms:GenerateDataKey permission.

D.The S3 bucket does not exist.

AnswerC

Even if the IAM role has KMS permissions, the key policy might not allow the role to use the key for encryption.

Why this answer

SageMaker data capture encrypts captured data at rest in S3 using server-side encryption with AWS KMS (SSE-KMS). When a customer managed KMS key is used, the SageMaker execution role must have the kms:GenerateDataKey permission to encrypt the data before writing it to S3. Even if the IAM role has other KMS permissions, without kms:GenerateDataKey, the data capture write operation fails silently, and CloudWatch logs may not show errors because the failure occurs at the KMS encryption step before the S3 PutObject call.

Exam trap

The trap here is that candidates focus on the S3 bucket policy's explicit Deny and assume it blocks all writes, but they overlook the condition key aws:SecureTransport, which makes the Deny only apply to non-HTTPS requests, and they miss the subtle KMS permission requirement for data capture encryption.

How to eliminate wrong answers

Option A is wrong because the bucket policy does not contain an explicit deny that overrides all allows; the Deny statement only applies when aws:SecureTransport is false, which is a condition that is not met (the request uses HTTPS). Option B is wrong because the bucket policy denies PutObject only when aws:SecureTransport is false, but SageMaker data capture uses HTTPS (SecureTransport is true), so the Deny does not apply. Option D is wrong because if the S3 bucket did not exist, SageMaker would log an error in CloudWatch logs (e.g., NoSuchBucket), but the question states no errors are found in the logs.

Full explanation →

825

Multi-Selecteasy

A company wants to deploy a trained model to a SageMaker endpoint with automatic scaling based on traffic. Which TWO configurations are required? (Choose two.)

Select 2 answers

A.Use a multi-model endpoint

B.Enable data capture

C.Set up an Application Auto Scaling policy

D.Configure a lifecycle configuration

E.Create a CloudWatch alarm

AnswersC, E

Auto Scaling policy defines how to scale the endpoint.

Why this answer

Application Auto Scaling is the AWS service that automatically adjusts the number of instances for a SageMaker endpoint based on demand. You define a scaling policy (e.g., target tracking, step scaling) that tells Auto Scaling when to add or remove instances, which is essential for handling variable traffic without manual intervention.

Exam trap

The trap here is that candidates often confuse 'required configurations for scaling' with 'optional features that improve monitoring or cost efficiency,' leading them to select data capture or multi-model endpoints instead of recognizing that a CloudWatch alarm is the trigger mechanism for the scaling policy.

Full explanation →

Page 11 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 →