Exam Bundle

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 Northgate Telecom correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

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 Northgate Telecom correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

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 Northgate Telecom correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

Distinguish covariate drift from verified performance degradation and evaluate outcome labels and model-quality metrics separately. It does not directly address the Harborline Logistics case: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The relevant acceptance criterion for this case is: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

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 Harborline Logistics case: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The relevant acceptance criterion for this case is: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

Version monitoring baselines with each released model and capture a reviewed transition policy between old and new expectations. It does not directly address the Harborline Logistics case: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The relevant acceptance criterion for this case is: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

A representative request cohort produces traceable per-model score differences and unacceptable changes block promotion. This would verify a different operation: Run shadow or controlled A/B inference comparisons with logged model version and matched request IDs before full rollout. That separate action addresses: A retrained model is deployed without comparing its output distributions with the approved production model, causing unexplained score shifts. It cannot establish the required Harborline Logistics correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

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 Harborline Logistics correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

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 Harborline Logistics correction for: A model training job writes regulated outputs to an unencrypted S3 location despite a documented data-at-rest encryption standard. The decisive acceptance check is instead: New output artifacts have the documented KMS key metadata and an attempted unencrypted write is rejected by bucket policy.

Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. It does not directly address the Silvercrest University case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Use consistent random traffic allocation and analyze outcomes per experimental assignment and predefined business slices. It does not directly address the Silvercrest University case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Apply reviewed S3 lifecycle transition and expiration policies aligned to audit retention and replay requirements. It does not directly address the Silvercrest University case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

A representative request cohort produces traceable per-model score differences and unacceptable changes block promotion. This would verify a different operation: Run shadow or controlled A/B inference comparisons with logged model version and matched request IDs before full rollout. That separate action addresses: A retrained model is deployed without comparing its output distributions with the approved production model, causing unexplained score shifts. It cannot establish the required Silvercrest University correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

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 Silvercrest University correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

A reference set with known labels produces a measurable recall trend and an agreed quality alert fires when the threshold is breached. This would verify a different operation: Create a governed delayed-label collection path and compare production predictions with matched observed labels for model quality monitoring. That separate action addresses: A production classifier's false-negative rate rises over several months, but predictions are logged without collecting any eventual ground-truth outcomes. It cannot establish the required Silvercrest University correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Inspect SageMaker service quotas and scaling target limits and request justified quota changes before increasing traffic. It does not directly address the Pinecrest Hotels case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Create a SageMaker Model Monitor data-quality baseline and schedule inference feature-distribution checks against it. It does not directly address the Pinecrest Hotels case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Correlate payload sizes, invocation mix, ModelLatency and resource metrics to identify the actual throughput constraint. It does not directly address the Pinecrest Hotels case: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The relevant acceptance criterion for this case is: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

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 Pinecrest Hotels correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

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 Pinecrest Hotels correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

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 Pinecrest Hotels correction for: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. The decisive acceptance check is instead: A test model role reads its permitted subset and is denied access to unrelated original customer attributes.

Use AWS Cost Explorer and properly applied resource tags to compare endpoint, training and storage cost changes over time. It does not directly address the Oakridge Public Services case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

Use comparable inference benchmarks across supported instance families and evaluate total cost per thousand successful requests. It does not directly address the Oakridge Public Services case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

Configure bounded and redacted inference data capture with access controls, sampling and retention matched to monitoring requirements. It does not directly address the Oakridge Public Services case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Oakridge Public Services correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Oakridge Public Services correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Oakridge Public Services correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

Distinguish covariate drift from verified performance degradation and evaluate outcome labels and model-quality metrics separately. It does not directly address the Harborview Insurance case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

Monitor the appropriate GPU utilization, memory and throughput metrics for the selected hosting architecture. It does not directly address the Harborview Insurance case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

Run shadow or controlled A/B inference comparisons with logged model version and matched request IDs before full rollout. It does not directly address the Harborview Insurance case: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The relevant acceptance criterion for this case is: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Harborview Insurance correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Harborview Insurance correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.

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 Harborview Insurance correction for: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. The decisive acceptance check is instead: A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully.