Exam Bundle

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.

Correct the offline-store S3 and IAM configuration and verify feature group creation and data delivery permissions. It does not directly address the Oakridge Public Services 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.

Classify regional attributes and keep processing and storage in approved AWS Regions with authorized data residency controls. It does not directly address the Oakridge Public Services 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.

Separate and explicitly version S3 prefixes or manifests for train, validation and test data with role-based write control. It does not directly address the Oakridge Public Services 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 deliberately delayed record lands in its documented event-time window rather than the time when the collector received it. This would verify a different operation: Retain event-time timestamps and apply the streaming processor's supported window and watermark policy for late arrivals. That separate action addresses: A streaming feature pipeline stores event timestamps as ingestion time only, causing late-arriving mobile events to be counted in the wrong training interval. It cannot establish the required Oakridge Public Services 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 rerun uses the same immutable S3 manifest and produces identical input checksums without public endpoint dependency. This would verify a different operation: Land a versioned, integrity-checked source copy in an authorized S3 data lake before launching repeatable processing jobs. That separate action addresses: A SageMaker processing job repeatedly downloads a multi-gigabyte model-input dataset from a distant public endpoint and fails on unstable external transfers. It cannot establish the required Oakridge Public Services 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.

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 Oakridge Public Services 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.

Attach source system, ingest time and immutable batch manifest metadata to accepted training records during data integration. It does not directly address the Meadowbrook Finance case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. It does not directly address the Meadowbrook Finance case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

Define an as-of-time feature cutoff and exclude any data collected after the target prediction time. It does not directly address the Meadowbrook Finance case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

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 Meadowbrook Finance correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

The completed manifest references every expected part exactly once and no writer replaces another part's S3 object. This would verify a different operation: Write immutable uniquely named S3 objects and publish a versioned manifest after all parallel data-part writes complete. That separate action addresses: Multiple processing workers simultaneously append sample files to one S3 object key and accidentally overwrite each other's contribution to the model dataset. It cannot establish the required Meadowbrook Finance correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

New feature records are queryable from the intended offline store after normal delivery delay while the online store remains functional. This would verify a different operation: Correct the offline-store S3 and IAM configuration and verify feature group creation and data delivery permissions. That separate action addresses: The SageMaker Feature Store offline store is configured with a wrong S3 bucket and the expected historical training features never appear for query. It cannot establish the required Meadowbrook Finance correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

Protect the token mapping with separate least-privilege access and encryption controls and limit its retention to approved workflows. It does not directly address the Redstone Aviation case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

Correct the offline-store S3 and IAM configuration and verify feature group creation and data delivery permissions. It does not directly address the Redstone Aviation case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

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 Redstone Aviation case: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The relevant acceptance criterion for this case is: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

A replay of the same source window yields the same per-key feature history despite differing arrival order between partitions. This would verify a different operation: Persist partition and event sequence metadata in the landing dataset and define deterministic replay order for each key. That separate action addresses: A Kinesis-to-S3 feature pipeline creates out-of-order files without documenting stream partition keys, making subsequent replay inconsistent. It cannot establish the required Redstone Aviation correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

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 Redstone Aviation correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

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 Redstone Aviation correction for: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. The decisive acceptance check is instead: A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample.

Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. It does not directly address the Highland Education case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

Split the original records first, then apply synthetic oversampling exclusively to the training split. It does not directly address the Highland Education case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

Write immutable uniquely named S3 objects and publish a versioned manifest after all parallel data-part writes complete. It does not directly address the Highland Education case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

A replay of the same source window yields the same per-key feature history despite differing arrival order between partitions. This would verify a different operation: Persist partition and event sequence metadata in the landing dataset and define deterministic replay order for each key. That separate action addresses: A Kinesis-to-S3 feature pipeline creates out-of-order files without documenting stream partition keys, making subsequent replay inconsistent. It cannot establish the required Highland Education correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

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 Highland Education correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

The larger test corpus completes staging without local disk exhaustion and model workers read the documented dataset version. This would verify a different operation: Select scalable shared or object storage such as S3 or compatible FSx for Lustre access according to the actual training access pattern. That separate action addresses: A batch inference preparation job loads tens of terabytes through a single small EC2 disk, causing the local staging volume to fill before training begins. It cannot establish the required Highland Education correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

Define annotation guidelines and use supported consensus or adjudication workflows before including labels in model training. It does not directly address the Maplewood Schools case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

Implement a schema-level separation of label and predictor columns and verify feature lineage prior to fitting the model. It does not directly address the Maplewood Schools case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

Apply retention and lifecycle rules compatible with artifact lineage and archive immutable source objects required for approved reproducibility. It does not directly address the Maplewood Schools case: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The relevant acceptance criterion for this case is: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

A deliberately delayed record lands in its documented event-time window rather than the time when the collector received it. This would verify a different operation: Retain event-time timestamps and apply the streaming processor's supported window and watermark policy for late arrivals. That separate action addresses: A streaming feature pipeline stores event timestamps as ingestion time only, causing late-arriving mobile events to be counted in the wrong training interval. It cannot establish the required Maplewood Schools correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

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 Maplewood Schools correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.

A deliberately labeled test row never exposes its target through the predictor schema and the suspicious accuracy is re-evaluated. This would verify a different operation: Implement a schema-level separation of label and predictor columns and verify feature lineage prior to fitting the model. That separate action addresses: A data scientist encodes the target label as an input feature for convenience and obtains a nearly perfect training score. It cannot establish the required Maplewood Schools correction for: A training set combines click counts over seven-day windows but the online feature computation uses calendar-week counts instead. The decisive acceptance check is instead: A controlled event series produces identical seven-day feature values in both training and real-time serving paths.