Exam Bundle

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 Harborline Logistics correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

A synthetic peak test reaches the latency objective while instance count scales back after demand subsides. This would verify a different operation: Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. That separate action addresses: An inference workload receives highly variable request bursts and a fixed number of endpoint instances causes long queues at peak. It cannot establish the required Harborline Logistics correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

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 Harborline Logistics correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

Choose a private supported endpoint and VPC integration design with restricted consumers and approved ingress controls. It does not directly address the Northgate Telecom case: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The relevant acceptance criterion for this case is: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

Maintain versioned model artifacts and use a controlled deployment strategy with retained previous endpoint configuration. It does not directly address the Northgate Telecom case: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The relevant acceptance criterion for this case is: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. It does not directly address the Northgate Telecom case: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The relevant acceptance criterion for this case is: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

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 Northgate Telecom correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

A replacement task starts from the approved artifact version without needing an untracked disk originally attached to another node. This would verify a different operation: Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. That separate action addresses: A model deployment relies on one manually created EBS volume that a replacement task cannot attach after failure. It cannot establish the required Northgate Telecom correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

A synthetic peak test reaches the latency objective while instance count scales back after demand subsides. This would verify a different operation: Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. That separate action addresses: An inference workload receives highly variable request bursts and a fixed number of endpoint instances causes long queues at peak. It cannot establish the required Northgate Telecom correction for: A quality gate evaluates only global F1 score while a new candidate violates the acceptable error limit for a protected segment. The decisive acceptance check is instead: A test candidate with a critical slice regression is blocked despite acceptable aggregate F1 performance.

Reference a reviewed immutable ECR image digest alongside the exact model artifact version in the deployment configuration. It does not directly address the Pinecrest Hotels case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Compare Lambda, SageMaker asynchronous inference or container hosting based on payload size, memory and duration constraints. It does not directly address the Pinecrest Hotels case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Define a lightweight readiness and liveness interface distinct from resource-intensive inference operations. It does not directly address the Pinecrest Hotels case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

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 Pinecrest Hotels correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

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 Pinecrest Hotels correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

A synthetic peak test reaches the latency objective while instance count scales back after demand subsides. This would verify a different operation: Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. That separate action addresses: An inference workload receives highly variable request bursts and a fixed number of endpoint instances causes long queues at peak. It cannot establish the required Pinecrest Hotels correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Select an appropriate SageMaker endpoint scaling metric such as invocations per instance and tune thresholds from measured traffic. It does not directly address the Silvercrest University case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Use the intended durable artifact storage pattern and reproducible infrastructure definitions rather than node-local attachment assumptions. It does not directly address the Silvercrest University case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. It does not directly address the Silvercrest University case: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The relevant acceptance criterion for this case is: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

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 Silvercrest University correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

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 Silvercrest University correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

A synthetic peak test reaches the latency objective while instance count scales back after demand subsides. This would verify a different operation: Choose autoscaled real-time hosting with appropriate minimum capacity and measured scaling response to the traffic pattern. That separate action addresses: An inference workload receives highly variable request bursts and a fixed number of endpoint instances causes long queues at peak. It cannot establish the required Silvercrest University correction for: An ML orchestration service retries an endpoint update after a partial failure and attempts to register the same model package repeatedly. The decisive acceptance check is instead: A simulated retry completes without duplicate registry versions or an inconsistent endpoint configuration.

Build and publish a runtime image for the target supported architecture and pin matching instance and container metadata. It does not directly address the Harborview Insurance case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

Implement the required model loading, health and invocation handlers for the supported SageMaker custom container interface. It does not directly address the Harborview Insurance case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

Version the task definition, container image and service deployment configuration as reviewed infrastructure changes. It does not directly address the Harborview Insurance case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs. This would verify a different operation: Build and publish a runtime image for the target supported architecture and pin matching instance and container metadata. That separate action addresses: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. It cannot establish the required Harborview Insurance correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

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 Harborview Insurance correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

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 Harborview Insurance correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

Remove embedded credentials and use least-privilege runtime IAM roles or approved secret injection with image scanning. It does not directly address the Oakridge Public Services case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

Configure minimum and maximum capacity with the supported scalable target and test the scaling policy's CloudWatch metric. It does not directly address the Oakridge Public Services case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

Configure the supported SageMaker VPC subnet, security group and endpoint-access rules for required private dependencies. It does not directly address the Oakridge Public Services case: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The relevant acceptance criterion for this case is: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

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 Oakridge Public Services correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

A clean model endpoint starts on the intended instance and no executable-format error appears in the startup logs. This would verify a different operation: Build and publish a runtime image for the target supported architecture and pin matching instance and container metadata. That separate action addresses: An inference platform chooses an EC2 instance family without ensuring that the container architecture matches its CPU instruction set. It cannot establish the required Oakridge Public Services correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.

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 Oakridge Public Services correction for: A cross-account promotion pipeline copies model artifacts but loses the KMS permissions required for the destination account to load them. The decisive acceptance check is instead: A destination test role retrieves the artifact and decrypts it while an unrelated account remains denied.