Exam Bundle

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.

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 Lakeside Research case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

Validate nullable field semantics and reject or impute explicit missing tokens without converting them to legitimate zero values. It does not directly address the Lakeside Research case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

Enable controlled dataset versioning or publish immutable object checksums and a training input manifest for every model build. It does not directly address the Lakeside Research case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

The processing task reads the expected partition objects and its manifest records the correct S3 prefix without missing files. This would verify a different operation: Align the SageMaker processing input URI with the actual produced S3 dataset location and validate the execution role's read permission. That separate action addresses: A SageMaker preprocessing task cannot access the training corpus because its input S3 key prefix differs from the Glue output partition prefix. It cannot establish the required Lakeside Research correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

A lineage audit confirms all feature timestamps precede the corresponding label decision time and accuracy is recalculated. This would verify a different operation: Define an as-of-time feature cutoff and exclude any data collected after the target prediction time. That separate action addresses: A predictive maintenance model trains on sensor readings collected after a recorded machine failure and reports unrealistic validation accuracy. It cannot establish the required Lakeside Research correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

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 Lakeside Research correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

Classify and remove unnecessary protected columns before the ML staging layer and enforce restricted access to retained originals. It does not directly address the Eastshore Energy case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

Introduce an appropriate CDC or streaming ingestion design that preserves update ordering and deduplicates repeated change events. It does not directly address the Eastshore Energy case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

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 Eastshore Energy case: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The relevant acceptance criterion for this case is: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

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 Eastshore Energy correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

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 Eastshore Energy correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

A held-out adjudication sample meets the agreed inter-annotator agreement threshold and disputed items remain traceable. This would verify a different operation: Define annotation guidelines and use supported consensus or adjudication workflows before including labels in model training. That separate action addresses: SageMaker Ground Truth annotators disagree frequently on ambiguous classification labels yet the pipeline treats every raw label as ground truth. It cannot establish the required Eastshore Energy correction for: A team concatenates customer names into feature vectors before masking personal data despite a training dataset policy forbidding direct identifiers. The decisive acceptance check is instead: The model input schema contains no disallowed raw identifiers while the join workflow retains authorized traceable tokens.

Define annotation guidelines and use supported consensus or adjudication workflows before including labels in model training. It does not directly address the Riverton Utilities case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

Define an as-of-time feature cutoff and exclude any data collected after the target prediction time. It does not directly address the Riverton Utilities case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Riverton Utilities case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Riverton Utilities correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied. This would verify a different operation: Classify regional attributes and keep processing and storage in approved AWS Regions with authorized data residency controls. That separate action addresses: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. It cannot establish the required Riverton Utilities correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Riverton Utilities correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Cedarfield Hospitality case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Cedarfield Hospitality case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

Retain event-time timestamps and apply the streaming processor's supported window and watermark policy for late arrivals. It does not directly address the Cedarfield Hospitality case: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The relevant acceptance criterion for this case is: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

A benchmark reads fewer files, preserves event totals and lowers processing overhead for the same approved date partition. This would verify a different operation: Introduce a compaction process that creates suitably sized columnar objects and retains partition and source lineage in the curated dataset. That separate action addresses: An ML data lake receives tiny telemetry objects every second and Spark processing time is dominated by listing and opening millions of files. It cannot establish the required Cedarfield Hospitality correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

A compliance scan finds sensitive samples only in their permitted regions and a disallowed cross-region copy is denied. This would verify a different operation: Classify regional attributes and keep processing and storage in approved AWS Regions with authorized data residency controls. That separate action addresses: A data preparation flow mixes historical US and EU user records without enforcing the documented regional storage restriction for personal attributes. It cannot establish the required Cedarfield Hospitality correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Cedarfield Hospitality correction for: A sentiment pipeline blindly translates all customer messages into English even though translation changes domain-specific product identifiers. The decisive acceptance check is instead: A bilingual reference set retains the required product terms and its label agreement remains inside the approved quality range.

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 Alpine Healthcare case: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The relevant acceptance criterion for this case is: A second training run reads the expected materialized feature version and shows lower repeated transformation time.

Use an authorized transfer plan with manifest or checksum verification and record the source snapshot identifier for lineage. It does not directly address the Alpine Healthcare case: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The relevant acceptance criterion for this case is: A second training run reads the expected materialized feature version and shows lower repeated transformation time.

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 Alpine Healthcare case: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The relevant acceptance criterion for this case is: A second training run reads the expected materialized feature version and shows lower repeated transformation time.

A training role cannot access the mapping store while an explicitly authorized re-identification role can complete an audited lookup. This would verify a different operation: Protect the token mapping with separate least-privilege access and encryption controls and limit its retention to approved workflows. That separate action addresses: An ML pipeline stores masked user IDs but uses a reversible mapping file in a publicly accessible S3 location alongside training data. It cannot establish the required Alpine Healthcare correction for: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The decisive acceptance check is instead: A second training run reads the expected materialized feature version and shows lower repeated transformation time.

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 Alpine Healthcare correction for: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The decisive acceptance check is instead: A second training run reads the expected materialized feature version and shows lower repeated transformation time.

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 Alpine Healthcare correction for: A tabular feature set repeatedly recomputes the same expensive historical aggregations for every training job without a reusable feature definition. The decisive acceptance check is instead: A second training run reads the expected materialized feature version and shows lower repeated transformation time.