cert
cert-1
cert-2

Pass Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AWS Certified Machine Learning Engineer - Associate MLA-C01 Exam - Verified By Experts
AWS Certified Machine Learning Engineer - Associate MLA-C01 Premium Bundle
$29.98

AWS Certified Machine Learning Engineer - Associate MLA-C01 Premium Bundle

$79.99
$109.97
  • Premium File 270 Questions & Answers. Last update: Oct 24, 2026
  • Training Course 244 Video Lectures
  • Study Guide 548 Pages
 
$109.97
$79.99
accept 42 downloads in last 7 days
block-screenshots
Purchase Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Exam Training Products Individually
Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Premium File
Premium File 270 Q&A
$76.99$69.99
Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Video Training Course
Training Course 244 Lectures
$21.99 $19.99
Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 PDF Study Guide
Study Guide 548 Pages
$21.99 $19.99
Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Practice Test 51

Question 500

During production evaluation of a SageMaker AI model candidate, the following condition is observed: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. The release is blocked until the underlying model behavior is understood. Which TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.

  1. Configure SageMaker Automatic Model Tuning with a bounded search space, objective metric, budget, and justified Bayesian or random strategy.
  2. Inspect confusion matrix, class prevalence, false-negative cost, and precision-recall curves across thresholds.
  3. Remove label-derived or post-outcome features, rebuild a point-in-time split, and recompute explanations and holdout metrics.
  4. Profile model memory, throughput, communication overhead, and per-device utilization.
  5. Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput.

Explanation

Correct Answers

D:

Profile model memory, throughput, communication overhead, and per-device utilization. This directly tests data parallelism versus model parallelism in the reported AWS ML workflow. Data parallelism shards data across replicas; model parallelism is more relevant when the model itself cannot fit on one device. It distinguishes the problem before choosing a change. The related targeted response is: Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. Operational setting: During production evaluation of a SageMaker AI model candidate.

E:

Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput. This is the appropriate controlled remedy for data parallelism versus model parallelism. Data parallelism shards data across replicas; model parallelism is more relevant when the model itself cannot fit on one device. Verify the cause with: Profile model memory, throughput, communication overhead, and per-device utilization. Then confirm: Multiple workers reduce epoch time with acceptable convergence and measured communication overhead. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. Operational setting: During production evaluation of a SageMaker AI model candidate.

Incorrect Answers

A:

Configure SageMaker Automatic Model Tuning with a bounded search space, objective metric, budget, and justified Bayesian or random strategy. This selection concerns hyperparameter bayesian tuning strategy rather than the required diagnostic-and-remedy pair for data parallelism versus model parallelism. Use evidence: Profile model memory, throughput, communication overhead, and per-device utilization. and the matching correction: Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput. Signal: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. Operational setting: During production evaluation of a SageMaker AI model candidate.

B:

Inspect confusion matrix, class prevalence, false-negative cost, and precision-recall curves across thresholds. This selection concerns precision versus recall fraud threshold rather than the required diagnostic-and-remedy pair for data parallelism versus model parallelism. Use evidence: Profile model memory, throughput, communication overhead, and per-device utilization. and the matching correction: Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput. Signal: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. Operational setting: During production evaluation of a SageMaker AI model candidate.

C:

Remove label-derived or post-outcome features, rebuild a point-in-time split, and recompute explanations and holdout metrics. This selection concerns clarify feature attribution against target leakage rather than the required diagnostic-and-remedy pair for data parallelism versus model parallelism. Use evidence: Profile model memory, throughput, communication overhead, and per-device utilization. and the matching correction: Prefer data parallel training with synchronized gradients when the model fits per device and the bottleneck is dataset throughput. Signal: A deep model fits on one GPU but training takes too long over a very large dataset; the team suggests splitting individual layers across devices without evidence of model-memory pressure. Operational setting: During production evaluation of a SageMaker AI model candidate.

Question 501

While reproducing a training incident in an independent SageMaker experiment, the following condition is observed: A house-price model's RMSE increases sharply after a few exceptionally expensive properties enter the validation set, although typical absolute errors remain stable. The experiment must be compared fairly against its prior baseline. Which corrective action most directly addresses this ML workflow problem?

  1. Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels.
  2. Select a decision threshold using recall or cost-aware precision/recall targets and measure on the untouched holdout.
  3. Compare RMSE with MAE or robust error summaries and choose the metric matching the application's penalty for large misses.
  4. Use a time-series forecasting approach with past context and seasonal features, evaluating all intended future horizons.

