Question 840
Monthly ORC archives have a historical schema while recent CSV drops use a different column name. Which prevention step most appropriately addresses the root cause?
Explanation
Correct Answer
Store schema mappings and validate each new feed version. This is the most directly relevant preventive control because differing source names and types need deliberate reconciliation before union operations. A concrete acceptance check is: Both months populate the same contracted downstream columns. To reduce recurrence: Store schema mappings and validate each new feed version.
Incorrect Answers
Unsupported pushdown can transfer far more data than the result requires. For the observed behavior, differing source names and types need deliberate reconciliation before union operations.
Ephemeral local state is lost when compute is replaced. The controlling issue in this question is that differing source names and types need deliberate reconciliation before union operations.
Direct cloud object credentials grant broader storage access than the intended shared table contract. The reported failure instead depends on this fact: differing source names and types need deliberate reconciliation before union operations.