Exam Bundle

A manifest audit finds every record in exactly its intended split with no overlapping S3 object references. This would verify a different operation: Separate and explicitly version S3 prefixes or manifests for train, validation and test data with role-based write control. That separate action addresses: An S3 training inventory uses object prefixes that mix production and evaluation records, causing the preparation job to include the wrong dataset split. It cannot establish the required Brookside Manufacturing correction for: A streaming Lambda transformer retries failed events but appends duplicate feature writes each time its invocation is replayed. The decisive acceptance check is instead: Two deliveries of one test event result in one accepted logical feature update and a failed payload remains retriable.

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 Brookside Manufacturing correction for: A streaming Lambda transformer retries failed events but appends duplicate feature writes each time its invocation is replayed. The decisive acceptance check is instead: Two deliveries of one test event result in one accepted logical feature update and a failed payload remains retriable.

The benchmark query scans fewer bytes and still returns identical approved training rows and feature values. This would verify a different operation: Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. That separate action addresses: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. It cannot establish the required Brookside Manufacturing correction for: A streaming Lambda transformer retries failed events but appends duplicate feature writes each time its invocation is replayed. The decisive acceptance check is instead: Two deliveries of one test event result in one accepted logical feature update and a failed payload remains retriable.

Correct the offline-store S3 and IAM configuration and verify feature group creation and data delivery permissions. It does not directly address the Harborline Logistics case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Write immutable uniquely named S3 objects and publish a versioned manifest after all parallel data-part writes complete. It does not directly address the Harborline Logistics case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Push filters and projections into an appropriate query or unload operation before delivering selected fields to the training pipeline. It does not directly address the Harborline Logistics case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

A scheduled retention test can still retrieve every manifest object needed to reproduce the archived model version. This would verify a different operation: Apply retention and lifecycle rules compatible with artifact lineage and archive immutable source objects required for approved reproducibility. That separate action addresses: A training manifest refers to S3 objects that were removed by an aggressive lifecycle rule, so reproducible model builds fail months later. It cannot establish the required Harborline Logistics correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

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 Harborline Logistics correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

The duplicate audit shows coherent labels within matching-image clusters and a reviewed exception log tracks ambiguous cases. This would verify a different operation: Fingerprint and review duplicate image groups and reconcile their class labels before publishing the approved training set. That separate action addresses: A classification training set contains duplicated near-identical product images assigned conflicting labels, creating avoidable noise. It cannot establish the required Harborline Logistics correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Add schema, null-rate and range checks using AWS Glue Data Quality or equivalent before the training step begins. It does not directly address the Northgate Telecom case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Classify and remove unnecessary protected columns before the ML staging layer and enforce restricted access to retained originals. It does not directly address the Northgate Telecom case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Run the appropriate Clarify data-bias analysis and record the fairness baseline and approved mitigation assessment before model release. It does not directly address the Northgate Telecom case: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The relevant acceptance criterion for this case is: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

The faulty batch is quarantined based on the defined feature threshold and a clean control batch continues processing. This would verify a different operation: Add schema, null-rate and range checks using AWS Glue Data Quality or equivalent before the training step begins. That separate action addresses: An automated data quality gate checks only row counts while a critical feature's null rate jumps from one percent to 40 percent. It cannot establish the required Northgate Telecom correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

A manifest audit finds every record in exactly its intended split with no overlapping S3 object references. This would verify a different operation: Separate and explicitly version S3 prefixes or manifests for train, validation and test data with role-based write control. That separate action addresses: An S3 training inventory uses object prefixes that mix production and evaluation records, causing the preparation job to include the wrong dataset split. It cannot establish the required Northgate Telecom correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

An audit of transformed images preserves orientation-sensitive labels and prohibited flips are absent from model training. This would verify a different operation: Restrict image augmentation to clinically valid transformations and verify label invariance for each permitted operation. That separate action addresses: A clinical image dataset uses an augmentation pipeline that reverses left-right orientation despite labels depending on laterality. It cannot establish the required Northgate Telecom correction for: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. The decisive acceptance check is instead: A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts.