Explanation

Correct Answer

C:

Compare RMSE with MAE or robust error summaries and choose the metric matching the application's penalty for large misses. This is the appropriate controlled remedy for rmse versus mae outlier sensitivity. Squaring residuals gives large errors disproportionately high weight; MAE weights magnitudes linearly. Verify the cause with: Inspect squared versus absolute residual contributions, target distribution, and large-error business costs. Then confirm: The evaluation report shows both typical error and extreme-error impact with a justified primary metric. Reported signal: A house-price model's RMSE increases sharply after a few exceptionally expensive properties enter the validation set, although typical absolute errors remain stable. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Incorrect Answers

A:

Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. This addresses a different issue involving sagemaker built-in blazingtext choice. It does not correct the stated rmse versus mae outlier sensitivity mechanism. The targeted response is: Compare RMSE with MAE or robust error summaries and choose the metric matching the application's penalty for large misses. Case evidence: A house-price model's RMSE increases sharply after a few exceptionally expensive properties enter the validation set, although typical absolute errors remain stable. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

B:

Select a decision threshold using recall or cost-aware precision/recall targets and measure on the untouched holdout. This addresses a different issue involving precision versus recall fraud threshold. It does not correct the stated rmse versus mae outlier sensitivity mechanism. The targeted response is: Compare RMSE with MAE or robust error summaries and choose the metric matching the application's penalty for large misses. Case evidence: A house-price model's RMSE increases sharply after a few exceptionally expensive properties enter the validation set, although typical absolute errors remain stable. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

D:

Use a time-series forecasting approach with past context and seasonal features, evaluating all intended future horizons. This addresses a different issue involving time-series forecast horizon and seasonality. It does not correct the stated rmse versus mae outlier sensitivity mechanism. The targeted response is: Compare RMSE with MAE or robust error summaries and choose the metric matching the application's penalty for large misses. Case evidence: A house-price model's RMSE increases sharply after a few exceptionally expensive properties enter the validation set, although typical absolute errors remain stable. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Question 502

At the model-governance gate before promotion of a new ML artifact, the following condition is observed: A rare equipment-failure classifier reports a high ROC-AUC but its operational queue contains mostly false alarms. The team needs a defensible technical decision rather than an untracked workaround. Which investigation provides the most decisive FIRST evidence for the underlying problem?

  1. Inspect experiment run lineage, dataset/version hashes, code revisions, random seeds, and metric definitions.
  2. Measure class prevalence, precision-recall curve, ROC curve, and alert volume at the intended operating threshold.
  3. Inspect the supervised labels, text representation, model-input format, and the desired classification output.
  4. Check whether trustworthy target labels exist and compare feature distance scaling and cluster stability on a sample.

Explanation

Correct Answer

B:

Measure class prevalence, precision-recall curve, ROC curve, and alert volume at the intended operating threshold. This directly tests roc-auc versus pr-auc for rare events in the reported AWS ML workflow. With rare positive classes, precision and operational false-alert counts can be more revealing than ROC-AUC alone. It distinguishes the problem before choosing a change. The related targeted response is: Evaluate PR-AUC and precision at required recall alongside ROC-AUC, and select a deployment threshold for actual prevalence. Reported signal: A rare equipment-failure classifier reports a high ROC-AUC but its operational queue contains mostly false alarms. Operational setting: At the model-governance gate before promotion of a new ML artifact.

Incorrect Answers

A:

Inspect experiment run lineage, dataset/version hashes, code revisions, random seeds, and metric definitions. This is a possible diagnostic for reproducible sagemaker experiments comparisons, but it does not directly test the roc-auc versus pr-auc for rare events failure reported here. Prioritize: Measure class prevalence, precision-recall curve, ROC curve, and alert volume at the intended operating threshold. The relevant case is: A rare equipment-failure classifier reports a high ROC-AUC but its operational queue contains mostly false alarms. Operational setting: At the model-governance gate before promotion of a new ML artifact.

C:

