Answer: `GRANT ALL PRIVILEGES ON TABLE sales TO new.engineer@company.com;`

## Explanation **Correct Answer: A** `GRANT ALL PRIVILEGES ON TABLE sales TO new.engineer@company.com;` is the correct command to grant full permissions on the table to the new data engineer. **Why other options are incorrect:** **B.** `GRANT USAGE ON TABLE sales TO new.engineer@company.com;` - This only grants USAGE privilege, which is insufficient for full management. USAGE typically allows using the object but not modifying it. **C.** `GRANT ALL PRIVILEGES ON TABLE new.engineer@company.com TO sales;` - This has the syntax reversed. It's trying to grant privileges on the user 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 the table but not modifying, creating, or deleting data. **E.** `GRANT SELECT CREATE MODIFY ON TABLE sales TO new.engineer@company.com;` - This syntax is incorrect. In SQL GRANT statements, you typically use `ALL PRIVILEGES` for full permissions or list specific privileges separately, but `CREATE` is not a valid privilege for a table (CREATE is for schemas/databases). **Key Points:** - `ALL PRIVILEGES` grants all available privileges on the specified object - The correct syntax is `GRANT ALL PRIVILEGES ON TABLE [table_name] TO [user/role];` - For full management capabilities including SELECT, INSERT, UPDATE, DELETE, and other operations, `ALL PRIVILEGES` is required - In Databricks Unity Catalog, this would grant all applicable privileges on the table to the specified principal

Author: Keng Suppaseth