Databricks Certified Data Engineer Associate Exam - Topic 4 Question 52 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Associate exam

Question #: 52
Topic #: 4

[All Databricks Certified Data Engineer Associate Questions]

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?

ADatabase

BFunction

CView

DTemporary view

ETable

Show Suggested Answer

Suggested Answer: E

: A table is a data entity that is stored in a physical location and can be accessed by other data engineers in other sessions. A table can be created from one or more tables using theCREATE TABLEorCREATE TABLE AS SELECTcommands. A table can also be registered from an existing DataFrame using thespark.catalog.createTablemethod. A table can be queried using SQL or DataFrame APIs. A table can also be updated, deleted, or appended using theMERGE INTOcommand or the DeltaTable API.Reference:

Create a table

Create a table from a query result

[Query a table]

[Update, delete, or merge into a table]

by Sheron at Jul 14, 2025, 12:56 PM

Limited Time Offer

25%

Off

Get Premium Databricks Certified Data Engineer Associate Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Una

4 months ago

Temporary view? Nah, that won't persist across sessions.

upvoted 0 times

...

Maia

4 months ago

Wait, can a Function really be used like that? Sounds odd.

upvoted 0 times

...

Theola

4 months ago

Definitely a Table! It needs to be saved physically.

upvoted 0 times

...

Emerson

4 months ago

A View wouldn't work since it doesn't save data.

upvoted 0 times

...

Florencia

4 months ago

I think a Database is the way to go. More robust!

upvoted 0 times

...

Glenn

5 months ago

I’m confused about the Temporary view option. I don’t think it can be used by others in different sessions, right?

upvoted 0 times

...

Jenelle

5 months ago

I practiced a similar question where we had to choose between a Database and a Table. I feel like a Table is the right choice here.

upvoted 0 times

...

Hannah

5 months ago

I'm not entirely sure, but I remember something about Views being more for virtual representations. Could it be a View instead?

upvoted 0 times

...

Matthew

5 months ago

I think the answer might be a Table since it needs to be saved physically and used by other engineers.

upvoted 0 times

...

Sylvie

5 months ago

Hmm, this is a tricky one. I'm stuck between C - View and E - Table. I'll need to carefully consider the pros and cons of each option to determine the best fit for the requirements given in the question.

upvoted 0 times

...

Matilda

6 months ago

I feel pretty confident about this one. The key details are that the data entity needs to be shareable and persisted. That points to C - View as the best choice. Views are a great way to encapsulate data from multiple tables and make it accessible to other users.

upvoted 0 times

...

Willodean

6 months ago

Okay, let me break this down. The data entity needs to be reusable and saved to a physical location. That rules out A - Database and B - Function. I'm leaning towards C - View, but I'll double-check the differences between that and E - Table.

upvoted 0 times

...

Amber

6 months ago

Hmm, I'm a bit unsure about this one. I'm trying to decide between C - View and E - Table. I'll need to think through the differences between those two options carefully.

upvoted 0 times

...

Nettie

6 months ago

This seems like a straightforward question. I think the answer is C - View, since a view can be used by other data engineers and it can be saved to a physical location.

upvoted 0 times

...

Nichelle

8 months ago

I agree with Yolando, a table would be the most appropriate choice for this situation.

upvoted 0 times

...

Refugia

8 months ago

I bet the answer is C. Views are just so darn convenient, you know? Plus, who doesn't love a good data entity that can be reused across sessions?

upvoted 0 times

Long

7 months ago

I agree with you, but I still think C) View is the best option for reusability and convenience.

upvoted 0 times

...

Fatima

7 months ago

I think the answer is A) Database. It's a more permanent solution for storing the data entity.

upvoted 0 times

...

Yolando

8 months ago

I think a table would be the best option because it can be saved to a physical location.

upvoted 0 times

...

Keith

8 months ago

A function could work, but then you'd have to call it every time you need the data. A view seems like the way to go here.

upvoted 0 times

Yolande

7 months ago

C) View

upvoted 0 times

...

Jeannetta

7 months ago

B) Function

upvoted 0 times

...

Tonja

7 months ago

A) Database

upvoted 0 times

...

Angelo

8 months ago

I disagree, I believe a view would be more suitable for this scenario.

upvoted 0 times

...

Yolande

8 months ago

Temporary views are great for quick, one-off analyses, but this sounds like a more long-term solution. I'd go with a regular view.

upvoted 0 times

Leatha

7 months ago

User 3: A view makes sense, it can be saved to a physical location and used by multiple sessions.

upvoted 0 times

...

Frank

7 months ago

User 2: Yeah, I agree. It's more suitable for long-term use by other data engineers.

upvoted 0 times

...

Jesusa

8 months ago

User 1: I think a regular view would be the best option for this scenario.

upvoted 0 times

...

Lilli

9 months ago

I think the data engineer should create a database.

upvoted 0 times

...

Makeda

9 months ago

Hmm, I'm not sure a view is the right choice. Wouldn't a table be more appropriate since the data needs to be saved to a physical location?

upvoted 0 times

Raymon

7 months ago

User 2: Yeah, I agree. A view might not be the right option in this case.

upvoted 0 times

...

Stephaine

8 months ago

User 1: I think a table would be the best choice for saving the data to a physical location.

upvoted 0 times

...

Lavonna

9 months ago

I think a view would be the best option here. It allows for reusability and persistence without the need to recreate the data every time.

upvoted 0 times

Tammi

8 months ago

I agree, a view would provide the reusability and persistence needed.

upvoted 0 times

...

Tammi

8 months ago

View sounds like the best option for this scenario.

upvoted 0 times

...