Exam Bundle

A test model role reads its permitted subset and is denied access to unrelated original customer attributes. This would verify a different operation: Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. That separate action addresses: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. It cannot establish the required Brookside Manufacturing correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

The inference container accesses authorized model artifacts privately and an external egress test remains blocked. This would verify a different operation: Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. That separate action addresses: A production inference container is placed in subnets with internet egress although its required datasets and dependencies are private AWS services. It cannot establish the required Brookside Manufacturing correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

The production role loads the shared artifact and a separate untrusted account still receives an access denial. This would verify a different operation: Configure precise cross-account package, S3 and KMS key permissions for the trusted production consumer role. That separate action addresses: A cross-account model registry package is shared with a production account but the referenced encrypted S3 model artifact cannot be decrypted there. It cannot establish the required Brookside Manufacturing correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

Measure invocation patterns and replace unnecessary continuous capacity with supported scheduled batch or appropriately scaled alternatives. It does not directly address the Bluehaven Transit case: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The relevant acceptance criterion for this case is: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. It does not directly address the Bluehaven Transit case: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The relevant acceptance criterion for this case is: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

Apply consistent project, environment and model cost-allocation tags and activate the corresponding billing reports. It does not directly address the Bluehaven Transit case: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The relevant acceptance criterion for this case is: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

The revised sweep consumes fewer training hours and still identifies a candidate meeting the accepted validation target. This would verify a different operation: Enable appropriate tuning-job completion limits and early termination policies where supported for the selected metric. That separate action addresses: An expensive SageMaker hyperparameter search continues after clearly underperforming trials without any early stopping or experiment budget. It cannot establish the required Bluehaven Transit correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

A simulated untrusted pull request cannot assume the production release role and an approved release still deploys successfully. This would verify a different operation: Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. That separate action addresses: An automated ML CI/CD runner accepts source contributions from untrusted forks while holding direct privileges to production SageMaker resources. It cannot establish the required Bluehaven Transit correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

An anonymous request is denied while a permitted training role retrieves its intended objects successfully. This would verify a different operation: Enable the appropriate S3 Block Public Access configuration and scope bucket access to authorized ML roles. That separate action addresses: An S3 bucket holding labeled training images allows anonymous object reads because a legacy public-read policy was copied into production. It cannot establish the required Bluehaven Transit correction for: A SageMaker endpoint stores all prediction payloads in logs despite a governance rule prohibiting raw customer identifiers in captured inference data. The decisive acceptance check is instead: An authorized monitoring sample supports drift analysis and a security scan finds no forbidden raw identifiers in captured payloads.

Instrument authorized distributed traces or structured per-stage timings, using AWS X-Ray where supported, to isolate bottlenecks. It does not directly address the Northgate Telecom case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Separate training, model approval and production deployment identities with explicit role and approval boundaries. It does not directly address the Northgate Telecom case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. It does not directly address the Northgate Telecom case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

A test model role reads its permitted subset and is denied access to unrelated original customer attributes. This would verify a different operation: Publish an approved data subset or governed view and grant read access only to the required machine learning project roles. That separate action addresses: A team shares a full customer dataset across projects by broadening S3 bucket access instead of providing a minimally scoped training extract. It cannot establish the required Northgate Telecom correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

A cost model using observed utilization demonstrates the break-even point and documents the selected financial tradeoff. This would verify a different operation: Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. That separate action addresses: A team purchases reserved inference capacity without measuring whether its utilization is predictable enough to offset commitment cost. It cannot establish the required Northgate Telecom correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

The selected instance meets the latency requirement with measured lower normalized cost than the oversized GPU option. This would verify a different operation: Use comparable inference benchmarks across supported instance families and evaluate total cost per thousand successful requests. That separate action addresses: An enterprise ML team assumes a larger GPU instance always reduces cost although the model is small and memory bandwidth is not a bottleneck. It cannot establish the required Northgate Telecom correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Configure precise cross-account package, S3 and KMS key permissions for the trusted production consumer role. It does not directly address the Harborline Logistics case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Pin a governed immutable model artifact version and validate checksums or signatures through the approved release process. It does not directly address the Harborline Logistics case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Separate training, model approval and production deployment identities with explicit role and approval boundaries. It does not directly address the Harborline Logistics case: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The relevant acceptance criterion for this case is: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

