Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a Fabric tenant that contains a lakehouse named Lakehouse1. Lakehouse1 contains a Delta table named Customer. When you query Customer, you discover that the query is slow to execute. You suspect that maintenance was NOT performed on the table. You need to identify whether maintenance tasks were performed on Customer. Solution: You run the following Spark SQL statement: DESCRIBE HISTORY customer Does this meet the goal?

Question

Accepted Answer

A. Yes A Spark command such as `DESCRIBE HISTORY <table_name>` on a Delta table logs all operations, including maintenance tasks like OPTIMIZE, VACUUM, and ZORDER, thereby allowing identification of when these tasks were executed. This command specifically exposes the table's transaction log, detailing each modification.

Answer

B. No Any Spark command that does not specifically query the Delta table's transaction log or operational history would fail to meet the goal of identifying past maintenance tasks.

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might h

Question

Options

How the community answered

Why each option

Topics

Community Discussion