How can a directory table be used when working with unstructured data? (Choose two.)

Question

Options

• AFile access URLs can be shared with collaborators and partners.
• BData stored in an external stage can be queried as if the data was inside a table in Snowflake.
• CAll unstructured files on a stage can be queried using the SELECT * FROM
• DAll unstructured files on a stage can be queried using the
• EA directory table can be joined with other tables to produce a view of unstructured data that

• A
  89% (24)
• B
  4% (1)
• D
  7% (2)

Explanation

Option A is correct because directory tables store metadata for staged files - including a FILE_URL column - which generates scoped or pre-signed URLs that can be shared externally with collaborators and partners for secure file access.

Option E is correct because a directory table is a standard Snowflake table-like object that can be joined with other structured tables (e.g., a customer table joined to an invoice PDF directory table), enabling you to build views or queries that combine unstructured file metadata with relational data.

Option B is wrong because it describes external tables, not directory tables. External tables let you query raw data in an external stage as if it were a Snowflake table; directory tables only expose file metadata (URL, size, ETag, etc.), not the file contents.

Options C and D are wrong because a directory table does not expose the content of unstructured files - SELECT * returns metadata rows (one per file), not file data itself. You cannot query the actual bytes of an image or PDF this way.

Memory tip: Think of a directory table as a card catalog in a library - it tells you where files are and how to get them (URLs, for option A) and can be cross-referenced with other data (joins, for option E), but it doesn't let you read the books directly (ruling out B, C, D).

No community discussion yet for this question.