Explanation
Let's analyze each option:
A. Table - ✅ CORRECT
- Tables are persistent data entities that are saved to physical storage (like Delta Lake)
- They can be accessed by other data engineers in different sessions
- They exist beyond the current session and can be queried by multiple users
- Tables store data physically on storage
B. Function - ❌ INCORRECT
- Functions are reusable code blocks, not data entities
- They don't store data from tables
- They are not saved to physical locations as data storage
C. View - ❌ INCORRECT
- Views are virtual tables that don't store data physically
- They are saved definitions that reference underlying tables
- While they can be used by other engineers in other sessions, they don't save data to a physical location
- Views only store the query definition, not the actual data
D. Temporary view - ❌ INCORRECT
- Temporary views are session-scoped and cannot be accessed by other data engineers in other sessions
- They are not saved to physical locations
- They disappear when the session ends
Key Requirements from the question:
- Created from a couple of tables ✓ (Tables can be created from other tables using CTAS or similar operations)
- Used by other data engineers in other sessions ✓ (Tables are accessible across sessions)
- Saved to a physical location ✓ (Tables store data physically in storage)
Only Table meets all three requirements. Views (including temporary views) don't save data physically, and functions aren't data entities created from tables.