CERTIFIED-DATA-ENGINEER-PROFESSIONAL Question #113: Real Exam Question with Answer & Explanation

Question

A data architect has heard about lake's built-in versioning and time travel capabilities. For auditing purposes they have a requirement to maintain a full of all valid street addresses as they appear in the customers table. The architect is interested in implementing a Type 1 table, overwriting existing records with new values and relying on Delta Lake time travel to support long-term auditing. A data engineer on the project feels that a Type 2 table will provide better performance and scalability. Which piece of information is critical to this decision?

Options

• ADelta Lake time travel does not scale well in cost or latency to provide a long-term versioning
• BDelta Lake time travel cannot be used to query previous versions of these tables because Type 1
• CShallow clones can be combined with Type 1 tables to accelerate historic queries for long-term
• DData corruption can occur if a query fails in a partially completed state because Type 2 tables
• EDelta Lake only supports Type 0 tables; once records are inserted to a Delta Lake table, they

Explanation

Delta Lake's time travel feature allows users to access previous versions of a table, providing a powerful tool for auditing and versioning. However, using time travel as a long-term versioning solution for auditing purposes can be less optimal in terms of cost and performance, especially as the volume of data and the number of versions grow. For maintaining a full history of valid street addresses as they appear in a customers table, using a Type 2 table (where each update creates a new record with versioning) might provide better scalability and performance by avoiding the overhead associated with accessing older versions of a large table. While Type 1 tables, where existing records are overwritten with new values, seem simpler and can leverage time travel for auditing, the critical piece of information is that time travel might not scale well in cost or latency for long-term versioning needs, making a Type 2 approach more viable for performance and

No community discussion yet for this question.