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 20

Question 190

During an approved rollout of an AWS ML inference workload, the following condition is observed: An inference service needs a separate preprocessing transform before a predictor, but the team inserts inconsistent transformation code into many client applications. The team must meet its documented availability and rollback constraints. Which measured outcome would confirm that the correction worked as intended?

  1. The deployment loads artifacts privately and blocked public routes remain unused.
  2. The endpoint applies the same preprocessor to every client request and produces the expected model input schema.
  3. Large inputs complete without client request timeout and clients receive tracked result locations or failure notifications.
  4. Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not.

Explanation

Correct Answer

B:

The endpoint applies the same preprocessor to every client request and produces the expected model input schema. This is the acceptance evidence for the described multi-container inference pipeline responsibilities scenario. A managed inference pipeline chains preprocessing and prediction steps consistently, reducing client-side skew. The corrective implementation it validates is: Use a compatible SageMaker inference pipeline with ordered containers or a single packaged equivalent for shared preprocessing. Reported signal: An inference service needs a separate preprocessing transform before a predictor, but the team inserts inconsistent transformation code into many client applications. Operational setting: During an approved rollout of an AWS ML inference workload.

Incorrect Answers

A:

The deployment loads artifacts privately and blocked public routes remain unused. This could validate sagemaker vpc endpoint access for private artifacts, but it does not establish that multi-container inference pipeline responsibilities is resolved for this workload. Confirm instead: The endpoint applies the same preprocessor to every client request and produces the expected model input schema. Observed problem: An inference service needs a separate preprocessing transform before a predictor, but the team inserts inconsistent transformation code into many client applications. Operational setting: During an approved rollout of an AWS ML inference workload.

C:

Large inputs complete without client request timeout and clients receive tracked result locations or failure notifications. This could validate asynchronous endpoint for large payloads, but it does not establish that multi-container inference pipeline responsibilities is resolved for this workload. Confirm instead: The endpoint applies the same preprocessor to every client request and produces the expected model input schema. Observed problem: An inference service needs a separate preprocessing transform before a predictor, but the team inserts inconsistent transformation code into many client applications. Operational setting: During an approved rollout of an AWS ML inference workload.

D:

Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not. This could validate eventbridge conditional retraining trigger, but it does not establish that multi-container inference pipeline responsibilities is resolved for this workload. Confirm instead: The endpoint applies the same preprocessor to every client request and produces the expected model input schema. Observed problem: An inference service needs a separate preprocessing transform before a predictor, but the team inserts inconsistent transformation code into many client applications. Operational setting: During an approved rollout of an AWS ML inference workload.

Question 191

During an approved rollout of an AWS ML inference workload, the following condition is observed: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. The team must meet its documented availability and rollback constraints. Which measured outcome would confirm that the correction worked as intended?

  1. The deployment loads artifacts privately and blocked public routes remain unused.
  2. A limited slice serves the new version while metrics are monitored before any broad rollout.
  3. Distinct requested model IDs return correct predictions with acceptable cold load latency and lower aggregate idle cost.
  4. Cold-start p95 improves during planned demand windows while capacity cost remains measured.

Explanation

Correct Answer

A:

The deployment loads artifacts privately and blocked public routes remain unused. This is the acceptance evidence for the described sagemaker vpc endpoint access for private artifacts scenario. VPC isolation requires explicit supported network paths to AWS services; IAM permission alone does not create connectivity. The corrective implementation it validates is: Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. Reported signal: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: During an approved rollout of an AWS ML inference workload.

Incorrect Answers

B:

A limited slice serves the new version while metrics are monitored before any broad rollout. This could validate canary variant rollout for model changes, but it does not establish that sagemaker vpc endpoint access for private artifacts is resolved for this workload. Confirm instead: The deployment loads artifacts privately and blocked public routes remain unused. Observed problem: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: During an approved rollout of an AWS ML inference workload.

C:

Distinct requested model IDs return correct predictions with acceptable cold load latency and lower aggregate idle cost. This could validate multi-model endpoint hosting tradeoff, but it does not establish that sagemaker vpc endpoint access for private artifacts is resolved for this workload. Confirm instead: The deployment loads artifacts privately and blocked public routes remain unused. Observed problem: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: During an approved rollout of an AWS ML inference workload.

