Exam Bundle

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 Northgate Telecom correction for: An inference workload maintains two always-on high-memory SageMaker endpoints for models invoked only during a brief nightly window. The decisive acceptance check is instead: The nightly workload still meets its completion target while cost reports show reduced idle serving hours.

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 Northgate Telecom correction for: An inference workload maintains two always-on high-memory SageMaker endpoints for models invoked only during a brief nightly window. The decisive acceptance check is instead: The nightly workload still meets its completion target while cost reports show reduced idle serving hours.

A controlled prediction from the new variant appears in the correct monitoring dataset and the old variant is not mistaken for current. This would verify a different operation: Update monitored endpoint or variant configuration and baseline references as part of the versioned deployment process. That separate action addresses: A risk model is deployed with a new model version but its SageMaker Model Monitor schedule continues capturing only the old endpoint variant. It cannot establish the required Northgate Telecom correction for: An inference workload maintains two always-on high-memory SageMaker endpoints for models invoked only during a brief nightly window. The decisive acceptance check is instead: The nightly workload still meets its completion target while cost reports show reduced idle serving hours.

Enable the appropriate S3 Block Public Access configuration and scope bucket access to authorized ML roles. It does not directly address the Pinecrest Hotels case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. It does not directly address the Pinecrest Hotels case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

Monitor end-to-end feature freshness, dependency errors and successful business prediction rates in addition to endpoint health. It does not directly address the Pinecrest Hotels case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

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 Pinecrest Hotels correction for: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

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 Pinecrest Hotels correction for: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

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 Pinecrest Hotels correction for: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

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 Silvercrest University case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

Create a SageMaker Model Monitor data-quality baseline and schedule inference feature-distribution checks against it. It does not directly address the Silvercrest University case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

Version monitoring baselines with each released model and capture a reviewed transition policy between old and new expectations. It does not directly address the Silvercrest University case: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The relevant acceptance criterion for this case is: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

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 attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output. This would verify a different operation: Monitor inference request schema and null-value rates against a versioned accepted contract before treating the endpoint as healthy. That separate action addresses: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. It cannot establish the required Silvercrest University correction for: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

A synthetic slice regression is detected even though the overall average metric remains inside its broad threshold. This would verify a different operation: Create monitored business slices and evaluate approved per-segment metrics and bias indicators using retained ground-truth labels. That separate action addresses: A service tracks only average model prediction values while a narrow segment receives systematically poor results that aggregate statistics hide. It cannot establish the required Silvercrest University correction for: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. The decisive acceptance check is instead: Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team.

Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. It does not directly address the Harborview Insurance case: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

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: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

Monitor inference request schema and null-value rates against a versioned accepted contract before treating the endpoint as healthy. It does not directly address the Harborview Insurance case: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

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 Harborview Insurance correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

A controlled prediction from the new variant appears in the correct monitoring dataset and the old variant is not mistaken for current. This would verify a different operation: Update monitored endpoint or variant configuration and baseline references as part of the versioned deployment process. That separate action addresses: A risk model is deployed with a new model version but its SageMaker Model Monitor schedule continues capturing only the old endpoint variant. It cannot establish the required Harborview Insurance correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available. This would verify a different operation: Monitor end-to-end feature freshness, dependency errors and successful business prediction rates in addition to endpoint health. That separate action addresses: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. It cannot establish the required Harborview Insurance correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

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 Oakridge Public Services case: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

Use governed de-identification and scoped labeling-access controls before creating the labeling workforce task. It does not directly address the Oakridge Public Services case: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

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 Oakridge Public Services case: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The relevant acceptance criterion for this case is: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

A missing-feature test request raises the expected data-quality signal and compatible requests retain their normal score output. This would verify a different operation: Monitor inference request schema and null-value rates against a versioned accepted contract before treating the endpoint as healthy. That separate action addresses: A deployed model's training-serving schema changes silently when one upstream feature is renamed, leaving most online predictions based on missing values. It cannot establish the required Oakridge Public Services correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

A simulated stale feature feed triggers a dependency alarm even though the SageMaker endpoint remains available. This would verify a different operation: Monitor end-to-end feature freshness, dependency errors and successful business prediction rates in addition to endpoint health. That separate action addresses: Production predictions fail silently during a partial downstream feature outage while endpoint uptime remains normal. It cannot establish the required Oakridge Public Services correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

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 Oakridge Public Services correction for: A budget owner discovers large GPU training overspend only after the invoice arrives because no cost threshold notification exists. The decisive acceptance check is instead: A controlled budget threshold scenario generates the intended notice before a hard cost-cap assumption is made.

Monitor inference request schema and null-value rates against a versioned accepted contract before treating the endpoint as healthy. It does not directly address the Meadowbrook Finance case: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The relevant acceptance criterion for this case is: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.

Distinguish covariate drift from verified performance degradation and evaluate outcome labels and model-quality metrics separately. It does not directly address the Meadowbrook Finance case: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The relevant acceptance criterion for this case is: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.

Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. It does not directly address the Meadowbrook Finance case: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The relevant acceptance criterion for this case is: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.

A controlled disparity case is surfaced by the intended bias metric and the report records sample sizes and review limitations. This would verify a different operation: Use appropriate SageMaker Clarify post-training bias measures and valid governed outcome data with documented fairness interpretation. That separate action addresses: A post-deployment bias analysis aggregates only predictions while never comparing their distribution with relevant protected-group outcomes. It cannot establish the required Meadowbrook Finance correction for: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The decisive acceptance check is instead: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.

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 Meadowbrook Finance correction for: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The decisive acceptance check is instead: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.

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 Meadowbrook Finance correction for: A training fleet uses expensive On-Demand instances for fault-tolerant short experiments without considering managed Spot capacity. The decisive acceptance check is instead: A representative interruptible run resumes safely and its measured total cost is below the approved On-Demand baseline.