Snowflake recommends using the insertReport endpoint rather than the loadHistoryScan when working with Snowpipe. Which statement best explains why?

• A. Because an excessive usage of the loadHistoryScan tends to lead to API throttling (and it returns the error code 429).
• B. The loadHistoryScan endpoint is deprecated and will no longer be updated by Snowflake.
• C. Because the reports give more information
• D. The insertReport endpoint is used for real-time streaming only

Answer: (A)

The main idea is avoiding API throttling in Snowpipe. The loadHistoryScan endpoint is a heavier, read-oriented operation that scans load history. If you poll it frequently to monitor your loads, you can hit the API’s rate limits and receive a 429 Too Many Requests error, which disrupts ingestion. The insertReport endpoint is designed for reporting the result of a load as part of the ingestion workflow, so it doesn’t rely on the same heavy history-scanning pattern. Using insertReport helps keep the pipeline responsive and avoids triggering throttling, making it the recommended approach. The other options aren’t correct because loadHistoryScan isn’t stated as deprecated, and the benefit isn’t simply “more information” or “real-time streaming only.”