Exam Bundle

The silver output excludes the rejected rows while pipeline proceeds would demonstrate the separate action Use `ON VIOLATION DROP ROW` or an equivalent supported expectation setting, which addresses “A valid silver table should omit rows that fail a noncritical quality predicate.” It does not verify the requirement “An expectation is misconfigured to reject legal nullable optional fields” following Restrict the predicate to required columns per the data contract.

The expectation violation count rises while raw records stay available would demonstrate the separate action Use a warning expectation and retain the raw rows, which addresses “All failing records should be counted but retained in a diagnostic bronze target.” It does not verify the requirement “An expectation is misconfigured to reject legal nullable optional fields” following Restrict the predicate to required columns per the data contract.

The update stops with the named expectation failure pertains to a different control (Use `ON VIOLATION FAIL UPDATE` or equivalent strict expectation) and a different need (A critical primary-key validation must stop the entire pipeline on failure). It cannot establish that Restrict the predicate to required columns per the data contract met the stated goal.

Use an appropriate DECIMAL precision and scale is appropriate when “A decimal calculation needs fixed financial precision rather than binary floating-point drift”; it would be verified by Summed sample transactions match exact expected cent values. It does not directly satisfy “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch,” whose relevant acceptance evidence is Invalid input becomes null and is counted as a conversion failure.

This action solves a different issue: “Critical currency values must reject malformed numeric input rather than silently become zero.” Its normal signal is Invalid monetary values are rejected with explicit evidence. Here the requested behavior is “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch,” so that signal is not sufficient.

This action solves a different issue: “Product IDs contain meaningful leading zeroes and must not be normalized to integers.” Its normal signal is The curated ID preserves prefixes and leading zero digits. Here the requested behavior is “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch,” so that signal is not sufficient.

A test spanning daylight-saving transition maps to the correct UTC instant pertains to a different control (Parse timestamps with the declared source time zone and normalize to UTC) and a different need (Event timestamps need a consistent UTC interpretation before time-window aggregation). It cannot establish that Use `TRY_CAST` with downstream null or error handling met the stated goal.

This signal belongs to the adjacent case “A decimal calculation needs fixed financial precision rather than binary floating-point drift,” whose remedy is Use an appropriate DECIMAL precision and scale. The observed result for the present requirement is Invalid input becomes null and is counted as a conversion failure.

The curated ID preserves prefixes and leading zero digits pertains to a different control (Store and transform the identifier as STRING) and a different need (Product IDs contain meaningful leading zeroes and must not be normalized to integers). It cannot establish that Use `TRY_CAST` with downstream null or error handling met the stated goal.

The alternative Use an appropriate DECIMAL precision and scale has a distinct purpose—A decimal calculation needs fixed financial precision rather than binary floating-point drift. It would not establish the required outcome (Critical currency values must reject malformed numeric input rather than silently become zero); the necessary verification concerns Invalid monetary values are rejected with explicit evidence.

This action solves a different issue: “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch.” Its normal signal is Invalid input becomes null and is counted as a conversion failure. Here the requested behavior is “Critical currency values must reject malformed numeric input rather than silently become zero,” so that signal is not sufficient.

The alternative Store and transform the identifier as STRING has a distinct purpose—Product IDs contain meaningful leading zeroes and must not be normalized to integers. It would not establish the required outcome (Critical currency values must reject malformed numeric input rather than silently become zero); the necessary verification concerns Invalid monetary values are rejected with explicit evidence.

The curated ID preserves prefixes and leading zero digits would demonstrate the separate action Store and transform the identifier as STRING, which addresses “Product IDs contain meaningful leading zeroes and must not be normalized to integers.” It does not verify the requirement “Critical currency values must reject malformed numeric input rather than silently become zero” following Apply strict cast validation and route invalid records to a failure path.

This signal belongs to the adjacent case “A decimal calculation needs fixed financial precision rather than binary floating-point drift,” whose remedy is Use an appropriate DECIMAL precision and scale. The observed result for the present requirement is Invalid monetary values are rejected with explicit evidence.

A test spanning daylight-saving transition maps to the correct UTC instant would demonstrate the separate action Parse timestamps with the declared source time zone and normalize to UTC, which addresses “Event timestamps need a consistent UTC interpretation before time-window aggregation.” It does not verify the requirement “Critical currency values must reject malformed numeric input rather than silently become zero” following Apply strict cast validation and route invalid records to a failure path.

This action solves a different issue: “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch.” Its normal signal is Invalid input becomes null and is counted as a conversion failure. Here the requested behavior is “Event timestamps need a consistent UTC interpretation before time-window aggregation,” so that signal is not sufficient.

Store and transform the identifier as STRING is appropriate when “Product IDs contain meaningful leading zeroes and must not be normalized to integers”; it would be verified by The curated ID preserves prefixes and leading zero digits. It does not directly satisfy “Event timestamps need a consistent UTC interpretation before time-window aggregation,” whose relevant acceptance evidence is A test spanning daylight-saving transition maps to the correct UTC instant.

