Exam Bundle

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 Cedarfield Hospitality correction for: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The decisive acceptance check is instead: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

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 Cedarfield Hospitality correction for: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The decisive acceptance check is instead: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

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

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 Riverton Utilities case: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The relevant acceptance criterion for this case is: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

Provision test environments from IaC and implement a reviewed cleanup action with protective rules for shared resources. It does not directly address the Riverton Utilities case: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The relevant acceptance criterion for this case is: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Riverton Utilities case: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The relevant acceptance criterion for this case is: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

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

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 Riverton Utilities correction for: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The decisive acceptance check is instead: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

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 Riverton Utilities correction for: A model's automatic deployment increases error rates, but the pipeline has no health-driven rollback condition or retained previous version. The decisive acceptance check is instead: A simulated bad candidate triggers the rollback and the restored endpoint returns the documented prior model responses.

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 Juniper Media case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

Use a governed endpoint-variant routing or other supported traffic allocation design with versioned model identifiers. It does not directly address the Juniper Media case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

Benchmark CPU or suitable serverless hosting and select the deployment offering that meets utilization and latency requirements. It does not directly address the Juniper Media case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Juniper Media correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Juniper Media correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Juniper Media correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

Separate infrastructure deployment roles from runtime execution roles with narrowly scoped resource access policies. It does not directly address the Alpine Healthcare case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Alpine Healthcare case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

Express the approved endpoint, model and networking settings in CloudFormation or AWS CDK infrastructure definitions with reviewed parameters. It does not directly address the Alpine Healthcare case: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The relevant acceptance criterion for this case is: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Alpine Healthcare correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Alpine Healthcare correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Alpine Healthcare correction for: A pipeline combines data transformation, training and evaluation in one opaque shell command, obscuring which stage failed. The decisive acceptance check is instead: A deliberately failed transform reports its stage and blocks downstream deployment without losing prior successful artifacts.

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 Keystone BioLabs case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. It does not directly address the Keystone BioLabs case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

Compare Lambda, SageMaker asynchronous inference or container hosting based on payload size, memory and duration constraints. It does not directly address the Keystone BioLabs case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

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 Keystone BioLabs correction for: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The decisive acceptance check is instead: An auditor resolves a production model to the exact source commit that passed the original automated tests.

The runtime can read its designated artifacts and log streams but cannot modify unrelated CloudFormation stacks. This would verify a different operation: Separate infrastructure deployment roles from runtime execution roles with narrowly scoped resource access policies. That separate action addresses: A deployment template grants one IAM role both model-serving permissions and broad stack-administration privileges unrelated to inference. It cannot establish the required Keystone BioLabs correction for: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The decisive acceptance check is instead: An auditor resolves a production model to the exact source commit that passed the original automated tests.

The selected instance family meets throughput and latency targets with a documented cost-per-inference measurement. This would verify a different operation: Compare supported CPU, GPU or inference-optimized instances using matched representative throughput and latency tests. That separate action addresses: A high-volume endpoint runs on small CPUs despite a documented model benchmark showing matrix inference benefits from accelerator hardware. It cannot establish the required Keystone BioLabs correction for: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The decisive acceptance check is instead: An auditor resolves a production model to the exact source commit that passed the original automated tests.

Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. It does not directly address the Timberline Foods case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. It does not directly address the Timberline Foods case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

Separate infrastructure deployment roles from runtime execution roles with narrowly scoped resource access policies. It does not directly address the Timberline Foods case: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The relevant acceptance criterion for this case is: An auditor resolves a production model to the exact source commit that passed the original automated tests.

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 Timberline Foods correction for: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The decisive acceptance check is instead: An auditor resolves a production model to the exact source commit that passed the original automated tests.

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

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 Timberline Foods correction for: A model endpoint is redeployed from a branch after its source is rebased, making the exact source revision impossible to reconstruct. The decisive acceptance check is instead: An auditor resolves a production model to the exact source commit that passed the original automated tests.