This would test a different behavior, chiefly separate ownership and policy administration through appropriate Unity Catalog roles and policy scopes. Governance separation of duties prevents ordinary data stewards from bypassing central data protection. The specific evidence needed here is that the service identity can create only approved objects and cannot alter unrelated catalogs.

This would test a different behavior, chiefly audit Unity Catalog privilege inheritance and move broad grants to the intended narrow scope. Privileges at higher securable levels can affect descendant objects and must match the access design. The specific evidence needed here is that the service identity can create only approved objects and cannot alter unrelated catalogs.

This would test a different behavior, chiefly transfer ownership to an approved group and review inherited grants in a controlled change. Group-based ownership supports continuity and separates stewardship from individual employee accounts. The specific evidence needed here is that the service identity can create only approved objects and cannot alter unrelated catalogs.

Unity Catalog queries require applicable path-usage privileges in addition to object-level read grants. That option implements verify and grant required USE CATALOG and USE SCHEMA privileges alongside narrowly scoped SELECT. It addresses a different problem; here the distinguishing need is to audit Unity Catalog privilege inheritance and move broad grants to the intended narrow scope.

Read privileges do not imply object creation; Unity Catalog uses scoped privileges for different operations. That option implements grant only the necessary CREATE or USE privileges on the intended securable hierarchy. It addresses a different problem; here the distinguishing need is to audit Unity Catalog privilege inheritance and move broad grants to the intended narrow scope.

Governance separation of duties prevents ordinary data stewards from bypassing central data protection. That option implements separate ownership and policy administration through appropriate Unity Catalog roles and policy scopes. It addresses a different problem; here the distinguishing need is to audit Unity Catalog privilege inheritance and move broad grants to the intended narrow scope.

This would test a different behavior, chiefly apply a Unity Catalog row-filter policy to the shared table with authorized division logic. Row filters enforce row-level visibility on each query instead of trusting users to remember a WHERE clause. The specific evidence needed here is that removing a local table grant cannot bypass the central mask and a new matching table is protected automatically.

This would test a different behavior, chiefly grant the appropriate access to the governed view and enforce required underlying rights and controls. View definition alone is not a substitute for object permissions; access paths must be authorized explicitly. The specific evidence needed here is that removing a local table grant cannot bypass the central mask and a new matching table is protected automatically.

This would test a different behavior, chiefly attach a Unity Catalog column mask with a suitable identity-aware masking function. Column masks transform sensitive values at query time without generating separate physical copies per audience. The specific evidence needed here is that removing a local table grant cannot bypass the central mask and a new matching table is protected automatically.

A curated shared interface separates consumer contracts from internal table shape and sensitive columns. That option implements publish an approved share-compatible governed view or data product exposing only the agreed schema. It addresses a different problem; here the distinguishing need is to configure a Databricks-to-Databricks OpenSharing share and recipient for approved assets.

Open sharing allows authorized non-Databricks recipients to access shared data through a protocol interface. That option implements use Databricks-to-open OpenSharing with an eligible recipient and supported client protocol. It addresses a different problem; here the distinguishing need is to configure a Databricks-to-Databricks OpenSharing share and recipient for approved assets.

Provider-side recipient control stops future access to shared resources without relying on deleting past exports. That option implements revoke or update the OpenSharing recipient permissions and verify access is denied. It addresses a different problem; here the distinguishing need is to configure a Databricks-to-Databricks OpenSharing share and recipient for approved assets.

This would test a different behavior, chiefly run or enable the supported statistics collection and optimization process for the managed table. File statistics and layout information help the engine eliminate irrelevant data during queries. The specific evidence needed here is that ingestion latency improves and table-file distribution stays within defined operating targets.

This would test a different behavior, chiefly enable the required predictive optimization capability for automatic clustering maintenance. Automatic key selection and clustering operations rely on predictive optimization to act on usage patterns. The specific evidence needed here is that ingestion latency improves and table-file distribution stays within defined operating targets.

This would test a different behavior, chiefly enable predictive optimization for eligible Unity Catalog managed tables where supported. Predictive optimization manages operations such as optimization and cleanup using observed table needs. The specific evidence needed here is that ingestion latency improves and table-file distribution stays within defined operating targets.

Automatic liquid clustering selects keys from usage patterns and works with predictive optimization. That option implements enable automatic liquid clustering with CLUSTER BY AUTO on an eligible managed table. It addresses a different problem; here the distinguishing need is to run an appropriate OPTIMIZE operation after modifying the liquid-clustering definition.

Liquid clustering is a replacement layout option rather than an add-on to ZORDER on the same table. That option implements choose one supported clustering layout strategy and do not combine ZORDER with liquid clustering. It addresses a different problem; here the distinguishing need is to run an appropriate OPTIMIZE operation after modifying the liquid-clustering definition.

