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 Westhaven Retail correction for: A stack update changes an inference endpoint's network settings without showing whether the change broadens inbound access. The decisive acceptance check is instead: A risky security-group expansion is blocked during review and a permitted private endpoint change deploys successfully.

An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout. This would verify a different operation: Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. That separate action addresses: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. It cannot establish the required Westhaven Retail correction for: A stack update changes an inference endpoint's network settings without showing whether the change broadens inbound access. The decisive acceptance check is instead: A risky security-group expansion is blocked during review and a permitted private endpoint change deploys successfully.

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 Westhaven Retail correction for: A stack update changes an inference endpoint's network settings without showing whether the change broadens inbound access. The decisive acceptance check is instead: A risky security-group expansion is blocked during review and a permitted private endpoint change deploys successfully.

Tune target tracking, cooldown and minimum capacity from observed workload periodicity rather than setting a zero-tolerance threshold. It does not directly address the Brookside Manufacturing case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. It does not directly address the Brookside Manufacturing case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Adapt the container entrypoint, model artifact retrieval and health interface to the actual selected ECS deployment environment. It does not directly address the Brookside Manufacturing case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

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 Brookside Manufacturing correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

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 Brookside Manufacturing correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

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 Brookside Manufacturing correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Maintain versioned model artifacts and use a controlled deployment strategy with retained previous endpoint configuration. It does not directly address the Bluehaven Transit case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Provision the approved VPC endpoint or controlled network route and its route table and access policies for model-artifact reads. It does not directly address the Bluehaven Transit case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Select an appropriate SageMaker endpoint scaling metric such as invocations per instance and tune thresholds from measured traffic. It does not directly address the Bluehaven Transit case: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The relevant acceptance criterion for this case is: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

A controlled burst increases the active endpoint instance count above one and scales down after cooldown. This would verify a different operation: Configure minimum and maximum capacity with the supported scalable target and test the scaling policy's CloudWatch metric. That separate action addresses: A SageMaker endpoint autoscaling policy has maximum capacity fixed at one instance and never adds capacity despite visible alarm breaches. It cannot establish the required Bluehaven Transit correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Health probes confirm readiness without increasing model invocation counts or delaying normal business predictions. This would verify a different operation: Define a lightweight readiness and liveness interface distinct from resource-intensive inference operations. That separate action addresses: A container inference service sends health checks to a path that triggers costly full model predictions and exhausts request capacity during rollouts. It cannot establish the required Bluehaven Transit correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

A fresh ECS task passes its health check and serves a controlled request without depending on SageMaker-only paths. This would verify a different operation: Adapt the container entrypoint, model artifact retrieval and health interface to the actual selected ECS deployment environment. That separate action addresses: A new model is deployed to ECS but its container expects SageMaker environment paths and does not satisfy the container orchestration service's HTTP health contract. It cannot establish the required Bluehaven Transit correction for: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. The decisive acceptance check is instead: A deliberately failing test stops the pipeline and no new production model version is published from that commit.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Northgate Telecom case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Use SageMaker Batch Transform or an appropriate scheduled batch inference workflow instead of an always-on real-time endpoint. It does not directly address the Northgate Telecom case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Express the approved endpoint, model and networking settings in CloudFormation or AWS CDK infrastructure definitions with reviewed parameters. It does not directly address the Northgate Telecom case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

A private model startup retrieves the authorized S3 artifact without an unintended public network route. This would verify a different operation: Provision the approved VPC endpoint or controlled network route and its route table and access policies for model-artifact reads. That separate action addresses: A private ML deployment needs an S3 model artifact but the VPC-only environment lacks a suitable S3 endpoint or authorized egress path. It cannot establish the required Northgate Telecom correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

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 Northgate Telecom correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

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 Northgate Telecom correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. It does not directly address the Harborline Logistics case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Version the task definition, container image and service deployment configuration as reviewed infrastructure changes. It does not directly address the Harborline Logistics case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Separate infrastructure deployment roles from runtime execution roles with narrowly scoped resource access policies. It does not directly address the Harborline Logistics case: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The relevant acceptance criterion for this case is: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

A replay of transient spikes avoids oscillation while sustained load still triggers the required scale-out action. This would verify a different operation: Tune target tracking, cooldown and minimum capacity from observed workload periodicity rather than setting a zero-tolerance threshold. That separate action addresses: An auto-scaled inference endpoint scales out during every brief request spike and incurs unnecessary instance churn and warm-up overhead. It cannot establish the required Harborline Logistics correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

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 Harborline Logistics correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

A private model startup retrieves the authorized S3 artifact without an unintended public network route. This would verify a different operation: Provision the approved VPC endpoint or controlled network route and its route table and access policies for model-artifact reads. That separate action addresses: A private ML deployment needs an S3 model artifact but the VPC-only environment lacks a suitable S3 endpoint or authorized egress path. It cannot establish the required Harborline Logistics correction for: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. The decisive acceptance check is instead: Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments.

Benchmark CPU or suitable serverless hosting and select the deployment offering that meets utilization and latency requirements. It does not directly address the Silvercrest University case: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The relevant acceptance criterion for this case is: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.

Provision the approved VPC endpoint or controlled network route and its route table and access policies for model-artifact reads. It does not directly address the Silvercrest University case: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The relevant acceptance criterion for this case is: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Silvercrest University case: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The relevant acceptance criterion for this case is: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.

The nightly batch finishes inside its approved window and idle endpoint costs are removed from the daily bill. This would verify a different operation: Use SageMaker Batch Transform or an appropriate scheduled batch inference workflow instead of an always-on real-time endpoint. That separate action addresses: A demand forecast model is invoked once overnight for millions of rows, but the team keeps a real-time SageMaker endpoint running all day. It cannot establish the required Silvercrest University correction for: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The decisive acceptance check is instead: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.

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 Silvercrest University correction for: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The decisive acceptance check is instead: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.

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 Silvercrest University correction for: A SageMaker Pipelines workflow trains and deploys without recording evaluation output, so every candidate is automatically approved. The decisive acceptance check is instead: A deliberately underperforming candidate remains unapproved and a passing candidate records its evaluation evidence.