Exam Bundle

A representative live test receives each decision within the checkout deadline without waiting for a batch schedule. This would verify a different operation: Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. That separate action addresses: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. It cannot establish the required Brookside Manufacturing correction for: A private ML deployment needs an S3 model artifact but the VPC-only environment lacks a suitable S3 endpoint or authorized egress path. The decisive acceptance check is instead: A private model startup retrieves the authorized S3 artifact without an unintended public network route.

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 Brookside Manufacturing correction for: A private ML deployment needs an S3 model artifact but the VPC-only environment lacks a suitable S3 endpoint or authorized egress path. The decisive acceptance check is instead: A private model startup retrieves the authorized S3 artifact without an unintended public network route.

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 Brookside Manufacturing correction for: A private ML deployment needs an S3 model artifact but the VPC-only environment lacks a suitable S3 endpoint or authorized egress path. The decisive acceptance check is instead: A private model startup retrieves the authorized S3 artifact without an unintended public network route.

Split the workflow into traceable SageMaker Pipelines or Step Functions stages with typed inputs, outputs and failure handling. It does not directly address the Harborline Logistics case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. It does not directly address the Harborline Logistics case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Use a governed endpoint-variant routing or other supported traffic allocation design with versioned model identifiers. It does not directly address the Harborline Logistics case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

The disconnected edge device completes an approved inference and later reports its model version when connectivity returns. This would verify a different operation: Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. That separate action addresses: An edge camera must infer while offline, but the model architecture depends on a continuously reachable cloud real-time endpoint. It cannot establish the required Harborline Logistics correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

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 Harborline Logistics correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

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 Harborline Logistics correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Include stable dataset IDs and idempotency controls in the orchestration design, preserving run lineage and concurrency policies. It does not directly address the Northgate Telecom case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. It does not directly address the Northgate Telecom case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Measure cache behavior and choose suitable memory capacity or a dedicated deployment for the critical high-frequency model. It does not directly address the Northgate Telecom case: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The relevant acceptance criterion for this case is: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

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 Northgate Telecom correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

A representative live test receives each decision within the checkout deadline without waiting for a batch schedule. This would verify a different operation: Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. That separate action addresses: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. It cannot establish the required Northgate Telecom correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

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 Northgate Telecom correction for: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. The decisive acceptance check is instead: A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime.

Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. It does not directly address the Pinecrest Hotels case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Implement a controlled canary or blue-green rollout with CloudWatch alarm gates and automatic rollback to the approved prior version. It does not directly address the Pinecrest Hotels case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Compare Lambda, SageMaker asynchronous inference or container hosting based on payload size, memory and duration constraints. It does not directly address the Pinecrest Hotels case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

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 Pinecrest Hotels correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

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 Pinecrest Hotels correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance. This would verify a different operation: Include explicitly approved per-segment acceptance checks and fairness review in the conditional deployment gates. That separate action addresses: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. It cannot establish the required Pinecrest Hotels correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Split the workflow into traceable SageMaker Pipelines or Step Functions stages with typed inputs, outputs and failure handling. It does not directly address the Silvercrest University case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. It does not directly address the Silvercrest University case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Make the retraining input a named immutable dataset manifest and persist it in the pipeline execution parameters. It does not directly address the Silvercrest University case: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The relevant acceptance criterion for this case is: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

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 Silvercrest University correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

The deployed task reports the exact image digest emitted by the reviewed build stage. This would verify a different operation: Pass an immutable ECR image digest as a build artifact to the deployment stage rather than reconstructing a tag. That separate action addresses: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. It cannot establish the required Silvercrest University correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

A known request traverses the versioned preprocessing and prediction stages and produces the expected output after deployment. This would verify a different operation: Use a supported SageMaker inference pipeline or reviewed multi-container design with compatible input and output contracts. That separate action addresses: An inference service chains preprocessing and prediction in application code that cannot be versioned with the SageMaker deployed model. It cannot establish the required Silvercrest University correction for: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. The decisive acceptance check is instead: A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs.

Evaluate SageMaker multi-model endpoints where model memory and isolation requirements permit compatible shared hosting. It does not directly address the Harborview Insurance case: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The relevant acceptance criterion for this case is: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.

Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. It does not directly address the Harborview Insurance case: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The relevant acceptance criterion for this case is: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.

Pin reviewed source commits or release tags and record their identities with immutable model and image artifacts. It does not directly address the Harborview Insurance case: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The relevant acceptance criterion for this case is: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.

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 Harborview Insurance correction for: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The decisive acceptance check is instead: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.

A staged rollback restores the approved prior model version and representative requests return to baseline behavior. This would verify a different operation: Maintain versioned model artifacts and use a controlled deployment strategy with retained previous endpoint configuration. That separate action addresses: A production team deploys an updated fraud model by replacing the only model artifact, leaving no usable rollback option. It cannot establish the required Harborview Insurance correction for: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The decisive acceptance check is instead: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.

A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence. This would verify a different operation: Add evaluation and conditional model-quality steps linked to the model registry approval process. That separate action addresses: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. It cannot establish the required Harborview Insurance correction for: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. The decisive acceptance check is instead: A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node.