Exam Bundle

That observation is a valid indicator for “New data assets must appear in searches for a recognized business domain” when using Apply appropriate business-domain naming, descriptions and tags. The scenario instead tests “Only a restricted stewardship group may modify governed tag definitions”; the relevant result is Unapproved users cannot change governed classification definitions.

This signal belongs to the adjacent case “Documentation differs between an old column name and current data contract,” whose remedy is Update column comments and schema documentation after review. The observed result for the present requirement is Unapproved users cannot change governed classification definitions.

Catalog Explorer displays the approved description and owner pertains to a different control (Add a meaningful table comment and owner metadata in Unity Catalog) and a different need (A critical table has no business description or owner documentation). It cannot establish that Set tag-governance permissions for the steward role met the stated goal.

This action solves a different issue: “A compliance team asks who created a derived customer metric and when it was modified.” Its normal signal is Documented ownership and change records identify responsible principals. Here the requested behavior is “Auditors ask which source tables feed a final customer lifetime value view,” so that signal is not sufficient.

Query or visualize downstream lineage from the source asset is appropriate when “A raw ingestion table is being replaced and owners must identify impacted reports”; it would be verified by The impact list includes dependent tables and reports. It does not directly satisfy “Auditors ask which source tables feed a final customer lifetime value view,” whose relevant acceptance evidence is Lineage links the final view to its upstream source tables.

This action solves a different issue: “An ETL transformation fails and an owner needs to identify its upstream data contract.” Its normal signal is The upstream asset and field contract associated with the transform are identified. Here the requested behavior is “Auditors ask which source tables feed a final customer lifetime value view,” so that signal is not sufficient.

Documented ownership and change records identify responsible principals would demonstrate the separate action Inspect UC object metadata and audit history as available, which addresses “A compliance team asks who created a derived customer metric and when it was modified.” It does not verify the requirement “Auditors ask which source tables feed a final customer lifetime value view” following Inspect Unity Catalog column/table lineage for the view.

The provenance chain shows the input and governed output dependency pertains to a different control (Inspect supported column-level lineage and associated policy metadata) and a different need (One column must be traced through a masked transformation into an aggregate). It cannot establish that Inspect Unity Catalog column/table lineage for the view met the stated goal.

That observation is a valid indicator for “An ETL transformation fails and an owner needs to identify its upstream data contract” when using Use lineage with source schema descriptions and pipeline metadata. The scenario instead tests “Auditors ask which source tables feed a final customer lifetime value view”; the relevant result is Lineage links the final view to its upstream source tables.

Inspect UC object metadata and audit history as available is appropriate when “A compliance team asks who created a derived customer metric and when it was modified”; it would be verified by Documented ownership and change records identify responsible principals. It does not directly satisfy “A raw ingestion table is being replaced and owners must identify impacted reports,” whose relevant acceptance evidence is The impact list includes dependent tables and reports.

This action solves a different issue: “One column must be traced through a masked transformation into an aggregate.” Its normal signal is The provenance chain shows the input and governed output dependency. Here the requested behavior is “A raw ingestion table is being replaced and owners must identify impacted reports,” so that signal is not sufficient.

This action solves a different issue: “Auditors ask which source tables feed a final customer lifetime value view.” Its normal signal is Lineage links the final view to its upstream source tables. Here the requested behavior is “A raw ingestion table is being replaced and owners must identify impacted reports,” so that signal is not sufficient.

This signal belongs to the adjacent case “A compliance team asks who created a derived customer metric and when it was modified,” whose remedy is Inspect UC object metadata and audit history as available. The observed result for the present requirement is The impact list includes dependent tables and reports.

That observation is a valid indicator for “An ETL transformation fails and an owner needs to identify its upstream data contract” when using Use lineage with source schema descriptions and pipeline metadata. The scenario instead tests “A raw ingestion table is being replaced and owners must identify impacted reports”; the relevant result is The impact list includes dependent tables and reports.

The provenance chain shows the input and governed output dependency pertains to a different control (Inspect supported column-level lineage and associated policy metadata) and a different need (One column must be traced through a masked transformation into an aggregate). It cannot establish that Query or visualize downstream lineage from the source asset met the stated goal.

Query or visualize downstream lineage from the source asset belongs to the separate case “A raw ingestion table is being replaced and owners must identify impacted reports,” where The impact list includes dependent tables and reports would be expected. That differs from the condition in this stem: “A compliance team asks who created a derived customer metric and when it was modified.”

The alternative Inspect Unity Catalog column/table lineage for the view has a distinct purpose—Auditors ask which source tables feed a final customer lifetime value view. It would not establish the required outcome (A compliance team asks who created a derived customer metric and when it was modified); the necessary verification concerns Documented ownership and change records identify responsible principals.

