Exam Bundle

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.

This action solves a different issue: “A source table owner changes but permissions should remain explicit and traceable.” Its normal signal is New ownership and effective privileges match the approved policy. Here the requested behavior is “An external recipient should access only one approved aggregate table,” so that signal is not sufficient.

Revoke its share recipient credentials or share permissions belongs to the separate case “A former partner's sharing authorization expires,” where The partner's previous credential cannot read the dataset would be expected. That differs from the condition in this stem: “An external recipient should access only one approved aggregate table.”

The alternative Review and enforce an approved projection before sharing has a distinct purpose—A shared dataset contains a newly added sensitive column. It would not establish the required outcome (An external recipient should access only one approved aggregate table); the necessary verification concerns The recipient can query the permitted aggregate but not raw datasets.

The partner's previous credential cannot read the dataset pertains to a different control (Revoke its share recipient credentials or share permissions) and a different need (A former partner's sharing authorization expires). It cannot establish that Scope the Delta Sharing share to the explicitly authorized object met the stated goal.

That observation is a valid indicator for “A governance board wants a list of which recipients access a sensitive share” when using Review supported share/recipient metadata and audit events. The scenario instead tests “An external recipient should access only one approved aggregate table”; the relevant result is The recipient can query the permitted aggregate but not raw datasets.

New ownership and effective privileges match the approved policy would demonstrate the separate action Update appropriate UC ownership and grants through governed change control, which addresses “A source table owner changes but permissions should remain explicit and traceable.” It does not verify the requirement “An external recipient should access only one approved aggregate table” following Scope the Delta Sharing share to the explicitly authorized object.

Scope the Delta Sharing share to the explicitly authorized object is appropriate when “An external recipient should access only one approved aggregate table”; it would be verified by The recipient can query the permitted aggregate but not raw datasets. It does not directly satisfy “A former partner's sharing authorization expires,” whose relevant acceptance evidence is The partner's previous credential cannot read the dataset.

This action solves a different issue: “A source table owner changes but permissions should remain explicit and traceable.” Its normal signal is New ownership and effective privileges match the approved policy. Here the requested behavior is “A former partner's sharing authorization expires,” so that signal is not sufficient.

Review and enforce an approved projection before sharing is appropriate when “A shared dataset contains a newly added sensitive column”; it would be verified by The recipient-visible schema excludes the restricted attribute. It does not directly satisfy “A former partner's sharing authorization expires,” whose relevant acceptance evidence is The partner's previous credential cannot read the dataset.

The inventory identifies authorized recipients and relevant access history would demonstrate the separate action Review supported share/recipient metadata and audit events, which addresses “A governance board wants a list of which recipients access a sensitive share.” It does not verify the requirement “A former partner's sharing authorization expires” following Revoke its share recipient credentials or share permissions.

This signal belongs to the adjacent case “A shared dataset contains a newly added sensitive column,” whose remedy is Review and enforce an approved projection before sharing. The observed result for the present requirement is The partner's previous credential cannot read the dataset.

New ownership and effective privileges match the approved policy would demonstrate the separate action Update appropriate UC ownership and grants through governed change control, which addresses “A source table owner changes but permissions should remain explicit and traceable.” It does not verify the requirement “A former partner's sharing authorization expires” following Revoke its share recipient credentials or share permissions.

Scope the Delta Sharing share to the explicitly authorized object belongs to the separate case “An external recipient should access only one approved aggregate table,” where The recipient can query the permitted aggregate but not raw datasets would be expected. That differs from the condition in this stem: “A shared dataset contains a newly added sensitive column.”

This action solves a different issue: “A source table owner changes but permissions should remain explicit and traceable.” Its normal signal is New ownership and effective privileges match the approved policy. Here the requested behavior is “A shared dataset contains a newly added sensitive column,” so that signal is not sufficient.

This action solves a different issue: “A former partner's sharing authorization expires.” Its normal signal is The partner's previous credential cannot read the dataset. Here the requested behavior is “A shared dataset contains a newly added sensitive column,” so that signal is not sufficient.

