Answer: Catalog Explorer

## Explanation **Correct Answer: C. Catalog Explorer** In Databricks, the Catalog Explorer is the primary interface for managing and reviewing permissions on Delta tables and other data objects. Here's why: 1. **Catalog Explorer Purpose**: The Catalog Explorer provides a unified view of all data objects (tables, views, schemas, catalogs) in the Databricks Lakehouse Platform. It includes detailed metadata and permission management capabilities. 2. **Permission Review**: Within Catalog Explorer, users can: - Navigate to specific tables - View table details and metadata - Check their own permissions on the table - See what operations they're allowed to perform (SELECT, MODIFY, etc.) 3. **Why Other Options Are Incorrect**: - **A. Jobs**: This is for managing and monitoring job executions, not for reviewing table permissions. - **B. Dashboards**: This is for creating and viewing business intelligence dashboards, not for permission management. - **D. Repos**: This is for version control and collaborative development using Git repositories, not for table permission review. 4. **Practical Usage**: To review permissions in Catalog Explorer: - Navigate to the Data section in Databricks - Browse to the specific catalog, schema, and table - The table details will show permission information - Users can also use the `SHOW GRANT` SQL command to check permissions programmatically This question tests knowledge of Databricks' data governance tools and where to find permission information, which is crucial for data engineers working with secure data pipelines.

Author: Keng Suppaseth