Exam Bundle

A simulated late failure resumes from a completed checkpoint without repeating successful expensive stages. This is evidence for a different corrective change: Persist validated intermediate artifacts and allow safe resume from completed pipeline stages. That other change addresses: A long multi-stage training job loses all intermediate work when a downstream stage fails just before deployment. It does not validate the specific Silverline Insurance remediation for: The pipeline runner executes as a project administrator and can change unrelated production services even though it only needs designated data and model permissions. The necessary check instead is: The intended DAG succeeds while attempts to modify unrelated project services receive permission denial.

Holdout identity and permissions checks confirm test records were excluded from fit and tuning. This is evidence for a different corrective change: Create an isolated versioned evaluation split that the training step cannot read for optimization. That other change addresses: A training pipeline evaluates a model on the same rows used for fitting because the only available dataset path is labeled training. It does not validate the specific Silverline Insurance remediation for: The pipeline runner executes as a project administrator and can change unrelated production services even though it only needs designated data and model permissions. The necessary check instead is: The intended DAG succeeds while attempts to modify unrelated project services receive permission denial.

A complete run records stage dependencies, retries, and lineage without an operator manually invoking each stage. This is evidence for a different corrective change: Use Gemini Enterprise Agent Platform Pipelines with versioned, parameterized stages for the supported workflow. That other change addresses: A straightforward model workflow is built from a fragile hand-managed shell scheduler even though it needs repeatable managed pipeline components. It does not validate the specific Silverline Insurance remediation for: The pipeline runner executes as a project administrator and can change unrelated production services even though it only needs designated data and model permissions. The necessary check instead is: The intended DAG succeeds while attempts to modify unrelated project services receive permission denial.

Use Managed Service for Apache Airflow when cross-system DAG orchestration and scheduling requirements justify it. This action could be suitable for a different engineering incident: A data-platform team must coordinate ML jobs with enterprise ingestion schedules and approval tasks spanning several managed services. It does not directly correct the reported Northgate Clinical Systems failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Register the output artifact with its immutable digest, approved evaluation, and source pipeline run. This action could be suitable for a different engineering incident: A successful pipeline writes a model to an arbitrary folder without immutable version information, leaving registry entries out of sync. It does not directly correct the reported Northgate Clinical Systems failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Use Gemini Enterprise Agent Platform Pipelines with versioned, parameterized stages for the supported workflow. This action could be suitable for a different engineering incident: A straightforward model workflow is built from a fragile hand-managed shell scheduler even though it needs repeatable managed pipeline components. It does not directly correct the reported Northgate Clinical Systems failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

The registry version resolves to the final pipeline output hash and associated metrics. This is evidence for a different corrective change: Register the output artifact with its immutable digest, approved evaluation, and source pipeline run. That other change addresses: A successful pipeline writes a model to an arbitrary folder without immutable version information, leaving registry entries out of sync. It does not validate the specific Northgate Clinical Systems remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

A complete run records stage dependencies, retries, and lineage without an operator manually invoking each stage. This is evidence for a different corrective change: Use Gemini Enterprise Agent Platform Pipelines with versioned, parameterized stages for the supported workflow. That other change addresses: A straightforward model workflow is built from a fragile hand-managed shell scheduler even though it needs repeatable managed pipeline components. It does not validate the specific Northgate Clinical Systems remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

