Exam Bundle

The selected instance meets the latency requirement with measured lower normalized cost than the oversized GPU option. This would verify a different operation: Use comparable inference benchmarks across supported instance families and evaluate total cost per thousand successful requests. That separate action addresses: An enterprise ML team assumes a larger GPU instance always reduces cost although the model is small and memory bandwidth is not a bottleneck. It cannot establish the required Redstone Aviation correction for: An inference endpoint logs complete customer request bodies including personal information even though troubleshooting needs only aggregate timings. The decisive acceptance check is instead: A controlled personal-data request produces timing and error records without the prohibited raw identifiers.

The nightly workload still meets its completion target while cost reports show reduced idle serving hours. This would verify a different operation: Measure invocation patterns and replace unnecessary continuous capacity with supported scheduled batch or appropriately scaled alternatives. That separate action addresses: An inference workload maintains two always-on high-memory SageMaker endpoints for models invoked only during a brief nightly window. It cannot establish the required Redstone Aviation correction for: An inference endpoint logs complete customer request bodies including personal information even though troubleshooting needs only aggregate timings. The decisive acceptance check is instead: A controlled personal-data request produces timing and error records without the prohibited raw identifiers.

A finished training execution releases its compute automatically and leaves only approved persistent artifacts for later evaluation. This would verify a different operation: Use pipeline-dependent training resource lifecycle controls with completion-triggered teardown and failure handling. That separate action addresses: A training environment repeatedly provisions expensive instances after data preparation finishes and leaves them idle until an operator manually stops them. It cannot establish the required Redstone Aviation correction for: An inference endpoint logs complete customer request bodies including personal information even though troubleshooting needs only aggregate timings. The decisive acceptance check is instead: A controlled personal-data request produces timing and error records without the prohibited raw identifiers.

Define seasonal reference windows and calibrated drift thresholds rather than using an inappropriate static training baseline for all periods. It does not directly address the Highland Education case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. It does not directly address the Highland Education case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Create AWS Budgets alerts with defined cost thresholds and route notifications to the accountable ML operations owner. It does not directly address the Highland Education case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

A synthetic slice regression is detected even though the overall average metric remains inside its broad threshold. This would verify a different operation: Create monitored business slices and evaluate approved per-segment metrics and bias indicators using retained ground-truth labels. That separate action addresses: A service tracks only average model prediction values while a narrow segment receives systematically poor results that aggregate statistics hide. It cannot establish the required Highland Education correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records. This would verify a different operation: Track total received records, rejected records and successful predictions with clear denominators across batch processing. That separate action addresses: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. It cannot establish the required Highland Education correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

A low-traffic replay meets p95 response requirements and documents the cost of maintaining necessary warm capacity. This would verify a different operation: Choose a suitable minimum serving capacity or compatible hosting method and validate the idle-cost versus cold-start tradeoff. That separate action addresses: A model endpoint scales to zero immediately after every request but subsequent cold starts repeatedly violate the low-latency objective. It cannot establish the required Highland Education correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Track high-percentile ModelLatency and relevant invocation or backlog metrics with thresholds based on the service-level objective. It does not directly address the Maplewood Schools case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Create a governed delayed-label collection path and compare production predictions with matched observed labels for model quality monitoring. It does not directly address the Maplewood Schools case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Create AWS Budgets alerts with defined cost thresholds and route notifications to the accountable ML operations owner. It does not directly address the Maplewood Schools case: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The relevant acceptance criterion for this case is: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

A controlled event's original prediction joins to the matching eventual label without exposing unauthorized personal identifiers. This would verify a different operation: Retain privacy-preserving stable correlation keys through prediction capture and delayed outcome ingestion. That separate action addresses: An inference monitoring workflow cannot associate captured predictions with later labels because request identifiers are stripped during processing. It cannot establish the required Maplewood Schools correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts. This would verify a different operation: Version monitoring baselines with each released model and capture a reviewed transition policy between old and new expectations. That separate action addresses: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. It cannot establish the required Maplewood Schools correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

A controlled payload replay reproduces the bottleneck and the targeted correction restores throughput without indiscriminate scaling. This would verify a different operation: Correlate payload sizes, invocation mix, ModelLatency and resource metrics to identify the actual throughput constraint. That separate action addresses: A model's endpoint throughput suddenly falls but the operator adds instances before investigating payload size changes in incoming traffic. It cannot establish the required Maplewood Schools correction for: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. The decisive acceptance check is instead: A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage.

