Exam Bundle

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 Oakridge Public Services correction for: A clinical image dataset uses an augmentation pipeline that reverses left-right orientation despite labels depending on laterality. The decisive acceptance check is instead: An audit of transformed images preserves orientation-sensitive labels and prohibited flips are absent from model training.

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 Oakridge Public Services correction for: A clinical image dataset uses an augmentation pipeline that reverses left-right orientation despite labels depending on laterality. The decisive acceptance check is instead: An audit of transformed images preserves orientation-sensitive labels and prohibited flips are absent from model training.

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 clinical image dataset uses an augmentation pipeline that reverses left-right orientation despite labels depending on laterality. The decisive acceptance check is instead: An audit of transformed images preserves orientation-sensitive labels and prohibited flips are absent from model training.

Change the workflow to write complete immutable S3 objects and publish a new object or manifest version instead of POSIX-style append. It does not directly address the Meadowbrook Finance case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

Use time-aware joins against effective-dated reference values to reconstruct the features available when each event occurred. It does not directly address the Meadowbrook Finance case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

Adopt a tested document chunking and aggregation strategy aligned to the model's maximum input length. It does not directly address the Meadowbrook Finance case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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 Meadowbrook Finance correction for: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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 Meadowbrook Finance correction for: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. It does not directly address the Redstone Aviation case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

Choose a guarded nonnegative log transformation and test boundary handling before saving the feature pipeline. It does not directly address the Redstone Aviation case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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 Redstone Aviation case: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The relevant acceptance criterion for this case is: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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 Redstone Aviation correction for: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training. This would verify a different operation: Fit and persist a categorical encoder on the training set with an explicit unknown-category handling policy for all later inputs. That separate action addresses: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. It cannot establish the required Redstone Aviation correction for: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

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 Redstone Aviation correction for: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. The decisive acceptance check is instead: A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup.

Convert the curated training data to partitioned Parquet with column statistics and choose partitions aligned to actual predicates. It does not directly address the Highland Education case: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Highland Education case: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

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 multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

A historical example contains the category active at its original event timestamp instead of a later corrected label. This would verify a different operation: Use time-aware joins against effective-dated reference values to reconstruct the features available when each event occurred. That separate action addresses: A batch transformation joins slowly changing reference categories using today's labels for all historic examples, leaking future feature state. It cannot establish the required Highland Education correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

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 Highland Education correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

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 Highland Education correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. It does not directly address the Maplewood Schools case: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. It does not directly address the Maplewood Schools case: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

Version a single canonical text normalization and tokenizer artifact and use it in both processing and serving containers. It does not directly address the Maplewood Schools case: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The relevant acceptance criterion for this case is: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

A controlled rebuild with the same recipe and source manifest reproduces feature checksums and row counts. This would verify a different operation: Record and deploy a specific reviewed recipe version together with input snapshot identifiers for every training dataset build. That separate action addresses: An AWS Glue DataBrew recipe is edited directly in production and a rerun cannot reproduce the original training features. It cannot establish the required Maplewood Schools correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

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 Maplewood Schools correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

A second training run reads the expected materialized feature version and shows lower repeated transformation time. This would verify a different operation: Materialize governed versioned features with an appropriate offline store and documented recomputation schedule. That separate action addresses: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. It cannot establish the required Maplewood Schools correction for: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. The decisive acceptance check is instead: Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test.

Define a validated label encoding dictionary and reject unmapped target values before model training starts. It does not directly address the Lakeside Research case: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The relevant acceptance criterion for this case is: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.

Perform approved irreversible masking or tokenization before feature extraction and restrict the original identifier fields. It does not directly address the Lakeside Research case: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The relevant acceptance criterion for this case is: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.

Choose a guarded nonnegative log transformation and test boundary handling before saving the feature pipeline. It does not directly address the Lakeside Research case: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The relevant acceptance criterion for this case is: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.

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 Lakeside Research correction for: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The decisive acceptance check is instead: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.

The controlled high-rate producer stays within accepted write limits and downstream lag returns to the target threshold. This would verify a different operation: Measure partition-key distribution and provision or scale stream capacity using suitable shard or on-demand settings. That separate action addresses: A high-volume inference feature ingest uses one Kinesis shard even after throughput grows, leading to sustained throttling of producer records. It cannot establish the required Lakeside Research correction for: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The decisive acceptance check is instead: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.

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 Lakeside Research correction for: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. The decisive acceptance check is instead: A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields.