Databricks Certified Data Engineer - Associate

Explanation

Option A is correct because:

1. GRANT ALL PRIVILEGES is the correct SQL syntax in Databricks Unity Catalog to grant all available privileges on a table
2. The syntax follows the pattern: GRANT ALL PRIVILEGES ON TABLE <table_name> TO <principal>;
3. This grants the team full permissions including SELECT, MODIFY, CREATE, DROP, and other privileges needed to fully manage the table

Why other options are incorrect:

• Option B: GRANT SELECT CREATE MODIFY ON TABLE sales TO team; - This syntax is invalid. In Databricks Unity Catalog, you cannot combine multiple privilege types in a single GRANT statement like this. You would need separate GRANT statements for each privilege.
• Option C: GRANT SELECT ON TABLE sales TO team; - This only grants SELECT privilege, not full permissions needed to manage the project.
• Option D: GRANT USAGE ON TABLE sales TO team; - USAGE privilege is for schemas/databases, not tables. For tables, you need specific privileges like SELECT, MODIFY, etc.
• Option E: GRANT ALL PRIVILEGES ON TABLE team TO sales; - This reverses the table and principal, attempting to grant privileges on a table called 'team' to 'sales', which doesn't make sense in this context.

Key Points:

• In Databricks Unity Catalog, ALL PRIVILEGES is a special privilege that grants all available privileges on the object
• The correct syntax is GRANT ALL PRIVILEGES ON TABLE <table_name> TO <principal>;
• This is essential for data governance and access control in production environments