Exam Bundle

The transform runs and exact revenue sample results match pertains to a different control (Restore validated numeric typing and strict cast handling) and a different need (A nullable amount column was accidentally converted to string and subsequent SUM failed). It cannot establish that Compare against fixed baseline fixtures and revert unsafe transformation met the stated goal.

Gold latest event date matches the expected processing date would demonstrate the separate action Add the missing job dependency and a freshness assertion, which addresses “Data from yesterday appears in current dashboard due to missing upstream refresh dependency.” It does not verify the requirement “An optimization change altered numerical results unexpectedly” following Compare against fixed baseline fixtures and revert unsafe transformation.

That observation is a valid indicator for “Source rows are duplicated by retries and the gold SUM is too high” when using Deduplicate on business event ID before aggregation and repair affected periods. The scenario instead tests “An optimization change altered numerical results unexpectedly”; the relevant result is Regression tests confirm unchanged business measures after repair.

Keep curated schema contracts at the silver/gold boundary is appropriate when “A source schema changes and analysts must be protected from direct raw structure changes”; it would be verified by Published analytics schemas remain valid while raw inputs evolve. It does not directly satisfy “Raw source payloads must remain available for audit and reproducible reprocessing,” whose relevant acceptance evidence is A source event can be retrieved exactly from bronze after a silver reprocessing run.

Build a silver table with controlled schema, deduplication and quality rules is appropriate when “The platform needs conformed validated records for downstream reusable analytics”; it would be verified by The silver table passes agreed record-level business tests. It does not directly satisfy “Raw source payloads must remain available for audit and reproducible reprocessing,” whose relevant acceptance evidence is A source event can be retrieved exactly from bronze after a silver reprocessing run.

This action solves a different issue: “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs.” Its normal signal is Rebuilt gold matches reference metrics without re-ingesting source files. Here the requested behavior is “Raw source payloads must remain available for audit and reproducible reprocessing,” so that signal is not sufficient.

Gold totals reconcile to validated silver source measures pertains to a different control (Create gold tables or metric views from validated silver data) and a different need (Dashboards require stable business-level aggregate tables). It cannot establish that Persist source-accurate immutable or append-only bronze records with provenance met the stated goal.

Rebuilt gold matches reference metrics without re-ingesting source files would demonstrate the separate action Reprocess gold from retained validated silver and controlled transformations, which addresses “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs.” It does not verify the requirement “Raw source payloads must remain available for audit and reproducible reprocessing” following Persist source-accurate immutable or append-only bronze records with provenance.

Published analytics schemas remain valid while raw inputs evolve would demonstrate the separate action Keep curated schema contracts at the silver/gold boundary, which addresses “A source schema changes and analysts must be protected from direct raw structure changes.” It does not verify the requirement “Raw source payloads must remain available for audit and reproducible reprocessing” following Persist source-accurate immutable or append-only bronze records with provenance.

This action solves a different issue: “A source schema changes and analysts must be protected from direct raw structure changes.” Its normal signal is Published analytics schemas remain valid while raw inputs evolve. Here the requested behavior is “The platform needs conformed validated records for downstream reusable analytics,” so that signal is not sufficient.

The alternative Create gold tables or metric views from validated silver data has a distinct purpose—Dashboards require stable business-level aggregate tables. It would not establish the required outcome (The platform needs conformed validated records for downstream reusable analytics); the necessary verification concerns The silver table passes agreed record-level business tests.

The alternative Persist source-accurate immutable or append-only bronze records with provenance has a distinct purpose—Raw source payloads must remain available for audit and reproducible reprocessing. It would not establish the required outcome (The platform needs conformed validated records for downstream reusable analytics); the necessary verification concerns The silver table passes agreed record-level business tests.

This signal belongs to the adjacent case “Raw source payloads must remain available for audit and reproducible reprocessing,” whose remedy is Persist source-accurate immutable or append-only bronze records with provenance. The observed result for the present requirement is The silver table passes agreed record-level business tests.

That observation is a valid indicator for “Dashboards require stable business-level aggregate tables” when using Create gold tables or metric views from validated silver data. The scenario instead tests “The platform needs conformed validated records for downstream reusable analytics”; the relevant result is The silver table passes agreed record-level business tests.

This signal belongs to the adjacent case “A source schema changes and analysts must be protected from direct raw structure changes,” whose remedy is Keep curated schema contracts at the silver/gold boundary. The observed result for the present requirement is The silver table passes agreed record-level business tests.

The alternative Keep curated schema contracts at the silver/gold boundary has a distinct purpose—A source schema changes and analysts must be protected from direct raw structure changes. It would not establish the required outcome (Dashboards require stable business-level aggregate tables); the necessary verification concerns Gold totals reconcile to validated silver source measures.