Inspect the supervised labels, text representation, model-input format, and the desired classification output. This is a possible diagnostic for sagemaker built-in blazingtext choice, but it does not directly test the roc-auc versus pr-auc for rare events failure reported here. Prioritize: Measure class prevalence, precision-recall curve, ROC curve, and alert volume at the intended operating threshold. The relevant case is: A rare equipment-failure classifier reports a high ROC-AUC but its operational queue contains mostly false alarms. Operational setting: At the model-governance gate before promotion of a new ML artifact.

D:

Check whether trustworthy target labels exist and compare feature distance scaling and cluster stability on a sample. This is a possible diagnostic for clustering for unlabeled customer segments, but it does not directly test the roc-auc versus pr-auc for rare events failure reported here. Prioritize: Measure class prevalence, precision-recall curve, ROC curve, and alert volume at the intended operating threshold. The relevant case is: A rare equipment-failure classifier reports a high ROC-AUC but its operational queue contains mostly false alarms. Operational setting: At the model-governance gate before promotion of a new ML artifact.

Question 503

As a regulated ML workload prepares for an automated regional rollout, the following condition is observed: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. The team must demonstrate a repeatable monitoring or security control. Which TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.

  1. Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations.
  2. Inspect online versus offline feature computation code, event-time cutoffs, freshness, and sampled entity values.
  3. Apply consistent approved cost allocation tags to ML jobs and supported linked resources and activate relevant reporting.
  4. Capture stable prediction identifiers and ingest verified labels with matching keys for model-quality analysis.
  5. Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family.

Explanation

Correct Answers

A:

Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. This directly tests inference recommender benchmarking instance family in the reported AWS ML workflow. Rightsizing depends on workload measurements rather than the training machine or instance size alone. It distinguishes the problem before choosing a change. The related targeted response is: Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

E:

Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. This is the appropriate controlled remedy for inference recommender benchmarking instance family. Rightsizing depends on workload measurements rather than the training machine or instance size alone. Verify the cause with: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. Then confirm: A chosen instance meets throughput and latency targets at lower measured cost per thousand predictions. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

Incorrect Answers

B:

Inspect online versus offline feature computation code, event-time cutoffs, freshness, and sampled entity values. This selection concerns training-serving feature skew incident rather than the required diagnostic-and-remedy pair for inference recommender benchmarking instance family. Use evidence: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. and the matching correction: Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. Signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

C:

Apply consistent approved cost allocation tags to ML jobs and supported linked resources and activate relevant reporting. This selection concerns tag-based ml training cost attribution rather than the required diagnostic-and-remedy pair for inference recommender benchmarking instance family. Use evidence: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. and the matching correction: Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. Signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

D:

Capture stable prediction identifiers and ingest verified labels with matching keys for model-quality analysis. This selection concerns model monitor ground truth association rather than the required diagnostic-and-remedy pair for inference recommender benchmarking instance family. Use evidence: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. and the matching correction: Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. Signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

Question 504

At a production AWS ML data lake supporting customer-facing predictions, the following condition is observed: A daily S3 dataset consists of millions of tiny Parquet files, and training startup spends more time opening objects than scanning data. Engineers must avoid changing unrelated source partitions. What should the ML engineer inspect FIRST to distinguish this failure from unrelated issues?

  1. Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput.
  2. Inspect the stream retention setting, consumer checkpoint timestamps, and the oldest available sequence or time position.
  3. Inspect prediction errors around midnight and feature representations for the periodic hour variable.
  4. Inspect sampler placement, duplicate neighbor IDs, fold membership, and class-conditioned metric changes.

Explanation

Correct Answer

A:

Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. This directly tests columnar file compaction for small objects in the reported AWS ML workflow. Excessive small files create metadata and request overhead even with a columnar data format. It distinguishes the problem before choosing a change. The related targeted response is: Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. Reported signal: A daily S3 dataset consists of millions of tiny Parquet files, and training startup spends more time opening objects than scanning data. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.

Incorrect Answers

B:

Inspect the stream retention setting, consumer checkpoint timestamps, and the oldest available sequence or time position. This is a possible diagnostic for kinesis consumer retention gap, but it does not directly test the columnar file compaction for small objects failure reported here. Prioritize: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. The relevant case is: A daily S3 dataset consists of millions of tiny Parquet files, and training startup spends more time opening objects than scanning data. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.

C:

Inspect prediction errors around midnight and feature representations for the periodic hour variable. This is a possible diagnostic for time-series cyclical calendar feature, but it does not directly test the columnar file compaction for small objects failure reported here. Prioritize: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. The relevant case is: A daily S3 dataset consists of millions of tiny Parquet files, and training startup spends more time opening objects than scanning data. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.