A scheduled DAG respects ingestion completion, approval dependencies, and recoverable task retries. This is evidence for a different corrective change: Use Managed Service for Apache Airflow when cross-system DAG orchestration and scheduling requirements justify it. That other change addresses: A data-platform team must coordinate ML jobs with enterprise ingestion schedules and approval tasks spanning several managed services. It does not validate the specific Northgate Clinical Systems remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Register the output artifact with its immutable digest, approved evaluation, and source pipeline run. This action could be suitable for a different engineering incident: A successful pipeline writes a model to an arbitrary folder without immutable version information, leaving registry entries out of sync. It does not directly correct the reported Stonewell Payments failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Add a safety and privacy evaluation gate with reviewed adversarial and refusal cases to the training pipeline. This action could be suitable for a different engineering incident: An LLM evaluation pipeline optimizes instruction following but never measures safe refusals on sensitive customer requests. It does not directly correct the reported Stonewell Payments failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Add automated train-serving feature parity checks using a shared golden fixture set as a release gate. This action could be suitable for a different engineering incident: A deployed model's online preprocessing changes independently from training transformations and silently alters numeric feature scaling. It does not directly correct the reported Stonewell Payments failure: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The discriminating acceptance check here is: Two runs against the same manifest resolve identical container digests and consistent outputs.

The registry version resolves to the final pipeline output hash and associated metrics. This is evidence for a different corrective change: Register the output artifact with its immutable digest, approved evaluation, and source pipeline run. That other change addresses: A successful pipeline writes a model to an arbitrary folder without immutable version information, leaving registry entries out of sync. It does not validate the specific Stonewell Payments remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

A deliberately altered online scale fails the release gate and the correct transform passes. This is evidence for a different corrective change: Add automated train-serving feature parity checks using a shared golden fixture set as a release gate. That other change addresses: A deployed model's online preprocessing changes independently from training transformations and silently alters numeric feature scaling. It does not validate the specific Stonewell Payments remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

An unsafe candidate fails the release pipeline even if its standard instruction score is high. This is evidence for a different corrective change: Add a safety and privacy evaluation gate with reviewed adversarial and refusal cases to the training pipeline. That other change addresses: An LLM evaluation pipeline optimizes instruction following but never measures safe refusals on sensitive customer requests. It does not validate the specific Stonewell Payments remediation for: A reproducible training pipeline uses an unpinned latest container tag, so identical input manifests produce different dependencies after updates. The necessary check instead is: Two runs against the same manifest resolve identical container digests and consistent outputs.

Bind pipeline stages to narrow service identities and enforce scoped permissions for each resource. This action could be suitable for a different engineering incident: The pipeline runner executes as a project administrator and can change unrelated production services even though it only needs designated data and model permissions. It does not directly correct the reported Harbor Rail Logistics failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Declare explicit directed dependencies that prevent training and registration from starting before input validation passes. This action could be suitable for a different engineering incident: A training pipeline sometimes registers a model before the data validation task finishes because dependencies are represented only in informal naming. It does not directly correct the reported Harbor Rail Logistics failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Package the preprocessing transform as a reusable versioned component shared between offline training and serving. This action could be suitable for a different engineering incident: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. It does not directly correct the reported Harbor Rail Logistics failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass. This is evidence for a different corrective change: Package the preprocessing transform as a reusable versioned component shared between offline training and serving. That other change addresses: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. It does not validate the specific Harbor Rail Logistics remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

The intended DAG succeeds while attempts to modify unrelated project services receive permission denial. This is evidence for a different corrective change: Bind pipeline stages to narrow service identities and enforce scoped permissions for each resource. That other change addresses: The pipeline runner executes as a project administrator and can change unrelated production services even though it only needs designated data and model permissions. It does not validate the specific Harbor Rail Logistics remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

An injected slow validation stage blocks downstream tasks until its successful completion. This is evidence for a different corrective change: Declare explicit directed dependencies that prevent training and registration from starting before input validation passes. That other change addresses: A training pipeline sometimes registers a model before the data validation task finishes because dependencies are represented only in informal naming. It does not validate the specific Harbor Rail Logistics remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Capture immutable dataset versions, transformation container digests, and execution parameters for each pipeline. This action could be suitable for a different engineering incident: An ML team reruns a pipeline against a mutable dataset without recording a snapshot and cannot explain different results between runs. It does not directly correct the reported Aster Pharma failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Add automated train-serving feature parity checks using a shared golden fixture set as a release gate. This action could be suitable for a different engineering incident: A deployed model's online preprocessing changes independently from training transformations and silently alters numeric feature scaling. It does not directly correct the reported Aster Pharma failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Add a controlled manual approval step after automated evidence collection and before production promotion. This action could be suitable for a different engineering incident: A sensitive-risk model is automatically deployed after evaluation even though an accountable human sign-off is required. It does not directly correct the reported Aster Pharma failure: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The discriminating acceptance check here is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

