Exam Bundle

The destination manifest reconciles object counts and checksums with the source snapshot and identifies any failed transfers. This would verify a different operation: Use an authorized transfer plan with manifest or checksum verification and record the source snapshot identifier for lineage. That separate action addresses: A sensitive ML corpus copied by DataSync into S3 has no reproducible record that the transferred objects match the approved source snapshot. It cannot establish the required Meadowbrook Finance correction for: SageMaker Ground Truth annotators disagree frequently on ambiguous classification labels yet the pipeline treats every raw label as ground truth. The decisive acceptance check is instead: A held-out adjudication sample meets the agreed inter-annotator agreement threshold and disputed items remain traceable.

A controlled event series produces identical seven-day feature values in both training and real-time serving paths. This would verify a different operation: Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. That separate action addresses: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. It cannot establish the required Meadowbrook Finance correction for: SageMaker Ground Truth annotators disagree frequently on ambiguous classification labels yet the pipeline treats every raw label as ground truth. The decisive acceptance check is instead: A held-out adjudication sample meets the agreed inter-annotator agreement threshold and disputed items remain traceable.

Two deliveries of one test event result in one accepted logical feature update and a failed payload remains retriable. This would verify a different operation: Make the feature write idempotent using event identifiers or version checks and send repeated failures to a controlled recovery path. That separate action addresses: A streaming Lambda transformer retries failed events but appends duplicate feature writes each time its invocation is replayed. It cannot establish the required Meadowbrook Finance correction for: SageMaker Ground Truth annotators disagree frequently on ambiguous classification labels yet the pipeline treats every raw label as ground truth. The decisive acceptance check is instead: A held-out adjudication sample meets the agreed inter-annotator agreement threshold and disputed items remain traceable.

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 Maplewood Schools case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

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 Maplewood Schools case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. It does not directly address the Maplewood Schools case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

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 Maplewood Schools correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

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 Maplewood Schools correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens. This would verify a different operation: Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. That separate action addresses: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. It cannot establish the required Maplewood Schools correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. It does not directly address the Highland Education case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

Use an authorized transfer plan with manifest or checksum verification and record the source snapshot identifier for lineage. It does not directly address the Highland Education case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. It does not directly address the Highland Education case: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The relevant acceptance criterion for this case is: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens. This would verify a different operation: Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. That separate action addresses: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. It cannot establish the required Highland Education correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

A controlled event series produces identical seven-day feature values in both training and real-time serving paths. This would verify a different operation: Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. That separate action addresses: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. It cannot establish the required Highland Education correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

The destination manifest reconciles object counts and checksums with the source snapshot and identifies any failed transfers. This would verify a different operation: Use an authorized transfer plan with manifest or checksum verification and record the source snapshot identifier for lineage. That separate action addresses: A sensitive ML corpus copied by DataSync into S3 has no reproducible record that the transferred objects match the approved source snapshot. It cannot establish the required Highland Education correction for: A source CSV sends the literal string NULL for missing prices, but the preparation job treats it as a valid zero-dollar transaction. The decisive acceptance check is instead: A test input with NULL is marked missing and a true zero-dollar record remains distinguishable in the clean dataset.

Persist partition and event sequence metadata in the landing dataset and define deterministic replay order for each key. It does not directly address the Eastshore Energy case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Standardize image dimensions, channel ordering and value normalization in the shared preprocessing artifact. It does not directly address the Eastshore Energy case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Use a suitable embedding or hashing approach with collision and memory impact assessed for the model objective. It does not directly address the Eastshore Energy case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

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 Eastshore Energy correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

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 Eastshore Energy correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens. This would verify a different operation: Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. That separate action addresses: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. It cannot establish the required Eastshore Energy correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Correct the offline-store S3 and IAM configuration and verify feature group creation and data delivery permissions. It does not directly address the Lakeside Research case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. It does not directly address the Lakeside Research case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Lakeside Research case: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The relevant acceptance criterion for this case is: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

A known test image produces matching normalized pixel tensors in offline and online environments. This would verify a different operation: Standardize image dimensions, channel ordering and value normalization in the shared preprocessing artifact. That separate action addresses: An image classification pipeline resizes training images with one color-channel convention and production inputs with another. It cannot establish the required Lakeside Research correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

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 Lakeside Research correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

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 Lakeside Research correction for: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. The decisive acceptance check is instead: A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object.

Adopt a tested document chunking and aggregation strategy aligned to the model's maximum input length. It does not directly address the Cedarfield Hospitality 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.

Define a validated label encoding dictionary and reject unmapped target values before model training starts. It does not directly address the Cedarfield Hospitality 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.

Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. It does not directly address the Cedarfield Hospitality 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 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.