Exam Bundle

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 Northgate Telecom correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

The final report records positive-class recall and precision on the original distribution, not only inflated aggregate accuracy. This would verify a different operation: Measure class balance and compare stratified resampling or class weighting on training data while preserving an untouched evaluation set. That separate action addresses: A marketing propensity model has a class distribution of 98 percent negative examples and selection by accuracy alone hides poor positive detection. It cannot establish the required Northgate Telecom correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

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 Northgate Telecom correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

Use time-aware joins against effective-dated reference values to reconstruct the features available when each event occurred. It does not directly address the Harborline Logistics case: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The relevant acceptance criterion for this case is: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

Export and version the complete flow definition as a repeatable SageMaker processing step rather than a notebook-only action. It does not directly address the Harborline Logistics case: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The relevant acceptance criterion for this case is: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

Standardize image dimensions, channel ordering and value normalization in the shared preprocessing artifact. It does not directly address the Harborline Logistics case: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The relevant acceptance criterion for this case is: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

The final report records positive-class recall and precision on the original distribution, not only inflated aggregate accuracy. This would verify a different operation: Measure class balance and compare stratified resampling or class weighting on training data while preserving an untouched evaluation set. That separate action addresses: A marketing propensity model has a class distribution of 98 percent negative examples and selection by accuracy alone hides poor positive detection. It cannot establish the required Harborline Logistics correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

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 Harborline Logistics correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

Distance-sensitive evaluation improves and the identical stored scale parameters are used during training and online inference. This would verify a different operation: Fit a standardization or scaling transform on training data only and apply the saved transform to validation and inference inputs. That separate action addresses: 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. It cannot establish the required Harborline Logistics correction for: A data engineering job stores a large column-oriented training dataset as thousands of verbose JSON files and suffers excessive scan costs in Athena. The decisive acceptance check is instead: The benchmark query scans fewer bytes and still returns identical approved training rows and feature values.

Implement the same window boundaries, event-time cutoff and aggregation logic for offline and online feature creation. It does not directly address the Silvercrest University case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Split the original records first, then apply synthetic oversampling exclusively to the training split. It does not directly address the Silvercrest University case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Use explicit versioned feature names and document producer-consumer contracts for the stored feature definitions. It does not directly address the Silvercrest University case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

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 Silvercrest University correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

A test replay with multiple versions yields one expected customer record and preserves the authorized last-update fields. This would verify a different operation: Deduplicate on stable business identity and event-version rules, retaining the latest accepted entity state as required. That separate action addresses: An ETL pipeline drops duplicate customers using every column as a key even though repeated events have different update timestamps. It cannot establish the required Silvercrest University correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

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 Silvercrest University correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Use explicit versioned feature names and document producer-consumer contracts for the stored feature definitions. It does not directly address the Pinecrest Hotels case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Deduplicate on stable business identity and event-version rules, retaining the latest accepted entity state as required. It does not directly address the Pinecrest Hotels case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Apply retention and lifecycle rules compatible with artifact lineage and archive immutable source objects required for approved reproducibility. It does not directly address the Pinecrest Hotels case: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The relevant acceptance criterion for this case is: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

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 Pinecrest Hotels correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Evaluation documents with relevant late sections contribute to the resulting model input and the length limits remain enforced. This would verify a different operation: Adopt a tested document chunking and aggregation strategy aligned to the model's maximum input length. That separate action addresses: An NLP preparation stage truncates every long document to its first paragraph, systematically dropping the labeled information near the end. It cannot establish the required Pinecrest Hotels correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Zero and positive test values transform into finite documented values and the resulting feature remains suitable for the model. This would verify a different operation: Choose a guarded nonnegative log transformation and test boundary handling before saving the feature pipeline. That separate action addresses: An ML regression dataset has a heavily skewed positive feature, but an unguarded logarithmic transform generates invalid values for zero entries. It cannot establish the required Pinecrest Hotels correction for: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. The decisive acceptance check is instead: The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files.

Profile the feature distribution by label and apply documented context-aware outlier handling rather than global blind filtering. It does not directly address the Oakridge Public Services case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

Enable controlled dataset versioning or publish immutable object checksums and a training input manifest for every model build. It does not directly address the Oakridge Public Services case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

Fingerprint and review duplicate image groups and reconcile their class labels before publishing the approved training set. It does not directly address the Oakridge Public Services case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

A test replay with multiple versions yields one expected customer record and preserves the authorized last-update fields. This would verify a different operation: Deduplicate on stable business identity and event-version rules, retaining the latest accepted entity state as required. That separate action addresses: An ETL pipeline drops duplicate customers using every column as a key even though repeated events have different update timestamps. It cannot establish the required Oakridge Public Services correction for: 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. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

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 Oakridge Public Services correction for: 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. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

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 newly deployed Glue ingestion job tries to infer the schema of evolving JSON events, and a changed field type silently becomes a null column. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

Learn imputation statistics exclusively from the training split and reuse those fixed values on held-out datasets. It does not directly address the Harborview Insurance case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

Choose a guarded nonnegative log transformation and test boundary handling before saving the feature pipeline. It does not directly address the Harborview Insurance case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

Use a stratified or otherwise class-aware splitting method with declared minimum representation checks for the holdout set. It does not directly address the Harborview Insurance case: 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. The relevant acceptance criterion for this case is: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

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 Harborview Insurance correction for: 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. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

A clean automated run produces the same features as the reviewed interactive flow on a fixed reference sample. This would verify a different operation: Export and version the complete flow definition as a repeatable SageMaker processing step rather than a notebook-only action. That separate action addresses: A SageMaker Data Wrangler flow contains an interactive manual step that is not reflected in the exported production preprocessing job. It cannot establish the required Harborview Insurance correction for: 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. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.

A multilingual test phrase yields the same token IDs in the training pipeline and deployed inference endpoint. This would verify a different operation: Version a single canonical text normalization and tokenizer artifact and use it in both processing and serving containers. That separate action addresses: A text classifier tokenizes raw Unicode text differently in batch training and the real-time inference application. It cannot establish the required Harborview Insurance correction for: 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. The decisive acceptance check is instead: A field-type regression is quarantined and a compatible schema revision remains queryable with the expected typed attributes.