How can the Snowpipe REST API be used to keep a log of data load history?

Question

Options

• ACall insertReport every 20 minutes, fetching the last 10,000 entries.
• BCall loadHistoryScan every minute for the maximum time range.
• CCall insertReport every 8 minutes for a 10-minute time range.
• DCall loadHistoryScan every 10 minutes for a 15-minutes range.

• A
  11% (4)
• B
  5% (2)
• C
  3% (1)
• D
  81% (30)

Explanation

The Snowpipe REST API provides two relevant endpoints for load history: insertReport and loadHistoryScan. To maintain a continuous, gap-free log, you must call with overlapping time windows. Option D - calling loadHistoryScan every 10 minutes for a 15-minute time range - creates a 5-minute overlap between consecutive calls, ensuring no load events fall through the cracks between polling intervals. Option C uses insertReport every 8 minutes for a 10-minute range (2-minute overlap), which is less reliable and insertReport has a max range of ~10 minutes with a 10,000-file cap. Option A (every 20 minutes for 10,000 entries) risks missing entries that fall outside the 10-minute max window. Option B is incorrect because calling loadHistoryScan every minute for the maximum range is unnecessarily frequent and wasteful. Option D's 10-minute poll with 15-minute window is the recommended pattern for reliable history logging.

No community discussion yet for this question.