SOL-C01 · Question #184
You have enabled auto-ingest using Snowpipe for a stage containing image files. You want to create a Directory Table to track the metadata of these image files (name, size, last modified time). After
The correct answer is C. Set the 'directoryTableAutorefreshEnabled' parameter to TRUE at the account level using 'ALTER. In Snowflake, Directory Tables track metadata for files stored in stages. By default, they do not automatically refresh when new files are added. To enable automatic refreshing at the account level, you set the 'directoryTableAutorefreshEnabled' parameter to TRUE using ALTER ACCO
Question
You have enabled auto-ingest using Snowpipe for a stage containing image files. You want to create a Directory Table to track the metadata of these image files (name, size, last modified time). After creating the Directory Table, you notice that it is not automatically updated when new image files are added to the stage. What steps should you take to ensure the Directory Table is automatically updated when new image files are added to the stage?
Options
- ASchedule a task to periodically refresh the Directory Table using the ALTER DIRECTORY
- BConfigure an event notification service (e.g., AWS SQS) to trigger a Snowpipe load whenever a
- CSet the 'directoryTableAutorefreshEnabled' parameter to TRUE at the account level using 'ALTER
- DDirectory Tables do not automatically refresh. You must always manually refresh them using the
- ESet the 'directoryTableAutorefreshEnabled' parameter to TRUE when creating or altering the stage
How the community answered
(34 responses)- A9% (3)
- C82% (28)
- D6% (2)
- E3% (1)
Explanation
In Snowflake, Directory Tables track metadata for files stored in stages. By default, they do not automatically refresh when new files are added. To enable automatic refreshing at the account level, you set the 'directoryTableAutorefreshEnabled' parameter to TRUE using ALTER ACCOUNT. This global setting enables event-driven auto-refresh behavior for Directory Tables across the account, leveraging the event notification infrastructure (such as AWS SQS) that is already in place for Snowpipe. Option A (a scheduled task) works but is polling-based rather than event-driven, adding latency. Option D is incorrect because auto-refresh can be enabled. Option E also mentions stage-level configuration, but the account-level setting in option C is what controls this behavior globally.
Topics
Community Discussion
No community discussion yet for this question.