Exam Bundle

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.

Apply a supported certification/quality signal after governance review is appropriate when “A dataset should be marked as validated for enterprise reuse”; it would be verified by Discoverability surfaces show the asset's approved trusted status. It does not directly satisfy “Different departments calculate net revenue using inconsistent formulas,” whose relevant acceptance evidence is Independent consumers return the same metric for equivalent filters.

The alternative Publish clear metric definitions and source lineage in the catalog has a distinct purpose—A key business metric is built from undocumented source columns. It would not establish the required outcome (Different departments calculate net revenue using inconsistent formulas); the necessary verification concerns Independent consumers return the same metric for equivalent filters.

This action solves a different issue: “An outdated table should no longer be suggested for new reports.” Its normal signal is Catalog discovery indicates the table is retired. Here the requested behavior is “Different departments calculate net revenue using inconsistent formulas,” so that signal is not sufficient.

Owners can verify both documented retention and actual cleanup jobs would demonstrate the separate action Record and enforce the approved retention and lifecycle metadata, which addresses “An audit requires a documented retention policy for a catalog table.” It does not verify the requirement “Different departments calculate net revenue using inconsistent formulas” following Define an authoritative reusable metric view with the approved expression.

That observation is a valid indicator for “An outdated table should no longer be suggested for new reports” when using Mark the object as deprecated and point users to replacement data. The scenario instead tests “Different departments calculate net revenue using inconsistent formulas”; the relevant result is Independent consumers return the same metric for equivalent filters.

Users can inspect the formula, source and business description would demonstrate the separate action Publish clear metric definitions and source lineage in the catalog, which addresses “A key business metric is built from undocumented source columns.” It does not verify the requirement “Different departments calculate net revenue using inconsistent formulas” following Define an authoritative reusable metric view with the approved expression.

Define an authoritative reusable metric view with the approved expression belongs to the separate case “Different departments calculate net revenue using inconsistent formulas,” where Independent consumers return the same metric for equivalent filters would be expected. That differs from the condition in this stem: “A key business metric is built from undocumented source columns.”

Apply a supported certification/quality signal after governance review belongs to the separate case “A dataset should be marked as validated for enterprise reuse,” where Discoverability surfaces show the asset's approved trusted status would be expected. That differs from the condition in this stem: “A key business metric is built from undocumented source columns.”

The alternative Record and enforce the approved retention and lifecycle metadata has a distinct purpose—An audit requires a documented retention policy for a catalog table. It would not establish the required outcome (A key business metric is built from undocumented source columns); the necessary verification concerns Users can inspect the formula, source and business description.

This signal belongs to the adjacent case “A dataset should be marked as validated for enterprise reuse,” whose remedy is Apply a supported certification/quality signal after governance review. The observed result for the present requirement is Users can inspect the formula, source and business description.

Independent consumers return the same metric for equivalent filters would demonstrate the separate action Define an authoritative reusable metric view with the approved expression, which addresses “Different departments calculate net revenue using inconsistent formulas.” It does not verify the requirement “A key business metric is built from undocumented source columns” following Publish clear metric definitions and source lineage in the catalog.

Owners can verify both documented retention and actual cleanup jobs pertains to a different control (Record and enforce the approved retention and lifecycle metadata) and a different need (An audit requires a documented retention policy for a catalog table). It cannot establish that Publish clear metric definitions and source lineage in the catalog met the stated goal.

The alternative Record and enforce the approved retention and lifecycle metadata has a distinct purpose—An audit requires a documented retention policy for a catalog table. It would not establish the required outcome (A dataset should be marked as validated for enterprise reuse); the necessary verification concerns Discoverability surfaces show the asset's approved trusted status.

This action solves a different issue: “Different departments calculate net revenue using inconsistent formulas.” Its normal signal is Independent consumers return the same metric for equivalent filters. Here the requested behavior is “A dataset should be marked as validated for enterprise reuse,” so that signal is not sufficient.

Mark the object as deprecated and point users to replacement data is appropriate when “An outdated table should no longer be suggested for new reports”; it would be verified by Catalog discovery indicates the table is retired. It does not directly satisfy “A dataset should be marked as validated for enterprise reuse,” whose relevant acceptance evidence is Discoverability surfaces show the asset's approved trusted status.

