Snowflake recommends relying more on which endpoint to avoid rate limits when monitoring data loads?

• A. loadHistoryScan
• B. insertReport
• C. getReport
• D. historyScan

Answer: (B)

Relying on push-style reporting rather than constant polling keeps API usage predictable and helps avoid rate limits when tracking load progress. The insertReport endpoint is built for ingestion pipelines to push the results of each load operation into Snowflake’s monitoring system. By emitting a report as soon as a file is loaded, you provide timely status updates without repeatedly querying Snowflake for status, which reduces the volume of read requests and lowers the chance of hitting rate limits.

In contrast, the other endpoints are pull-based. Getting a report or scanning history requires you to poll Snowflake to retrieve status or history, which can generate a high volume of requests during peak loads and increase rate-limit risk. Therefore, using insertReport to push load status is the most scalable, rate-limit-friendly approach.