Ultimate access to all questions.
Answer-first summary for fast verification
Answer: Table
In the context described, creating a "Table" is the most suitable choice. Tables in SQL are data entities that exist independently of any session and are saved in a physical location. They can be accessed and manipulated by other data engineers in different sessions, which aligns with the requirements stated. **Key reasons:** 1. **Persistent storage**: Tables are physically saved to storage locations (like HDFS, cloud storage, etc.) 2. **Session-independent**: Tables persist beyond individual sessions and can be accessed by multiple users 3. **Shared access**: Other data engineers can query and use the table in their own sessions **Why other options are incorrect:** - **Database**: A database is a collection of objects (tables, views, etc.), not a data entity created from tables - **Function**: Functions perform operations but aren't data entities created from tables - **View**: Views are virtual and not physically stored; they're just saved queries - **Temporary view**: Temporary views are session-scoped and disappear when the session ends
Author: Keng Suppaseth
No comments yet.
A data engineer wants to create a data entity from a couple of tables. The data entity must be used by other data engineers in other sessions. It also must be saved to a physical location. Which of the following data entities should the data engineer create?
A
Database
B
Function
C
View
D
Temporary view
E
Table