D:

Cold-start p95 improves during planned demand windows while capacity cost remains measured. This could validate sagemaker endpoint provisioned concurrency tradeoff, but it does not establish that sagemaker vpc endpoint access for private artifacts is resolved for this workload. Confirm instead: The deployment loads artifacts privately and blocked public routes remain unused. Observed problem: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: During an approved rollout of an AWS ML inference workload.

Question 192

While reproducing a training incident in an independent SageMaker experiment, the following condition is observed: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. The experiment must be compared fairly against its prior baseline. Which TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.

  1. Use justified feature selection or sparsity constraints fitted on training folds before retraining.
  2. Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests.
  3. Inspect routing mode, shadow traffic duplication, inference latency, output divergence, and payload compatibility.
  4. Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process.
  5. Use a time-series forecasting approach with past context and seasonal features, evaluating all intended future horizons.

Explanation

Correct Answers

B:

Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests. This directly tests interpretability for high-stakes prediction in the reported AWS ML workflow. Feature attribution can support explanation, but model choice must reflect transparency requirements and attribution is not causality. It distinguishes the problem before choosing a change. The related targeted response is: Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

D:

Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process. This is the appropriate controlled remedy for interpretability for high-stakes prediction. Feature attribution can support explanation, but model choice must reflect transparency requirements and attribution is not causality. Verify the cause with: Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests. Then confirm: Reviewers can identify stable feature drivers for representative decisions without misleading causal claims. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Incorrect Answers

A:

Use justified feature selection or sparsity constraints fitted on training folds before retraining. This selection concerns feature selection to reduce overparameterization rather than the required diagnostic-and-remedy pair for interpretability for high-stakes prediction. Use evidence: Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests. and the matching correction: Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process. Signal: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

C:

Inspect routing mode, shadow traffic duplication, inference latency, output divergence, and payload compatibility. This selection concerns shadow deployment model evaluation without response change rather than the required diagnostic-and-remedy pair for interpretability for high-stakes prediction. Use evidence: Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests. and the matching correction: Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process. Signal: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

E:

Use a time-series forecasting approach with past context and seasonal features, evaluating all intended future horizons. This selection concerns time-series forecast horizon and seasonality rather than the required diagnostic-and-remedy pair for interpretability for high-stakes prediction. Use evidence: Inspect documented explanation requirements, candidate feature contributions, and available post-hoc interpretation tests. and the matching correction: Compare a more interpretable model or add tested SageMaker Clarify explainability to the decision process. Signal: A credit-risk pilot selects a high-performing opaque model even though reviewers must justify material prediction features to an auditor. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Question 193

During production evaluation of a SageMaker AI model candidate, the following condition is observed: A support team needs text classification using labeled messages, but engineers choose a clustering algorithm that produces no class-specific predictions. The release is blocked until the underlying model behavior is understood. Which investigation provides the most decisive FIRST evidence for the underlying problem?

  1. Assess tabular feature structure, sample size, baseline metrics, inference constraints, and model interpretability requirements.
  2. Inspect feature importance stability, variance across folds, regularization and model dimensionality.
  3. Inspect the supervised labels, text representation, model-input format, and the desired classification output.
  4. Inspect training job InputDataConfig, environment variables such as SM_CHANNEL_TRAINING, and container paths.

Explanation

Correct Answer

C:

Inspect the supervised labels, text representation, model-input format, and the desired classification output. This directly tests sagemaker built-in blazingtext choice in the reported AWS ML workflow. Supervised text classification requires labels and task-specific evaluation rather than unlabeled similarity clusters. It distinguishes the problem before choosing a change. The related targeted response is: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. Reported signal: A support team needs text classification using labeled messages, but engineers choose a clustering algorithm that produces no class-specific predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.

Incorrect Answers

A:

Assess tabular feature structure, sample size, baseline metrics, inference constraints, and model interpretability requirements. This is a possible diagnostic for xgboost tabular classification baseline, but it does not directly test the sagemaker built-in blazingtext choice failure reported here. Prioritize: Inspect the supervised labels, text representation, model-input format, and the desired classification output. The relevant case is: A support team needs text classification using labeled messages, but engineers choose a clustering algorithm that produces no class-specific predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.