Apply strict cast validation and route invalid records to a failure path is appropriate when “Critical currency values must reject malformed numeric input rather than silently become zero”; it would be verified by Invalid monetary values are rejected with explicit evidence. It does not directly satisfy “Event timestamps need a consistent UTC interpretation before time-window aggregation,” whose relevant acceptance evidence is A test spanning daylight-saving transition maps to the correct UTC instant.

That observation is a valid indicator for “Critical currency values must reject malformed numeric input rather than silently become zero” when using Apply strict cast validation and route invalid records to a failure path. The scenario instead tests “Event timestamps need a consistent UTC interpretation before time-window aggregation”; the relevant result is A test spanning daylight-saving transition maps to the correct UTC instant.

This signal belongs to the adjacent case “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch,” whose remedy is Use `TRY_CAST` with downstream null or error handling. The observed result for the present requirement is A test spanning daylight-saving transition maps to the correct UTC instant.

This signal belongs to the adjacent case “Product IDs contain meaningful leading zeroes and must not be normalized to integers,” whose remedy is Store and transform the identifier as STRING. The observed result for the present requirement is A test spanning daylight-saving transition maps to the correct UTC instant.

The alternative Apply strict cast validation and route invalid records to a failure path has a distinct purpose—Critical currency values must reject malformed numeric input rather than silently become zero. It would not establish the required outcome (A decimal calculation needs fixed financial precision rather than binary floating-point drift); the necessary verification concerns Summed sample transactions match exact expected cent values.

Use `TRY_CAST` with downstream null or error handling belongs to the separate case “An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch,” where Invalid input becomes null and is counted as a conversion failure would be expected. That differs from the condition in this stem: “A decimal calculation needs fixed financial precision rather than binary floating-point drift.”

Store and transform the identifier as STRING is appropriate when “Product IDs contain meaningful leading zeroes and must not be normalized to integers”; it would be verified by The curated ID preserves prefixes and leading zero digits. It does not directly satisfy “A decimal calculation needs fixed financial precision rather than binary floating-point drift,” whose relevant acceptance evidence is Summed sample transactions match exact expected cent values.

That observation is a valid indicator for “Critical currency values must reject malformed numeric input rather than silently become zero” when using Apply strict cast validation and route invalid records to a failure path. The scenario instead tests “A decimal calculation needs fixed financial precision rather than binary floating-point drift”; the relevant result is Summed sample transactions match exact expected cent values.

Invalid input becomes null and is counted as a conversion failure pertains to a different control (Use `TRY_CAST` with downstream null or error handling) and a different need (An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch). It cannot establish that Use an appropriate DECIMAL precision and scale met the stated goal.

That observation is a valid indicator for “Product IDs contain meaningful leading zeroes and must not be normalized to integers” when using Store and transform the identifier as STRING. The scenario instead tests “A decimal calculation needs fixed financial precision rather than binary floating-point drift”; the relevant result is Summed sample transactions match exact expected cent values.

Use an appropriate DECIMAL precision and scale is appropriate when “A decimal calculation needs fixed financial precision rather than binary floating-point drift”; it would be verified by Summed sample transactions match exact expected cent values. It does not directly satisfy “Product IDs contain meaningful leading zeroes and must not be normalized to integers,” whose relevant acceptance evidence is The curated ID preserves prefixes and leading zero digits.

The alternative Use `TRY_CAST` with downstream null or error handling has a distinct purpose—An untrusted numeric string could contain invalid text and should not abort an entire exploratory batch. It would not establish the required outcome (Product IDs contain meaningful leading zeroes and must not be normalized to integers); the necessary verification concerns The curated ID preserves prefixes and leading zero digits.

Parse timestamps with the declared source time zone and normalize to UTC is appropriate when “Event timestamps need a consistent UTC interpretation before time-window aggregation”; it would be verified by A test spanning daylight-saving transition maps to the correct UTC instant. It does not directly satisfy “Product IDs contain meaningful leading zeroes and must not be normalized to integers,” whose relevant acceptance evidence is The curated ID preserves prefixes and leading zero digits.

A test spanning daylight-saving transition maps to the correct UTC instant pertains to a different control (Parse timestamps with the declared source time zone and normalize to UTC) and a different need (Event timestamps need a consistent UTC interpretation before time-window aggregation). It cannot establish that Store and transform the identifier as STRING met the stated goal.

That observation is a valid indicator for “Critical currency values must reject malformed numeric input rather than silently become zero” when using Apply strict cast validation and route invalid records to a failure path. The scenario instead tests “Product IDs contain meaningful leading zeroes and must not be normalized to integers”; the relevant result is The curated ID preserves prefixes and leading zero digits.

This signal belongs to the adjacent case “A decimal calculation needs fixed financial precision rather than binary floating-point drift,” whose remedy is Use an appropriate DECIMAL precision and scale. The observed result for the present requirement is The curated ID preserves prefixes and leading zero digits.