Exam Bundle

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 Maplewood Schools correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 Maplewood Schools correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 Maplewood Schools correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The relevant acceptance criterion for this case is: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. It does not directly address the Highland Education case: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The relevant acceptance criterion for this case is: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. It does not directly address the Highland Education case: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The relevant acceptance criterion for this case is: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 Highland Education correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 Highland Education correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

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 Highland Education correction for: A model receives rare null-heavy inputs in production that were absent from training and a batch of such requests produces unstable predictions. The decisive acceptance check is instead: An injected malformed feature vector is handled according to policy and creates an attributable monitoring event.

Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. It does not directly address the Eastshore Energy case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Use pipeline-dependent training resource lifecycle controls with completion-triggered teardown and failure handling. It does not directly address the Eastshore Energy case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. It does not directly address the Eastshore Energy case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

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 quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

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 Eastshore Energy correction for: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

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 Eastshore Energy correction for: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Apply identity-based domain and resource permission boundaries with segregated workspace roles and least privilege. It does not directly address the Lakeside Research case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Redact or omit sensitive input fields from logs and emit privacy-safe structured metadata with governed retention. It does not directly address the Lakeside Research case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Replace embedded access keys with authorized IAM roles and secure short-lived credential delivery for the notebook environment. It does not directly address the Lakeside Research case: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The relevant acceptance criterion for this case is: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

The inference container accesses authorized model artifacts privately and an external egress test remains blocked. This would verify a different operation: Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. That separate action addresses: A production inference container is placed in subnets with internet egress although its required datasets and dependencies are private AWS services. It cannot establish the required Lakeside Research correction for: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

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: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

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 Lakeside Research correction for: A quality dashboard plots only the mean model score, hiding gradual calibration drift as actual event rates change over time. The decisive acceptance check is instead: A deliberately miscalibrated sample breaches the documented reliability threshold while a well-calibrated control remains acceptable.

Evaluate supported alternate instance families or regional capacity and introduce a tested provisioning fallback compatible with residency rules. It does not directly address the Cedarfield Hospitality case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

Inspect SageMaker service quotas and scaling target limits and request justified quota changes before increasing traffic. It does not directly address the Cedarfield Hospitality case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

Enable appropriate organization or account CloudTrail trails with secure retention and access controls for relevant management events. It does not directly address the Cedarfield Hospitality case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

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 Cedarfield Hospitality 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 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 Cedarfield Hospitality 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 simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully. This would verify a different operation: Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. That separate action addresses: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. It cannot establish the required Cedarfield Hospitality 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.

Enable the appropriate S3 Block Public Access configuration and scope bucket access to authorized ML roles. It does not directly address the Riverton Utilities case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. It does not directly address the Riverton Utilities case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

Configure precise cross-account package, S3 and KMS key permissions for the trusted production consumer role. It does not directly address the Riverton Utilities case: A production A/B test compares models on different customer cohorts without controlling allocation, making observed performance differences misleading. The relevant acceptance criterion for this case is: The assignment audit shows representative variant groups and the evaluation respects the intended statistical comparison design.

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.