
Ultimate access to all questions.
A data engineer wants to create a relational object by pulling data from two tables. The relational object must be used by other data engineers in other sessions. In order to save on storage costs, the data engineer wants to avoid copying and storing physical data.
Which of the following relational objects should the data engineer create?
A
View
B
Temporary view
C
Delta Table
D
Database
E
Spark SQL Table
Explanation:
Correct Answer: A (View)
Why View is the correct choice:
No physical data storage: A view is a virtual table that does not store data physically. It's essentially a saved SQL query that gets executed when the view is referenced. This aligns perfectly with the requirement to "avoid copying and storing physical data" to save on storage costs.
Persistent across sessions: Unlike temporary views, regular views are persistent and can be accessed by other data engineers in other sessions. The requirement states "must be used by other data engineers in other sessions."
Relational object: A view is indeed a relational object that can pull data from multiple tables (in this case, two tables).
Why other options are incorrect:
B. Temporary view: Temporary views are session-scoped and cannot be accessed by other data engineers in other sessions. They disappear when the session ends.
C. Delta Table: Delta tables store physical data on storage, which would incur storage costs. This contradicts the requirement to avoid copying and storing physical data.
D. Database: A database is a container for tables and other objects, not a relational object that pulls data from tables. It doesn't meet the requirement of creating a relational object from two tables.
E. Spark SQL Table: This would create a physical table that stores data, which would incur storage costs and copy data.
Key Concepts:
This solution allows the data engineer to create a reusable, persistent relational object that other team members can access without duplicating storage costs.