Persist source-accurate immutable or append-only bronze records with provenance belongs to the separate case “Raw source payloads must remain available for audit and reproducible reprocessing,” where A source event can be retrieved exactly from bronze after a silver reprocessing run would be expected. That differs from the condition in this stem: “Dashboards require stable business-level aggregate tables.”

The alternative Build a silver table with controlled schema, deduplication and quality rules has a distinct purpose—The platform needs conformed validated records for downstream reusable analytics. It would not establish the required outcome (Dashboards require stable business-level aggregate tables); the necessary verification concerns Gold totals reconcile to validated silver source measures.

This signal belongs to the adjacent case “Raw source payloads must remain available for audit and reproducible reprocessing,” whose remedy is Persist source-accurate immutable or append-only bronze records with provenance. The observed result for the present requirement is Gold totals reconcile to validated silver source measures.

This signal belongs to the adjacent case “The platform needs conformed validated records for downstream reusable analytics,” whose remedy is Build a silver table with controlled schema, deduplication and quality rules. The observed result for the present requirement is Gold totals reconcile to validated silver source measures.

This signal belongs to the adjacent case “A source schema changes and analysts must be protected from direct raw structure changes,” whose remedy is Keep curated schema contracts at the silver/gold boundary. The observed result for the present requirement is Gold totals reconcile to validated silver source measures.

The alternative Persist source-accurate immutable or append-only bronze records with provenance has a distinct purpose—Raw source payloads must remain available for audit and reproducible reprocessing. It would not establish the required outcome (A source schema changes and analysts must be protected from direct raw structure changes); the necessary verification concerns Published analytics schemas remain valid while raw inputs evolve.

Reprocess gold from retained validated silver and controlled transformations is appropriate when “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs”; it would be verified by Rebuilt gold matches reference metrics without re-ingesting source files. It does not directly satisfy “A source schema changes and analysts must be protected from direct raw structure changes,” whose relevant acceptance evidence is Published analytics schemas remain valid while raw inputs evolve.

The alternative Create gold tables or metric views from validated silver data has a distinct purpose—Dashboards require stable business-level aggregate tables. It would not establish the required outcome (A source schema changes and analysts must be protected from direct raw structure changes); the necessary verification concerns Published analytics schemas remain valid while raw inputs evolve.

That observation is a valid indicator for “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs” when using Reprocess gold from retained validated silver and controlled transformations. The scenario instead tests “A source schema changes and analysts must be protected from direct raw structure changes”; the relevant result is Published analytics schemas remain valid while raw inputs evolve.

That observation is a valid indicator for “The platform needs conformed validated records for downstream reusable analytics” when using Build a silver table with controlled schema, deduplication and quality rules. The scenario instead tests “A source schema changes and analysts must be protected from direct raw structure changes”; the relevant result is Published analytics schemas remain valid while raw inputs evolve.

A source event can be retrieved exactly from bronze after a silver reprocessing run pertains to a different control (Persist source-accurate immutable or append-only bronze records with provenance) and a different need (Raw source payloads must remain available for audit and reproducible reprocessing). It cannot establish that Keep curated schema contracts at the silver/gold boundary met the stated goal.

Keep curated schema contracts at the silver/gold boundary is appropriate when “A source schema changes and analysts must be protected from direct raw structure changes”; it would be verified by Published analytics schemas remain valid while raw inputs evolve. It does not directly satisfy “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs,” whose relevant acceptance evidence is Rebuilt gold matches reference metrics without re-ingesting source files.

Persist source-accurate immutable or append-only bronze records with provenance belongs to the separate case “Raw source payloads must remain available for audit and reproducible reprocessing,” where A source event can be retrieved exactly from bronze after a silver reprocessing run would be expected. That differs from the condition in this stem: “A pipeline defect is discovered in gold logic and the team needs to rebuild outputs.”

The alternative Build a silver table with controlled schema, deduplication and quality rules has a distinct purpose—The platform needs conformed validated records for downstream reusable analytics. It would not establish the required outcome (A pipeline defect is discovered in gold logic and the team needs to rebuild outputs); the necessary verification concerns Rebuilt gold matches reference metrics without re-ingesting source files.

Published analytics schemas remain valid while raw inputs evolve pertains to a different control (Keep curated schema contracts at the silver/gold boundary) and a different need (A source schema changes and analysts must be protected from direct raw structure changes). It cannot establish that Reprocess gold from retained validated silver and controlled transformations met the stated goal.

This signal belongs to the adjacent case “Dashboards require stable business-level aggregate tables,” whose remedy is Create gold tables or metric views from validated silver data. The observed result for the present requirement is Rebuilt gold matches reference metrics without re-ingesting source files.

A source event can be retrieved exactly from bronze after a silver reprocessing run pertains to a different control (Persist source-accurate immutable or append-only bronze records with provenance) and a different need (Raw source payloads must remain available for audit and reproducible reprocessing). It cannot establish that Reprocess gold from retained validated silver and controlled transformations met the stated goal.