Exam Bundle

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.

Land a versioned, integrity-checked source copy in an authorized S3 data lake before launching repeatable processing jobs. It does not directly address the Silvercrest University case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

Persist partition and event sequence metadata in the landing dataset and define deterministic replay order for each key. It does not directly address the Silvercrest University case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

Apply retention and lifecycle rules compatible with artifact lineage and archive immutable source objects required for approved reproducibility. It does not directly address the Silvercrest University case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Silvercrest University correction for: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Silvercrest University correction for: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Pinecrest Hotels case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

Select scalable shared or object storage such as S3 or compatible FSx for Lustre access according to the actual training access pattern. It does not directly address the Pinecrest Hotels case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Pinecrest Hotels case: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The relevant acceptance criterion for this case is: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

Every required rare class appears at least the configured minimum count in evaluation and no training row is duplicated into test. This would verify a different operation: Use a stratified or otherwise class-aware splitting method with declared minimum representation checks for the holdout set. That separate action addresses: A multi-class label dataset is split without stratification and a rare class is missing entirely from the evaluation partition. It cannot establish the required Pinecrest Hotels correction for: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Pinecrest Hotels correction for: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Pinecrest Hotels correction for: A training dataset has missing sensor measurements that are filled using the global mean calculated from test and validation records. The decisive acceptance check is instead: The held-out split does not affect learned fill values and a repeated inference request reproduces the expected imputed feature.

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 Oakridge Public Services case: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

Define an authoritative join key and a validated join cardinality before merging the two approved data sources. It does not directly address the Oakridge Public Services case: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Oakridge Public Services case: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes. This would verify a different operation: Register and validate an explicit schema or compatible evolution policy before promoting events into the curated training zone. That separate action addresses: A newly deployed Glue ingestion job tries to infer the schema of evolving JSON events, and a changed field type silently becomes a null column. It cannot establish the required Oakridge Public Services correction for: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 Oakridge Public Services correction for: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 Harborview Insurance case: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

Use chronological training, validation and final holdout windows with a gap where leakage risk requires one. It does not directly address the Harborview Insurance case: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The relevant acceptance criterion for this case is: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 Harborview Insurance correction for: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

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 Harborview Insurance correction for: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. The decisive acceptance check is instead: A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Redstone Aviation case: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The relevant acceptance criterion for this case is: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.

Measure class balance and compare stratified resampling or class weighting on training data while preserving an untouched evaluation set. It does not directly address the Redstone Aviation case: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The relevant acceptance criterion for this case is: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.

Retain event-time timestamps and apply the streaming processor's supported window and watermark policy for late arrivals. It does not directly address the Redstone Aviation case: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The relevant acceptance criterion for this case is: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.

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 Redstone Aviation correction for: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The decisive acceptance check is instead: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.

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 Redstone Aviation correction for: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The decisive acceptance check is instead: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.

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: A data-wrangling job treats all high-value transactions as outliers and deletes legitimate rare fraud cases critical to model recall. The decisive acceptance check is instead: The retained training sample preserves known rare positives and a held-out fraud recall check remains within the target band.