Databricks Certified Data Engineer - Associate

Explanation

To query a table in Databricks Unity Catalog, a user needs the SELECT permission on that specific table. Let's break down the requirements:

1. Current permissions: The data engineer already has USAGE on the database retail. This allows them to see the database and its objects, but not necessarily access the tables within it.

2. Required permission: To query (read data from) the sales table, the data engineer needs the SELECT permission on that table.

3. Analysis of options:

   • Option A: GRANT USAGE ON TABLE sales - This grants the ability to see the table exists, but not to query it.
   • Option B: GRANT CREATE ON TABLE sales - This grants permission to create new tables in the same schema, not to query existing tables.
   • Option C: GRANT SELECT ON TABLE sales - CORRECT. This grants the permission to query (SELECT) data from the sales table.
   • Option D: GRANT USAGE ON TABLE new.engineer@company.com TO sales - This syntax is incorrect and reversed; it's trying to grant permissions on a user to a table.
   • Option E: GRANT SELECT ON TABLE new.engineer@company.com TO sales - This syntax is also incorrect and reversed.

4. Key point: In Databricks Unity Catalog, permissions are hierarchical. While USAGE on the database is required to see the database, SELECT on the table is required to actually query the data. The data engineer already has database USAGE, so only table-level SELECT permission is needed.

Correct Answer: C