A passing but unapproved model remains nonproduction; approved promotion records the reviewer and artifact hash. This is evidence for a different corrective change: Add a controlled manual approval step after automated evidence collection and before production promotion. That other change addresses: A sensitive-risk model is automatically deployed after evaluation even though an accountable human sign-off is required. It does not validate the specific Aster Pharma remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

A replay with the recorded manifest reproduces output hashes or documented numeric tolerances. This is evidence for a different corrective change: Capture immutable dataset versions, transformation container digests, and execution parameters for each pipeline. That other change addresses: An ML team reruns a pipeline against a mutable dataset without recording a snapshot and cannot explain different results between runs. It does not validate the specific Aster Pharma remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

A deliberately altered online scale fails the release gate and the correct transform passes. This is evidence for a different corrective change: Add automated train-serving feature parity checks using a shared golden fixture set as a release gate. That other change addresses: A deployed model's online preprocessing changes independently from training transformations and silently alters numeric feature scaling. It does not validate the specific Aster Pharma remediation for: A deployed model cannot be traced back to the source transformations because pipeline output records omit component-level metadata. The necessary check instead is: An auditor can traverse from a serving model version to input dataset and execution IDs without missing links.

Apply versioned schema checks and fail fast on incompatible field changes before feature materialization. This action could be suitable for a different engineering incident: A data provider renames a key field and the pipeline substitutes empty strings, silently changing all model input features. It does not directly correct the reported Brookfield Credit Union failure: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The discriminating acceptance check here is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.

Persist validated intermediate artifacts and allow safe resume from completed pipeline stages. This action could be suitable for a different engineering incident: A long multi-stage training job loses all intermediate work when a downstream stage fails just before deployment. It does not directly correct the reported Brookfield Credit Union failure: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The discriminating acceptance check here is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.

Add a controlled manual approval step after automated evidence collection and before production promotion. This action could be suitable for a different engineering incident: A sensitive-risk model is automatically deployed after evaluation even though an accountable human sign-off is required. It does not directly correct the reported Brookfield Credit Union failure: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The discriminating acceptance check here is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.

A passing but unapproved model remains nonproduction; approved promotion records the reviewer and artifact hash. This is evidence for a different corrective change: Add a controlled manual approval step after automated evidence collection and before production promotion. That other change addresses: A sensitive-risk model is automatically deployed after evaluation even though an accountable human sign-off is required. It does not validate the specific Brookfield Credit Union remediation for: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The necessary check instead is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.

A simulated late failure resumes from a completed checkpoint without repeating successful expensive stages. This is evidence for a different corrective change: Persist validated intermediate artifacts and allow safe resume from completed pipeline stages. That other change addresses: A long multi-stage training job loses all intermediate work when a downstream stage fails just before deployment. It does not validate the specific Brookfield Credit Union remediation for: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The necessary check instead is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.

A synthetic renamed field is quarantined and the registered training schema stays intact. This is evidence for a different corrective change: Apply versioned schema checks and fail fast on incompatible field changes before feature materialization. That other change addresses: A data provider renames a key field and the pipeline substitutes empty strings, silently changing all model input features. It does not validate the specific Brookfield Credit Union remediation for: An online fraud model receives raw categories but the training DAG applied a different tokenizer hidden inside a notebook. The necessary check instead is: Identical raw fixtures produce matching transformed features in both paths and automated parity tests pass.