D:

Inspect sampler placement, duplicate neighbor IDs, fold membership, and class-conditioned metric changes. This is a possible diagnostic for class imbalance handled inside cross-validation, but it does not directly test the columnar file compaction for small objects failure reported here. Prioritize: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. The relevant case is: A daily S3 dataset consists of millions of tiny Parquet files, and training startup spends more time opening objects than scanning data. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.

Question 505

During a production MLOps reliability and security review, the following condition is observed: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. The owner needs an auditable resolution without broadening privileges. Select TWO: the appropriate diagnostic check and the targeted implementation change.

  1. Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks.
  2. Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window.
  3. Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest.
  4. Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation.
  5. Use stable user-cohort assignment or an appropriate experiment design while keeping exposed groups measurable.

Explanation

Correct Answers

A:

Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. This is the appropriate controlled remedy for model monitor violation alert calibration. Monitoring must balance sensitivity and alert fatigue; treating every small statistical change as an incident is unreliable. Verify the cause with: Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. Then confirm: Representative benign fluctuations stay quiet while a known severe schema or distribution break pages the owner. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. Operational setting: During a production MLOps reliability and security review.

D:

Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. This directly tests model monitor violation alert calibration in the reported AWS ML workflow. Monitoring must balance sensitivity and alert fatigue; treating every small statistical change as an incident is unreliable. It distinguishes the problem before choosing a change. The related targeted response is: Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. Operational setting: During a production MLOps reliability and security review.

Incorrect Answers

B:

Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. This selection concerns cloudwatch 5xxerrors endpoint saturation rather than the required diagnostic-and-remedy pair for model monitor violation alert calibration. Use evidence: Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. and the matching correction: Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. Signal: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. Operational setting: During a production MLOps reliability and security review.

C:

Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. This selection concerns model artifact supply-chain integrity rather than the required diagnostic-and-remedy pair for model monitor violation alert calibration. Use evidence: Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. and the matching correction: Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. Signal: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. Operational setting: During a production MLOps reliability and security review.

E:

Use stable user-cohort assignment or an appropriate experiment design while keeping exposed groups measurable. This selection concerns champion challenger a/b assignment consistency rather than the required diagnostic-and-remedy pair for model monitor violation alert calibration. Use evidence: Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. and the matching correction: Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. Signal: A monitor issues thousands of alerts after a small harmless shift in an optional numeric feature and on-call engineers begin ignoring all violations. Operational setting: During a production MLOps reliability and security review.

Question 506

During a production MLOps reliability and security review, the following condition is observed: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. The owner needs an auditable resolution without broadening privileges. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.

  1. Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails.
  2. Inspect resource tags, cost allocation tag activation, Cost Explorer grouping, and unallocated resource types.
  3. Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access.
  4. Configure data capture and an appropriate Model Monitor baseline with scheduled data-quality checks.
  5. Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence.

Explanation

Correct Answers

A:

Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. This is the appropriate controlled remedy for cross-account s3 bucket exfiltration protection. Least privilege must constrain the destination resource; an unrestricted object-write policy can enable data exfiltration. Verify the cause with: Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. Then confirm: A test write to an approved prefix succeeds, while writes to unapproved external destinations are denied. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. Operational setting: During a production MLOps reliability and security review.

E:

Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. This directly tests cross-account s3 bucket exfiltration protection in the reported AWS ML workflow. Least privilege must constrain the destination resource; an unrestricted object-write policy can enable data exfiltration. It distinguishes the problem before choosing a change. The related targeted response is: Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. Operational setting: During a production MLOps reliability and security review.

Incorrect Answers

B:

Inspect resource tags, cost allocation tag activation, Cost Explorer grouping, and unallocated resource types. This selection concerns tag-based ml training cost attribution rather than the required diagnostic-and-remedy pair for cross-account s3 bucket exfiltration protection. Use evidence: Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. and the matching correction: Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. Signal: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. Operational setting: During a production MLOps reliability and security review.

C:

Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. This selection concerns s3 sse-kms cross-account model artifact access rather than the required diagnostic-and-remedy pair for cross-account s3 bucket exfiltration protection. Use evidence: Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. and the matching correction: Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. Signal: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. Operational setting: During a production MLOps reliability and security review.