The development user can create approved experiments in the correct domain but receives AccessDenied for protected production operations. This would verify a different operation: Apply identity-based domain and resource permission boundaries with segregated workspace roles and least privilege. That separate action addresses: A SageMaker Studio user can create experiments in a production domain even though their intended access is restricted to development. It cannot establish the required Harborline Logistics correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

A deliberately vulnerable test image is blocked and a compliant approved digest reaches the deployment stage. This would verify a different operation: Integrate ECR image scanning and an enforced reviewed vulnerability acceptance gate before deploying the immutable image digest. That separate action addresses: A training pipeline publishes an unscanned container image with known vulnerable dependencies directly to the production ECR repository. It cannot establish the required Harborline Logistics correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

A cost model using observed utilization demonstrates the break-even point and documents the selected financial tradeoff. This would verify a different operation: Compare actual steady-state resource usage and purchasing alternatives before choosing a suitable commitment or On-Demand strategy. That separate action addresses: A team purchases reserved inference capacity without measuring whether its utilization is predictable enough to offset commitment cost. It cannot establish the required Harborline Logistics correction for: A model serving container returns HTTP 200 for all requests even when its predictor emits empty outputs due to a failed feature lookup. The decisive acceptance check is instead: A controlled missing-lookup request produces a measurable model-error event rather than being counted as a valid prediction.

Scope CloudWatch log actions to required resource ARNs and separate log configuration permissions from ordinary invocation needs. It does not directly address the Silvercrest University case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Inspect SageMaker service quotas and scaling target limits and request justified quota changes before increasing traffic. It does not directly address the Silvercrest University case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. It does not directly address the Silvercrest University case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

The selected instance meets the latency requirement with measured lower normalized cost than the oversized GPU option. This would verify a different operation: Use comparable inference benchmarks across supported instance families and evaluate total cost per thousand successful requests. That separate action addresses: An enterprise ML team assumes a larger GPU instance always reduces cost although the model is small and memory bandwidth is not a bottleneck. It cannot establish the required Silvercrest University correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

A code scan finds no static secret and the notebook's execution role can use only its intended dataset resources. This would verify a different operation: Replace embedded access keys with authorized IAM roles and secure short-lived credential delivery for the notebook environment. That separate action addresses: A SageMaker notebook user stores long-lived AWS credentials in the notebook source so other project members can inspect them. It cannot establish the required Silvercrest University correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

A production task retrieves its secret with the authorized role while build logs reveal no plaintext credential. This would verify a different operation: Use AWS Secrets Manager or an approved secret provider with a scoped runtime role and suppress secret values from pipeline logs. That separate action addresses: An automated deployment retrieves a production database password from a plaintext environment variable stored in a shared build log. It cannot establish the required Silvercrest University correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Limit the SageMaker execution role and bucket policy to the approved data prefix and required object operations. It does not directly address the Pinecrest Hotels case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Enforce protected build contexts, isolated untrusted code execution and restricted deployment credentials available only after review. It does not directly address the Pinecrest Hotels case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Redact or omit sensitive input fields from logs and emit privacy-safe structured metadata with governed retention. It does not directly address the Pinecrest Hotels case: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The relevant acceptance criterion for this case is: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

Cost Explorer separates test and production project charges by approved tags without assigning shared costs to the wrong team. This would verify a different operation: Apply consistent project, environment and model cost-allocation tags and activate the corresponding billing reports. That separate action addresses: A team attributes all SageMaker training expenses to a shared account and cannot explain spending differences across model projects. It cannot establish the required Pinecrest Hotels correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

The inference container accesses authorized model artifacts privately and an external egress test remains blocked. This would verify a different operation: Use approved private subnets, security groups and VPC endpoints where supported to restrict unnecessary network egress. That separate action addresses: A production inference container is placed in subnets with internet egress although its required datasets and dependencies are private AWS services. It cannot establish the required Pinecrest Hotels correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.

The runtime writes to the intended log stream but cannot modify an unrelated service's logging resources. This would verify a different operation: Scope CloudWatch log actions to required resource ARNs and separate log configuration permissions from ordinary invocation needs. That separate action addresses: A model deployment can write arbitrary CloudWatch Logs groups because its inference IAM role includes broad administrative logging permissions. It cannot establish the required Pinecrest Hotels correction for: A model monitoring job alerts on every small weekly seasonal variation and overwhelms operators despite meeting business quality requirements. The decisive acceptance check is instead: A normal seasonal replay stays below the reviewed alert threshold and an injected abnormal shift still produces an alert.