Databricks Certified Data Engineer - Associate

Explanation

Let's analyze each option:

A. GRANT USAGE ON DATABASE customers TO team;

• This only grants USAGE privilege, which allows the team to see the database and its objects, but not full management privileges.

B. GRANT ALL PRIVILEGES ON DATABASE team TO customers;

• This is incorrect because it's granting privileges on the wrong database ('team' instead of 'customers') and to the wrong entity ('customers' instead of 'team').

C. GRANT SELECT PRIVILEGES ON DATABASE customers TO teams;

• This only grants SELECT privileges, which is insufficient for full management. Also, note the typo 'teams' instead of 'team'.

D. GRANT SELECT CREATE MODIFY USAGE PRIVILEGES ON DATABASE customers TO team;

• While this grants multiple privileges, it's not the standard way to grant all privileges. The syntax is also incorrect - in Databricks SQL, you cannot list individual privileges like this for database-level grants.

E. GRANT ALL PRIVILEGES ON DATABASE customers TO team;

• CORRECT: This is the standard Databricks SQL command to grant all available privileges on a database to a user or group. It grants full management capabilities including:
  • CREATE TABLE
  • CREATE VIEW
  • CREATE FUNCTION
  • MODIFY
  • SELECT
  • USAGE
  • And other privileges

In Databricks Unity Catalog, GRANT ALL PRIVILEGES ON DATABASE is the proper command to give complete administrative control over a database, allowing the team to create, modify, and manage all objects within the database.