Liquid clustering improves skip locality without creating a separate object-directory partition for every user. That option implements prefer liquid clustering over extremely high-cardinality static partitions for this access pattern. It addresses a different problem; here the distinguishing need is to run an appropriate OPTIMIZE operation after modifying the liquid-clustering definition.

This would test a different behavior, chiefly repair the Unity Catalog connection credentials and confirm source-account permissions for Lakeflow Connect. Connector authentication and source privileges are prerequisites for consistent managed CDC extraction. The specific evidence needed here is that a new source update appears downstream and connector health no longer reports missing CDC prerequisites.

This would test a different behavior, chiefly use a supported Lakeflow Connect database connector with its managed ingestion pipeline. Lakeflow Connect integrates initial snapshot ingestion and CDC replication for supported database sources. The specific evidence needed here is that a new source update appears downstream and connector health no longer reports missing CDC prerequisites.

This would test a different behavior, chiefly scope the Lakeflow Connect ingestion configuration and source permissions to approved tables. Table selection and least-privileged source access limit unnecessary extraction of sensitive data. The specific evidence needed here is that a new source update appears downstream and connector health no longer reports missing CDC prerequisites.

This would test a different behavior, chiefly compare SQL warehouse activity and billing usage using supported monitoring system tables. Correlating usage and activity distinguishes busy compute from idle provisioning and waste. The specific evidence needed here is that a controlled policy-change test appears before its corresponding access attempt in the correlated report.

This would test a different behavior, chiefly analyze the supported audit system tables over the relevant principal, object and time range. Centralized audit event records provide historical evidence of actions that a current permission listing cannot show. The specific evidence needed here is that a controlled policy-change test appears before its corresponding access attempt in the correlated report.

This would test a different behavior, chiefly query the supported Databricks billing and usage system tables with workload or resource attribution. System tables expose account-level metering and usage records that can be aggregated by job or compute. The specific evidence needed here is that a controlled policy-change test appears before its corresponding access attempt in the correlated report.

Array expansion creates line-item rows while a parent key preserves source relationship. That option implements parse the nested array and use an explode operation while retaining the parent event identifier. It addresses a different problem; here the distinguishing need is to apply a supported AI function such as ai_query to approved text with explicit result checks.

VARIANT supports evolving semi-structured values while downstream projections can enforce typed contracts. That option implements store flexible semi-structured payloads in a VARIANT column with intentional extraction of queried paths. It addresses a different problem; here the distinguishing need is to apply a supported AI function such as ai_query to approved text with explicit result checks.

Semi-structured values need explicit conversion before trusted numeric aggregations and calculations. That option implements extract and cast the required VARIANT path into a validated numeric column with error handling. It addresses a different problem; here the distinguishing need is to apply a supported AI function such as ai_query to approved text with explicit result checks.

Execution metrics identify whether memory pressure comes from wide shuffles, skew or configuration. That option implements inspect Spark UI memory, shuffle spill and executor logs to choose a join or memory fix. It addresses a different problem; here the distinguishing need is to use Spark UI task timelines and shuffle metrics to isolate skewed partitions before applying a targeted fix.

An accidental Cartesian product can multiply intermediate rows and dominate cost. That option implements inspect the physical plan and query profile to find a missing or incorrect join predicate. It addresses a different problem; here the distinguishing need is to use Spark UI task timelines and shuffle metrics to isolate skewed partitions before applying a targeted fix.

Scan-level evidence distinguishes inefficient reads from subsequent aggregation performance. That option implements use query profile scan metrics to identify predicate pushdown or data-skipping regressions. It addresses a different problem; here the distinguishing need is to use Spark UI task timelines and shuffle metrics to isolate skewed partitions before applying a targeted fix.

This would test a different behavior, chiefly use Spark UI task timelines and shuffle metrics to isolate skewed partitions before applying a targeted fix. Disproportionate task durations and shuffle bytes reveal skew rather than general CPU scarcity. The specific evidence needed here is that after rewrite, scanned bytes decrease and the filtered result set remains identical.

This would test a different behavior, chiefly inspect the physical plan and query profile to find a missing or incorrect join predicate. An accidental Cartesian product can multiply intermediate rows and dominate cost. The specific evidence needed here is that after rewrite, scanned bytes decrease and the filtered result set remains identical.

This would test a different behavior, chiefly inspect executor logs and Spark UI failed task details to isolate the offending partition and data. Task-level diagnostics provide specific executor exceptions and data locations hidden by the top-level job status. The specific evidence needed here is that after rewrite, scanned bytes decrease and the filtered result set remains identical.