That observation is a valid indicator for “A governance board wants a list of which recipients access a sensitive share” when using Review supported share/recipient metadata and audit events. The scenario instead tests “A shared dataset contains a newly added sensitive column”; the relevant result is The recipient-visible schema excludes the restricted attribute.

That observation is a valid indicator for “A source table owner changes but permissions should remain explicit and traceable” when using Update appropriate UC ownership and grants through governed change control. The scenario instead tests “A shared dataset contains a newly added sensitive column”; the relevant result is The recipient-visible schema excludes the restricted attribute.

The partner's previous credential cannot read the dataset pertains to a different control (Revoke its share recipient credentials or share permissions) and a different need (A former partner's sharing authorization expires). It cannot establish that Review and enforce an approved projection before sharing met the stated goal.

Review and enforce an approved projection before sharing belongs to the separate case “A shared dataset contains a newly added sensitive column,” where The recipient-visible schema excludes the restricted attribute would be expected. That differs from the condition in this stem: “A governance board wants a list of which recipients access a sensitive share.”

Update appropriate UC ownership and grants through governed change control is appropriate when “A source table owner changes but permissions should remain explicit and traceable”; it would be verified by New ownership and effective privileges match the approved policy. It does not directly satisfy “A governance board wants a list of which recipients access a sensitive share,” whose relevant acceptance evidence is The inventory identifies authorized recipients and relevant access history.

This action solves a different issue: “An external recipient should access only one approved aggregate table.” Its normal signal is The recipient can query the permitted aggregate but not raw datasets. Here the requested behavior is “A governance board wants a list of which recipients access a sensitive share,” so that signal is not sufficient.

This signal belongs to the adjacent case “An external recipient should access only one approved aggregate table,” whose remedy is Scope the Delta Sharing share to the explicitly authorized object. The observed result for the present requirement is The inventory identifies authorized recipients and relevant access history.

That observation is a valid indicator for “A source table owner changes but permissions should remain explicit and traceable” when using Update appropriate UC ownership and grants through governed change control. The scenario instead tests “A governance board wants a list of which recipients access a sensitive share”; the relevant result is The inventory identifies authorized recipients and relevant access history.

The recipient-visible schema excludes the restricted attribute would demonstrate the separate action Review and enforce an approved projection before sharing, which addresses “A shared dataset contains a newly added sensitive column.” It does not verify the requirement “A governance board wants a list of which recipients access a sensitive share” following Review supported share/recipient metadata and audit events.

Review supported share/recipient metadata and audit events belongs to the separate case “A governance board wants a list of which recipients access a sensitive share,” where The inventory identifies authorized recipients and relevant access history would be expected. That differs from the condition in this stem: “A source table owner changes but permissions should remain explicit and traceable.”

Scope the Delta Sharing share to the explicitly authorized object is appropriate when “An external recipient should access only one approved aggregate table”; it would be verified by The recipient can query the permitted aggregate but not raw datasets. It does not directly satisfy “A source table owner changes but permissions should remain explicit and traceable,” whose relevant acceptance evidence is New ownership and effective privileges match the approved policy.

Revoke its share recipient credentials or share permissions belongs to the separate case “A former partner's sharing authorization expires,” where The partner's previous credential cannot read the dataset would be expected. That differs from the condition in this stem: “A source table owner changes but permissions should remain explicit and traceable.”

The inventory identifies authorized recipients and relevant access history pertains to a different control (Review supported share/recipient metadata and audit events) and a different need (A governance board wants a list of which recipients access a sensitive share). It cannot establish that Update appropriate UC ownership and grants through governed change control met the stated goal.

That observation is a valid indicator for “A former partner's sharing authorization expires” when using Revoke its share recipient credentials or share permissions. The scenario instead tests “A source table owner changes but permissions should remain explicit and traceable”; the relevant result is New ownership and effective privileges match the approved policy.

That observation is a valid indicator for “An external recipient should access only one approved aggregate table” when using Scope the Delta Sharing share to the explicitly authorized object. The scenario instead tests “A source table owner changes but permissions should remain explicit and traceable”; the relevant result is New ownership and effective privileges match the approved policy.