Exam Bundle

That observation is a valid indicator for “A table is optimized for selective queries on high-cardinality fields” when using Use supported liquid clustering for the eligible managed table. The scenario instead tests “A consumer reports unsupported table protocol features after a writer upgrade”; the relevant result is The consumer successfully loads the table's current protocol.

That observation is a valid indicator for “A primary Databricks pipeline needs ACID transactions and Delta features” when using Use a supported Delta table for the curated dataset. The scenario instead tests “A consumer reports unsupported table protocol features after a writer upgrade”; the relevant result is The consumer successfully loads the table's current protocol.

The partner's supported Iceberg reader discovers and queries the expected snapshot pertains to a different control (Use a supported Iceberg table or interoperable format layout for the shared workload) and a different need (An external partner needs Iceberg-compatible open table metadata). It cannot establish that Choose a compatible reader/runtime or a supported migration approach 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 “Teams calculate conversion rate differently and need a central metric formula,” whose relevant acceptance evidence is Different dashboards return the same conversion rate for matching filters.

Define reusable measures and dimensions in a UC metric view is appropriate when “Analysts must group one standardized measure by many different dimensions”; it would be verified by A query groups the same measure by region and product without rewriting the formula. It does not directly satisfy “Teams calculate conversion rate differently and need a central metric formula,” whose relevant acceptance evidence is Different dashboards return the same conversion rate for matching filters.

This action solves a different issue: “A metric view's definitions no longer align with approved financial formulas.” Its normal signal is Every referenced KPI equals the approved reference calculation. Here the requested behavior is “Teams calculate conversion rate differently and need a central metric formula,” so that signal is not sufficient.

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 Different dashboards return the same conversion rate for matching filters.

This signal belongs to the adjacent case “A metric view's definitions no longer align with approved financial formulas,” whose remedy is Version and retest the governed measure expressions against known fixtures. The observed result for the present requirement is Different dashboards return the same conversion rate for matching filters.

Finance queries succeed while unauthorized principals are denied pertains to a different control (Apply UC privileges to the metric view and underlying governance) and a different need (Only finance analysts may access sensitive revenue measures). It cannot establish that Create a Unity Catalog metric view with governed measure definitions met the stated goal.

Update the governed metric view and validate dependent consumers is appropriate when “A metric definition is corrected and all reports should reference the new version”; it would be verified by Reports using the view return the revised consistent business metric. It does not directly satisfy “Analysts must group one standardized measure by many different dimensions,” whose relevant acceptance evidence is A query groups the same measure by region and product without rewriting the formula.

This action solves a different issue: “A metric view's definitions no longer align with approved financial formulas.” Its normal signal is Every referenced KPI equals the approved reference calculation. Here the requested behavior is “Analysts must group one standardized measure by many different dimensions,” so that signal is not sufficient.

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 “Analysts must group one standardized measure by many different dimensions,” so that signal is not sufficient.

An as-of fact join finds at most one dimension version per event time pertains to a different control (Validate and repair nonoverlapping effective-date ranges) and a different need (A dimension contains overlapping SCD2 validity intervals for the same natural key). It cannot establish that Define reusable measures and dimensions in a UC metric view met the stated goal.

That observation is a valid indicator for “A metric requires an approved aggregation over a source table without storing a copy for each grouping” when using Query the metric view's measure at runtime with selected dimensions. The scenario instead tests “Analysts must group one standardized measure by many different dimensions”; the relevant result is A query groups the same measure by region and product without rewriting the formula.

Queries group facts by the correct date, product and store attributes would demonstrate the separate action Build a sales fact table linked to conformed dimensions by surrogate keys, which addresses “Revenue should be analyzed by date, product and store using a stable relational model.” It does not verify the requirement “Analysts must group one standardized measure by many different dimensions” following Define reusable measures and dimensions in a UC metric view.

The alternative Define reusable measures and dimensions in a UC metric view has a distinct purpose—Analysts must group one standardized measure by many different dimensions. It would not establish the required outcome (A metric requires an approved aggregation over a source table without storing a copy for each grouping); the necessary verification concerns Computed totals reflect current source records for each grouping.

Create gold tables or metric views from validated silver data is appropriate when “Dashboards require stable business-level aggregate tables”; it would be verified by Gold totals reconcile to validated silver source measures. It does not directly satisfy “A metric requires an approved aggregation over a source table without storing a copy for each grouping,” whose relevant acceptance evidence is Computed totals reflect current source records for each grouping.

