Exam Bundle

This signal belongs to the adjacent case “A partner runs non-Databricks compute and needs open-protocol access,” whose remedy is Use Delta Sharing open sharing with appropriate recipient credentials. The observed result for the present requirement is Old credential use fails while replacement authorized access succeeds.

This signal belongs to the adjacent case “A recipient also uses Databricks with compatible Unity Catalog sharing,” whose remedy is Use Databricks-to-Databricks sharing for the authorized recipient. The observed result for the present requirement is Old credential use fails while replacement authorized access succeeds.

The recipient sees authorized data objects but not unrelated workspace files would demonstrate the separate action Grant share access only to the intended tables or views, which addresses “An owner wants to share selected curated objects while keeping source notebooks private.” It does not verify the requirement “A recipient's token was leaked and all data access from that credential must stop” following Rotate or revoke the recipient's open sharing credentials.

The alternative Refresh the supported foreign catalog metadata or mappings has a distinct purpose—A foreign schema evolves and analysts cannot see a new remote column. It would not establish the required outcome (Analysts must query an external supported database without first copying it into Databricks); the necessary verification concerns A governed query joins a foreign table with local data.

Materialize selected data into Delta when latency and egress make federation inefficient belongs to the separate case “A frequently accessed large foreign table causes slow queries across the network,” where Repeated local analytical queries run without remote full scans would be expected. That differs from the condition in this stem: “Analysts must query an external supported database without first copying it into Databricks.”

Store connection credentials in a governed UC connection is appropriate when “The external database credentials must not be embedded inside analysis notebooks”; it would be verified by Analysts query the foreign catalog using delegated privileges. It does not directly satisfy “Analysts must query an external supported database without first copying it into Databricks,” whose relevant acceptance evidence is A governed query joins a foreign table with local data.

Analysts query the foreign catalog using delegated privileges pertains to a different control (Store connection credentials in a governed UC connection) and a different need (The external database credentials must not be embedded inside analysis notebooks). It cannot establish that Create a Unity Catalog Lakehouse Federation connection and foreign catalog met the stated goal.

The foreign table displays the expected new column after refresh would demonstrate the separate action Refresh the supported foreign catalog metadata or mappings, which addresses “A foreign schema evolves and analysts cannot see a new remote column.” It does not verify the requirement “Analysts must query an external supported database without first copying it into Databricks” following Create a Unity Catalog Lakehouse Federation connection and foreign catalog.

Repeated local analytical queries run without remote full scans pertains to a different control (Materialize selected data into Delta when latency and egress make federation inefficient) and a different need (A frequently accessed large foreign table causes slow queries across the network). It cannot establish that Create a Unity Catalog Lakehouse Federation connection and foreign catalog met the stated goal.

Create a Unity Catalog Lakehouse Federation connection and foreign catalog belongs to the separate case “Analysts must query an external supported database without first copying it into Databricks,” where A governed query joins a foreign table with local data would be expected. That differs from the condition in this stem: “The external database credentials must not be embedded inside analysis notebooks.”

This action solves a different issue: “A frequently accessed large foreign table causes slow queries across the network.” Its normal signal is Repeated local analytical queries run without remote full scans. Here the requested behavior is “The external database credentials must not be embedded inside analysis notebooks,” so that signal is not sufficient.

Refresh the supported foreign catalog metadata or mappings is appropriate when “A foreign schema evolves and analysts cannot see a new remote column”; it would be verified by The foreign table displays the expected new column after refresh. It does not directly satisfy “The external database credentials must not be embedded inside analysis notebooks,” whose relevant acceptance evidence is Analysts query the foreign catalog using delegated privileges.

This signal belongs to the adjacent case “Only a subset of analysts may query a connected external finance database,” whose remedy is Apply least-privilege UC grants on the connection/foreign objects. The observed result for the present requirement is Analysts query the foreign catalog using delegated privileges.

A governed query joins a foreign table with local data pertains to a different control (Create a Unity Catalog Lakehouse Federation connection and foreign catalog) and a different need (Analysts must query an external supported database without first copying it into Databricks). It cannot establish that Store connection credentials in a governed UC connection met the stated goal.

That observation is a valid indicator for “A frequently accessed large foreign table causes slow queries across the network” when using Materialize selected data into Delta when latency and egress make federation inefficient. The scenario instead tests “The external database credentials must not be embedded inside analysis notebooks”; the relevant result is Analysts query the foreign catalog using delegated privileges.

Store connection credentials in a governed UC connection is appropriate when “The external database credentials must not be embedded inside analysis notebooks”; it would be verified by Analysts query the foreign catalog using delegated privileges. It does not directly satisfy “A frequently accessed large foreign table causes slow queries across the network,” whose relevant acceptance evidence is Repeated local analytical queries run without remote full scans.

