Answer: GRANT USAGE ON DATABASE customers TO team;

## Explanation **Correct Answer: D** **Why Option D is correct:** 1. The `USAGE` privilege on a database allows users/groups to see the database and its contents (tables, views, etc.) 2. The syntax `GRANT USAGE ON DATABASE customers TO team;` grants the team group permission to access and view the database structure 3. This matches the requirement: "access to database customers in order to see what tables already exist" **Why other options are incorrect:** **Option A:** `GRANT VIEW ON CATALOG customers TO team;` - `VIEW` is not a valid privilege for catalogs in Databricks Unity Catalog - `customers` is a database, not a catalog - The syntax is incorrect for the requirement **Option B:** `GRANT CREATE ON DATABASE customers TO team;` - `CREATE` privilege allows creating objects (tables, views) within the database - This goes beyond the requirement of just viewing existing tables - The team only needs to see what tables exist, not create new ones **Option C:** `GRANT USAGE ON CATALOG team TO customers;` - This reverses the grant direction (granting to customers instead of team) - `team` is a group, not a catalog - The syntax is completely backwards **Key Concepts:** - In Databricks Unity Catalog, `USAGE` privilege on a database allows: - Viewing the database - Listing tables/views in the database - Describing the database - The privilege hierarchy in Unity Catalog is: Catalog → Schema (Database) → Table/View - `GRANT USAGE ON DATABASE <database_name> TO <group_name>;` is the correct syntax for granting database access

Author: Keng Suppaseth