Question 310
During a cost optimization assessment at Evermere Health, the lakehouse administrator identifies a Databricks issue: A lookup attribute must always show the latest label and no historical label versions are needed. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
A changed label replaces the prior value without creating unnecessary historical dimension rows. The observation provides evidence that the proposed fix (Choose an SCD Type 1 overwrite strategy for that specific attribute.) addressed the reported issue (A lookup attribute must always show the latest label and no historical label versions are needed.) for Evermere Health and its care team access and regulated data handling. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
An event published during the test appears in the destination within the required freshness interval. This is suitable evidence for another condition (A source produces continuous events requiring minute-level freshness but the team proposes a once-nightly batch load.) after a different response (Choose a streaming ingestion design with an achievable latency and checkpointing strategy.). For Evermere Health, it does not prove the required result: A changed label replaces the prior value without creating unnecessary historical dimension rows.
A lifecycle test confirms the specified external files are retained or managed files are governed as documented. This is suitable evidence for another condition (A data owner expects managed and external tables to delete underlying files identically on DROP.) after a different response (Choose managed or external Unity Catalog tables by explicit storage-ownership and cleanup requirements.). For Evermere Health, it does not prove the required result: A changed label replaces the prior value without creating unnecessary historical dimension rows.
Both authorized query engines return matching records from the selected supported table representation. This is suitable evidence for another condition (A catalog's operational data must be queried across multiple engines with table-level metadata interoperability.) after a different response (Evaluate Delta or Iceberg compatibility and supported Unity Catalog table features against engine requirements.). For Evermere Health, it does not prove the required result: A changed label replaces the prior value without creating unnecessary historical dimension rows.