Distinguish covariate drift from verified performance degradation and evaluate outcome labels and model-quality metrics separately. It does not directly address the Lakeside Research case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Inspect SageMaker service quotas and scaling target limits and request justified quota changes before increasing traffic. It does not directly address the Lakeside Research case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Add model-specific output-validity checks and application error metrics alongside endpoint health measurements. It does not directly address the Lakeside Research case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

A controlled scale-out reaches the revised allowed capacity and queue depth returns to its operating threshold. This would verify a different operation: Inspect SageMaker service quotas and scaling target limits and request justified quota changes before increasing traffic. That separate action addresses: A scaling endpoint's queue grows despite spare traffic capacity because the service hits its allowed instance scaling quota. It cannot establish the required Lakeside Research correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team. This would verify a different operation: Apply consistent project, environment and model cost-allocation tags and activate the corresponding billing reports. That separate action addresses: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. It cannot establish the required Lakeside Research correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made. This would verify a different operation: Create AWS Budgets alerts with defined cost thresholds and route notifications to the accountable ML operations owner. That separate action addresses: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. It cannot establish the required Lakeside Research correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Track total received records, rejected records and successful predictions with clear denominators across batch processing. It does not directly address the Eastshore Energy case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Monitor predicted probability buckets against observed outcome frequencies using suitable delayed labels and calibration baselines. It does not directly address the Eastshore Energy case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Create a governed delayed-label collection path and compare production predictions with matched observed labels for model quality monitoring. It does not directly address the Eastshore Energy case: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The relevant acceptance criterion for this case is: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline. This would verify a different operation: Evaluate SageMaker Managed Spot Training with checkpointing and compare interruption risk and effective completion cost. That separate action addresses: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. It cannot establish the required Eastshore Energy correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

A low-traffic replay meets p95 response requirements and documents the cost of maintaining necessary warm capacity. This would verify a different operation: Choose a suitable minimum serving capacity or compatible hosting method and validate the idle-cost versus cold-start tradeoff. That separate action addresses: A model endpoint scales to zero immediately after every request but subsequent cold starts repeatedly violate the low-latency objective. It cannot establish the required Eastshore Energy correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation. This would verify a different operation: Use AWS Cost Explorer and properly applied resource tags to compare endpoint, training and storage cost changes over time. That separate action addresses: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. It cannot establish the required Eastshore Energy correction for: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. The decisive acceptance check is instead: A training role cannot approve its own model package and a designated release role can promote a reviewed version.

Create monitored business slices and evaluate approved per-segment metrics and bias indicators using retained ground-truth labels. It does not directly address the Riverton Utilities case: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The relevant acceptance criterion for this case is: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.

Correlate payload sizes, invocation mix, ModelLatency and resource metrics to identify the actual throughput constraint. It does not directly address the Riverton Utilities case: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The relevant acceptance criterion for this case is: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.

Apply reviewed S3 lifecycle transition and expiration policies aligned to audit retention and replay requirements. It does not directly address the Riverton Utilities case: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The relevant acceptance criterion for this case is: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.

Objects past the retention window transition or expire as intended while protected evidence remains retrievable. This would verify a different operation: Apply reviewed S3 lifecycle transition and expiration policies aligned to audit retention and replay requirements. That separate action addresses: S3 inference request captures accumulate indefinitely in a costly storage class even after their approved monitoring retention period expires. It cannot establish the required Riverton Utilities correction for: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The decisive acceptance check is instead: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.

A representative slow request shows the delay attributed to one documented processing stage rather than undifferentiated total time. This would verify a different operation: Instrument authorized distributed traces or structured per-stage timings, using AWS X-Ray where supported, to isolate bottlenecks. That separate action addresses: An ML API has intermittent latency spikes but CloudWatch cannot reveal whether the delay occurs in preprocessing or downstream inference. It cannot establish the required Riverton Utilities correction for: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The decisive acceptance check is instead: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.

A cost model using observed utilization demonstrates the break-even point and documents the selected financial tradeoff. This would verify a different operation: Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. That separate action addresses: A team purchases reserved inference capacity without measuring whether its utilization is predictable enough to offset commitment cost. It cannot establish the required Riverton Utilities correction for: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. The decisive acceptance check is instead: A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination.