Answer: Table

## Explanation The correct answer is **A. Table** because: 1. **Persistence across sessions**: Tables are physically stored in a location (like DBFS, cloud storage) and can be accessed by multiple users across different sessions. 2. **Physical storage requirement**: The question explicitly states the data entity "must be saved to a physical location" - tables are physically materialized and stored. 3. **Cross-session accessibility**: Tables are cataloged in the metastore and can be shared among data engineers working in different sessions. ### Why other options are incorrect: - **B. Function**: Functions are reusable logic, not data entities created from tables. - **C. View**: Views are logical abstractions over tables/queries but are not physically stored - they are computed on-demand. - **D. Temporary view**: Temporary views are session-scoped and not accessible across sessions, nor are they physically stored. In Databricks, when you need a persistent, shareable data entity that is physically stored, you create a table. This could be a managed table (stored in the metastore location) or an external table (pointing to an external storage location).

Author: Keng Suppaseth