Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A data engineer wants to create a relational object by pulling data from two tables. The relational object does not need to 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?
Real Exam
Community
KKeng
0
A
Spark SQL Table
B
View
C
Database
D
Temporary view
E
Delta Table
Explanation:
Explanation:
A temporary view is the correct choice because:
- Session-based scope: Temporary views exist only for the duration of the current Spark session and are automatically dropped when the session ends.
- No physical storage: Temporary views don't create physical copies of data on storage - they are logical views defined by a query.
- Cost-effective: Since no data is duplicated or stored separately, storage costs are minimized.
- Private to session: Other data engineers in other sessions cannot access the temporary view, which matches the requirement that it doesn't need to be used by others.
Why other options are incorrect:
- Spark SQL Table (A): Creates a physical table that stores data persistently, increasing storage costs.
- View (B): While views don't store physical data, they are persistent and can be accessed by other users/sessions.
- Database (C): A database is a container for tables/views, not a relational object created by pulling data from tables.
- Delta Table (E): Creates a physical Delta table that stores data persistently, increasing storage costs.
Key characteristics of temporary views:
- Created with
CREATE TEMP VIEW view_name AS query - Session ends when: opening a new notebook, detaching/reattaching a cluster, installing a Python package, or restarting a cluster
- Ideal for intermediate transformations that don't need persistence or sharing across sessions.
Comments
Loading comments...