Exam Certified Data Engineer Associate topic 1 question 24 discussion

Questions says : 1. The data entity must be used by other data engineers in other sessions. 2. It also must be saved to a physical location. Here View doesn't store data in physical location , from the options only table stores data in physical location So answer should be 'E' which is Table.

Just got 100% in the exam. Table was a correct answer.

E. Table Creating a table ensures that the data entity is saved to a physical location and can be used by other data engineers in different sessions. Tables persist data and metadata, making them suitable for long-term storage and sharing across sessions.

The correct answer is "E". A view does not save to a physical location; only caching a SELECT statement.

physical location means table

E. as view doesnt has any location

E is correct

E. Table Usage by Other Sessions: Tables in a database are persistent data structures that can be accessed by multiple users and sessions concurrently. Saved to a Physical Location: Tables store data physically in a structured manner on disk or in a storage system, making them suitable for long-term storage. Usage by Other Data Engineers: Other data engineers can query, access, and work with the data within the table, making it a feasible choice for shared access among multiple users or sessions. While other entities like views or temporary views can provide different ways to represent or filter data, a table fits the criteria best when the data engineer requires a persistent physical storage entity accessible by other sessions and users for data manipulation, retrieval, and storage.

I think the key to the answer is that it refers to the Data Entinty, and not to the data itself, when it mentions "the Data Entity must be used by other Data Engineers", and "It must be saved to a physical location". From this PoV, both C and E would be correct, however, creating a new table would incur in processing to a static state the relationship from "a couple of tables". While this make sense to many use cases, this would require either a Workflow or a DLT to make it work, which goes over the requested scope. C is the best answer for the requested scenario.

Key point to remember during answering this question: " It also must be saved to a physical location" So answer should be 'E' which is Table.

C is the right answer. View is a data entity and its definition is physically saved so other users can consume view

The correct answer is E because it has to be physically saved. View is in memory.

Correct : E

E. Table To create a data entity that can be used by other data engineers in other sessions and must be saved to a physical location, you should create a table. Tables in a database are physical storage structures that hold data, and they can be accessed and shared by multiple users and sessions. By creating a table, you provide a permanent and structured storage location for the data entity that can be used across different sessions and by other users as needed. Options like databases (A) can be used to organize tables, views (C) can provide virtual representations of data, and temporary views (D) are temporary in nature and don't save data to a physical location. Functions (B) are typically used for processing data or performing calculations, not for storing data.

View does not have a physical location so answer has to be E

View Doesn't physical location

The answer is E: "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. A "Database" is a collection of tables, views, and other database objects. A "Function" is a stored procedure that performs an operation. A "View" is a virtual table based on the result-set of an SQL statement, but it is not stored physically. A "Temporary view" is a feature that allows you to store the result of a query as a view that disappears once your session with the database is closed.