Question 240
Seabright Municipal Works processes public-sector records and operations with controlled access to customer records. The investigation finds: An analyst cannot tell which downstream reports will change when an important source column is renamed. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
The impact review identifies the reports and pipelines using the affected source field. The observation provides evidence that the proposed fix (Inspect Unity Catalog lineage and downstream dependencies before applying the schema change.) addressed the reported issue (An analyst cannot tell which downstream reports will change when an important source column is renamed.) for Seabright Municipal Works and its public-sector records and operations. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
The audit role sees the expected masked values and the approved role's intended access is preserved. This is suitable evidence for another condition (An auditor can view customer identifiers but policy forbids exposing direct identity values to that role.) after a different response (Configure a suitable Unity Catalog column mask for the protected identity field.). For Seabright Municipal Works, it does not prove the required result: The impact review identifies the reports and pipelines using the affected source field.
Catalog metadata identifies the restricted fields and the correct access policy is enforced for a test reader. This is suitable evidence for another condition (A table contains both public and restricted fields and downstream users cannot find a clear catalog classification.) after a different response (Apply accurate table and column classifications with an accountable review and governance policy.). For Seabright Municipal Works, it does not prove the required result: The impact review identifies the reports and pipelines using the affected source field.
A controlled pipeline run produces the expected upstream and downstream lineage relationships. This is suitable evidence for another condition (A table lineage graph is incomplete because important pipelines write outside the governed catalog and the team asserts all dependencies are known.) after a different response (Review supported lineage capture and route eligible workloads through Unity Catalog-governed objects.). For Seabright Municipal Works, it does not prove the required result: The impact review identifies the reports and pipelines using the affected source field.