Owners can verify both documented retention and actual cleanup jobs pertains to a different control (Record and enforce the approved retention and lifecycle metadata) and a different need (An audit requires a documented retention policy for a catalog table). It cannot establish that Apply a supported certification/quality signal after governance review met the stated goal.

This signal belongs to the adjacent case “A key business metric is built from undocumented source columns,” whose remedy is Publish clear metric definitions and source lineage in the catalog. The observed result for the present requirement is Discoverability surfaces show the asset's approved trusted status.

This signal belongs to the adjacent case “Different departments calculate net revenue using inconsistent formulas,” whose remedy is Define an authoritative reusable metric view with the approved expression. The observed result for the present requirement is Discoverability surfaces show the asset's approved trusted status.

Publish clear metric definitions and source lineage in the catalog belongs to the separate case “A key business metric is built from undocumented source columns,” where Users can inspect the formula, source and business description would be expected. That differs from the condition in this stem: “An outdated table should no longer be suggested for new reports.”

The alternative Define an authoritative reusable metric view with the approved expression has a distinct purpose—Different departments calculate net revenue using inconsistent formulas. It would not establish the required outcome (An outdated table should no longer be suggested for new reports); the necessary verification concerns Catalog discovery indicates the table is retired.

Apply a supported certification/quality signal after governance review belongs to the separate case “A dataset should be marked as validated for enterprise reuse,” where Discoverability surfaces show the asset's approved trusted status would be expected. That differs from the condition in this stem: “An outdated table should no longer be suggested for new reports.”

This signal belongs to the adjacent case “A dataset should be marked as validated for enterprise reuse,” whose remedy is Apply a supported certification/quality signal after governance review. The observed result for the present requirement is Catalog discovery indicates the table is retired.

Owners can verify both documented retention and actual cleanup jobs pertains to a different control (Record and enforce the approved retention and lifecycle metadata) and a different need (An audit requires a documented retention policy for a catalog table). It cannot establish that Mark the object as deprecated and point users to replacement data met the stated goal.

Independent consumers return the same metric for equivalent filters would demonstrate the separate action Define an authoritative reusable metric view with the approved expression, which addresses “Different departments calculate net revenue using inconsistent formulas.” It does not verify the requirement “An outdated table should no longer be suggested for new reports” following Mark the object as deprecated and point users to replacement data.

Publish clear metric definitions and source lineage in the catalog is appropriate when “A key business metric is built from undocumented source columns”; it would be verified by Users can inspect the formula, source and business description. It does not directly satisfy “An audit requires a documented retention policy for a catalog table,” whose relevant acceptance evidence is Owners can verify both documented retention and actual cleanup jobs.

The alternative Mark the object as deprecated and point users to replacement data has a distinct purpose—An outdated table should no longer be suggested for new reports. It would not establish the required outcome (An audit requires a documented retention policy for a catalog table); the necessary verification concerns Owners can verify both documented retention and actual cleanup jobs.

Apply a supported certification/quality signal after governance review is appropriate when “A dataset should be marked as validated for enterprise reuse”; it would be verified by Discoverability surfaces show the asset's approved trusted status. It does not directly satisfy “An audit requires a documented retention policy for a catalog table,” whose relevant acceptance evidence is Owners can verify both documented retention and actual cleanup jobs.

Discoverability surfaces show the asset's approved trusted status would demonstrate the separate action Apply a supported certification/quality signal after governance review, which addresses “A dataset should be marked as validated for enterprise reuse.” It does not verify the requirement “An audit requires a documented retention policy for a catalog table” following Record and enforce the approved retention and lifecycle metadata.

That observation is a valid indicator for “An outdated table should no longer be suggested for new reports” when using Mark the object as deprecated and point users to replacement data. The scenario instead tests “An audit requires a documented retention policy for a catalog table”; the relevant result is Owners can verify both documented retention and actual cleanup jobs.

That observation is a valid indicator for “Different departments calculate net revenue using inconsistent formulas” when using Define an authoritative reusable metric view with the approved expression. The scenario instead tests “An audit requires a documented retention policy for a catalog table”; the relevant result is Owners can verify both documented retention and actual cleanup jobs.