Question 540
An organization running Snowflake reports: A dashboard suddenly reports lower revenue after a transformation change and the team cannot identify upstream data dependencies. What observation most directly confirms the correction?
Explanation
Correct Answer
This verifies data lineage assessment because the data lineage from source tables to derived metrics is undocumented or not inspected. The corresponding corrective action is: Trace the supported lineage and relevant SQL transformations before changing warehouse settings. A green status for a different component would not independently establish this result.
Incorrect Answers
Sensitive-data classification and tagging have not kept pace with schema creation. “Classify affected columns and apply approved sensitivity tags and associated protection controls” would address that alternative cause, not the condition in this question: the data lineage from source tables to derived metrics is undocumented or not inspected.
“Apply an appropriate row access policy using governed region mappings and role context” responds to this separate finding: the table lacks an effective row-level access rule bound to regional entitlement. This question instead needs “Trace the supported lineage and relevant SQL transformations before changing warehouse settings”, so the alternative does not meet the stated condition.
The applied dynamic masking policy or effective role conditions do not protect that column. “Attach or correct an appropriate masking policy and validate it against permitted roles” applies to that separate problem. The observed case is a dashboard suddenly reports lower revenue after a transformation change and the team cannot identify upstream data dependencies; choosing this alternative would address the wrong failure mode.