Question 830
A new JSON event contains an unexpected nested field, and an ingestion pipeline silently discards it. Which long-term safeguard BEST reduces recurrence?
Explanation
Correct Answer
Alert on rescued-column counts and unexpected schema changes. This is the most directly relevant preventive control because source fields outside the expected schema need explicit evolution or rescue handling. A concrete acceptance check is: A test new field is captured and promoted only after schema review. To reduce recurrence: Alert on rescued-column counts and unexpected schema changes.
Incorrect Answers
Snapshot completion does not guarantee subsequent live change capture. Here the important technical distinction is that source fields outside the expected schema need explicit evolution or rescue handling.
Direct cloud object credentials grant broader storage access than the intended shared table contract. The reported failure instead depends on this fact: source fields outside the expected schema need explicit evolution or rescue handling.
A change log represents operations on entities, not independent final-state records. That consideration does not remove the current constraint: source fields outside the expected schema need explicit evolution or rescue handling.