Amazon AWS Certified Machine Learning Engineer - Associate MLA-C01 Practice Test 100
Question 990
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. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.
- Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events.
- Use structured logging and scoped CloudWatch Logs Insights queries to aggregate failures by training job and time.
- Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access.
- Enable appropriate CloudTrail S3 data events for the sensitive dataset with protected storage and retention.
- Inspect captured request IDs, ground-truth keys, and the quality monitor dataset schema.
Explanation
Correct Answers
A:Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events. This directly tests s3 sse-kms cross-account model artifact access in the reported AWS ML workflow. S3 object permission does not imply access to the KMS encryption key used on the object. It distinguishes the problem before choosing a change. The related targeted response is: Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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.
C:Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. This is the appropriate controlled remedy for s3 sse-kms cross-account model artifact access. S3 object permission does not imply access to the KMS encryption key used on the object. Verify the cause with: Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events. Then confirm: The endpoint loads the intended encrypted artifact while unrelated principals cannot decrypt it. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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
B:Use structured logging and scoped CloudWatch Logs Insights queries to aggregate failures by training job and time. This selection concerns cloudwatch logs insights error correlation rather than the required diagnostic-and-remedy pair for s3 sse-kms cross-account model artifact access. Use evidence: Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events. and the matching correction: Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. 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.
D:Enable appropriate CloudTrail S3 data events for the sensitive dataset with protected storage and retention. This selection concerns cloudtrail training data access audit coverage rather than the required diagnostic-and-remedy pair for s3 sse-kms cross-account model artifact access. Use evidence: Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events. and the matching correction: Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. 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.
E:Inspect captured request IDs, ground-truth keys, and the quality monitor dataset schema. This selection concerns model monitor ground truth association rather than the required diagnostic-and-remedy pair for s3 sse-kms cross-account model artifact access. Use evidence: Inspect S3 object encryption, key policy, grant permissions, IAM role, and denied KMS decrypt events. and the matching correction: Authorize the specific serving role to decrypt with the relevant KMS key under a restricted key policy and S3 access. 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.
Question 991
During production evaluation of a SageMaker AI model candidate, the following condition is observed: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. The release is blocked until the underlying model behavior is understood. Which TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.
- Configure SageMaker Automatic Model Tuning with a bounded search space, objective metric, budget, and justified Bayesian or random strategy.
- Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses.
- Use justified feature selection or sparsity constraints fitted on training folds before retraining.
- Inspect feature importance stability, variance across folds, regularization and model dimensionality.
- Inspect target types, business loss function, sample labels, and whether the required output is continuous or categorical.
Explanation
Correct Answers
C:Use justified feature selection or sparsity constraints fitted on training folds before retraining. This is the appropriate controlled remedy for feature selection to reduce overparameterization. Unnecessary high-dimensional inputs can increase variance and compute cost; selection itself must avoid evaluation leakage. Verify the cause with: Inspect feature importance stability, variance across folds, regularization and model dimensionality. Then confirm: Holdout quality stays acceptable while model size and run-to-run instability decrease. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. Operational setting: During production evaluation of a SageMaker AI model candidate.
D:Inspect feature importance stability, variance across folds, regularization and model dimensionality. This directly tests feature selection to reduce overparameterization in the reported AWS ML workflow. Unnecessary high-dimensional inputs can increase variance and compute cost; selection itself must avoid evaluation leakage. It distinguishes the problem before choosing a change. The related targeted response is: Use justified feature selection or sparsity constraints fitted on training folds before retraining. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. Operational setting: During production evaluation of a SageMaker AI model candidate.
Incorrect Answers
A:Configure SageMaker Automatic Model Tuning with a bounded search space, objective metric, budget, and justified Bayesian or random strategy. This selection concerns hyperparameter bayesian tuning strategy rather than the required diagnostic-and-remedy pair for feature selection to reduce overparameterization. Use evidence: Inspect feature importance stability, variance across folds, regularization and model dimensionality. and the matching correction: Use justified feature selection or sparsity constraints fitted on training folds before retraining. Signal: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. Operational setting: During production evaluation of a SageMaker AI model candidate.
B:Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses. This selection concerns shadow deployment model evaluation without response change rather than the required diagnostic-and-remedy pair for feature selection to reduce overparameterization. Use evidence: Inspect feature importance stability, variance across folds, regularization and model dimensionality. and the matching correction: Use justified feature selection or sparsity constraints fitted on training folds before retraining. Signal: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. Operational setting: During production evaluation of a SageMaker AI model candidate.
E:Inspect target types, business loss function, sample labels, and whether the required output is continuous or categorical. This selection concerns regression versus classification problem formulation rather than the required diagnostic-and-remedy pair for feature selection to reduce overparameterization. Use evidence: Inspect feature importance stability, variance across folds, regularization and model dimensionality. and the matching correction: Use justified feature selection or sparsity constraints fitted on training folds before retraining. Signal: A text classifier includes thousands of weak correlated features and becomes unstable across repeated training runs. Operational setting: During production evaluation of a SageMaker AI model candidate.
Question 992
While reproducing the alert in an isolated AWS ML integration account, the following condition is observed: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. The proposed change must preserve logging and least privilege. Which TWO steps best establish the evidence and correct the identified root cause? Select TWO.
- Scale compatible asynchronous inference capacity or tune workload and queue alarms for pending-request age.
- Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails.
- Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation.
- Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest.
- Pin an immutable approved artifact version or content digest and verify integrity before deployment.
Explanation
Correct Answers
D:Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. This directly tests model artifact supply-chain integrity in the reported AWS ML workflow. Object names alone do not guarantee model provenance; supply-chain checks bind deployment to reviewed bytes. It distinguishes the problem before choosing a change. The related targeted response is: Pin an immutable approved artifact version or content digest and verify integrity before deployment. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
E:Pin an immutable approved artifact version or content digest and verify integrity before deployment. This is the appropriate controlled remedy for model artifact supply-chain integrity. Object names alone do not guarantee model provenance; supply-chain checks bind deployment to reviewed bytes. Verify the cause with: Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. Then confirm: The deployed model bytes match the signed or approved manifest and a tampered artifact fails validation. This is one part of a select-two decision; the matching evidence and corrective action are both required. Reported signal: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
Incorrect Answers
A:Scale compatible asynchronous inference capacity or tune workload and queue alarms for pending-request age. This selection concerns asynchronous inference queue backlog alert rather than the required diagnostic-and-remedy pair for model artifact supply-chain integrity. Use evidence: Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. and the matching correction: Pin an immutable approved artifact version or content digest and verify integrity before deployment. Signal: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
B:Restrict writes to approved bucket prefixes and apply appropriate resource and organizational guardrails. This selection concerns cross-account s3 bucket exfiltration protection rather than the required diagnostic-and-remedy pair for model artifact supply-chain integrity. Use evidence: Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. and the matching correction: Pin an immutable approved artifact version or content digest and verify integrity before deployment. Signal: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
C:Inspect constraint threshold selection, false-positive incidents, feature importance and baseline seasonal variation. This selection concerns model monitor violation alert calibration rather than the required diagnostic-and-remedy pair for model artifact supply-chain integrity. Use evidence: Compare evaluated artifact hash, S3 object version, package provenance, and deployment manifest. and the matching correction: Pin an immutable approved artifact version or content digest and verify integrity before deployment. Signal: A release pipeline downloads an ML model artifact from a mutable object key and deploys it without checking whether its bytes changed since approval. Operational setting: While reproducing the alert in an isolated AWS ML integration account.
Question 993
At a production AWS ML data lake supporting customer-facing predictions, the following condition is observed: A source feed silently begins emitting missing customer IDs, and the downstream pipeline trains on rows with null entity keys instead of failing. Engineers must avoid changing unrelated source partitions. Which investigation provides the most decisive FIRST evidence for the underlying problem?
- Inspect categorical cardinality, sparse matrix dimensions, feature contribution, and generalization to unseen identifiers.
- Inspect feature availability timestamps and whether each label time follows the last feature observation.
- Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines.
- Inspect quantiles, heavy-tail plots, outliers, and the target model's response to feature scale.
Explanation
Correct Answer
C:Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. This directly tests glue data quality non-null contract in the reported AWS ML workflow. Schema existence alone cannot establish semantic completeness or identifier uniqueness in ML inputs. It distinguishes the problem before choosing a change. The related targeted response is: Enforce a required non-null or uniqueness contract with thresholds; quarantine violating partitions before feature publication. Reported signal: A source feed silently begins emitting missing customer IDs, and the downstream pipeline trains on rows with null entity keys instead of failing. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
Incorrect Answers
A: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 glue data quality non-null contract failure reported here. Prioritize: Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. The relevant case is: A source feed silently begins emitting missing customer IDs, and the downstream pipeline trains on rows with null entity keys instead of failing. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
B:Inspect feature availability timestamps and whether each label time follows the last feature observation. This is a possible diagnostic for chronological split for forecast evaluation, but it does not directly test the glue data quality non-null contract failure reported here. Prioritize: Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. The relevant case is: A source feed silently begins emitting missing customer IDs, and the downstream pipeline trains on rows with null entity keys instead of failing. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
D:Inspect quantiles, heavy-tail plots, outliers, and the target model's response to feature scale. This is a possible diagnostic for skewed numerical feature log transformation, but it does not directly test the glue data quality non-null contract failure reported here. Prioritize: Inspect AWS Glue Data Quality rule evaluations, missing-key rates, source partitions, and prior accepted baselines. The relevant case is: A source feed silently begins emitting missing customer IDs, and the downstream pipeline trains on rows with null entity keys instead of failing. Operational setting: At a production AWS ML data lake supporting customer-facing predictions.
Question 994
While testing a second region for recoverable deployment of the same ML service, the following condition is observed: An online classifier faces bursty demand and latency spikes because auto scaling tracks host CPU while requests spend most time waiting for accelerated inference. The deployment must be reproducible without manual console-only fixes. Which engineering response resolves the actual issue without masking the symptoms?
- Use SageMaker asynchronous inference with S3 input/output and suitable queue and notification settings.
- Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance.
- Filter appropriate validated data-ready events and trigger retraining only after the required dataset manifest is complete.
- Set adequate minimum capacity, scaling limits, alarms, and request backpressure for the expected traffic ramp.
Explanation
Correct Answer
B:Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance. This is the appropriate controlled remedy for sagemaker endpoint auto scaling metric selection. CPU percentage can be poorly correlated with accelerator-bound inference demand; scale on a meaningful signal. Verify the cause with: Compare invocation count per instance, model latency, GPU utilization, and the behavior of current scaling policy. Then confirm: Capacity responds to peak request load and p95 latency improves without continual scale oscillation. Reported signal: An online classifier faces bursty demand and latency spikes because auto scaling tracks host CPU while requests spend most time waiting for accelerated inference. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Incorrect Answers
A:Use SageMaker asynchronous inference with S3 input/output and suitable queue and notification settings. This addresses a different issue involving asynchronous endpoint for large payloads. It does not correct the stated sagemaker endpoint auto scaling metric selection mechanism. The targeted response is: Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance. Case evidence: An online classifier faces bursty demand and latency spikes because auto scaling tracks host CPU while requests spend most time waiting for accelerated inference. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:Filter appropriate validated data-ready events and trigger retraining only after the required dataset manifest is complete. This addresses a different issue involving eventbridge conditional retraining trigger. It does not correct the stated sagemaker endpoint auto scaling metric selection mechanism. The targeted response is: Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance. Case evidence: An online classifier faces bursty demand and latency spikes because auto scaling tracks host CPU while requests spend most time waiting for accelerated inference. Operational setting: While testing a second region for recoverable deployment of the same ML service.
D:Set adequate minimum capacity, scaling limits, alarms, and request backpressure for the expected traffic ramp. This addresses a different issue involving endpoint scale-to-zero cold capacity planning. It does not correct the stated sagemaker endpoint auto scaling metric selection mechanism. The targeted response is: Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance. Case evidence: An online classifier faces bursty demand and latency spikes because auto scaling tracks host CPU while requests spend most time waiting for accelerated inference. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 995
While testing a second region for recoverable deployment of the same ML service, 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 deployment must be reproducible without manual console-only fixes. Which corrective action most directly addresses this ML workflow problem?
- 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.
- Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance.
- Use SageMaker asynchronous inference with S3 input/output and suitable queue and notification settings.
Explanation
Correct Answer
A:Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. This is the appropriate controlled remedy for sagemaker vpc endpoint access for private artifacts. VPC isolation requires explicit supported network paths to AWS services; IAM permission alone does not create connectivity. Verify the cause with: Inspect route tables, S3 VPC endpoint association, security policies, endpoint policies, and S3 access logs. Then confirm: The deployment loads artifacts privately and blocked public routes remain unused. 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: 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 addresses a different issue involving multi-container inference pipeline responsibilities. It does not correct the stated sagemaker vpc endpoint access for private artifacts mechanism. The targeted response is: Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. Case evidence: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: While testing a second region for recoverable deployment of the same ML service.
C:Configure a justified endpoint variant auto scaling policy using a workload-relevant supported metric such as invocations per instance. This addresses a different issue involving sagemaker endpoint auto scaling metric selection. It does not correct the stated sagemaker vpc endpoint access for private artifacts mechanism. The targeted response is: Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. Case evidence: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: While testing a second region for recoverable deployment of the same ML service.
D:Use SageMaker asynchronous inference with S3 input/output and suitable queue and notification settings. This addresses a different issue involving asynchronous endpoint for large payloads. It does not correct the stated sagemaker vpc endpoint access for private artifacts mechanism. The targeted response is: Provide an approved S3 gateway or interface endpoint path and least-privilege bucket/role permissions without unnecessarily opening internet egress. Case evidence: A private-subnet inference deployment cannot retrieve its S3 model artifact because the network has no authorized path to the bucket. Operational setting: While testing a second region for recoverable deployment of the same ML service.
Question 996
As a regulated ML workload prepares for an automated regional rollout, the following condition is observed: A deployed credit-risk model begins receiving applicants with income distributions unlike training data, but dashboard operators only track endpoint HTTP 200 rates. The team must demonstrate a repeatable monitoring or security control. What postchange observation provides the strongest acceptance evidence?
- Changed feature distributions produce attributable violations even while endpoint availability remains healthy.
- Auditors see reproducible subgroup statistics and alarms for material disparities rather than only global totals.
- Backlog age stabilizes and requests complete within the agreed service-level window.
- Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms.
Explanation
Correct Answer
A:Changed feature distributions produce attributable violations even while endpoint availability remains healthy. This is the acceptance evidence for the described sagemaker model monitor feature drift baseline scenario. Endpoint uptime does not demonstrate feature-distribution stability; monitoring compares current inputs with expected statistics. The corrective implementation it validates is: Configure data capture and an appropriate Model Monitor baseline with scheduled data-quality checks. Reported signal: A deployed credit-risk model begins receiving applicants with income distributions unlike training data, but dashboard operators only track endpoint HTTP 200 rates. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
Incorrect Answers
B:Auditors see reproducible subgroup statistics and alarms for material disparities rather than only global totals. This could validate clarify postdeployment group bias monitoring, but it does not establish that sagemaker model monitor feature drift baseline is resolved for this workload. Confirm instead: Changed feature distributions produce attributable violations even while endpoint availability remains healthy. Observed problem: A deployed credit-risk model begins receiving applicants with income distributions unlike training data, but dashboard operators only track endpoint HTTP 200 rates. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
C:Backlog age stabilizes and requests complete within the agreed service-level window. This could validate asynchronous inference queue backlog alert, but it does not establish that sagemaker model monitor feature drift baseline is resolved for this workload. Confirm instead: Changed feature distributions produce attributable violations even while endpoint availability remains healthy. Observed problem: A deployed credit-risk model begins receiving applicants with income distributions unlike training data, but dashboard operators only track endpoint HTTP 200 rates. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
D: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 sagemaker model monitor feature drift baseline is resolved for this workload. Confirm instead: Changed feature distributions produce attributable violations even while endpoint availability remains healthy. Observed problem: A deployed credit-risk model begins receiving applicants with income distributions unlike training data, but dashboard operators only track endpoint HTTP 200 rates. Operational setting: As a regulated ML workload prepares for an automated regional rollout.
Question 997
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 TWO complementary choices provide the decisive diagnosis AND corrective response? Select TWO.
- Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses.
- Train a gradient-boosted tree baseline such as SageMaker XGBoost and compare it against more complex candidates.
- Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels.
- Inspect the supervised labels, text representation, model-input format, and the desired classification output.
- Inspect feature importance stability, variance across folds, regularization and model dimensionality.
Explanation
Correct Answers
C: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. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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.
D: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. This is one part of a select-two decision; the matching evidence and corrective action are both required. 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:Deploy a SageMaker shadow variant for observational comparison before promoting the new model to served responses. This selection concerns shadow deployment model evaluation without response change rather than the required diagnostic-and-remedy pair for sagemaker built-in blazingtext choice. Use evidence: Inspect the supervised labels, text representation, model-input format, and the desired classification output. and the matching correction: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. 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.
B:Train a gradient-boosted tree baseline such as SageMaker XGBoost and compare it against more complex candidates. This selection concerns xgboost tabular classification baseline rather than the required diagnostic-and-remedy pair for sagemaker built-in blazingtext choice. Use evidence: Inspect the supervised labels, text representation, model-input format, and the desired classification output. and the matching correction: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. 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.
E:Inspect feature importance stability, variance across folds, regularization and model dimensionality. This selection concerns feature selection to reduce overparameterization rather than the required diagnostic-and-remedy pair for sagemaker built-in blazingtext choice. Use evidence: Inspect the supervised labels, text representation, model-input format, and the desired classification output. and the matching correction: Use an appropriate text classification model or supported SageMaker BlazingText supervised approach with validated labels. 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.
Question 998
During a production MLOps reliability and security review, the following condition is observed: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. The owner needs an auditable resolution without broadening privileges. What should the ML engineer inspect FIRST to distinguish this failure from unrelated issues?
- Compare ModelLatency with OverheadLatency, client network timing, invocation counts, and endpoint 5XX responses.
- Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations.
- Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence.
- Compare incoming captured feature statistics against a stored training baseline and review SageMaker Model Monitor drift alerts.
Explanation
Correct Answer
B:Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. This directly tests inference recommender benchmarking instance family in the reported AWS ML workflow. Rightsizing depends on workload measurements rather than the training machine or instance size alone. It distinguishes the problem before choosing a change. The related targeted response is: Use SageMaker Inference Recommender or equivalent controlled load tests to rightsize the serving instance family. Reported signal: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: During a production MLOps reliability and security review.
Incorrect Answers
A:Compare ModelLatency with OverheadLatency, client network timing, invocation counts, and endpoint 5XX responses. This is a possible diagnostic for cloudwatch invocations and modellatency distinction, but it does not directly test the inference recommender benchmarking instance family failure reported here. Prioritize: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. The relevant case is: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: During a production MLOps reliability and security review.
C:Inspect identity and destination bucket policies, resource ARNs, organization restrictions, and CloudTrail data-event evidence. This is a possible diagnostic for cross-account s3 bucket exfiltration protection, but it does not directly test the inference recommender benchmarking instance family failure reported here. Prioritize: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. The relevant case is: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: During a production MLOps reliability and security review.
D:Compare incoming captured feature statistics against a stored training baseline and review SageMaker Model Monitor drift alerts. This is a possible diagnostic for sagemaker model monitor feature drift baseline, but it does not directly test the inference recommender benchmarking instance family failure reported here. Prioritize: Measure memory, throughput, p95 latency and cost across supported candidate endpoint configurations. The relevant case is: A model is deployed to a large general-purpose instance based only on notebook habits, with no comparison of lower-cost inference-optimized choices. Operational setting: During a production MLOps reliability and security review.
Question 999
During an approved rollout of an AWS ML inference workload, the following condition is observed: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. The team must meet its documented availability and rollback constraints. Which investigation provides the most decisive FIRST evidence for the underlying problem?
- Compare invocation count per instance, model latency, GPU utilization, and the behavior of current scaling policy.
- Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits.
- Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format.
- Inspect container startup logs, listening port, health endpoint, MIME types, and inference response contract.
Explanation
Correct Answer
B:Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. This directly tests serverless inference for intermittent requests in the reported AWS ML workflow. Serverless capacity trades some cold-start behavior and resource limits for reduced idle endpoint commitment. It distinguishes the problem before choosing a change. The related targeted response is: Use SageMaker Serverless Inference where the model and latency envelope fit, or justify provisioned capacity if it does not. Reported signal: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an approved rollout of an AWS ML inference workload.
Incorrect Answers
A:Compare invocation count per instance, model latency, GPU utilization, and the behavior of current scaling policy. This is a possible diagnostic for sagemaker endpoint auto scaling metric selection, but it does not directly test the serverless inference for intermittent requests failure reported here. Prioritize: Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. The relevant case is: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an approved rollout of an AWS ML inference workload.
C:Inspect target processor, supported Neo compiler configurations, operator compatibility, and deployment artifact format. This is a possible diagnostic for sagemaker neo edge compiler compatibility, but it does not directly test the serverless inference for intermittent requests failure reported here. Prioritize: Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. The relevant case is: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an approved rollout of an AWS ML inference workload.
D:Inspect container startup logs, listening port, health endpoint, MIME types, and inference response contract. This is a possible diagnostic for bring-your-own-inference-container contract, but it does not directly test the serverless inference for intermittent requests failure reported here. Prioritize: Profile request arrival intervals, cold-start tolerance, memory needs, and compatible serverless inference limits. The relevant case is: A small CPU inference model receives only occasional requests, but a permanently provisioned endpoint stays idle for most hours. Operational setting: During an approved rollout of an AWS ML inference workload.
Question 1000
As a regulated ML workload prepares for an automated regional rollout, 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 team must demonstrate a repeatable monitoring or security control. What targeted change should be implemented after verifying the stated cause?
- Use supported managed Spot Training with durable checkpoints for interruptible phases and retain On-Demand capacity when deadlines demand it.
- Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window.
- Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks.
- Enable appropriate CloudTrail S3 data events for the sensitive dataset with protected storage and retention.
Explanation
Correct Answer
B:Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. This is the appropriate controlled remedy for cloudwatch 5xxerrors endpoint saturation. Daily averages can conceal short capacity failures; monitoring must use an incident-relevant interval. Verify the cause with: Inspect endpoint 5XXErrors, InvocationsPerInstance, instance availability, and per-minute latency distribution. Then confirm: Peak-window 5xx rate and p95 latency fall below service objectives with verified alarms. 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: As a regulated ML workload prepares for an automated regional rollout.
Incorrect Answers
A:Use supported managed Spot Training with durable checkpoints for interruptible phases and retain On-Demand capacity when deadlines demand it. This addresses a different issue involving spot training cost versus interruption recovery. It does not correct the stated cloudwatch 5xxerrors endpoint saturation mechanism. The targeted response is: Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. Case evidence: 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: As a regulated ML workload prepares for an automated regional rollout.
C:Tune justified thresholds and group actionable monitor violations by severity without suppressing critical data-integrity checks. This addresses a different issue involving model monitor violation alert calibration. It does not correct the stated cloudwatch 5xxerrors endpoint saturation mechanism. The targeted response is: Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. Case evidence: 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: As a regulated ML workload prepares for an automated regional rollout.
D:Enable appropriate CloudTrail S3 data events for the sensitive dataset with protected storage and retention. This addresses a different issue involving cloudtrail training data access audit coverage. It does not correct the stated cloudwatch 5xxerrors endpoint saturation mechanism. The targeted response is: Configure actionable alarms, capacity, and supported scaling or backpressure based on the burst window. Case evidence: 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: As a regulated ML workload prepares for an automated regional rollout.
