Which statement accurately differentiates the loadHistoryScan and insertReport endpoints in Snowpipe?

• A. LoadHistoryScan views the history between two points in time, whereas the insertReport endpoint returns events for the last 10 minutes only
• B. InsertReport views the history between two points in time, whereas the loadHistoryScan endpoint returns events for the last 10 minutes only
• C. LoadHistoryScan provides metadata only; insertReport provides full event history
• D. Neither endpoint supports time-based history queries

Answer: (A)

Snowpipe uses two endpoints with distinct roles: one is for retrieving historical load activity over a specified time window, and the other is for posting ingestion events in real time, with responses focused on a recent, short window.

The loadHistoryScan endpoint is designed to let you view the load history between two points in time. You specify a start and end time, and the response returns the load operations that occurred within that interval. This makes it a true time-bounded history query.

The insertReport endpoint, on the other hand, is for reporting new ingestion events as they happen. It acts like a streaming feed of recent events, and its responses are limited to events from the last roughly ten minutes. It isn’t meant to retrieve broad historical history, but to confirm recent activity as events are reported.

So the statement that matches how these endpoints work is that loadHistoryScan views history between two times, while insertReport returns events for a recent short window (about the last 10 minutes). The other options misstate the time scope or the type of data each endpoint provides.