Databricks Certified Data Engineer - Associate

Explanation

Let's analyze each option:

A. GRANT ALL PRIVILEGES ON TABLE sales TO new.engineer@company.com; ✅

• This is the correct command to grant full permissions on the table.
• ALL PRIVILEGES grants all available privileges on the table, including SELECT, INSERT, UPDATE, DELETE, CREATE, MODIFY, etc.
• The syntax follows the standard pattern: GRANT ALL PRIVILEGES ON TABLE <table_name> TO <user>;

B. GRANT USAGE ON TABLE sales TO new.engineer@company.com; ❌

• USAGE privilege is insufficient for full management of the table.
• USAGE typically allows basic access but not full administrative privileges.

C. GRANT ALL PRIVILEGES ON TABLE new.engineer@company.com TO sales; ❌

• This syntax is incorrect and reversed.
• It attempts to grant privileges on the user email to the table, which doesn't make sense.

D. GRANT SELECT ON TABLE sales TO new.engineer@company.com; ❌

• This only grants SELECT privilege, which allows reading data but not modifying or managing the table.
• Insufficient for full project management.

E. GRANT SELECT CREATE MODIFY ON TABLE sales TO new.engineer@company.com; ❌

• This syntax is invalid - you cannot list multiple specific privileges this way.
• The correct way to grant multiple specific privileges would be separate GRANT statements or use ALL PRIVILEGES.

Key Points:

• ALL PRIVILEGES is the standard SQL command for granting full permissions on database objects
• The syntax must follow: GRANT ALL PRIVILEGES ON TABLE <table_name> TO <user_or_role>;
• This grants all available table-level privileges including SELECT, INSERT, UPDATE, DELETE, and administrative privileges