Exam Bundle

A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage. This would verify a different operation: Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. That separate action addresses: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. It cannot establish the required Highland Education correction for: An inference architecture replicates model artifacts to every deployment even though regional copies already exist and frequent downloads dominate startup time. The decisive acceptance check is instead: Endpoint startup time decreases while the loaded model checksum still matches the approved release artifact.

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 Highland Education correction for: An inference architecture replicates model artifacts to every deployment even though regional copies already exist and frequent downloads dominate startup time. The decisive acceptance check is instead: Endpoint startup time decreases while the loaded model checksum still matches the approved release artifact.

A code scan finds no static secret and the notebook's execution role can use only its intended dataset resources. This would verify a different operation: Replace embedded access keys with authorized IAM roles and secure short-lived credential delivery for the notebook environment. That separate action addresses: A SageMaker notebook user stores long-lived AWS credentials in the notebook source so other project members can inspect them. It cannot establish the required Highland Education correction for: An inference architecture replicates model artifacts to every deployment even though regional copies already exist and frequent downloads dominate startup time. The decisive acceptance check is instead: Endpoint startup time decreases while the loaded model checksum still matches the approved release artifact.

Version monitoring baselines with each released model and capture a reviewed transition policy between old and new expectations. It does not directly address the Eastshore Energy case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. It does not directly address the Eastshore Energy case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Enable the appropriate S3 Block Public Access configuration and scope bucket access to authorized ML roles. It does not directly address the Eastshore Energy case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

The development user can create approved experiments in the correct domain but receives AccessDenied for protected production operations. This would verify a different operation: Apply identity-based domain and resource permission boundaries with segregated workspace roles and least privilege. That separate action addresses: A SageMaker Studio user can create experiments in a production domain even though their intended access is restricted to development. It cannot establish the required Eastshore Energy correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction. This would verify a different operation: Add model-specific output-validity checks and application error metrics alongside endpoint health measurements. That separate action addresses: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. It cannot establish the required Eastshore Energy correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

The runtime writes to the intended log stream but cannot modify an unrelated service's logging resources. This would verify a different operation: Scope CloudWatch log actions to required resource ARNs and separate log configuration permissions from ordinary invocation needs. That separate action addresses: A model deployment can write arbitrary CloudWatch Logs groups because its inference IAM role includes broad administrative logging permissions. It cannot establish the required Eastshore Energy correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Use appropriate SageMaker Clarify post-training bias measures and valid governed outcome data with documented fairness interpretation. It does not directly address the Lakeside Research case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Scope CloudWatch log actions to required resource ARNs and separate log configuration permissions from ordinary invocation needs. It does not directly address the Lakeside Research case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Limit the SageMaker execution role and bucket policy to the approved data prefix and required object operations. It does not directly address the Lakeside Research case: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The relevant acceptance criterion for this case is: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

An authorized tenant role decrypts only its dataset and a cross-tenant key operation is denied. This would verify a different operation: Apply dataset-specific KMS grants or key policies and distinct IAM roles aligned with tenant segregation requirements. That separate action addresses: An ML feature store contains regulated fields encrypted with an AWS KMS key, but a shared role can decrypt every organization's dataset. It cannot establish the required Lakeside Research correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

A test labeling worker can view only approved anonymized images and cannot retrieve the original patient metadata. This would verify a different operation: Use governed de-identification and scoped labeling-access controls before creating the labeling workforce task. That separate action addresses: An ML data labeling job grants external workers access to original unmasked patient records even though only de-identified images are required. It cannot establish the required Lakeside Research correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

A controlled personal-data request produces timing and error records without the prohibited raw identifiers. This would verify a different operation: Redact or omit sensitive input fields from logs and emit privacy-safe structured metadata with governed retention. That separate action addresses: An inference endpoint logs complete customer request bodies including personal information even though troubleshooting needs only aggregate timings. It cannot establish the required Lakeside Research correction for: An operations team tracks aggregate monthly AWS charges but cannot isolate a sudden cost increase to new model endpoints. The decisive acceptance check is instead: A tagged cost breakdown identifies the new resource responsible for the measured increase and supports an accountable remediation.

Configure precise cross-account package, S3 and KMS key permissions for the trusted production consumer role. It does not directly address the Cedarfield Hospitality case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

Use appropriate SageMaker Clarify post-training bias measures and valid governed outcome data with documented fairness interpretation. It does not directly address the Cedarfield Hospitality case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

Require appropriate SSE-KMS settings on the output bucket and ensure the training role is authorized to use the chosen key. It does not directly address the Cedarfield Hospitality case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert. This would verify a different operation: Define seasonal reference windows and calibrated drift thresholds rather than using an inappropriate static training baseline for all periods. That separate action addresses: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. It cannot establish the required Cedarfield Hospitality correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

The training role reads its authorized feature objects but a test access to an unrelated bucket is denied. This would verify a different operation: Limit the SageMaker execution role and bucket policy to the approved data prefix and required object operations. That separate action addresses: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. It cannot establish the required Cedarfield Hospitality correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads. This would verify a different operation: Configure bounded and redacted inference data capture with access controls, sampling and retention matched to monitoring requirements. That separate action addresses: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. It cannot establish the required Cedarfield Hospitality correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

Distinguish covariate drift from verified performance degradation and evaluate outcome labels and model-quality metrics separately. It does not directly address the Riverton Utilities case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

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 Riverton Utilities case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

Pin a governed immutable model artifact version and validate checksums or signatures through the approved release process. It does not directly address the Riverton Utilities case: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The relevant acceptance criterion for this case is: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction. This would verify a different operation: Add model-specific output-validity checks and application error metrics alongside endpoint health measurements. That separate action addresses: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. It cannot establish the required Riverton Utilities correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

An injected malformed feature vector is handled according to policy and creates an attributable monitoring event. This would verify a different operation: Apply input validation with monitored missingness and a documented safe fallback or rejection policy for out-of-contract requests. That separate action addresses: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. It cannot establish the required Riverton Utilities correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads. This would verify a different operation: Configure bounded and redacted inference data capture with access controls, sampling and retention matched to monitoring requirements. That separate action addresses: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. It cannot establish the required Riverton Utilities correction for: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. The decisive acceptance check is instead: A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints.

Update monitored endpoint or variant configuration and baseline references as part of the versioned deployment process. It does not directly address the Juniper Media case: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The relevant acceptance criterion for this case is: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.

Measure invocation patterns and replace unnecessary continuous capacity with supported scheduled batch or appropriately scaled alternatives. It does not directly address the Juniper Media case: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The relevant acceptance criterion for this case is: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.

Track total received records, rejected records and successful predictions with clear denominators across batch processing. It does not directly address the Juniper Media case: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The relevant acceptance criterion for this case is: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.

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 Juniper Media correction for: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The decisive acceptance check is instead: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.

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 Juniper Media correction for: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The decisive acceptance check is instead: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.

The benchmark identifies the accelerator bottleneck and the selected corrective capacity change reduces inference failures. This would verify a different operation: Monitor the appropriate GPU utilization, memory and throughput metrics for the selected hosting architecture. That separate action addresses: A CloudWatch dashboard claims the inference host is idle because CPU is low, yet GPU memory saturation causes inference throttling. It cannot establish the required Juniper Media correction for: An ML training execution role has wildcard permission to read every company S3 bucket although it needs one versioned feature prefix. The decisive acceptance check is instead: The training role reads its authorized feature objects but a test access to an unrelated bucket is denied.