Answer: GRANT USAGE ON DATABASE customers TO team;

## Explanation In Databricks Unity Catalog, the `USAGE` privilege is required to access and view objects within a database. Here's why option E is correct: 1. **USAGE privilege**: Grants the ability to use (access) a database and see its contents (tables, views, etc.) 2. **Syntax**: `GRANT USAGE ON DATABASE customers TO team;` - `USAGE` is the privilege being granted - `DATABASE customers` specifies the target database - `TO team` specifies the recipient group **Why other options are incorrect**: - **A**: `GRANT VIEW ON CATALOG customers TO team;` - Incorrect because: - `VIEW` is not a valid privilege for catalogs in this context - The team needs access to a database, not a catalog - `customers` is a database, not a catalog - **B**: `GRANT CREATE ON DATABASE customers TO team;` - Incorrect because: - `CREATE` privilege allows creating new objects (tables, views) in the database - The team only needs to see existing tables, not create new ones - **C**: `GRANT USAGE ON CATALOG team TO customers;` - Incorrect because: - Reverses the grant direction (granting to customers instead of team) - Uses `CATALOG` instead of `DATABASE` - `team` is a group, not a catalog - **D**: `GRANT CREATE ON DATABASE team TO customers;` - Incorrect because: - Reverses the grant direction - Uses wrong database name (`team` instead of `customers`) - Grants `CREATE` privilege instead of `USAGE` **Key Databricks Unity Catalog Privileges**: - `USAGE`: Required to access and view objects in a database - `SELECT`: Required to query data from tables - `CREATE`: Required to create new objects in a database - `MODIFY`: Required to modify existing objects The team needs `USAGE` on the database to see what tables exist, which is exactly what option E provides.

Author: Keng Suppaseth