Exam Bundle

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 production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The decisive acceptance check is instead: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

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 Riverton Utilities correction for: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The decisive acceptance check is instead: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

A production task retrieves its secret with the authorized role while build logs reveal no plaintext credential. This would verify a different operation: Use AWS Secrets Manager or an approved secret provider with a scoped runtime role and suppress secret values from pipeline logs. That separate action addresses: An automated deployment retrieves a production database password from a plaintext environment variable stored in a shared build log. It cannot establish the required Riverton Utilities correction for: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The decisive acceptance check is instead: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. It does not directly address the Juniper Media case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Correlate payload sizes, invocation mix, ModelLatency and resource metrics to identify the actual throughput constraint. It does not directly address the Juniper Media case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Apply identity-based domain and resource permission boundaries with segregated workspace roles and least privilege. It does not directly address the Juniper Media case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

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 Juniper Media correction for: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

An anonymous request is denied while a permitted training role retrieves its intended objects successfully. This would verify a different operation: Enable the appropriate S3 Block Public Access configuration and scope bucket access to authorized ML roles. That separate action addresses: An S3 bucket holding labeled training images allows anonymous object reads because a legacy public-read policy was copied into production. It cannot establish the required Juniper Media correction for: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

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 Juniper Media correction for: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Apply dataset-specific KMS grants or key policies and distinct IAM roles aligned with tenant segregation requirements. It does not directly address the Alpine Healthcare case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Evaluate supported alternate instance families or regional capacity and introduce a tested provisioning fallback compatible with residency rules. It does not directly address the Alpine Healthcare case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. It does not directly address the Alpine Healthcare case: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The relevant acceptance criterion for this case is: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

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: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

A controlled endpoint configuration change yields an attributable CloudTrail event retained at the authorized destination. This would verify a different operation: Enable appropriate organization or account CloudTrail trails with secure retention and access controls for relevant management events. That separate action addresses: A security auditor cannot trace who modified a SageMaker endpoint because AWS CloudTrail event retention and organization trails were never configured. It cannot establish the required Alpine Healthcare correction for: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

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 Alpine Healthcare correction for: A model owner uses one unversioned monitoring baseline for every retraining run, so legitimate model improvements trigger constant false alarms. The decisive acceptance check is instead: The monitoring metadata links the live model package to its correct reviewed baseline and tests produce expected alerts.

Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. It does not directly address the Keystone BioLabs case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

Apply reviewed S3 lifecycle transition and expiration policies aligned to audit retention and replay requirements. It does not directly address the Keystone BioLabs case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

Limit the SageMaker execution role and bucket policy to the approved data prefix and required object operations. It does not directly address the Keystone BioLabs case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

The revised sweep consumes fewer training hours and still identifies a candidate meeting the accepted validation target. This would verify a different operation: Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. That separate action addresses: An expensive SageMaker hyperparameter search continues after clearly underperforming trials without any early stopping or experiment budget. It cannot establish the required Keystone BioLabs correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Keystone BioLabs correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Keystone BioLabs correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

Apply reviewed S3 lifecycle transition and expiration policies aligned to audit retention and replay requirements. It does not directly address the Timberline Foods case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Timberline Foods case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

Instrument authorized distributed traces or structured per-stage timings, using AWS X-Ray where supported, to isolate bottlenecks. It does not directly address the Timberline Foods case: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The relevant acceptance criterion for this case is: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Timberline Foods correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Timberline Foods correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

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 Timberline Foods correction for: A batch prediction system drops malformed records but the monitoring report tracks only successfully scored inputs and understates total error rate. The decisive acceptance check is instead: A controlled malformed-input batch is counted in the rejection metric and overall error reporting includes all attempted records.

Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. It does not directly address the Westhaven Retail case: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The relevant acceptance criterion for this case is: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.

Correlate payload sizes, invocation mix, ModelLatency and resource metrics to identify the actual throughput constraint. It does not directly address the Westhaven Retail case: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The relevant acceptance criterion for this case is: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.

Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. It does not directly address the Westhaven Retail case: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The relevant acceptance criterion for this case is: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.

A training role cannot approve its own model package and a designated release role can promote a reviewed version. This would verify a different operation: Separate training, model approval and production deployment identities with explicit role and approval boundaries. That separate action addresses: A machine learning pipeline uses a single IAM role to train models, approve registry packages and update production endpoints. It cannot establish the required Westhaven Retail correction for: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The decisive acceptance check is instead: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.

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 Westhaven Retail correction for: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The decisive acceptance check is instead: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.

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 Westhaven Retail correction for: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. The decisive acceptance check is instead: A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available.