Use lineage with source schema descriptions and pipeline metadata belongs to the separate case “An ETL transformation fails and an owner needs to identify its upstream data contract,” where The upstream asset and field contract associated with the transform are identified would be expected. That differs from the condition in this stem: “A compliance team asks who created a derived customer metric and when it was modified.”

That observation is a valid indicator for “An ETL transformation fails and an owner needs to identify its upstream data contract” when using Use lineage with source schema descriptions and pipeline metadata. The scenario instead tests “A compliance team asks who created a derived customer metric and when it was modified”; the relevant result is Documented ownership and change records identify responsible principals.

This signal belongs to the adjacent case “Auditors ask which source tables feed a final customer lifetime value view,” whose remedy is Inspect Unity Catalog column/table lineage for the view. The observed result for the present requirement is Documented ownership and change records identify responsible principals.

This signal belongs to the adjacent case “A raw ingestion table is being replaced and owners must identify impacted reports,” whose remedy is Query or visualize downstream lineage from the source asset. The observed result for the present requirement is Documented ownership and change records identify responsible principals.

This action solves a different issue: “A compliance team asks who created a derived customer metric and when it was modified.” Its normal signal is Documented ownership and change records identify responsible principals. Here the requested behavior is “An ETL transformation fails and an owner needs to identify its upstream data contract,” so that signal is not sufficient.

Inspect Unity Catalog column/table lineage for the view is appropriate when “Auditors ask which source tables feed a final customer lifetime value view”; it would be verified by Lineage links the final view to its upstream source tables. It does not directly satisfy “An ETL transformation fails and an owner needs to identify its upstream data contract,” whose relevant acceptance evidence is The upstream asset and field contract associated with the transform are identified.

Inspect supported column-level lineage and associated policy metadata belongs to the separate case “One column must be traced through a masked transformation into an aggregate,” where The provenance chain shows the input and governed output dependency would be expected. That differs from the condition in this stem: “An ETL transformation fails and an owner needs to identify its upstream data contract.”

That observation is a valid indicator for “One column must be traced through a masked transformation into an aggregate” when using Inspect supported column-level lineage and associated policy metadata. The scenario instead tests “An ETL transformation fails and an owner needs to identify its upstream data contract”; the relevant result is The upstream asset and field contract associated with the transform are identified.

Lineage links the final view to its upstream source tables would demonstrate the separate action Inspect Unity Catalog column/table lineage for the view, which addresses “Auditors ask which source tables feed a final customer lifetime value view.” It does not verify the requirement “An ETL transformation fails and an owner needs to identify its upstream data contract” following Use lineage with source schema descriptions and pipeline metadata.

That observation is a valid indicator for “A raw ingestion table is being replaced and owners must identify impacted reports” when using Query or visualize downstream lineage from the source asset. The scenario instead tests “An ETL transformation fails and an owner needs to identify its upstream data contract”; the relevant result is The upstream asset and field contract associated with the transform are identified.

Query or visualize downstream lineage from the source asset belongs to the separate case “A raw ingestion table is being replaced and owners must identify impacted reports,” where The impact list includes dependent tables and reports would be expected. That differs from the condition in this stem: “One column must be traced through a masked transformation into an aggregate.”

The alternative Inspect UC object metadata and audit history as available has a distinct purpose—A compliance team asks who created a derived customer metric and when it was modified. It would not establish the required outcome (One column must be traced through a masked transformation into an aggregate); the necessary verification concerns The provenance chain shows the input and governed output dependency.

Use lineage with source schema descriptions and pipeline metadata belongs to the separate case “An ETL transformation fails and an owner needs to identify its upstream data contract,” where The upstream asset and field contract associated with the transform are identified would be expected. That differs from the condition in this stem: “One column must be traced through a masked transformation into an aggregate.”

Lineage links the final view to its upstream source tables would demonstrate the separate action Inspect Unity Catalog column/table lineage for the view, which addresses “Auditors ask which source tables feed a final customer lifetime value view.” It does not verify the requirement “One column must be traced through a masked transformation into an aggregate” following Inspect supported column-level lineage and associated policy metadata.

The impact list includes dependent tables and reports pertains to a different control (Query or visualize downstream lineage from the source asset) and a different need (A raw ingestion table is being replaced and owners must identify impacted reports). It cannot establish that Inspect supported column-level lineage and associated policy metadata met the stated goal.

That observation is a valid indicator for “A compliance team asks who created a derived customer metric and when it was modified” when using Inspect UC object metadata and audit history as available. The scenario instead tests “One column must be traced through a masked transformation into an aggregate”; the relevant result is The provenance chain shows the input and governed output dependency.