Exam Bundle

A controlled malformed sample enters the rejected-record path while valid rows retain their expected column names and feature values. This would verify a different operation: Define a validated incoming schema and reject malformed CSV records at ingestion before creating the curated training dataset. That separate action addresses: A scheduled training pipeline reads CSV from an S3 bucket, but individual files contain inconsistent delimiters and the parsing job silently shifts feature columns. It cannot establish the required Cedarfield Hospitality correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files. This would verify a different operation: Align the SageMaker processing input URI with the actual produced S3 dataset location and validate the execution role's read permission. That separate action addresses: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. It cannot establish the required Cedarfield Hospitality correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

The training schema references the intended version and a sampled stored record matches its declared transformation lineage. This would verify a different operation: Use explicit versioned feature names and document producer-consumer contracts for the stored feature definitions. That separate action addresses: A SageMaker Feature Store group publishes a transformed feature but training continues to read an older raw column with the same business label. It cannot establish the required Cedarfield Hospitality correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Riverton Utilities case: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The relevant acceptance criterion for this case is: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

Materialize governed versioned features with an appropriate offline store and documented recomputation schedule. It does not directly address the Riverton Utilities case: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The relevant acceptance criterion for this case is: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

Fit and persist a categorical encoder on the training set with an explicit unknown-category handling policy for all later inputs. It does not directly address the Riverton Utilities case: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The relevant acceptance criterion for this case is: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

A training-container read test reaches the specific feature files while a different identity cannot access the protected directory. This would verify a different operation: Configure authorized EFS access-point or POSIX permissions and ensure the job's VPC mount connectivity supports the intended path. That separate action addresses: A SageMaker training job reads from a shared EFS mount but fails because the container user lacks filesystem permissions on the feature directory. It cannot establish the required Riverton Utilities correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

A test encrypted object can be read by the approved role while an unrelated role remains denied by S3 or KMS authorization. This would verify a different operation: Grant narrowly scoped source-object and KMS decrypt permissions to the authorized consuming role and confirm the key policy permits the operation. That separate action addresses: An S3 ingestion workload receives intermittent AccessDenied errors because the producing account encrypts objects with a customer-managed KMS key inaccessible to the training role. It cannot establish the required Riverton Utilities correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features. This would verify a different operation: Apply an appropriate categorical encoding while preserving the region identifier's nominal semantics and missing-value policy. That separate action addresses: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. It cannot establish the required Riverton Utilities correction for: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. The decisive acceptance check is instead: A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied.

Align the SageMaker processing input URI with the actual produced S3 dataset location and validate the execution role's read permission. It does not directly address the Juniper Media case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Define an authoritative join key and a validated join cardinality before merging the two approved data sources. It does not directly address the Juniper Media case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Persist partition and event sequence metadata in the landing dataset and define deterministic replay order for each key. It does not directly address the Juniper Media case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

The training schema references the intended version and a sampled stored record matches its declared transformation lineage. This would verify a different operation: Use explicit versioned feature names and document producer-consumer contracts for the stored feature definitions. That separate action addresses: A SageMaker Feature Store group publishes a transformed feature but training continues to read an older raw column with the same business label. It cannot establish the required Juniper Media correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Subsequent readers select the newly committed version and no partial object contents are exposed as an accepted input. This would verify a different operation: Change the workflow to write complete immutable S3 objects and publish a new object or manifest version instead of POSIX-style append. That separate action addresses: A data ingestion script assumes S3 is a POSIX filesystem and tries in-place append operations on one object during batch preparation. It cannot establish the required Juniper Media correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features. This would verify a different operation: Apply an appropriate categorical encoding while preserving the region identifier's nominal semantics and missing-value policy. That separate action addresses: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. It cannot establish the required Juniper Media correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Record and deploy a specific reviewed recipe version together with input snapshot identifiers for every training dataset build. It does not directly address the Alpine Healthcare case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Align the SageMaker processing input URI with the actual produced S3 dataset location and validate the execution role's read permission. It does not directly address the Alpine Healthcare case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Measure partition-key distribution and provision or scale stream capacity using suitable shard or on-demand settings. It does not directly address the Alpine Healthcare case: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The relevant acceptance criterion for this case is: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample. This would verify a different operation: Export and version the complete flow definition as a repeatable SageMaker processing step rather than a notebook-only action. That separate action addresses: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. It cannot establish the required Alpine Healthcare correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

A test encrypted object can be read by the approved role while an unrelated role remains denied by S3 or KMS authorization. This would verify a different operation: Grant narrowly scoped source-object and KMS decrypt permissions to the authorized consuming role and confirm the key policy permits the operation. That separate action addresses: An S3 ingestion workload receives intermittent AccessDenied errors because the producing account encrypts objects with a customer-managed KMS key inaccessible to the training role. It cannot establish the required Alpine Healthcare correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

A measured extract contains only authorized columns and the intended time window while transfer volume decreases. This would verify a different operation: Push filters and projections into an appropriate query or unload operation before delivering selected fields to the training pipeline. That separate action addresses: A distributed feature preparation process overfetches every Redshift table column even though the model uses just a few features and one time period. It cannot establish the required Alpine Healthcare correction for: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. The decisive acceptance check is instead: The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing.

Configure authorized EFS access-point or POSIX permissions and ensure the job's VPC mount connectivity supports the intended path. It does not directly address the Keystone BioLabs case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Keystone BioLabs case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Make the feature write idempotent using event identifiers or version checks and send repeated failures to a controlled recovery path. It does not directly address the Keystone BioLabs case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception. This would verify a different operation: Define a validated label encoding dictionary and reject unmapped target values before model training starts. That separate action addresses: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. It cannot establish the required Keystone BioLabs correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

A forced consumer restart resumes from the committed position and produces no duplicated training events for the test partition. This would verify a different operation: Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. That separate action addresses: An event-driven fraud model receives new records in Kinesis, but the consumer uses a hard-coded shard checkpoint that replays the same events after restart. It cannot establish the required Keystone BioLabs correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample. This would verify a different operation: Export and version the complete flow definition as a repeatable SageMaker processing step rather than a notebook-only action. That separate action addresses: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. It cannot establish the required Keystone BioLabs correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Grant narrowly scoped source-object and KMS decrypt permissions to the authorized consuming role and confirm the key policy permits the operation. It does not directly address the Timberline Foods case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Export and version the complete flow definition as a repeatable SageMaker processing step rather than a notebook-only action. It does not directly address the Timberline Foods case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Learn imputation statistics exclusively from the training split and reuse those fixed values on held-out datasets. It does not directly address the Timberline Foods case: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The relevant acceptance criterion for this case is: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint. This would verify a different operation: Version a single canonical text normalization and tokenizer artifact and use it in both processing and serving containers. That separate action addresses: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. It cannot establish the required Timberline Foods correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features. This would verify a different operation: Apply an appropriate categorical encoding while preserving the region identifier's nominal semantics and missing-value policy. That separate action addresses: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. It cannot establish the required Timberline Foods correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.

A sampled reconciliation shows expected one-to-many relationships and the final training row count meets the documented bounds. This would verify a different operation: Define an authoritative join key and a validated join cardinality before merging the two approved data sources. That separate action addresses: An ML team combines order data from RDS and session data from S3 without a stable customer join key and accidentally multiplies training rows. It cannot establish the required Timberline Foods correction for: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. The decisive acceptance check is instead: The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries.