Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Practice Test 30
Question 290
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 corrective action most directly addresses this ML workflow problem?
- Encode hour with sine and cosine cyclic features and validate with a time-aware split.
- Apply a justified log1p transformation with documented treatment of invalid negatives and package it for serving.
- Use rolling-origin or chronological validation with strictly past-derived features and appropriate forecast horizons.
- Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema.
Explanation
Correct Answer
A: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. 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
B:Apply a justified log1p transformation with documented treatment of invalid negatives and package it for serving. This addresses a different issue involving skewed numerical feature log transformation. It does not correct the stated time-series cyclical calendar feature mechanism. The targeted response is: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Case evidence: 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.
C:Use rolling-origin or chronological validation with strictly past-derived features and appropriate forecast horizons. This addresses a different issue involving chronological split for forecast evaluation. It does not correct the stated time-series cyclical calendar feature mechanism. The targeted response is: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Case evidence: 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:Compact the partitioned dataset into appropriately sized Parquet objects without changing the record keys or schema. This addresses a different issue involving columnar file compaction for small objects. It does not correct the stated time-series cyclical calendar feature mechanism. The targeted response is: Encode hour with sine and cosine cyclic features and validate with a time-aware split. Case evidence: 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 291
During production evaluation of a SageMaker AI model candidate, the following condition is observed: Two notebooks deploy different model artifacts under the same informal name, so the team cannot reproduce which code and data generated production predictions. The release is blocked until the underlying model behavior is understood. What targeted change should be implemented after verifying the stated cause?
- Use an unsupervised clustering approach such as k-means after appropriate feature preparation and assess whether groups are meaningful.
- Register immutable model package versions with lineage and require explicit approval before promotion to production.
- Increase justified L2 regularization or reduce model capacity and revalidate with an untouched holdout.
- Remove label-derived or post-outcome features, rebuild a point-in-time split, and recompute explanations and holdout metrics.
Explanation
Correct Answer
B:Register immutable model package versions with lineage and require explicit approval before promotion to production. This is the appropriate controlled remedy for sagemaker model registry candidate approval. A human-readable model nickname is not a reproducible deployment identifier; versioned registry artifacts support controlled promotion. Verify the cause with: Inspect model package version, artifact URI, training metadata, data snapshot, and registry approval state. Then confirm: A production endpoint resolves to one approved model package version with traceable training lineage. Reported signal: Two notebooks deploy different model artifacts under the same informal name, so the team cannot reproduce which code and data generated production predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.
Incorrect Answers
A:Use an unsupervised clustering approach such as k-means after appropriate feature preparation and assess whether groups are meaningful. This addresses a different issue involving clustering for unlabeled customer segments. It does not correct the stated sagemaker model registry candidate approval mechanism. The targeted response is: Register immutable model package versions with lineage and require explicit approval before promotion to production. Case evidence: Two notebooks deploy different model artifacts under the same informal name, so the team cannot reproduce which code and data generated production predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.
C:Increase justified L2 regularization or reduce model capacity and revalidate with an untouched holdout. This addresses a different issue involving overfitting reduced with l2 regularization. It does not correct the stated sagemaker model registry candidate approval mechanism. The targeted response is: Register immutable model package versions with lineage and require explicit approval before promotion to production. Case evidence: Two notebooks deploy different model artifacts under the same informal name, so the team cannot reproduce which code and data generated production predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.
D:Remove label-derived or post-outcome features, rebuild a point-in-time split, and recompute explanations and holdout metrics. This addresses a different issue involving clarify feature attribution against target leakage. It does not correct the stated sagemaker model registry candidate approval mechanism. The targeted response is: Register immutable model package versions with lineage and require explicit approval before promotion to production. Case evidence: Two notebooks deploy different model artifacts under the same informal name, so the team cannot reproduce which code and data generated production predictions. Operational setting: During production evaluation of a SageMaker AI model candidate.
Question 292
While testing a second region for recoverable deployment of the same ML service, the following condition is observed: An edge vision model is deployed to a constrained device with a framework binary and operators assume any model artifact runs on its target accelerator. The deployment must be reproducible without manual console-only fixes. What should the ML engineer inspect FIRST to distinguish this failure from unrelated issues?
- Inspect the DAG of processing, training, evaluation and registration steps, along with parameter and artifact lineage.
- Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format.
- Inspect serverless invocation frequency, cold-start latency, supported provisioned concurrency settings, and cost.
- Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits.
Explanation
Correct Answer
B:Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format. This directly tests sagemaker neo edge compiler compatibility in the reported AWS ML workflow. Edge optimization depends on target hardware and supported operations, not merely copying a cloud training artifact. It distinguishes the problem before choosing a change. The related targeted response is: Compile the supported model for the specific edge target using SageMaker Neo or choose a compatible conversion route. Reported signal: An edge vision model is deployed to a constrained device with a framework binary and operators assume any model artifact runs on its target accelerator. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Incorrect Answers
A:Inspect the DAG of processing, training, evaluation and registration steps, along with parameter and artifact lineage. This is a possible diagnostic for sagemaker pipelines parameterized retraining, but it does not directly test the sagemaker neo edge compiler compatibility failure reported here. Prioritize: Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format. The relevant case is: An edge vision model is deployed to a constrained device with a framework binary and operators assume any model artifact runs on its target accelerator. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:Inspect serverless invocation frequency, cold-start latency, supported provisioned concurrency settings, and cost. This is a possible diagnostic for sagemaker endpoint provisioned concurrency tradeoff, but it does not directly test the sagemaker neo edge compiler compatibility failure reported here. Prioritize: Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format. The relevant case is: An edge vision model is deployed to a constrained device with a framework binary and operators assume any model artifact runs on its target accelerator. Operational setting: While testing a second region for recoverable deployment of the same ML service.
D:Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. This is a possible diagnostic for serverless inference for intermittent requests, but it does not directly test the sagemaker neo edge compiler compatibility failure reported here. Prioritize: Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format. The relevant case is: An edge vision model is deployed to a constrained device with a framework binary and operators assume any model artifact runs on its target accelerator. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 293
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. What targeted change should be implemented after verifying the stated cause?
- Write partitioned columnar Parquet data by event date, register accurate partitions in the catalog, and filter on partition keys.
- Choose partition keys with enough cardinality or reshard the stream for the intended throughput, while preserving required per-key ordering.
- Define event-time windows with appropriate lateness handling and a documented revision policy for late records.
- Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory.
Explanation
Correct Answer
D: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. 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
A:Write partitioned columnar Parquet data by event date, register accurate partitions in the catalog, and filter on partition keys. This addresses a different issue involving partition pruning in s3 parquet training input. It does not correct the stated glue spark join skew on dominant identifier mechanism. The targeted response is: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Case evidence: 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.
B:Choose partition keys with enough cardinality or reshard the stream for the intended throughput, while preserving required per-key ordering. This addresses a different issue involving kinesis data streams shard hot key. It does not correct the stated glue spark join skew on dominant identifier mechanism. The targeted response is: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Case evidence: 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:Define event-time windows with appropriate lateness handling and a documented revision policy for late records. This addresses a different issue involving streaming feature rolling window correctness. It does not correct the stated glue spark join skew on dominant identifier mechanism. The targeted response is: Repartition or salt the skewed join appropriately, or use a justified broadcast join when the small side fits memory. Case evidence: 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 294
As a regional data-pipeline rollout is validated against approved AWS storage and streams, the following condition is observed: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. The data team must preserve event-time meaning and lineage. Which verification result BEST demonstrates that the issue is resolved?
- Agreement on a held-out gold set rises without silently discarding rare legitimate classes.
- A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts.
- For every training row the joined feature timestamp is at or before its prediction timestamp and no label-derived value leaks.
- Validated records preserve the expected label and field order while malformed inputs are reported separately.
Explanation
Correct Answer
B:A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts. This is the acceptance evidence for the described model training data residency boundary scenario. Encrypting copied data does not automatically satisfy geographic residency constraints; placement and access must be controlled. The corrective implementation it validates is: Keep restricted records and dependent training artifacts in approved regions and deny unauthorized replication or cross-region exports. Reported signal: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Incorrect Answers
A:Agreement on a held-out gold set rises without silently discarding rare legitimate classes. This could validate ground truth labeling agreement review, but it does not establish that model training data residency boundary is resolved for this workload. Confirm instead: A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts. Observed problem: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
C:For every training row the joined feature timestamp is at or before its prediction timestamp and no label-derived value leaks. This could validate point-in-time feature data leakage, but it does not establish that model training data residency boundary is resolved for this workload. Confirm instead: A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts. Observed problem: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
D:Validated records preserve the expected label and field order while malformed inputs are reported separately. This could validate csv schema ambiguity during ingestion, but it does not establish that model training data residency boundary is resolved for this workload. Confirm instead: A test batch remains in the approved region with enforceable policy and audit evidence for all derived artifacts. Observed problem: A regulated ML pipeline copies EU-only customer records into an unapproved cross-region training bucket for convenience. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Question 295
During a production MLOps reliability and security review, the following condition is observed: A deployment pipeline is denied iam:PassRole for its approved SageMaker execution role, but the proposed fix allows passing every role in the account. The owner needs an auditable resolution without broadening privileges. What postchange observation provides the strongest acceptance evidence?
- Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms.
- The pipeline deploys with the authorized role and cannot assign an unrelated privileged role.
- The deployed model bytes match the signed or approved manifest and a tampered artifact fails validation.
- The monitor joins each known labeled request to the corresponding earlier prediction and computes expected metrics.
Explanation
Correct Answer
B:The pipeline deploys with the authorized role and cannot assign an unrelated privileged role. This is the acceptance evidence for the described iam passrole constraint for model deployment scenario. PassRole authorizes delegation of role credentials to a service; wide permissions can enable privilege escalation. The corrective implementation it validates is: Permit iam:PassRole only for the named execution role, constrained to the intended SageMaker service as appropriate. Reported signal: A deployment pipeline is denied iam:PassRole for its approved SageMaker execution role, but the proposed fix allows passing every role in the account. Operational setting: During a production MLOps reliability and security review.
Incorrect Answers
A:Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. This could validate cloudwatch 5xxerrors endpoint saturation, but it does not establish that iam passrole constraint for model deployment is resolved for this workload. Confirm instead: The pipeline deploys with the authorized role and cannot assign an unrelated privileged role. Observed problem: A deployment pipeline is denied iam:PassRole for its approved SageMaker execution role, but the proposed fix allows passing every role in the account. Operational setting: During a production MLOps reliability and security review.
C:The deployed model bytes match the signed or approved manifest and a tampered artifact fails validation. This could validate model artifact supply-chain integrity, but it does not establish that iam passrole constraint for model deployment is resolved for this workload. Confirm instead: The pipeline deploys with the authorized role and cannot assign an unrelated privileged role. Observed problem: A deployment pipeline is denied iam:PassRole for its approved SageMaker execution role, but the proposed fix allows passing every role in the account. Operational setting: During a production MLOps reliability and security review.
D: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 iam passrole constraint for model deployment is resolved for this workload. Confirm instead: The pipeline deploys with the authorized role and cannot assign an unrelated privileged role. Observed problem: A deployment pipeline is denied iam:PassRole for its approved SageMaker execution role, but the proposed fix allows passing every role in the account. Operational setting: During a production MLOps reliability and security review.
Question 296
While testing a second region for recoverable deployment of the same ML service, the following condition is observed: A model endpoint repeatedly deploys an image tagged latest, causing unexpectedly different runtime libraries after each redeploy. The deployment must be reproducible without manual console-only fixes. What targeted change should be implemented after verifying the stated cause?
- Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress.
- Use a compatible SageMaker inference pipeline with ordered containers or a single packaged equivalent for shared preprocessing.
- Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not.
- Reference an approved immutable image digest or controlled version tag and retain a reproducible build record.
Explanation
Correct Answer
D:Reference an approved immutable image digest or controlled version tag and retain a reproducible build record. This is the appropriate controlled remedy for ecr immutable image digest for inference. Mutable container tags can point to different images; reproducible ML deployment needs immutable artifact references. Verify the cause with: Inspect ECR image digest, tag history, pipeline manifests, and built-image package inventory. Then confirm: Identical deployment revisions resolve to the same container image digest and environment dependencies. Reported signal: A model endpoint repeatedly deploys an image tagged latest, causing unexpectedly different runtime libraries after each redeploy. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Incorrect Answers
A:Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. This addresses a different issue involving sagemaker vpc endpoint access for private artifacts. It does not correct the stated ecr immutable image digest for inference mechanism. The targeted response is: Reference an approved immutable image digest or controlled version tag and retain a reproducible build record. Case evidence: A model endpoint repeatedly deploys an image tagged latest, causing unexpectedly different runtime libraries after each redeploy. Operational setting: While testing a second region for recoverable deployment of the same ML service.
B:Use a compatible SageMaker inference pipeline with ordered containers or a single packaged equivalent for shared preprocessing. This addresses a different issue involving multi-container inference pipeline responsibilities. It does not correct the stated ecr immutable image digest for inference mechanism. The targeted response is: Reference an approved immutable image digest or controlled version tag and retain a reproducible build record. Case evidence: A model endpoint repeatedly deploys an image tagged latest, causing unexpectedly different runtime libraries after each redeploy. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. This addresses a different issue involving serverless inference for intermittent requests. It does not correct the stated ecr immutable image digest for inference mechanism. The targeted response is: Reference an approved immutable image digest or controlled version tag and retain a reproducible build record. Case evidence: A model endpoint repeatedly deploys an image tagged latest, causing unexpectedly different runtime libraries after each redeploy. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 297
During a controlled replay of the data-preparation workflow in a separate ML staging account, the following condition is observed: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. The dataset contract must remain reproducible for a backfill. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.
- Use controlled incremental extraction or a suitable read replica and throttle export jobs within the approved data freshness target.
- Compare vocabulary hashes, normalization steps, token IDs for test strings, and serialized preprocessing versions.
- Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field.
- Encode hour with sine and cosine cyclic features and validate with a time-aware split.
- Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features.
Explanation
Correct Answers
C:Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field. This directly tests glue schema evolution with mixed input types in the reported AWS ML workflow. A catalog entry does not automatically reconcile incompatible field types across all source partitions. It distinguishes the problem before choosing a change. The related targeted response is: Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
E:Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. This is the appropriate controlled remedy for glue schema evolution with mixed input types. A catalog entry does not automatically reconcile incompatible field types across all source partitions. Verify the cause with: Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field. Then confirm: Both supported source versions produce the agreed typed feature, and invalid values enter an auditable reject path. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Incorrect Answers
A:Use controlled incremental extraction or a suitable read replica and throttle export jobs within the approved data freshness target. This selection concerns rds extraction overload into ml rather than the required diagnostic-and-remedy pair for glue schema evolution with mixed input types. Use evidence: Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field. and the matching correction: Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. Signal: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
B:Compare vocabulary hashes, normalization steps, token IDs for test strings, and serialized preprocessing versions. This selection concerns text tokenization mismatch in serving rather than the required diagnostic-and-remedy pair for glue schema evolution with mixed input types. Use evidence: Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field. and the matching correction: Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. Signal: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. 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 selection concerns time-series cyclical calendar feature rather than the required diagnostic-and-remedy pair for glue schema evolution with mixed input types. Use evidence: Compare source schemas by partition, Glue Data Catalog types, and failed cast rows for the evolving field. and the matching correction: Define explicit compatible conversions and schema contracts, isolate incompatible versions, and validate before publishing features. Signal: New event producers change a numerical source field to strings while legacy objects remain numeric, causing the shared Glue transformation to fail. Operational setting: During a controlled replay of the data-preparation workflow in a separate ML staging account.
Question 298
While reproducing the alert in an isolated AWS ML integration account, the following condition is observed: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. The proposed change must preserve logging and least privilege. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.
- Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs.
- Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics.
- Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family.
- Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes.
- Capture stable prediction identifiers and ingest verified labels with matching keys for model-quality analysis.
Explanation
Correct Answers
B:Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics. This directly tests clarify postdeployment group bias monitoring in the reported AWS ML workflow. Aggregate performance can mask group-specific shifts; fairness monitoring must examine appropriate group metrics. It distinguishes the problem before choosing a change. The related targeted response is: Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
D:Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes. This is the appropriate controlled remedy for clarify postdeployment group bias monitoring. Aggregate performance can mask group-specific shifts; fairness monitoring must examine appropriate group metrics. Verify the cause with: Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics. Then confirm: Auditors see reproducible subgroup statistics and alarms for material disparities rather than only global totals. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
Incorrect Answers
A:Inspect image layers, environment configuration, secret source, runtime role permissions, and rotation logs. This selection concerns secret rotation for inference container credentials rather than the required diagnostic-and-remedy pair for clarify postdeployment group bias monitoring. Use evidence: Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics. and the matching correction: Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes. Signal: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
C:Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. This selection concerns inference recommender benchmarking instance family rather than the required diagnostic-and-remedy pair for clarify postdeployment group bias monitoring. Use evidence: Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics. and the matching correction: Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes. Signal: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
E:Capture stable prediction identifiers and ingest verified labels with matching keys for model-quality analysis. This selection concerns model monitor ground truth association rather than the required diagnostic-and-remedy pair for clarify postdeployment group bias monitoring. Use evidence: Inspect group-level prediction and label distributions, subgroup sample sizes, and configured bias metrics. and the matching correction: Use appropriate SageMaker Clarify model-bias monitoring and investigate supported group differences before deployment changes. Signal: A model's overall approval rate remains stable while approval differences between customer groups increase after a data-source migration. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
Question 299
While testing a second region for recoverable deployment of the same ML service, the following condition is observed: A custom image works when run locally but SageMaker cannot invoke it because the container lacks an expected health route and invocation handler. The deployment must be reproducible without manual console-only fixes. Which verification result BEST demonstrates that the issue is resolved?
- Only the intended completed data batch launches one controlled training workflow, while unrelated objects do not.
- A synthetic load surge meets error and latency SLOs without rejected provisioning due to quota or startup lag.
- The build uploads signed artifacts successfully while unauthorized buckets and prefixes remain denied.
- Endpoint health becomes Ready and inference returns the specified payload type for a known test request.
Explanation
Correct Answer
D:Endpoint health becomes Ready and inference returns the specified payload type for a known test request. This is the acceptance evidence for the described bring-your-own-inference-container contract scenario. A Docker image is not automatically a SageMaker-compatible inference server without the runtime HTTP contract. The corrective implementation it validates is: Implement the SageMaker inference container /ping and /invocations expectations or use a supported serving toolkit. Reported signal: A custom image works when run locally but SageMaker cannot invoke it because the container lacks an expected health route and invocation handler. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Incorrect Answers
A: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 bring-your-own-inference-container contract is resolved for this workload. Confirm instead: Endpoint health becomes Ready and inference returns the specified payload type for a known test request. Observed problem: A custom image works when run locally but SageMaker cannot invoke it because the container lacks an expected health route and invocation handler. Operational setting: While testing a second region for recoverable deployment of the same ML service.
B:A synthetic load surge meets error and latency SLOs without rejected provisioning due to quota or startup lag. This could validate endpoint scale-to-zero cold capacity planning, but it does not establish that bring-your-own-inference-container contract is resolved for this workload. Confirm instead: Endpoint health becomes Ready and inference returns the specified payload type for a known test request. Observed problem: A custom image works when run locally but SageMaker cannot invoke it because the container lacks an expected health route and invocation handler. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:The build uploads signed artifacts successfully while unauthorized buckets and prefixes remain denied. This could validate codebuild iam least-privilege artifact upload, but it does not establish that bring-your-own-inference-container contract is resolved for this workload. Confirm instead: Endpoint health becomes Ready and inference returns the specified payload type for a known test request. Observed problem: A custom image works when run locally but SageMaker cannot invoke it because the container lacks an expected health route and invocation handler. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 300
As a regional data-pipeline rollout is validated against approved AWS storage and streams, 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 data team must preserve event-time meaning and lineage. What postchange observation provides the strongest acceptance evidence?
- Both supported source versions produce the agreed typed feature, and invalid values enter an auditable reject path.
- Neighboring times across midnight map close in cyclic feature space and validation improves without leakage.
- Training converges more consistently, and the same raw request gives aligned standardized values online.
- The recovery run reads a complete expected interval from retained stream records or durable archive without silent gaps.
Explanation
Correct Answer
B:Neighboring times across midnight map close in cyclic feature space and validation improves without leakage. This is the acceptance evidence for the described time-series cyclical calendar feature scenario. Time-of-day has periodic topology; raw integer distance does not represent wraparound. The corrective implementation it validates is: Encode hour with sine and cosine cyclic features and validate with a time-aware split. 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: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
Incorrect Answers
A:Both supported source versions produce the agreed typed feature, and invalid values enter an auditable reject path. This could validate glue schema evolution with mixed input types, but it does not establish that time-series cyclical calendar feature is resolved for this workload. Confirm instead: Neighboring times across midnight map close in cyclic feature space and validation improves without leakage. Observed problem: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
C:Training converges more consistently, and the same raw request gives aligned standardized values online. This could validate standardization of numerical features, but it does not establish that time-series cyclical calendar feature is resolved for this workload. Confirm instead: Neighboring times across midnight map close in cyclic feature space and validation improves without leakage. Observed problem: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
D:The recovery run reads a complete expected interval from retained stream records or durable archive without silent gaps. This could validate kinesis consumer retention gap, but it does not establish that time-series cyclical calendar feature is resolved for this workload. Confirm instead: Neighboring times across midnight map close in cyclic feature space and validation improves without leakage. Observed problem: A demand model treats hour 23 and hour 0 as far apart when integer hour is used as a linear continuous feature. Operational setting: As a regional data-pipeline rollout is validated against approved AWS storage and streams.
