Question 360
Marshfield Bank processes payments and confidential client information under a least-privilege data policy. The investigation finds: A supported source database needs managed change-based ingestion but a custom script reloads its entire multi-terabyte table hourly. The team reports that the correction is complete. Which result BEST verifies that the specific issue was resolved?
Explanation
Correct Answer
Only the initial full load is followed by verified changes in later ingestion cycles. The observation provides evidence that the proposed fix (Use Lakeflow Connect with an eligible incremental or CDC connector and appropriate cursor or log configuration.) addressed the reported issue (A supported source database needs managed change-based ingestion but a custom script reloads its entire multi-terabyte table hourly.) for Marshfield Bank and its payments and confidential client information. It verifies an observable outcome instead of relying only on a completed task ticket.
Incorrect Answers
Replaying the ingestion task does not introduce duplicate destination business keys. This is suitable evidence for another condition (An ingestion pipeline replays a source's old rows after restart and fails to distinguish previously processed cursor positions.) after a different response (Maintain a supported Lakeflow connector checkpoint or monotonically increasing cursor under the connector's documented rules.). For Marshfield Bank, it does not prove the required result: Only the initial full load is followed by verified changes in later ingestion cycles.
Test events appear in the streaming source and progress metrics reflect the expected consumed sequence. This is suitable evidence for another condition (An Azure Event Hubs source must feed a Databricks stream but the team treats it as a local directory of files.) after a different response (Use a supported Spark connector or ingestion path for Azure Event Hubs with its connection and offset configuration.). For Marshfield Bank, it does not prove the required result: Only the initial full load is followed by verified changes in later ingestion cycles.
Historical rows remain intact and the new daily records are present exactly once. This is suitable evidence for another condition (A batch pipeline needs to write new daily records without overwriting historical rows, but it uses overwrite mode on its entire destination table.) after a different response (Choose an append or keyed merge write matching the intended incremental update contract.). For Marshfield Bank, it does not prove the required result: Only the initial full load is followed by verified changes in later ingestion cycles.