Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake ARA-C01 Exam - Topic 5 Question 70 Discussion

Posted by Melodie on Aug 14, 2026 at 12:26 AM

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

Suggested Answer: D

Snowpipe is a service that automates and optimizes the loading of data from external stages into Snowflake tables. Snowpipe uses a queue to ingest files as they become available in the stage.Snowpipe also provides REST endpoints to load data and retrieve load history reports1.

The loadHistoryScan endpoint returns the history of files that have been ingested by Snowpipe within a specified time range.The endpoint accepts the following parameters2:

pipe: The fully-qualified name of the pipe to query.

startTimeInclusive: The start of the time range to query, in ISO 8601 format. The value must be within the past 14 days.

endTimeExclusive: The end of the time range to query, in ISO 8601 format. The value must be later than the start time and within the past 14 days.

recentFirst: A boolean flag that indicates whether to return the most recent files first or last. The default value is false, which means the oldest files are returned first.

showSkippedFiles: A boolean flag that indicates whether to include files that were skipped by Snowpipe in the response. The default value is false, which means only files that were loaded are returned.

The loadHistoryScan endpoint can be used to keep a log of data load history by calling it periodically with a suitable time range. The best option among the choices is D, which is to call loadHistoryScan every 10 minutes for a 15-minute time range. This option ensures that the endpoint is called frequently enough to capture the latest files that have been ingested, and that the time range is wide enough to avoid missing any files that may have been delayed or retried by Snowpipe.The other options are either too infrequent, too narrow, or use the wrong endpoint3.


1: Introduction to Snowpipe | Snowflake Documentation

2: loadHistoryScan | Snowflake Documentation

3: Monitoring Snowpipe Load History | Snowflake Documentation

Get Premium ARA-C01 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
18 comments · newest first
CA
Carmen 2 days ago
Option C feels too short. Eight minutes is risky.
MA
Matthew 8 days ago
I prefer option B. More frequent checks seem safer.
TH
Theola 13 days ago
I think option A is the best. Regular updates are key.
BR
Brunilda 18 days ago
B ensures we don’t miss anything important.
EL
Eleni 23 days ago
A gives a good balance of frequency and data.
LU
Lucina 28 days ago
D is too long. 10 minutes is a stretch for logs.
ME
Merilyn 1 month ago
C sounds reasonable, but 8 minutes is odd.
DE
Demetra 1 month ago
I prefer B. Every minute seems more efficient.
DA
Dahlia 1 month ago
I think option A is the best. Regular updates are key.
LA
Lamonica 2 months ago
B) is solid for maximum data retrieval!
TO
Tora 2 months ago
C) seems too short, 8 minutes is cutting it close.
MA
Mabel 2 months ago
Wait, can you really get 10,000 entries every 20 minutes?
BE
Benton 2 months ago
I think D) makes more sense for broader coverage.
DA
Dalene 2 months ago
A) is the best choice for frequent updates!
RO
Rosio 2 months ago
I think D could be a good choice, but I'm uncertain if 10 minutes is the optimal interval for the load history.
KA
Kasandra 3 months ago
I feel like option C might be correct since 8 minutes seems reasonable for a short time range, but I can't remember the specifics.
LO
Lorrine 3 months ago
I remember practicing with loadHistoryScan, but I can't recall if it should be every minute or if that's too frequent.
GA
Garry 3 months ago
I think option A sounds familiar, but I'm not sure if 20 minutes is the right interval.
0/2000 characters

Save Cancel