Exam Bundle

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.

Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. It does not directly address the Cedarfield Hospitality case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

Choose SageMaker asynchronous inference or a supported job-based flow with input-output object locations and completion handling. It does not directly address the Cedarfield Hospitality case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

Compare Lambda, SageMaker asynchronous inference or container hosting based on payload size, memory and duration constraints. It does not directly address the Cedarfield Hospitality case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the 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 Cedarfield Hospitality correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

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 Cedarfield Hospitality correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

A deliberately failing test stops the pipeline and no new production model version is published from that commit. This would verify a different operation: Insert automated tests and a quality-gate approval stage before promoting an approved model package to production. That separate action addresses: A model deployment pipeline deploys directly from each developer commit without checking preprocessing unit tests or model evaluation thresholds. It cannot establish the required Cedarfield Hospitality correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. It does not directly address the Riverton Utilities case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

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 Riverton Utilities case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

Add evaluation and conditional model-quality steps linked to the model registry approval process. It does not directly address the Riverton Utilities case: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The relevant acceptance criterion for this case is: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls. This would verify a different operation: Measure cache behavior and choose suitable memory capacity or a dedicated deployment for the critical high-frequency model. That separate action addresses: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. It cannot establish the required Riverton Utilities correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

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 Riverton Utilities correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

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 Riverton Utilities correction for: A SageMaker endpoint runs inside private subnets but the security groups omit the intended dependency paths and container startup fails. The decisive acceptance check is instead: The model container loads from authorized private resources and an unapproved subnet remains unable to reach the endpoint.

Choose a private supported endpoint and VPC integration design with restricted consumers and approved ingress controls. It does not directly address the Juniper Media case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Optimize and package an appropriate model for supported edge execution with a tested offline runtime and update mechanism. It does not directly address the Juniper Media case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Split the workflow into traceable SageMaker Pipelines or Step Functions stages with typed inputs, outputs and failure handling. It does not directly address the Juniper Media case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration. This would verify a different operation: Use unique version identifiers, idempotent promotion operations and recoverable state tracking around the deployment stage. That separate action addresses: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. It cannot establish the required Juniper Media correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

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 Juniper Media correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

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 Juniper Media correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Pin reviewed source commits or release tags and record their identities with immutable model and image artifacts. It does not directly address the Alpine Healthcare case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Measure cache behavior and choose suitable memory capacity or a dedicated deployment for the critical high-frequency model. It does not directly address the Alpine Healthcare case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Adapt the container entrypoint, model artifact retrieval and health interface to the actual selected ECS deployment environment. It does not directly address the Alpine Healthcare case: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The relevant acceptance criterion for this case is: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

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 Alpine Healthcare correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

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 Alpine Healthcare correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

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 Alpine Healthcare correction for: A scalable inference endpoint uses CPU utilization as its only target metric despite requests waiting in invocation queues and little CPU usage. The decisive acceptance check is instead: An increasing request rate triggers timely scaling and p95 inference latency remains within the approved limit.

Measure cache behavior and choose suitable memory capacity or a dedicated deployment for the critical high-frequency model. It does not directly address the Keystone BioLabs case: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The relevant acceptance criterion for this case is: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.

Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. It does not directly address the Keystone BioLabs case: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The relevant acceptance criterion for this case is: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.

Deploy an appropriately scaled low-latency real-time inference endpoint and route transaction requests through the authorized path. It does not directly address the Keystone BioLabs case: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The relevant acceptance criterion for this case is: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.

A peak traffic replay meets p95 latency and shows the critical model remains available without repeated cold-load stalls. This would verify a different operation: Measure cache behavior and choose suitable memory capacity or a dedicated deployment for the critical high-frequency model. That separate action addresses: A multi-model server has frequent model cold loads that exceed the acceptance latency target for its highest-traffic model. It cannot establish the required Keystone BioLabs correction for: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The decisive acceptance check is instead: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.

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 Keystone BioLabs correction for: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The decisive acceptance check is instead: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.

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 Keystone BioLabs correction for: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. The decisive acceptance check is instead: Both environments deploy without name collisions and their resource tags and model endpoints remain separate.