MENU
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?
Suggested Answer: E
Get Premium Databricks Certified Data Engineer Associate Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
: 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 from a query result
Register a table from a DataFrame
[Query a table]
[Update, delete, or merge into a table]
35 comments · newest first
UN
Una
10 months ago
Temporary view? Nah, that won't persist across sessions.
MA
Maia
10 months ago
Wait, can a Function really be used like that? Sounds odd.
TH
Theola
10 months ago
Definitely a Table! It needs to be saved physically.
EM
Emerson
10 months ago
A View wouldn't work since it doesn't save data.
FL
Florencia
10 months ago
I think a Database is the way to go. More robust!
GL
Glenn
11 months ago
I’m confused about the Temporary view option. I don’t think it can be used by others in different sessions, right?
JE
Jenelle
11 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.
HA
Hannah
11 months ago
I'm not entirely sure, but I remember something about Views being more for virtual representations. Could it be a View instead?
MA
Matthew
11 months ago
I think the answer might be a Table since it needs to be saved physically and used by other engineers.
SY
Sylvie
12 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.
MA
Matilda
12 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.
WI
Willodean
12 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.
AM
Amber
1 year 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.
NE
Nettie
1 year 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.
NI
Nichelle
1 year ago
I agree with Yolando, a table would be the most appropriate choice for this situation.
RE
Refugia
1 year 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?
LO
Long
1 year ago
I agree with you, but I still think C) View is the best option for reusability and convenience.
FA
Fatima
1 year ago
I think the answer is A) Database. It's a more permanent solution for storing the data entity.
YO
Yolando
1 year ago
I think a table would be the best option because it can be saved to a physical location.
KE
Keith
1 year 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.
YO
Yolande
1 year ago
C) View
JE
Jeannetta
1 year ago
B) Function
TO
Tonja
1 year ago
A) Database
AN
Angelo
1 year ago
I disagree, I believe a view would be more suitable for this scenario.
YO
Yolande
1 year 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.
LE
Leatha
1 year ago
User 3: A view makes sense, it can be saved to a physical location and used by multiple sessions.
FR
Frank
1 year ago
User 2: Yeah, I agree. It's more suitable for long-term use by other data engineers.
JE
Jesusa
1 year ago
User 1: I think a regular view would be the best option for this scenario.
LI
Lilli
1 year ago
I think the data engineer should create a database.
MA
Makeda
1 year 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?
RA
Raymon
1 year ago
User 2: Yeah, I agree. A view might not be the right option in this case.
ST
Stephaine
1 year ago
User 1: I think a table would be the best choice for saving the data to a physical location.
LA
Lavonna
1 year 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.
TA
Tammi
1 year ago
I agree, a view would provide the reusability and persistence needed.
TA
Tammi
1 year ago
View sounds like the best option for this scenario.