Exam Bundle

A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node. This would verify a different operation: Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. That separate action addresses: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. It cannot establish the required Redstone Aviation correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

Two identical trigger messages resolve to the expected single logical model update without competing untracked releases. This would verify a different operation: Include stable dataset IDs and idempotency controls in the orchestration design, preserving run lineage and concurrency policies. That separate action addresses: A retraining pipeline can be launched twice for the same input data, creating competing model versions with indistinguishable metadata. It cannot establish the required Redstone Aviation correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint. This would verify a different operation: Configure the supported SageMaker VPC subnet, security group and endpoint-access rules for required private dependencies. That separate action addresses: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. It cannot establish the required Redstone Aviation correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. It does not directly address the Meadowbrook Finance case: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The relevant acceptance criterion for this case is: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. It does not directly address the Meadowbrook Finance case: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The relevant acceptance criterion for this case is: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

Insert automated tests and a quality-gate approval stage before promoting an approved model package to production. It does not directly address the Meadowbrook Finance case: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The relevant acceptance criterion for this case is: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

A pipeline test creates and removes only its temporary resources and no unused endpoint remains after the workflow completes. This would verify a different operation: Provision test environments from IaC and implement a reviewed cleanup action with protective rules for shared resources. That separate action addresses: A staging ML endpoint is left running after automated integration tests because infrastructure teardown is not tied to the testing lifecycle. It cannot establish the required Meadowbrook Finance correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

A replay of the execution reads identical object versions and generates a traceable, comparable training run. This would verify a different operation: Make the retraining input a named immutable dataset manifest and persist it in the pipeline execution parameters. That separate action addresses: A scheduled retraining pipeline uses the latest available dataset rather than the dataset cut recorded in its review ticket. It cannot establish the required Meadowbrook Finance correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

A risky security-group expansion is blocked during review and a permitted private endpoint change deploys successfully. This would verify a different operation: Require inspected infrastructure change sets and automated network-policy validation before applying the altered endpoint stack. That separate action addresses: A stack update changes an inference endpoint's network settings without showing whether the change broadens inbound access. It cannot establish the required Meadowbrook Finance correction for: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. The decisive acceptance check is instead: A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls.

Add an integration test that starts the intended runtime image with the frozen artifact and invokes a representative inference sample. It does not directly address the Maplewood Schools case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Split the workflow into traceable SageMaker Pipelines or Step Functions stages with typed inputs, outputs and failure handling. It does not directly address the Maplewood Schools case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. It does not directly address the Maplewood Schools case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

The pipeline detects an intentionally incompatible model artifact before endpoint deployment occurs. This would verify a different operation: Add an integration test that starts the intended runtime image with the frozen artifact and invokes a representative inference sample. That separate action addresses: A CI stage validates Python syntax but never tests whether the model container can actually load the published model artifact. It cannot establish the required Maplewood Schools correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

The endpoint becomes healthy and returns a valid prediction for a documented JSON request through the SageMaker invocation API. This would verify a different operation: Implement the required model loading, health and invocation handlers for the supported SageMaker custom container interface. That separate action addresses: A platform team deploys a custom PyTorch inference container without the correct SageMaker-compatible serving endpoint contract. It cannot establish the required Maplewood Schools correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

An authorized private caller reaches inference while an internet test caller cannot discover or invoke the protected endpoint. This would verify a different operation: Choose a private supported endpoint and VPC integration design with restricted consumers and approved ingress controls. That separate action addresses: An internal model deployment needs only private enterprise connectivity but is exposed through an unintended public API path. It cannot establish the required Maplewood Schools correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. It does not directly address the Highland Education case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Highland Education case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Benchmark end-to-end inference latency and select an approved Region or edge design aligned to residency and client location. It does not directly address the Highland Education case: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The relevant acceptance criterion for this case is: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Representative models load on demand and per-model latency and isolation checks meet the accepted limits at reduced aggregate cost. This would verify a different operation: Evaluate SageMaker multi-model endpoints where model memory and isolation requirements permit compatible shared hosting. That separate action addresses: A production endpoint hosts hundreds of small customer-specific models on separate instances, creating high fixed infrastructure cost. It cannot establish the required Highland Education correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

The test traffic follows the approved proportion and logs identify exactly which model variant served each request. This would verify a different operation: Use a governed endpoint-variant routing or other supported traffic allocation design with versioned model identifiers. That separate action addresses: A product runs several model variants but the frontend hard-codes one endpoint URL and cannot safely direct a controlled share of traffic to a candidate. It cannot establish the required Highland Education correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts. This would verify a different operation: Split the workflow into traceable SageMaker Pipelines or Step Functions stages with typed inputs, outputs and failure handling. That separate action addresses: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. It cannot establish the required Highland Education correction for: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. The decisive acceptance check is instead: A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment.

Benchmark CPU or suitable serverless hosting and select the deployment offering that meets utilization and latency requirements. It does not directly address the Eastshore Energy case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Eastshore Energy case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Use unique version identifiers, idempotent promotion operations and recoverable state tracking around the deployment stage. It does not directly address the Eastshore Energy case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

A representative maximum-size request completes under the chosen platform's supported limits without truncating the response. This would verify a different operation: Compare Lambda, SageMaker asynchronous inference or container hosting based on payload size, memory and duration constraints. That separate action addresses: An inference service needs quick per-document processing with substantial response payloads but a proposed Lambda implementation exceeds its documented resource or duration limits. It cannot establish the required Eastshore Energy correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

A synthetic peak test reaches the latency objective while instance count scales back after demand subsides. This would verify a different operation: Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. That separate action addresses: An inference workload receives highly variable request bursts and a fixed number of endpoint instances causes long queues at peak. It cannot establish the required Eastshore Energy correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses. This would verify a different operation: Implement a controlled canary or blue-green rollout with CloudWatch alarm gates and automatic rollback to the approved prior version. That separate action addresses: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. It cannot establish the required Eastshore Energy correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Insert automated tests and a quality-gate approval stage before promoting an approved model package to production. It does not directly address the Lakeside Research case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. It does not directly address the Lakeside Research case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Evaluate SageMaker multi-model endpoints where model memory and isolation requirements permit compatible shared hosting. It does not directly address the Lakeside Research case: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The relevant acceptance criterion for this case is: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

Requests from representative client Regions meet the permitted total latency without violating data-residency controls. This would verify a different operation: Benchmark end-to-end inference latency and select an approved Region or edge design aligned to residency and client location. That separate action addresses: A low-latency image model deployed to a generic instance experiences unnecessary network delay because request payloads transit a distant AWS Region. It cannot establish the required Lakeside Research correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline. This would verify a different operation: Benchmark CPU or suitable serverless hosting and select the deployment offering that meets utilization and latency requirements. That separate action addresses: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. It cannot establish the required Lakeside Research correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.

An auditor resolves a production model to the exact source commit that passed the original automated tests. This would verify a different operation: Pin reviewed source commits or release tags and record their identities with immutable model and image artifacts. That separate action addresses: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. It cannot establish the required Lakeside Research correction for: A deployment includes an inference image tagged latest in Amazon ECR, allowing a later push to silently change model runtime dependencies. The decisive acceptance check is instead: A repeated deployment selects the identical container digest and verified model artifact regardless of later tag updates.