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 Lakeside Research correction for: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

A test model role reads its permitted subset and is denied access to unrelated original customer attributes. This would verify a different operation: Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. That separate action addresses: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. It cannot establish the required Lakeside Research correction for: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

The production role loads the shared artifact and a separate untrusted account still receives an access denial. This would verify a different operation: Configure precise cross-account package, S3 and KMS key permissions for the trusted production consumer role. That separate action addresses: A cross-account model registry package is shared with a production account but the referenced encrypted S3 model artifact cannot be decrypted there. It cannot establish the required Lakeside Research correction for: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

Monitor the appropriate GPU utilization, memory and throughput metrics for the selected hosting architecture. It does not directly address the Eastshore Energy case: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The relevant acceptance criterion for this case is: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

Apply identity-based domain and resource permission boundaries with segregated workspace roles and least privilege. It does not directly address the Eastshore Energy case: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The relevant acceptance criterion for this case is: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

Use comparable inference benchmarks across supported instance families and evaluate total cost per thousand successful requests. It does not directly address the Eastshore Energy case: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The relevant acceptance criterion for this case is: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

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 Eastshore Energy correction for: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

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 production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

A tampered artifact is rejected before the endpoint loads it and an approved version passes integrity verification. This would verify a different operation: Pin a governed immutable model artifact version and validate checksums or signatures through the approved release process. That separate action addresses: A production model file is overwritten with a maliciously altered artifact because deployment does not verify integrity or origin. It cannot establish the required Eastshore Energy correction for: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. The decisive acceptance check is instead: A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached.

Scope CloudWatch log actions to required resource ARNs and separate log configuration permissions from ordinary invocation needs. It does not directly address the Riverton Utilities case: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

Evaluate supported alternate instance families or regional capacity and introduce a tested provisioning fallback compatible with residency rules. It does not directly address the Riverton Utilities case: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

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 deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

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 Riverton Utilities correction for: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy. This would verify a different operation: Require appropriate SSE-KMS settings on the output bucket and ensure the training role is authorized to use the chosen key. That separate action addresses: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. It cannot establish the required Riverton Utilities correction for: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

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 deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. It does not directly address the Cedarfield Hospitality case: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

Use pipeline-dependent training resource lifecycle controls with completion-triggered teardown and failure handling. It does not directly address the Cedarfield Hospitality case: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

Apply consistent project, environment and model cost-allocation tags and activate the corresponding billing reports. It does not directly address the Cedarfield Hospitality case: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The relevant acceptance criterion for this case is: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

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 Cedarfield Hospitality correction for: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

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 Cedarfield Hospitality correction for: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

A capacity-failure drill scales inference on an approved alternate target while meeting availability and data-residency constraints. This would verify a different operation: Evaluate supported alternate instance families or regional capacity and introduce a tested provisioning fallback compatible with residency rules. That separate action addresses: An ML platform switches all traffic to an accelerated instance type even though the chosen AWS Region has insufficient capacity for peak scaling. It cannot establish the required Cedarfield Hospitality correction for: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. The decisive acceptance check is instead: A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output.

Measure invocation patterns and replace unnecessary continuous capacity with supported scheduled batch or appropriately scaled alternatives. It does not directly address the Alpine Healthcare case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

Create AWS Budgets alerts with defined cost thresholds and route notifications to the accountable ML operations owner. It does not directly address the Alpine Healthcare case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. It does not directly address the Alpine Healthcare case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

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 Alpine Healthcare correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

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 Alpine Healthcare correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

A test model role reads its permitted subset and is denied access to unrelated original customer attributes. This would verify a different operation: Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. That separate action addresses: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. It cannot establish the required Alpine Healthcare correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

Limit the SageMaker execution role and bucket policy to the approved data prefix and required object operations. It does not directly address the Juniper Media case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

Track high-percentile ModelLatency and relevant invocation or backlog metrics with thresholds based on the service-level objective. It does not directly address the Juniper Media case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

Choose a suitable minimum serving capacity or compatible hosting method and validate the idle-cost versus cold-start tradeoff. It does not directly address the Juniper Media case: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The relevant acceptance criterion for this case is: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

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 Juniper Media correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

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 Juniper Media correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.

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 Juniper Media correction for: An operations dashboard treats a rising model input drift score as proof that prediction correctness already decreased without label evidence. The decisive acceptance check is instead: The monitoring report labels distribution shift and actual error metrics distinctly and does not infer accuracy loss from drift alone.