B:

Inspect feature importance stability, variance across folds, regularization and model dimensionality. This is a possible diagnostic for feature selection to reduce overparameterization, but it does not directly test the sagemaker built-in blazingtext choice failure reported here. Prioritize: Inspect the supervised labels, text representation, model-input format, and the desired classification output. The relevant case is: A support team needs text classification using labeled messages, but engineers choose a clustering algorithm that produces no class-specific predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.

D:

Inspect training job InputDataConfig, environment variables such as SM_CHANNEL_TRAINING, and container paths. This is a possible diagnostic for sagemaker script-mode data channel mismatch, but it does not directly test the sagemaker built-in blazingtext choice failure reported here. Prioritize: Inspect the supervised labels, text representation, model-input format, and the desired classification output. The relevant case is: A support team needs text classification using labeled messages, but engineers choose a clustering algorithm that produces no class-specific predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.

Question 194

While reproducing a training incident in an independent SageMaker experiment, the following condition is observed: A custom SageMaker training image exits before fitting because its entrypoint does not understand the job's expected channel paths and arguments. The experiment must be compared fairly against its prior baseline. Which verification result BEST demonstrates that the issue is resolved?

  1. Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs.
  2. The same container runs under managed training and reads the intended channel without hard-coded notebook filesystem assumptions.
  3. The managed training job starts the intended script and produces a usable model artifact in the output location.
  4. A rolling-origin backtest improves multi-step forecast error and respects temporal order.

Explanation

Correct Answer

C:

The managed training job starts the intended script and produces a usable model artifact in the output location. This is the acceptance evidence for the described training image compatibility for byoc scenario. Custom containers must implement the hosting or training contract; building a valid Docker image alone is insufficient. The corrective implementation it validates is: Adapt the custom training container to SageMaker training job conventions and verify locally against a representative channel layout. Reported signal: A custom SageMaker training image exits before fitting because its entrypoint does not understand the job's expected channel paths and arguments. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Incorrect Answers

A:

Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs. This could validate precision versus recall fraud threshold, but it does not establish that training image compatibility for byoc is resolved for this workload. Confirm instead: The managed training job starts the intended script and produces a usable model artifact in the output location. Observed problem: A custom SageMaker training image exits before fitting because its entrypoint does not understand the job's expected channel paths and arguments. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

B:

The same container runs under managed training and reads the intended channel without hard-coded notebook filesystem assumptions. This could validate sagemaker script-mode data channel mismatch, but it does not establish that training image compatibility for byoc is resolved for this workload. Confirm instead: The managed training job starts the intended script and produces a usable model artifact in the output location. Observed problem: A custom SageMaker training image exits before fitting because its entrypoint does not understand the job's expected channel paths and arguments. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

D:

A rolling-origin backtest improves multi-step forecast error and respects temporal order. This could validate time-series forecast horizon and seasonality, but it does not establish that training image compatibility for byoc is resolved for this workload. Confirm instead: The managed training job starts the intended script and produces a usable model artifact in the output location. Observed problem: A custom SageMaker training image exits before fitting because its entrypoint does not understand the job's expected channel paths and arguments. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Question 195

While reproducing a training incident in an independent SageMaker experiment, the following condition is observed: A retail analytics group needs to discover coherent groups of customers but has no verified segment labels for supervised classification. The experiment must be compared fairly against its prior baseline. Which measured outcome would confirm that the correction worked as intended?

  1. The same container runs under managed training and reads the intended channel without hard-coded notebook filesystem assumptions.
  2. A representative invoice set yields usable structured fields with measured extraction quality and minimal custom training.
  3. Multiple workers reduce epoch time with acceptable convergence and measured communication overhead.
  4. Stable clusters exhibit interpretable differences in held-out descriptors without claiming supervised classification accuracy.

Explanation

Correct Answer

D:

Stable clusters exhibit interpretable differences in held-out descriptors without claiming supervised classification accuracy. This is the acceptance evidence for the described clustering for unlabeled customer segments scenario. Unsupervised grouping does not require labeled segment classes and should not be judged by an unavailable label accuracy metric. The corrective implementation it validates is: Use an unsupervised clustering approach such as k-means after appropriate feature preparation and assess whether groups are meaningful. Reported signal: A retail analytics group needs to discover coherent groups of customers but has no verified segment labels for supervised classification. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Incorrect Answers

A:

The same container runs under managed training and reads the intended channel without hard-coded notebook filesystem assumptions. This could validate sagemaker script-mode data channel mismatch, but it does not establish that clustering for unlabeled customer segments is resolved for this workload. Confirm instead: Stable clusters exhibit interpretable differences in held-out descriptors without claiming supervised classification accuracy. Observed problem: A retail analytics group needs to discover coherent groups of customers but has no verified segment labels for supervised classification. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

B:

A representative invoice set yields usable structured fields with measured extraction quality and minimal custom training. This could validate managed ai service versus custom ocr model, but it does not establish that clustering for unlabeled customer segments is resolved for this workload. Confirm instead: Stable clusters exhibit interpretable differences in held-out descriptors without claiming supervised classification accuracy. Observed problem: A retail analytics group needs to discover coherent groups of customers but has no verified segment labels for supervised classification. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

C:

Multiple workers reduce epoch time with acceptable convergence and measured communication overhead. This could validate data parallelism versus model parallelism, but it does not establish that clustering for unlabeled customer segments is resolved for this workload. Confirm instead: Stable clusters exhibit interpretable differences in held-out descriptors without claiming supervised classification accuracy. Observed problem: A retail analytics group needs to discover coherent groups of customers but has no verified segment labels for supervised classification. Operational setting: While reproducing a training incident in an independent SageMaker experiment.

Question 196

During production evaluation of a SageMaker AI model candidate, the following condition is observed: A fraud-screening model has high global accuracy because most purchases are legitimate, while expensive fraud cases are often missed. The release is blocked until the underlying model behavior is understood. Which verification result BEST demonstrates that the issue is resolved?

  1. A rolling-origin backtest improves multi-step forecast error and respects temporal order.
  2. The tested alert rate and precision match the production workload rather than an optimistic single ROC figure.
  3. Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs.
  4. Multiple workers reduce epoch time with acceptable convergence and measured communication overhead.

Explanation

Correct Answer

C:

Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs. This is the acceptance evidence for the described precision versus recall fraud threshold scenario. Accuracy can conceal poor minority-class detection; threshold selection trades recall against precision. The corrective implementation it validates is: Select a decision threshold using recall or cost-aware precision/recall targets and measure on the untouched holdout. Reported signal: A fraud-screening model has high global accuracy because most purchases are legitimate, while expensive fraud cases are often missed. Operational setting: During production evaluation of a SageMaker AI model candidate.

Incorrect Answers

A:

A rolling-origin backtest improves multi-step forecast error and respects temporal order. This could validate time-series forecast horizon and seasonality, but it does not establish that precision versus recall fraud threshold is resolved for this workload. Confirm instead: Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs. Observed problem: A fraud-screening model has high global accuracy because most purchases are legitimate, while expensive fraud cases are often missed. Operational setting: During production evaluation of a SageMaker AI model candidate.

B:

The tested alert rate and precision match the production workload rather than an optimistic single ROC figure. This could validate roc-auc versus pr-auc for rare events, but it does not establish that precision versus recall fraud threshold is resolved for this workload. Confirm instead: Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs. Observed problem: A fraud-screening model has high global accuracy because most purchases are legitimate, while expensive fraud cases are often missed. Operational setting: During production evaluation of a SageMaker AI model candidate.

D:

Multiple workers reduce epoch time with acceptable convergence and measured communication overhead. This could validate data parallelism versus model parallelism, but it does not establish that precision versus recall fraud threshold is resolved for this workload. Confirm instead: Fraud recall meets the agreed target with documented review-volume and false-positive tradeoffs. Observed problem: A fraud-screening model has high global accuracy because most purchases are legitimate, while expensive fraud cases are often missed. Operational setting: During production evaluation of a SageMaker AI model candidate.

Question 197

