Exam Bundle

Two identical trigger messages resolve to the expected single logical model update without competing untracked releases. This would verify a different operation: Include stable dataset IDs and idempotency controls in the orchestration design, preserving run lineage and concurrency policies. That separate action addresses: A retraining pipeline can be launched twice for the same input data, creating competing model versions with indistinguishable metadata. It cannot establish the required Bluehaven Transit correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

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 Bluehaven Transit correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments. This would verify a different operation: Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. That separate action addresses: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. It cannot establish the required Bluehaven Transit correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

Select an appropriate SageMaker endpoint scaling metric such as invocations per instance and tune thresholds from measured traffic. It does not directly address the Brookside Manufacturing case: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The relevant acceptance criterion for this case is: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

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 web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The relevant acceptance criterion for this case is: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

Reference a reviewed immutable ECR image digest alongside the exact model artifact version in the deployment configuration. It does not directly address the Brookside Manufacturing case: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The relevant acceptance criterion for this case is: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

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 Brookside Manufacturing correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

The updated resource inventory shows justified instance families and the service maintains required per-variant latency. This would verify a different operation: Right-size compute per compatible variant using an inference benchmark and represent each selection in the deployment stack. That separate action addresses: A data scientist provisions GPUs for all endpoint variants even though most deployed lightweight models support cost-effective CPU hosting. It cannot establish the required Brookside Manufacturing correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

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 Brookside Manufacturing correction for: A web fraud detector requires low-latency inference for each checkout, but the proposed architecture waits for the next hourly batch transformation. The decisive acceptance check is instead: A representative live test receives each decision within the checkout deadline without waiting for a batch schedule.

Separate infrastructure deployment roles from runtime execution roles with narrowly scoped resource access policies. It does not directly address the Harborline Logistics case: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. It does not directly address the Harborline Logistics case: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Express the approved endpoint, model and networking settings in CloudFormation or AWS CDK infrastructure definitions with reviewed parameters. It does not directly address the Harborline Logistics case: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

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 Harborline Logistics correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

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 Harborline Logistics correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Both environments deploy without name collisions and their resource tags and model endpoints remain separate. This would verify a different operation: Parameterize account, Region and environment-specific identifiers and maintain isolated deployment stacks and resource references. That separate action addresses: A team's AWS CDK stack uses the same fixed resource names across development and production and fails when a second environment is deployed. It cannot establish the required Harborline Logistics correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Right-size compute per compatible variant using an inference benchmark and represent each selection in the deployment stack. It does not directly address the Northgate Telecom case: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Pass an immutable ECR image digest as a build artifact to the deployment stage rather than reconstructing a tag. It does not directly address the Northgate Telecom case: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

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 image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The relevant acceptance criterion for this case is: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

A fresh staging stack reproduces the approved resource structure and a change set exposes differences before deployment. This would verify a different operation: Express the approved endpoint, model and networking settings in CloudFormation or AWS CDK infrastructure definitions with reviewed parameters. That separate action addresses: An ML application is provisioned by manually clicking SageMaker console settings, so production and staging use different instance types and security groups. It cannot establish the required Northgate Telecom correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

A controlled ECS rollout replaces tasks with the intended version and returns successful health checks throughout transition. This would verify a different operation: Version the task definition, container image and service deployment configuration as reviewed infrastructure changes. That separate action addresses: An Amazon ECS model-serving service cannot be updated safely because its task definition and container port are modified directly on running hosts. It cannot establish the required Northgate Telecom correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

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 Northgate Telecom correction for: An image analysis API accepts infrequent large payloads with long processing times but times out when called synchronously through a normal endpoint. The decisive acceptance check is instead: An oversized test input is queued, processed and retrieved asynchronously without the client's synchronous timeout.

Version the task definition, container image and service deployment configuration as reviewed infrastructure changes. It does not directly address the Pinecrest Hotels case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Make the retraining input a named immutable dataset manifest and persist it in the pipeline execution parameters. It does not directly address the Pinecrest Hotels case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Insert automated tests and a quality-gate approval stage before promoting an approved model package to production. It does not directly address the Pinecrest Hotels case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

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: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

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 Pinecrest Hotels correction for: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

The pipeline detects an intentionally incompatible model artifact before endpoint deployment occurs. This would verify a different operation: Add an integration test that starts the intended runtime image with the frozen artifact and invokes a representative inference sample. That separate action addresses: A CI stage validates Python syntax but never tests whether the model container can actually load the published model artifact. It cannot establish the required Pinecrest Hotels correction for: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Design the artifact sharing, replication and KMS policies explicitly for each trusted cross-account stage. It does not directly address the Silvercrest University case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Parameterize account, Region and environment-specific identifiers and maintain isolated deployment stacks and resource references. It does not directly address the Silvercrest University case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Pass an immutable ECR image digest as a build artifact to the deployment stage rather than reconstructing a tag. It does not directly address the Silvercrest University case: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The relevant acceptance criterion for this case is: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

An unapproved model package is rejected and only a reviewed approved package reaches the endpoint update step. This would verify a different operation: Require the intended registered model package approval state and enforce a deployment role boundary at the promotion stage. That separate action addresses: A CodePipeline deployment stage accepts any model registry package regardless of its manual approval status. It cannot establish the required Silvercrest University correction for: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Only an approved data manifest triggers retraining and repeated notifications do not launch duplicate experiments. This would verify a different operation: Filter EventBridge or S3-trigger inputs to the intended versioned training dataset and apply an idempotent retraining key. That separate action addresses: An automated model retraining workflow starts every time any S3 object changes, including log and metadata files unrelated to training. It cannot establish the required Silvercrest University correction for: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.

Two identical trigger messages resolve to the expected single logical model update without competing untracked releases. This would verify a different operation: Include stable dataset IDs and idempotency controls in the orchestration design, preserving run lineage and concurrency policies. That separate action addresses: A retraining pipeline can be launched twice for the same input data, creating competing model versions with indistinguishable metadata. It cannot establish the required Silvercrest University correction for: A team serves a tiny low-traffic model on a provisioned GPU endpoint even though CPU inference meets the request latency target. The decisive acceptance check is instead: The representative load test meets latency targets and the chosen hosting cost falls below the idle GPU baseline.