A Data Engineer is designing a solution that will send report files generated and stored in a Snowflake stage to a customer, using email. The files can only be available for download for 60 minutes…

Question

Options

• AShare data using a scoped URL and the SYSTEM$SEND_EMAIL function.
• BShare data using pre-signed URL and the function.
• CShare data using a stage file URL and the SYSTEM$SEND_EMAIL function.
• DShare data using a scoped URL and write a custom Python script to send the email.

• A
  4% (1)
• B
  74% (17)
• C
  17% (4)
• D
  4% (1)

Explanation

Pre-signed URLs are specifically designed for time-limited, unauthenticated external access - you can set an expiration window (e.g., 60 minutes), after which the URL becomes invalid, perfectly matching the requirement for obsolete files. Combined with SYSTEM$SEND_EMAIL, this delivers a fully native Snowflake solution without custom code.

A is wrong because scoped URLs require the recipient to have Snowflake authentication - an external customer almost certainly won't have Snowflake credentials, making this impractical for customer-facing delivery.

C is wrong because stage file URLs (permanent/file URLs) do not expire - they remain valid indefinitely as long as the file exists, directly violating the 60-minute availability requirement.

D is wrong on two counts: scoped URLs again require Snowflake authentication, and writing a custom Python email script is unnecessary when SYSTEM$SEND_EMAIL already provides this capability natively.

Memory tip: Think "Pre-signed = Pre-set expiry, no password needed." Whenever a question involves sharing Snowflake staged files externally with a time limit, pre-signed URL is your answer - scoped URLs lock the door (require auth), stage URLs leave it open forever, but pre-signed URLs set a timer on the key.

No community discussion yet for this question.