Question 280
For a public-sector reporting unit, this issue must not recur: A COPY INTO load stops at a malformed record, but business wants a documented partial-load policy for valid rows. Which review control fits best?
Explanation
Correct Answer
Track rejected data and reconcile source counts after partial loads. This reduces recurrence of: COPY error-handling options alter treatment of malformed file rows and must match governance requirements. The verification should demonstrate: A controlled bad-row fixture yields the approved failure or continue behavior and observable load results.
Incorrect Answers
Validate representative nested arrays, nulls and malformed JSON before production loads. That safeguard is aimed at ANOTHER risk: An engineer sets JSON FILE FORMAT to CSV and loads a nested event record into a one-column raw table. It is less targeted than the control for: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.
Audit cloud trust relationships and allowed stage prefixes before onboarding new data. That safeguard is aimed at ANOTHER risk: A data lake S3 bucket is accessed using embedded access keys in a COPY script shared with contractors. It is less targeted than the control for: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.
Keep environment-specific account identifiers out of source-code assumptions. That safeguard is aimed at ANOTHER risk: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. It is less targeted than the control for: COPY error-handling options alter treatment of malformed file rows and must match governance requirements.