Exam Bundle

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 Granite SaaS correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Granite SaaS correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields. This would verify a different operation: Attach source system, ingest time and immutable batch manifest metadata to accepted training records during data integration. That separate action addresses: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. It cannot establish the required Granite SaaS correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Westhaven Retail case: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The relevant acceptance criterion for this case is: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Westhaven Retail case: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The relevant acceptance criterion for this case is: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

Measure partition-key distribution and provision or scale stream capacity using suitable shard or on-demand settings. It does not directly address the Westhaven Retail case: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The relevant acceptance criterion for this case is: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Westhaven Retail correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Westhaven Retail correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Westhaven Retail correction for: A churn model trains on customer age and transaction amount with unrelated scales, causing its distance-based feature representation to be dominated by transaction magnitude. The decisive acceptance check is instead: Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference.

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 Brookside Manufacturing case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Brookside Manufacturing case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

Use the streaming consumer's supported checkpoint and sequence-number handling with idempotent downstream record processing. It does not directly address the Brookside Manufacturing case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Brookside Manufacturing correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Brookside Manufacturing correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Brookside Manufacturing correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Bluehaven Transit case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Bluehaven Transit case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

Retain event-time timestamps and apply the streaming processor's supported window and watermark policy for late arrivals. It does not directly address the Bluehaven Transit case: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The relevant acceptance criterion for this case is: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

The training cutoff precedes the first validation observation and a forward rolling evaluation reproduces the expected boundaries. This would verify a different operation: Use chronological training, validation and final holdout windows with a gap where leakage risk requires one. That separate action addresses: A time-series demand model shuffles future demand records into an earlier training window, invalidating its forward-looking evaluation. It cannot establish the required Bluehaven Transit correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Bluehaven Transit correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

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 Bluehaven Transit correction for: A preprocessing notebook one-hot encodes categories separately for training and serving, producing different feature vector dimensions for unseen labels. The decisive acceptance check is instead: An unseen category follows the documented fallback and the endpoint receives the same stable feature vector dimensions as training.

Define a validated incoming schema and reject malformed CSV records at ingestion before creating the curated training dataset. It does not directly address the Northgate Telecom case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

Write immutable uniquely named S3 objects and publish a versioned manifest after all parallel data-part writes complete. It does not directly address the Northgate Telecom case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

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 Northgate Telecom case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

A disputed reference record can be traced to its originating S3 object and producing system without exposing prohibited user fields. This would verify a different operation: Attach source system, ingest time and immutable batch manifest metadata to accepted training records during data integration. That separate action addresses: A fraud model combines batch data from multiple sources but no provenance field identifies which source produced a disputed training record. It cannot establish the required Northgate Telecom correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

A similarity check finds no synthetic descendants in test data and the external holdout result reflects genuine generalization. This would verify a different operation: Split the original records first, then apply synthetic oversampling exclusively to the training split. That separate action addresses: A fraud model is trained on synthetic minority samples generated before splitting the source data, leading to near-duplicate examples in the test set. It cannot establish the required Northgate Telecom correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

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 Northgate Telecom correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

Fingerprint and review duplicate image groups and reconcile their class labels before publishing the approved training set. It does not directly address the Harborline Logistics case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

Use chronological training, validation and final holdout windows with a gap where leakage risk requires one. It does not directly address the Harborline Logistics case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

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 Harborline Logistics case: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The relevant acceptance criterion for this case is: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

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 Harborline Logistics correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

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 Harborline Logistics correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.

A repeated run references the same content hashes and rejects an unexpected overwrite of a previously accepted input object. This would verify a different operation: Enable controlled dataset versioning or publish immutable object checksums and a training input manifest for every model build. That separate action addresses: An S3 training dataset uses no immutable version identifier, so reruns silently train on objects updated during the model experiment. It cannot establish the required Harborline Logistics correction for: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. The decisive acceptance check is instead: Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model.