While testing a second region for recoverable deployment of the same ML service, the following condition is observed: A document embedding application has payloads too large for its synchronous inference path and some requests need minutes of processing. The deployment must be reproducible without manual console-only fixes. Which investigation provides the most decisive FIRST evidence for the underlying problem?

  1. Inspect payload sizes, model processing duration, caller timeout limits, and request concurrency.
  2. Inspect EventBridge rule patterns, source events, object prefixes, and pipeline execution histories.
  3. Inspect preprocessing version drift, input/output contracts, and the selected hosting container topology.
  4. Compare template parameters, stack drift results, change sets, and deployed endpoint settings.

Explanation

Correct Answer

A:

Inspect payload sizes, model processing duration, caller timeout limits, and request concurrency. This directly tests asynchronous endpoint for large payloads in the reported AWS ML workflow. Asynchronous inference decouples request submission from long-running processing and can work with larger payload contracts. It distinguishes the problem before choosing a change. The related targeted response is: Use SageMaker asynchronous inference with S3 input/output and suitable queue and notification settings. Reported signal: A document embedding application has payloads too large for its synchronous inference path and some requests need minutes of processing. Operational setting: While testing a second region for recoverable deployment of the same ML service.

Incorrect Answers

B:

Inspect EventBridge rule patterns, source events, object prefixes, and pipeline execution histories. This is a possible diagnostic for eventbridge conditional retraining trigger, but it does not directly test the asynchronous endpoint for large payloads failure reported here. Prioritize: Inspect payload sizes, model processing duration, caller timeout limits, and request concurrency. The relevant case is: A document embedding application has payloads too large for its synchronous inference path and some requests need minutes of processing. Operational setting: While testing a second region for recoverable deployment of the same ML service.

C:

Inspect preprocessing version drift, input/output contracts, and the selected hosting container topology. This is a possible diagnostic for multi-container inference pipeline responsibilities, but it does not directly test the asynchronous endpoint for large payloads failure reported here. Prioritize: Inspect payload sizes, model processing duration, caller timeout limits, and request concurrency. The relevant case is: A document embedding application has payloads too large for its synchronous inference path and some requests need minutes of processing. Operational setting: While testing a second region for recoverable deployment of the same ML service.

D:

Compare template parameters, stack drift results, change sets, and deployed endpoint settings. This is a possible diagnostic for cloudformation stack parameter drift, but it does not directly test the asynchronous endpoint for large payloads failure reported here. Prioritize: Inspect payload sizes, model processing duration, caller timeout limits, and request concurrency. The relevant case is: A document embedding application has payloads too large for its synchronous inference path and some requests need minutes of processing. Operational setting: While testing a second region for recoverable deployment of the same ML service.

Question 198

While reproducing the alert in an isolated AWS ML integration account, the following condition is observed: A recommendation endpoint drops peak requests with HTTP 5xx as invocations per instance rise, while the dashboard averages latency across an entire day. The proposed change must preserve logging and least privilege. Which verification result BEST demonstrates that the issue is resolved?

  1. Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms.
  2. The pipeline deploys with the authorized role and cannot assign an unrelated privileged role.
  3. Training jobs reach the intended service privately while unauthorized external egress stays blocked.
  4. The chosen fix reduces measured end-to-end p95 latency and component metrics explain the change.

Explanation

Correct Answer

A:

Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. This is the acceptance evidence for the described cloudwatch 5xxerrors endpoint saturation scenario. Daily averages can conceal short capacity failures; monitoring must use an incident-relevant interval. The corrective implementation it validates is: Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. Reported signal: A recommendation endpoint drops peak requests with HTTP 5xx as invocations per instance rise, while the dashboard averages latency across an entire day. Operational setting: While reproducing the alert in an isolated AWS ML integration account.

Incorrect Answers

B:

The pipeline deploys with the authorized role and cannot assign an unrelated privileged role. This could validate iam passrole constraint for model deployment, but it does not establish that cloudwatch 5xxerrors endpoint saturation is resolved for this workload. Confirm instead: Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. Observed problem: A recommendation endpoint drops peak requests with HTTP 5xx as invocations per instance rise, while the dashboard averages latency across an entire day. Operational setting: While reproducing the alert in an isolated AWS ML integration account.

C:

Training jobs reach the intended service privately while unauthorized external egress stays blocked. This could validate private vpc endpoint policy for sagemaker apis, but it does not establish that cloudwatch 5xxerrors endpoint saturation is resolved for this workload. Confirm instead: Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. Observed problem: A recommendation endpoint drops peak requests with HTTP 5xx as invocations per instance rise, while the dashboard averages latency across an entire day. Operational setting: While reproducing the alert in an isolated AWS ML integration account.