Measure partition-key distribution and provision or scale stream capacity using suitable shard or on-demand settings. It does not directly address the Pinecrest Hotels case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Classify regional attributes and keep processing and storage in approved AWS Regions with authorized data residency controls. It does not directly address the Pinecrest Hotels case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Split examples by patient identity and keep all records for one identity in only one dataset partition. It does not directly address the Pinecrest Hotels case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

The baseline report contains relevant protected-group comparisons and an accountable review documents any mitigation and residual risk. This would verify a different operation: Run the appropriate Clarify data-bias analysis and record the fairness baseline and approved mitigation assessment before model release. That separate action addresses: SageMaker Clarify pre-training bias metrics flag a demographic proportion imbalance but the team reports only overall training loss. It cannot establish the required Pinecrest Hotels correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied. This would verify a different operation: Classify regional attributes and keep processing and storage in approved AWS Regions with authorized data residency controls. That separate action addresses: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. It cannot establish the required Pinecrest Hotels correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

A lineage audit confirms all feature timestamps precede the corresponding label decision time and accuracy is recalculated. This would verify a different operation: Define an as-of-time feature cutoff and exclude any data collected after the target prediction time. That separate action addresses: A predictive maintenance model trains on sensor readings collected after a recorded machine failure and reports unrealistic validation accuracy. It cannot establish the required Pinecrest Hotels correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Introduce a compaction process that creates suitably sized columnar objects and retains partition and source lineage in the curated dataset. It does not directly address the Silvercrest University case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Attach source system, ingest time and immutable batch manifest metadata to accepted training records during data integration. It does not directly address the Silvercrest University case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Run the appropriate Clarify data-bias analysis and record the fairness baseline and approved mitigation assessment before model release. It does not directly address the Silvercrest University case: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The relevant acceptance criterion for this case is: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

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 Silvercrest University correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

The benchmark query scans fewer bytes and still returns identical approved training rows and feature values. This would verify a different operation: Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. That separate action addresses: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. It cannot establish the required Silvercrest University correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

A cross-split identity audit finds no patient overlap and the held-out metric is computed on previously unseen identities. This would verify a different operation: Split examples by patient identity and keep all records for one identity in only one dataset partition. That separate action addresses: An ML pipeline randomly splits multiple events from one patient across training and test datasets, leaking individual-specific signals. It cannot establish the required Silvercrest University correction for: A binary target is stored as strings with inconsistent capitalization and preprocessing silently maps one valid positive class to negative. The decisive acceptance check is instead: An input set with mixed-capitalization labels maps consistently while an unknown label triggers the declared quality exception.

Run the appropriate Clarify data-bias analysis and record the fairness baseline and approved mitigation assessment before model release. It does not directly address the Harborview Insurance case: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The relevant acceptance criterion for this case is: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.

Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. It does not directly address the Harborview Insurance case: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The relevant acceptance criterion for this case is: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.

Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. It does not directly address the Harborview Insurance case: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The relevant acceptance criterion for this case is: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.

A reproducible export contains the required records while production capacity and latency remain inside agreed limits. This would verify a different operation: Use a designed DynamoDB export to S3 or appropriate controlled query pattern instead of repeated unrestricted production table scans. That separate action addresses: A training pipeline needs recent transaction attributes from DynamoDB, but its ad hoc full table scan increases read capacity consumption during business hours. It cannot establish the required Harborview Insurance correction for: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The decisive acceptance check is instead: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.

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 Harborview Insurance correction for: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The decisive acceptance check is instead: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.

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 Harborview Insurance correction for: A numeric categorical code such as region ID is mistakenly treated as an ordered magnitude when supplied to a linear model. The decisive acceptance check is instead: Model input checks confirm no implied numerical ordering and all expected regions map to the approved encoded features.