Exam Certified Data Engineer Associate topic 1 question 146 discussion

Since the Catalogue and Schema has only Usage permission, Underlying tables in the view needs explicit Select privilege

To read a view, the permissions required depend on the compute type, Databricks Runtime version, and access mode: For all compute resources, you must have SELECT on the view itself, USE CATALOG on its parent catalog, and USE SCHEMA on its parent schema. This applies to all compute types that support Unity Catalog, including SQL warehouses, clusters in shared access mode, and clusters in single user access mode on Databricks Runtime 15.4 and above. For clusters on Databricks Runtime 15.3 and below that use single user access mode, you must also have SELECT on all tables and views that are referenced by the view, in addition to USE CATALOG on their parent catalogs and USE SCHEMA on their parent schemas.

B and key here is “Shared Cluster”. On a single cluster with a runtime prior to 15.4 it will need the permissions on view and tables. With Shared Access Cluster, only on the view.

For a view one does not need the permissions on the underlying table

In Databricks Unity Catalog, permissions are hierarchical and must cover all data objects involved. If a user needs to query a view, the following conditions apply: SELECT permission on the VIEW: Allows the user to query the view itself. SELECT permission on the underlying TABLE(s): Views depend on the underlying tables or data sources. The user must also have SELECT permissions on these tables to access the data exposed by the view.

B is correct. in databricks partner platform, it shows privileges on a view and says: as you see, no one has access to this table, but we could give access to the view without giving access to the underlying table. this is one of the main advantages of views.