D:

Configure data capture and an appropriate Model Monitor baseline with scheduled data-quality checks. This selection concerns sagemaker model monitor feature drift baseline rather than the required diagnostic-and-remedy pair for cross-account s3 bucket exfiltration protection. Use evidence: Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. and the matching correction: Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. Signal: An ML pipeline in one account is allowed to write model predictions to an unapproved external bucket because its role has overly broad s3:PutObject access. Operational setting: During a production MLOps reliability and security review.

Question 507

During an operational load and release rehearsal for SageMaker-hosted inference, the following condition is observed: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Change control requires measurable endpoint or pipeline acceptance evidence. Which engineering response resolves the actual issue without masking the symptoms?

  1. Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not.
  2. Use a measured canary or linear traffic-shift deployment with alarms and immediate rollback conditions.
  3. Grant the build role only required object and key operations for its specific artifact prefix and encryption key.
  4. Add schema, integration and sample endpoint inference tests to the ML build and deployment pipeline.

Explanation

Correct Answer

A:

Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. This is the appropriate controlled remedy for serverless inference for intermittent requests. Serverless capacity trades some cold-start behavior and resource limits for reduced idle endpoint commitment. Verify the cause with: Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. Then confirm: Low-frequency requests succeed within agreed latency while unused provisioned compute spend is reduced. Reported signal: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.

Incorrect Answers

B:

Use a measured canary or linear traffic-shift deployment with alarms and immediate rollback conditions. This addresses a different issue involving canary variant rollout for model changes. It does not correct the stated serverless inference for intermittent requests mechanism. The targeted response is: Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. Case evidence: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.

C:

Grant the build role only required object and key operations for its specific artifact prefix and encryption key. This addresses a different issue involving codebuild iam least-privilege artifact upload. It does not correct the stated serverless inference for intermittent requests mechanism. The targeted response is: Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. Case evidence: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.

D:

Add schema, integration and sample endpoint inference tests to the ML build and deployment pipeline. This addresses a different issue involving continuous integration unit and endpoint contract tests. It does not correct the stated serverless inference for intermittent requests mechanism. The targeted response is: Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. Case evidence: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.

Question 508

As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. The data team must preserve event-time meaning and lineage. Which corrective action most directly addresses this ML workflow problem?

  1. Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports.
  2. Use rolling-origin or chronological validation with strictly past-derived features and appropriate forecast horizons.
  3. Encode hour with sine and cosine cyclic features and validate with a time-aware split.
  4. Place shared POSIX-style working files on suitable EFS or FSx storage and keep immutable large artifacts in S3.

Explanation

Correct Answer

A:

Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. This is the appropriate controlled remedy for model training data residency boundary. Encrypting copied data does not automatically satisfy geographic residency constraints; placement and access must be controlled. Verify the cause with: Inspect S3 replication rules, region-specific bucket policies, Glue job destinations, KMS keys, and applicable residency controls. Then confirm: A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts. Reported signal: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Incorrect Answers

B:

Use rolling-origin or chronological validation with strictly past-derived features and appropriate forecast horizons. This addresses a different issue involving chronological split for forecast evaluation. It does not correct the stated model training data residency boundary mechanism. The targeted response is: Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. Case evidence: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

C:

Encode hour with sine and cosine cyclic features and validate with a time-aware split. This addresses a different issue involving time-series cyclical calendar feature. It does not correct the stated model training data residency boundary mechanism. The targeted response is: Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. Case evidence: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

D:

Place shared POSIX-style working files on suitable EFS or FSx storage and keep immutable large artifacts in S3. This addresses a different issue involving s3 versus efs training storage choice. It does not correct the stated model training data residency boundary mechanism. The targeted response is: Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. Case evidence: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Question 509

As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A demand forecast model is evaluated on randomly sampled days while features contain recent historical moving averages, creating unrealistic future information. The data team must preserve event-time meaning and lineage. Which verification result BEST demonstrates that the issue is resolved?

  1. Training read time and object operations decline while the resulting row count and checksums match.
  2. Every held-out forecast uses only data that existed at prediction time and its backtest follows real ordering.
  3. The recovery run reads a complete expected interval from retained stream records or durable archive without silent gaps.
  4. The report quantifies class or group imbalance with reproducible group counts and documents remediation assumptions.

Explanation

Correct Answer

B:

