Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Practice Test 71
Question 700
At the model-governance gate before promotion of a new ML artifact, the following condition is observed: A team chooses a SageMaker JumpStart model by popularity alone and overlooks its license, task fit, input contracts, and deployment costs. The team needs a defensible technical decision rather than an untracked workaround. Which verification result BEST demonstrates that the issue is resolved?
- A rolling-origin backtest improves multi-step forecast error and respects temporal order.
- The same container runs under managed training and reads the intended channel without hard-coded notebook filesystem assumptions.
- Training completes within GPU memory limits and reaches comparable optimizer behavior and accuracy.
- The chosen version meets task metrics and license conditions and its inference contract is reproducible.
Explanation
Correct Answer
D:The chosen version meets task metrics and license conditions and its inference contract is reproducible. This is the acceptance evidence for the described sagemaker jumpstart template provenance scenario. Pretrained model convenience does not remove licensing, fit-for-purpose evaluation, or operational constraints. The corrective implementation it validates is: Select a licensed, task-appropriate model and validate its performance and resource needs before a controlled deployment. Reported signal: A team chooses a SageMaker JumpStart model by popularity alone and overlooks its license, task fit, input contracts, and deployment costs. Operational setting: At the model-governance gate before promotion of a new ML artifact.
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 sagemaker jumpstart template provenance is resolved for this workload. Confirm instead: The chosen version meets task metrics and license conditions and its inference contract is reproducible. Observed problem: A team chooses a SageMaker JumpStart model by popularity alone and overlooks its license, task fit, input contracts, and deployment costs. Operational setting: At the model-governance gate before promotion of a new ML artifact.
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 sagemaker jumpstart template provenance is resolved for this workload. Confirm instead: The chosen version meets task metrics and license conditions and its inference contract is reproducible. Observed problem: A team chooses a SageMaker JumpStart model by popularity alone and overlooks its license, task fit, input contracts, and deployment costs. Operational setting: At the model-governance gate before promotion of a new ML artifact.
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 sagemaker jumpstart template provenance is resolved for this workload. Confirm instead: The chosen version meets task metrics and license conditions and its inference contract is reproducible. Observed problem: A team chooses a SageMaker JumpStart model by popularity alone and overlooks its license, task fit, input contracts, and deployment costs. Operational setting: At the model-governance gate before promotion of a new ML artifact.
Question 701
During a controlled replay of the data-preparation workflow in a separate ML staging account, the following condition is observed: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. The dataset contract must remain reproducible for a backfill. Which TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.
- Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports.
- Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query.
- Inspect prediction errors around midnight and feature representations for the periodic hour variable.
- Encode hour with sine and cosine cyclic features and validate with a time-aware split.
- Fit an appropriate scaler on training data and package the same transformation with inference preprocessing.
Explanation
Correct Answers
C:Inspect prediction errors around midnight and feature representations for the periodic hour variable. This directly tests time-series cyclical calendar feature in the reported AWS ML workflow. Time-of-day has periodic topology; raw integer distance does not represent wraparound. It distinguishes the problem before choosing a change. The related targeted response is: Encode hour with sine and cosine cyclic features and validate with a time-aware split. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
D:Encode hour with sine and cosine cyclic features and validate with a time-aware split. This is the appropriate controlled remedy for time-series cyclical calendar feature. Time-of-day has periodic topology; raw integer distance does not represent wraparound. Verify the cause with: Inspect prediction errors around midnight and feature representations for the periodic hour variable. Then confirm: Neighboring times across midnight map close in cyclic feature space and validation improves without leakage. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Incorrect Answers
A:Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. This selection concerns model training data residency boundary rather than the required diagnostic-and-remedy pair for time-series cyclical calendar feature. Use evidence: Inspect prediction errors around midnight and feature representations for the periodic hour variable. and the matching correction: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Signal: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
B:Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query. This selection concerns point-in-time feature data leakage rather than the required diagnostic-and-remedy pair for time-series cyclical calendar feature. Use evidence: Inspect prediction errors around midnight and feature representations for the periodic hour variable. and the matching correction: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Signal: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
E:Fit an appropriate scaler on training data and package the same transformation with inference preprocessing. This selection concerns standardization of numerical features rather than the required diagnostic-and-remedy pair for time-series cyclical calendar feature. Use evidence: Inspect prediction errors around midnight and feature representations for the periodic hour variable. and the matching correction: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Signal: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Question 702
As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A sentiment model trained with one tokenizer receives text encoded by a different tokenizer in production and generates incorrect input token IDs. The data team must preserve event-time meaning and lineage. Which corrective action most directly addresses this ML workflow problem?
- Split first; fit the imputer only on the training partition and apply those learned statistics to validation and test data.
- Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports.
- Use a CSV parser with explicit quoting and schema validation; quarantine malformed records before training.
- Package the training tokenizer and normalization configuration with the model artifact and require serving compatibility checks.
Explanation
Correct Answer
D:Package the training tokenizer and normalization configuration with the model artifact and require serving compatibility checks. This is the appropriate controlled remedy for text tokenization mismatch in serving. Model embeddings depend on stable token-ID semantics; swapping tokenizers changes the feature representation. Verify the cause with: Compare vocabulary hashes, normalization steps, token IDs for test strings, and serialized preprocessing versions. Then confirm: Identical inputs create identical token IDs in train and serving paths, including punctuation and unknown words. Reported signal: A sentiment model trained with one tokenizer receives text encoded by a different tokenizer in production and generates incorrect input token IDs. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Incorrect Answers
A:Split first; fit the imputer only on the training partition and apply those learned statistics to validation and test data. This addresses a different issue involving median imputation fitted on training split. It does not correct the stated text tokenization mismatch in serving mechanism. The targeted response is: Package the training tokenizer and normalization configuration with the model artifact and require serving compatibility checks. Case evidence: A sentiment model trained with one tokenizer receives text encoded by a different tokenizer in production and generates incorrect input token IDs. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
B:Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. This addresses a different issue involving model training data residency boundary. It does not correct the stated text tokenization mismatch in serving mechanism. The targeted response is: Package the training tokenizer and normalization configuration with the model artifact and require serving compatibility checks. Case evidence: A sentiment model trained with one tokenizer receives text encoded by a different tokenizer in production and generates incorrect input token IDs. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
C:Use a CSV parser with explicit quoting and schema validation; quarantine malformed records before training. This addresses a different issue involving csv schema ambiguity during ingestion. It does not correct the stated text tokenization mismatch in serving mechanism. The targeted response is: Package the training tokenizer and normalization configuration with the model artifact and require serving compatibility checks. Case evidence: A sentiment model trained with one tokenizer receives text encoded by a different tokenizer in production and generates incorrect input token IDs. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Question 703
While testing a second region for recoverable deployment of the same ML service, the following condition is observed: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. The deployment must be reproducible without manual console-only fixes. Select TWO: the appropriate diagnostic check and the targeted implementation change.
- Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements.
- Use a compatible SageMaker inference pipeline with ordered containers or a single packaged equivalent for shared preprocessing.
- Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior.
- Inspect model registry package versions, approval metadata, artifact hashes, and pipeline deployment inputs.
- Add schema, integration and sample endpoint inference tests to the ML build and deployment pipeline.
Explanation
Correct Answers
A:Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements. This directly tests multi-model endpoint hosting tradeoff in the reported AWS ML workflow. Multi-model hosting shares inference compute but can incur cache misses and is unsuitable when models require incompatible runtimes. It distinguishes the problem before choosing a change. The related targeted response is: Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior. This is the appropriate controlled remedy for multi-model endpoint hosting tradeoff. Multi-model hosting shares inference compute but can incur cache misses and is unsuitable when models require incompatible runtimes. Verify the cause with: Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements. Then confirm: Distinct requested model IDs return correct predictions with acceptable cold load latency and lower aggregate idle cost. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Incorrect Answers
B:Use a compatible SageMaker inference pipeline with ordered containers or a single packaged equivalent for shared preprocessing. This selection concerns multi-container inference pipeline responsibilities rather than the required diagnostic-and-remedy pair for multi-model endpoint hosting tradeoff. Use evidence: Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements. and the matching correction: Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior. Signal: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. Operational setting: While testing a second region for recoverable deployment of the same ML service.
D:Inspect model registry package versions, approval metadata, artifact hashes, and pipeline deployment inputs. This selection concerns model registry version promotion provenance rather than the required diagnostic-and-remedy pair for multi-model endpoint hosting tradeoff. Use evidence: Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements. and the matching correction: Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior. Signal: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. Operational setting: While testing a second region for recoverable deployment of the same ML service.
E:Add schema, integration and sample endpoint inference tests to the ML build and deployment pipeline. This selection concerns continuous integration unit and endpoint contract tests rather than the required diagnostic-and-remedy pair for multi-model endpoint hosting tradeoff. Use evidence: Inspect model sizes, framework compatibility, per-model request rates, load latency, and isolation requirements. and the matching correction: Use a compatible SageMaker multi-model endpoint with managed model loading and monitor cache/eviction behavior. Signal: A platform maintains hundreds of low-traffic similar models and deploys each to a dedicated always-running instance, causing high idle cost. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 704
During a controlled replay of the data-preparation workflow in a separate ML staging account, 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. The dataset contract must remain reproducible for a backfill. Select TWO: the appropriate diagnostic check and the targeted implementation change.
- Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput.
- Revise instructions, route ambiguous samples for expert adjudication, and monitor label quality per class.
- Inspect group sample sizes, label-positive fractions, and the appropriate SageMaker Clarify pretraining bias report.
- Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema.
- Use a CSV parser with explicit quoting and schema validation; quarantine malformed records before training.
Explanation
Correct Answers
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. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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: During a controlled replay of the data-preparation workflow in a separate ML staging account.
D:Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. This is the appropriate controlled remedy for columnar file compaction for small objects. Excessive small files create metadata and request overhead even with a columnar data format. Verify the cause with: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. Then confirm: Training read time and object operations decline while the resulting row count and checksums match. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Incorrect Answers
B:Revise instructions, route ambiguous samples for expert adjudication, and monitor label quality per class. This selection concerns ground truth labeling agreement review rather than the required diagnostic-and-remedy pair for columnar file compaction for small objects. Use evidence: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. and the matching correction: Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. 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: During a controlled replay of the data-preparation workflow in a separate ML staging account.
C:Inspect group sample sizes, label-positive fractions, and the appropriate SageMaker Clarify pretraining bias report. This selection concerns clarify label imbalance measurement rather than the required diagnostic-and-remedy pair for columnar file compaction for small objects. Use evidence: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. and the matching correction: Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. 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: During a controlled replay of the data-preparation workflow in a separate ML staging account.
E:Use a CSV parser with explicit quoting and schema validation; quarantine malformed records before training. This selection concerns csv schema ambiguity during ingestion rather than the required diagnostic-and-remedy pair for columnar file compaction for small objects. Use evidence: Measure file-size distribution, object request count, Spark task scheduling overhead, and read throughput. and the matching correction: Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. 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: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Question 705
As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A near-real-time account feature sums transactions using processing time, so late-arriving events land in the wrong window and produce inconsistent scores. The data team must preserve event-time meaning and lineage. What should the ML engineer inspect FIRST to distinguish this failure from unrelated issues?
- Inspect event timestamps, ingest timestamps, watermark configuration, and window outputs for delayed sample records.
- Check job names, bookmark settings, run history, source object timestamps, and the previously committed checkpoint.
- Inspect workload read/write semantics, shared access requirements, filesystem operations, and object-store request patterns.
- Inspect feature scale distributions, model sensitivity, and whether fitted scaler statistics are shared across serving and training.
Explanation
Correct Answer
A:Inspect event timestamps, ingest timestamps, watermark configuration, and window outputs for delayed sample records. This directly tests streaming feature rolling window correctness in the reported AWS ML workflow. Processing-time windows depend on arrival timing; event-time windows need explicit watermarks and late-event policy. It distinguishes the problem before choosing a change. The related targeted response is: Define event-time windows with appropriate lateness handling and a documented revision policy for late records. Reported signal: A near-real-time account feature sums transactions using processing time, so late-arriving events land in the wrong window and produce inconsistent scores. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Incorrect Answers
B:Check job names, bookmark settings, run history, source object timestamps, and the previously committed checkpoint. This is a possible diagnostic for glue job bookmark state error, but it does not directly test the streaming feature rolling window correctness failure reported here. Prioritize: Inspect event timestamps, ingest timestamps, watermark configuration, and window outputs for delayed sample records. The relevant case is: A near-real-time account feature sums transactions using processing time, so late-arriving events land in the wrong window and produce inconsistent scores. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
C:Inspect workload read/write semantics, shared access requirements, filesystem operations, and object-store request patterns. This is a possible diagnostic for s3 versus efs training storage choice, but it does not directly test the streaming feature rolling window correctness failure reported here. Prioritize: Inspect event timestamps, ingest timestamps, watermark configuration, and window outputs for delayed sample records. The relevant case is: A near-real-time account feature sums transactions using processing time, so late-arriving events land in the wrong window and produce inconsistent scores. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
D:Inspect feature scale distributions, model sensitivity, and whether fitted scaler statistics are shared across serving and training. This is a possible diagnostic for standardization of numerical features, but it does not directly test the streaming feature rolling window correctness failure reported here. Prioritize: Inspect event timestamps, ingest timestamps, watermark configuration, and window outputs for delayed sample records. The relevant case is: A near-real-time account feature sums transactions using processing time, so late-arriving events land in the wrong window and produce inconsistent scores. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Question 706
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 corrective action most directly addresses this ML workflow problem?
- Use tracked SageMaker Experiments runs with fixed comparable evaluation splits and a documented metric contract.
- Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels.
- Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses.
- Select a licensed, task-appropriate model and validate its performance and resource needs before a controlled deployment.
Explanation
Correct Answer
B:Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. This is the appropriate controlled remedy for sagemaker built-in blazingtext choice. Supervised text classification requires labels and task-specific evaluation rather than unlabeled similarity clusters. Verify the cause with: Inspect the supervised labels, text representation, model-input format, and the desired classification output. Then confirm: Held-out messages receive the intended class predictions and macro-averaged quality is measurable. 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:Use tracked SageMaker Experiments runs with fixed comparable evaluation splits and a documented metric contract. This addresses a different issue involving reproducible sagemaker experiments comparisons. It does not correct the stated sagemaker built-in blazingtext choice mechanism. The targeted response is: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. Case evidence: 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.
C:Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses. This addresses a different issue involving shadow deployment model evaluation without response change. It does not correct the stated sagemaker built-in blazingtext choice mechanism. The targeted response is: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. Case evidence: 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:Select a licensed, task-appropriate model and validate its performance and resource needs before a controlled deployment. This addresses a different issue involving sagemaker jumpstart template provenance. It does not correct the stated sagemaker built-in blazingtext choice mechanism. The targeted response is: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. Case evidence: 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 707
At a production AWS ML data lake supporting customer-facing predictions, the following condition is observed: An offline churn dataset uses the latest cancellation-status feature for all historical rows, exposing outcomes not known when earlier predictions would run. Engineers must avoid changing unrelated source partitions. Which observation most directly identifies the root cause of the reported behavior?
- Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query.
- Inspect per-class confusion, worker agreement, label instructions, and disagreements on an adjudicated reference set.
- Inspect categorical cardinality, sparse matrix dimensions, feature contribution, and generalization to unseen identifiers.
- Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines.
Explanation
Correct Answer
A:Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query. This directly tests point-in-time feature data leakage in the reported AWS ML workflow. A feature created after the prediction event cannot legitimately inform that earlier prediction. It distinguishes the problem before choosing a change. The related targeted response is: Perform point-in-time correct joins using the most recent eligible pre-prediction feature record, not the globally latest value. Reported signal: An offline churn dataset uses the latest cancellation-status feature for all historical rows, exposing outcomes not known when earlier predictions would run. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
Incorrect Answers
B:Inspect per-class confusion, worker agreement, label instructions, and disagreements on an adjudicated reference set. This is a possible diagnostic for ground truth labeling agreement review, but it does not directly test the point-in-time feature data leakage failure reported here. Prioritize: Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query. The relevant case is: An offline churn dataset uses the latest cancellation-status feature for all historical rows, exposing outcomes not known when earlier predictions would run. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
C:Inspect categorical cardinality, sparse matrix dimensions, feature contribution, and generalization to unseen identifiers. This is a possible diagnostic for high-cardinality categorical encoding, but it does not directly test the point-in-time feature data leakage failure reported here. Prioritize: Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query. The relevant case is: An offline churn dataset uses the latest cancellation-status feature for all historical rows, exposing outcomes not known when earlier predictions would run. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
D:Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. This is a possible diagnostic for glue data quality non-null contract, but it does not directly test the point-in-time feature data leakage failure reported here. Prioritize: Inspect feature event timestamps, target prediction cutoffs, and join predicates in the historical training query. The relevant case is: An offline churn dataset uses the latest cancellation-status feature for all historical rows, exposing outcomes not known when earlier predictions would run. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
Question 708
As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. 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.
- Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries.
- Remove or pseudonymize unnecessary PII before annotation and restrict access to the token mapping under separate controls.
- Increase appropriate retention before long maintenance and persist a durable downstream historical copy for replay beyond retention.
- Inspect shared entity identifiers across partitions and compare patient-level versus image-level evaluation results.
- Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes.
Explanation
Correct Answers
A:Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries. This directly tests s3 object event at-least-once processing in the reported AWS ML workflow. Event notifications can be delivered more than once; consuming an event is not proof of exactly-once effects. It distinguishes the problem before choosing a change. The related targeted response is: Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
E:Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes. This is the appropriate controlled remedy for s3 object event at-least-once processing. Event notifications can be delivered more than once; consuming an event is not proof of exactly-once effects. Verify the cause with: Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries. Then confirm: Replaying the same notification leaves exactly one corresponding logical training record and records deduplication. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Incorrect Answers
B:Remove or pseudonymize unnecessary PII before annotation and restrict access to the token mapping under separate controls. This selection concerns pii masking before model labeling rather than the required diagnostic-and-remedy pair for s3 object event at-least-once processing. Use evidence: Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries. and the matching correction: Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes. Signal: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
C:Increase appropriate retention before long maintenance and persist a durable downstream historical copy for replay beyond retention. This selection concerns kinesis consumer retention gap rather than the required diagnostic-and-remedy pair for s3 object event at-least-once processing. Use evidence: Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries. and the matching correction: Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes. Signal: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
D:Inspect shared entity identifiers across partitions and compare patient-level versus image-level evaluation results. This selection concerns group-leakage train and validation split rather than the required diagnostic-and-remedy pair for s3 object event at-least-once processing. Use evidence: Inspect event identifiers, object versions or ETags, processing ledger, and downstream record keys for duplicate deliveries. and the matching correction: Make the ingestion handler idempotent using a stable object/version key and conditional ledger writes. Signal: An S3 event-triggered feature ingestion function processes the same uploaded object twice, creating duplicate labeled samples. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Question 709
As a regulated ML workload prepares for an automated regional rollout, the following condition is observed: A SageMaker endpoint role has s3:GetObject for a model artifact, but download fails because the artifact is encrypted under a KMS key in a different account. The team must demonstrate a repeatable monitoring or security control. What postchange observation provides the strongest acceptance evidence?
- The monitor joins each known labeled request to the corresponding earlier prediction and computes expected metrics.
- The chosen fix reduces measured end-to-end p95 latency and component metrics explain the change.
- A test write to an approved prefix succeeds, while writes to unapproved external destinations are denied.
- The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it.
Explanation
Correct Answer
D:The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it. This is the acceptance evidence for the described s3 sse-kms cross-account model artifact access scenario. S3 object permission does not imply access to the KMS encryption key used on the object. The corrective implementation it validates is: Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. Reported signal: A SageMaker endpoint role has s3:GetObject for a model artifact, but download fails because the artifact is encrypted under a KMS key in a different account. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
Incorrect Answers
A:The monitor joins each known labeled request to the corresponding earlier prediction and computes expected metrics. This could validate model monitor ground truth association, but it does not establish that s3 sse-kms cross-account model artifact access is resolved for this workload. Confirm instead: The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it. Observed problem: A SageMaker endpoint role has s3:GetObject for a model artifact, but download fails because the artifact is encrypted under a KMS key in a different account. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
B: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 s3 sse-kms cross-account model artifact access is resolved for this workload. Confirm instead: The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it. Observed problem: A SageMaker endpoint role has s3:GetObject for a model artifact, but download fails because the artifact is encrypted under a KMS key in a different account. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
C:A test write to an approved prefix succeeds, while writes to unapproved external destinations are denied. This could validate cross-account s3 bucket exfiltration protection, but it does not establish that s3 sse-kms cross-account model artifact access is resolved for this workload. Confirm instead: The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it. Observed problem: A SageMaker endpoint role has s3:GetObject for a model artifact, but download fails because the artifact is encrypted under a KMS key in a different account. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
Question 710
During an operational load and release rehearsal for SageMaker-hosted inference, the following condition is observed: An ML system retrains on every S3 object event even when the object is a debug file, wasting resources and changing model versions unexpectedly. Change control requires measurable endpoint or pipeline acceptance evidence. What postchange observation provides the strongest acceptance evidence?
- The compiled artifact runs on the target device with validated outputs and acceptable memory and latency.
- Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not.
- The overnight batch completes within its service window while there is no idle always-on inference endpoint charge.
- A deliberately poor candidate halts before production while a passing approved candidate can proceed.
Explanation
Correct Answer
B:Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not. This is the acceptance evidence for the described eventbridge conditional retraining trigger scenario. Event-driven automation needs selective event patterns and readiness checks; every object-write event is not a retraining signal. The corrective implementation it validates is: Filter appropriate validated data-ready events and trigger retraining only after the required dataset manifest is complete. Reported signal: An ML system retrains on every S3 object event even when the object is a debug file, wasting resources and changing model versions unexpectedly. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.
Incorrect Answers
A:The compiled artifact runs on the target device with validated outputs and acceptable memory and latency. This could validate sagemaker neo edge compiler compatibility, but it does not establish that eventbridge conditional retraining trigger is resolved for this workload. Confirm instead: Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not. Observed problem: An ML system retrains on every S3 object event even when the object is a debug file, wasting resources and changing model versions unexpectedly. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.
C:The overnight batch completes within its service window while there is no idle always-on inference endpoint charge. This could validate real-time versus batch inference decision, but it does not establish that eventbridge conditional retraining trigger is resolved for this workload. Confirm instead: Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not. Observed problem: An ML system retrains on every S3 object event even when the object is a debug file, wasting resources and changing model versions unexpectedly. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.
D:A deliberately poor candidate halts before production while a passing approved candidate can proceed. This could validate codepipeline approval gate on model metrics, but it does not establish that eventbridge conditional retraining trigger is resolved for this workload. Confirm instead: Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not. Observed problem: An ML system retrains on every S3 object event even when the object is a debug file, wasting resources and changing model versions unexpectedly. Operational setting: During an operational load and release rehearsal for SageMaker-hosted inference.
