Exam Bundle

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.

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 Pinecrest Hotels 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.

Configure the supported SageMaker VPC subnet, security group and endpoint-access rules for required private dependencies. It does not directly address the Pinecrest Hotels 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.

Evaluate SageMaker multi-model endpoints where model memory and isolation requirements permit compatible shared hosting. It does not directly address the Pinecrest Hotels 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.

A rebuilt image contains no credential strings and a task retrieves only its authorized secret at runtime. This would verify a different operation: Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. That separate action addresses: An ML microservice container stores credentials in its Dockerfile and the image is uploaded to a shared ECR repository. It cannot establish the required Pinecrest Hotels 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 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 Pinecrest Hotels 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 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 Pinecrest Hotels 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.

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 Oakridge Public Services case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

Use a governed endpoint-variant routing or other supported traffic allocation design with versioned model identifiers. It does not directly address the Oakridge Public Services case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

Select an appropriate SageMaker endpoint scaling metric such as invocations per instance and tune thresholds from measured traffic. It does not directly address the Oakridge Public Services case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Oakridge Public Services correction for: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Oakridge Public Services correction for: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Oakridge Public Services correction for: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

Configure minimum and maximum capacity with the supported scalable target and test the scaling policy's CloudWatch metric. It does not directly address the Harborview Insurance case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

Provision test environments from IaC and implement a reviewed cleanup action with protective rules for shared resources. It does not directly address the Harborview Insurance case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Harborview Insurance case: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The relevant acceptance criterion for this case is: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Harborview Insurance correction for: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 Harborview Insurance correction for: A CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

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 CodeBuild job pushes an inference image to ECR but the subsequent deploy stage uses a different mutable image tag. The decisive acceptance check is instead: The deployed task reports the exact image digest emitted by the reviewed build stage.

Configure the supported SageMaker VPC subnet, security group and endpoint-access rules for required private dependencies. It does not directly address the Redstone Aviation case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. It does not directly address the Redstone Aviation case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. It does not directly address the Redstone Aviation case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Redstone Aviation correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Redstone Aviation correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Redstone Aviation correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

Provision test environments from IaC and implement a reviewed cleanup action with protective rules for shared resources. It does not directly address the Meadowbrook Finance case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

Use a supported SageMaker inference pipeline or reviewed multi-container design with compatible input and output contracts. It does not directly address the Meadowbrook Finance case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Meadowbrook Finance case: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The relevant acceptance criterion for this case is: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Meadowbrook Finance correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Meadowbrook Finance correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.

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 Meadowbrook Finance correction for: A model project uses one broad IAM role for CodePipeline, training and production inference, enabling build jobs to alter runtime resources. The decisive acceptance check is instead: A test build can publish only its approved artifact and is denied direct modification of the production endpoint.