Every held-out forecast uses only data that existed at prediction time and its backtest follows real ordering. This is the acceptance evidence for the described chronological split for forecast evaluation scenario. Random splits violate temporal causality when future observations influence features or train data. The corrective implementation it validates is: Use rolling-origin or chronological validation with strictly past-derived features and appropriate forecast horizons. Reported signal: A demand forecast model is evaluated on randomly sampled days while features contain recent historical moving averages, creating unrealistic future information. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Incorrect Answers

A:

Training read time and object operations decline while the resulting row count and checksums match. This could validate columnar file compaction for small objects, but it does not establish that chronological split for forecast evaluation is resolved for this workload. Confirm instead: Every held-out forecast uses only data that existed at prediction time and its backtest follows real ordering. Observed problem: A demand forecast model is evaluated on randomly sampled days while features contain recent historical moving averages, creating unrealistic future information. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

C:

The recovery run reads a complete expected interval from retained stream records or durable archive without silent gaps. This could validate kinesis consumer retention gap, but it does not establish that chronological split for forecast evaluation is resolved for this workload. Confirm instead: Every held-out forecast uses only data that existed at prediction time and its backtest follows real ordering. Observed problem: A demand forecast model is evaluated on randomly sampled days while features contain recent historical moving averages, creating unrealistic future information. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

D:

The report quantifies class or group imbalance with reproducible group counts and documents remediation assumptions. This could validate clarify label imbalance measurement, but it does not establish that chronological split for forecast evaluation is resolved for this workload. Confirm instead: Every held-out forecast uses only data that existed at prediction time and its backtest follows real ordering. Observed problem: A demand forecast model is evaluated on randomly sampled days while features contain recent historical moving averages, creating unrealistic future information. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Question 510

During production evaluation of a SageMaker AI model candidate, the following condition is observed: A neural network continues training for many epochs after validation loss begins increasing while training loss keeps falling. The release is blocked until the underlying model behavior is understood. Which verification result BEST demonstrates that the issue is resolved?

  1. Candidate comparisons reference equivalent datasets and metrics and can be rerun from stored lineage.
  2. Training stops before extended overfitting and the retained model corresponds to the best validated epoch.
  3. Training completes within GPU memory limits and reaches comparable optimizer behavior and accuracy.
  4. A model returns calibrated numerical amounts and is evaluated against continuous target error on held-out records.

Explanation

Correct Answer

B:

Training stops before extended overfitting and the retained model corresponds to the best validated epoch. This is the acceptance evidence for the described early stopping on validation plateau scenario. More epochs are not always better; validation loss can worsen while training loss continues to decrease. The corrective implementation it validates is: Enable patience-based early stopping and restore the checkpoint with the best validation metric. Reported signal: A neural network continues training for many epochs after validation loss begins increasing while training loss keeps falling. Operational setting: During production evaluation of a SageMaker AI model candidate.

Incorrect Answers

A:

Candidate comparisons reference equivalent datasets and metrics and can be rerun from stored lineage. This could validate reproducible sagemaker experiments comparisons, but it does not establish that early stopping on validation plateau is resolved for this workload. Confirm instead: Training stops before extended overfitting and the retained model corresponds to the best validated epoch. Observed problem: A neural network continues training for many epochs after validation loss begins increasing while training loss keeps falling. Operational setting: During production evaluation of a SageMaker AI model candidate.

C:

Training completes within GPU memory limits and reaches comparable optimizer behavior and accuracy. This could validate training batch size causes gpu memory exhaustion, but it does not establish that early stopping on validation plateau is resolved for this workload. Confirm instead: Training stops before extended overfitting and the retained model corresponds to the best validated epoch. Observed problem: A neural network continues training for many epochs after validation loss begins increasing while training loss keeps falling. Operational setting: During production evaluation of a SageMaker AI model candidate.

D:

A model returns calibrated numerical amounts and is evaluated against continuous target error on held-out records. This could validate regression versus classification problem formulation, but it does not establish that early stopping on validation plateau is resolved for this workload. Confirm instead: Training stops before extended overfitting and the retained model corresponds to the best validated epoch. Observed problem: A neural network continues training for many epochs after validation loss begins increasing while training loss keeps falling. Operational setting: During production evaluation of a SageMaker AI model candidate.

AWS Certified Machine Learning Engineer - Associate MLA-C01 Practice Tests