This action solves a different issue: “Only a subset of analysts may query a connected external finance database.” Its normal signal is Unauthorized principals cannot select the sensitive foreign tables. Here the requested behavior is “A frequently accessed large foreign table causes slow queries across the network,” so that signal is not sufficient.

Refresh the supported foreign catalog metadata or mappings belongs to the separate case “A foreign schema evolves and analysts cannot see a new remote column,” where The foreign table displays the expected new column after refresh would be expected. That differs from the condition in this stem: “A frequently accessed large foreign table causes slow queries across the network.”

That observation is a valid indicator for “Analysts must query an external supported database without first copying it into Databricks” when using Create a Unity Catalog Lakehouse Federation connection and foreign catalog. The scenario instead tests “A frequently accessed large foreign table causes slow queries across the network”; the relevant result is Repeated local analytical queries run without remote full scans.

Unauthorized principals cannot select the sensitive foreign tables pertains to a different control (Apply least-privilege UC grants on the connection/foreign objects) and a different need (Only a subset of analysts may query a connected external finance database). It cannot establish that Materialize selected data into Delta when latency and egress make federation inefficient met the stated goal.

This signal belongs to the adjacent case “The external database credentials must not be embedded inside analysis notebooks,” whose remedy is Store connection credentials in a governed UC connection. The observed result for the present requirement is Repeated local analytical queries run without remote full scans.

Apply least-privilege UC grants on the connection/foreign objects is appropriate when “Only a subset of analysts may query a connected external finance database”; it would be verified by Unauthorized principals cannot select the sensitive foreign tables. It does not directly satisfy “A foreign schema evolves and analysts cannot see a new remote column,” whose relevant acceptance evidence is The foreign table displays the expected new column after refresh.

The alternative Materialize selected data into Delta when latency and egress make federation inefficient has a distinct purpose—A frequently accessed large foreign table causes slow queries across the network. It would not establish the required outcome (A foreign schema evolves and analysts cannot see a new remote column); the necessary verification concerns The foreign table displays the expected new column after refresh.

The alternative Store connection credentials in a governed UC connection has a distinct purpose—The external database credentials must not be embedded inside analysis notebooks. It would not establish the required outcome (A foreign schema evolves and analysts cannot see a new remote column); the necessary verification concerns The foreign table displays the expected new column after refresh.

That observation is a valid indicator for “Only a subset of analysts may query a connected external finance database” when using Apply least-privilege UC grants on the connection/foreign objects. The scenario instead tests “A foreign schema evolves and analysts cannot see a new remote column”; the relevant result is The foreign table displays the expected new column after refresh.

Analysts query the foreign catalog using delegated privileges would demonstrate the separate action Store connection credentials in a governed UC connection, which addresses “The external database credentials must not be embedded inside analysis notebooks.” It does not verify the requirement “A foreign schema evolves and analysts cannot see a new remote column” following Refresh the supported foreign catalog metadata or mappings.

That observation is a valid indicator for “A frequently accessed large foreign table causes slow queries across the network” when using Materialize selected data into Delta when latency and egress make federation inefficient. The scenario instead tests “A foreign schema evolves and analysts cannot see a new remote column”; the relevant result is The foreign table displays the expected new column after refresh.

The alternative Refresh the supported foreign catalog metadata or mappings has a distinct purpose—A foreign schema evolves and analysts cannot see a new remote column. It would not establish the required outcome (Only a subset of analysts may query a connected external finance database); the necessary verification concerns Unauthorized principals cannot select the sensitive foreign tables.

Materialize selected data into Delta when latency and egress make federation inefficient is appropriate when “A frequently accessed large foreign table causes slow queries across the network”; it would be verified by Repeated local analytical queries run without remote full scans. It does not directly satisfy “Only a subset of analysts may query a connected external finance database,” whose relevant acceptance evidence is Unauthorized principals cannot select the sensitive foreign tables.

Store connection credentials in a governed UC connection belongs to the separate case “The external database credentials must not be embedded inside analysis notebooks,” where Analysts query the foreign catalog using delegated privileges would be expected. That differs from the condition in this stem: “Only a subset of analysts may query a connected external finance database.”

This signal belongs to the adjacent case “A frequently accessed large foreign table causes slow queries across the network,” whose remedy is Materialize selected data into Delta when latency and egress make federation inefficient. The observed result for the present requirement is Unauthorized principals cannot select the sensitive foreign tables.

That observation is a valid indicator for “A foreign schema evolves and analysts cannot see a new remote column” when using Refresh the supported foreign catalog metadata or mappings. The scenario instead tests “Only a subset of analysts may query a connected external finance database”; the relevant result is Unauthorized principals cannot select the sensitive foreign tables.

Analysts query the foreign catalog using delegated privileges would demonstrate the separate action Store connection credentials in a governed UC connection, which addresses “The external database credentials must not be embedded inside analysis notebooks.” It does not verify the requirement “Only a subset of analysts may query a connected external finance database” following Apply least-privilege UC grants on the connection/foreign objects.