D:

The chosen fix reduces measured end-to-end p95 latency and component metrics explain the change. This could validate cloudwatch invocations and modellatency distinction, but it does not establish that cloudwatch 5xxerrors endpoint saturation is resolved for this workload. Confirm instead: Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. Observed problem: A recommendation endpoint drops peak requests with HTTP 5xx as invocations per instance rise, while the dashboard averages latency across an entire day. Operational setting: While reproducing the alert in an isolated AWS ML integration account.

Question 199

As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. The data team must preserve event-time meaning and lineage. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.

  1. Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory.
  2. Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features.
  3. Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics.
  4. Apply a justified log1p transformation with documented treatment of invalid negatives and package it for serving.
  5. Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines.

Explanation

Correct Answers

A:

Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. This is the appropriate controlled remedy for glue spark join skew on dominant identifier. A low-cardinality or skewed key can concentrate a distributed join into one expensive partition. Verify the cause with: Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics. Then confirm: Long-tail task duration and shuffle spill decline without changing the joined record counts. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

C:

Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics. This directly tests glue spark join skew on dominant identifier in the reported AWS ML workflow. A low-cardinality or skewed key can concentrate a distributed join into one expensive partition. It distinguishes the problem before choosing a change. The related targeted response is: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Incorrect Answers

B:

Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. This selection concerns glue schema evolution with mixed input types rather than the required diagnostic-and-remedy pair for glue spark join skew on dominant identifier. Use evidence: Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics. and the matching correction: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Signal: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

D:

Apply a justified log1p transformation with documented treatment of invalid negatives and package it for serving. This selection concerns skewed numerical feature log transformation rather than the required diagnostic-and-remedy pair for glue spark join skew on dominant identifier. Use evidence: Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics. and the matching correction: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Signal: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

E:

Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. This selection concerns glue data quality non-null contract rather than the required diagnostic-and-remedy pair for glue spark join skew on dominant identifier. Use evidence: Inspect Spark stage durations, partition size distribution, join key frequencies, and executor spill metrics. and the matching correction: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Signal: A Spark transformation joins billions of records on a region key, and one region contains most observations, stalling one shuffle task. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.

Question 200

As a regulated ML workload prepares for an automated regional rollout, the following condition is observed: An inference container embeds a database password in its image, and every rollout reuses the credential even after an incident. The team must demonstrate a repeatable monitoring or security control. Which investigation provides the most decisive FIRST evidence for the underlying problem?

  1. Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest.
  2. Compare probability calibration plots, Brier score and event rates across recent labeled cohorts.
  3. Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs.
  4. Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations.

Explanation

Correct Answer

C:

Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs. This directly tests secret rotation for inference container credentials in the reported AWS ML workflow. Container artifacts can leak hard-coded secrets; runtime retrieval and rotation keep sensitive values outside build outputs. It distinguishes the problem before choosing a change. The related targeted response is: Remove embedded credentials, rotate the exposed secret, and retrieve current credentials through an approved managed secret service. Reported signal: An inference container embeds a database password in its image, and every rollout reuses the credential even after an incident. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

Incorrect Answers

A:

Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. This is a possible diagnostic for model artifact supply-chain integrity, but it does not directly test the secret rotation for inference container credentials failure reported here. Prioritize: Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs. The relevant case is: An inference container embeds a database password in its image, and every rollout reuses the credential even after an incident. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

B:

Compare probability calibration plots, Brier score and event rates across recent labeled cohorts. This is a possible diagnostic for serving output confidence calibration drift, but it does not directly test the secret rotation for inference container credentials failure reported here. Prioritize: Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs. The relevant case is: An inference container embeds a database password in its image, and every rollout reuses the credential even after an incident. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

D:

Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. This is a possible diagnostic for inference recommender benchmarking instance family, but it does not directly test the secret rotation for inference container credentials failure reported here. Prioritize: Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs. The relevant case is: An inference container embeds a database password in its image, and every rollout reuses the credential even after an incident. Operational setting: As a regulated ML workload prepares for an automated regional rollout.

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