Version and retest the governed measure expressions against known fixtures is appropriate when “A metric view's definitions no longer align with approved financial formulas”; it would be verified by Every referenced KPI equals the approved reference calculation. It does not directly satisfy “A metric requires an approved aggregation over a source table without storing a copy for each grouping,” whose relevant acceptance evidence is Computed totals reflect current source records for each grouping.

Only the current corrected attribute is returned for the dimension key pertains to a different control (Use SCD Type 1 overwrite semantics for that attribute) and a different need (A corrected dimension description should replace prior text with no requirement for history). It cannot establish that Query the metric view's measure at runtime with selected dimensions met the stated goal.

A query groups the same measure by region and product without rewriting the formula would demonstrate the separate action Define reusable measures and dimensions in a UC metric view, which addresses “Analysts must group one standardized measure by many different dimensions.” It does not verify the requirement “A metric requires an approved aggregation over a source table without storing a copy for each grouping” following Query the metric view's measure at runtime with selected dimensions.

That observation is a valid indicator for “A metric view's definitions no longer align with approved financial formulas” when using Version and retest the governed measure expressions against known fixtures. The scenario instead tests “A metric requires an approved aggregation over a source table without storing a copy for each grouping”; the relevant result is Computed totals reflect current source records for each grouping.

Define reusable measures and dimensions in a UC metric view belongs to the separate case “Analysts must group one standardized measure by many different dimensions,” where A query groups the same measure by region and product without rewriting the formula would be expected. That differs from the condition in this stem: “Only finance analysts may access sensitive revenue measures.”

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 “Only finance analysts may access sensitive revenue measures,” so that signal is not sufficient.

Version and retest the governed measure expressions against known fixtures is appropriate when “A metric view's definitions no longer align with approved financial formulas”; it would be verified by Every referenced KPI equals the approved reference calculation. It does not directly satisfy “Only finance analysts may access sensitive revenue measures,” whose relevant acceptance evidence is Finance queries succeed while unauthorized principals are denied.

Queries group facts by the correct date, product and store attributes pertains to a different control (Build a sales fact table linked to conformed dimensions by surrogate keys) and a different need (Revenue should be analyzed by date, product and store using a stable relational model). It cannot establish that Apply UC privileges to the metric view and underlying governance met the stated goal.

Different dashboards return the same conversion rate for matching filters would demonstrate the separate action Create a Unity Catalog metric view with governed measure definitions, which addresses “Teams calculate conversion rate differently and need a central metric formula.” It does not verify the requirement “Only finance analysts may access sensitive revenue measures” following Apply UC privileges to the metric view and underlying governance.

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 Finance queries succeed while unauthorized principals are denied.

Version and retest the governed measure expressions against known fixtures is appropriate when “A metric view's definitions no longer align with approved financial formulas”; it would be verified by Every referenced KPI equals the approved reference calculation. It does not directly satisfy “A metric definition is corrected and all reports should reference the new version,” whose relevant acceptance evidence is Reports using the view return the revised consistent business metric.

This action solves a different issue: “A corrected dimension description should replace prior text with no requirement for history.” Its normal signal is Only the current corrected attribute is returned for the dimension key. Here the requested behavior is “A metric definition is corrected and all reports should reference the new version,” so that signal is not sufficient.

The alternative Define reusable measures and dimensions in a UC metric view has a distinct purpose—Analysts must group one standardized measure by many different dimensions. It would not establish the required outcome (A metric definition is corrected and all reports should reference the new version); the necessary verification concerns Reports using the view return the revised consistent business metric.

The consumer successfully loads the table's current protocol would demonstrate the separate action Choose a compatible reader/runtime or a supported migration approach, which addresses “A consumer reports unsupported table protocol features after a writer upgrade.” It does not verify the requirement “A metric definition is corrected and all reports should reference the new version” following Update the governed metric view and validate dependent consumers.

That observation is a valid indicator for “Analysts must group one standardized measure by many different dimensions” when using Define reusable measures and dimensions in a UC metric view. The scenario instead tests “A metric definition is corrected and all reports should reference the new version”; the relevant result is Reports using the view return the revised consistent business metric.

Every referenced KPI equals the approved reference calculation pertains to a different control (Version and retest the governed measure expressions against known fixtures) and a different need (A metric view's definitions no longer align with approved financial formulas). It cannot establish that Update the governed metric view and validate dependent consumers met the stated goal.