A Snowflake user is attempting to query a table named 'CUSTOMERS within the SALES DB.PUBLIC' schema. However, they are receiving an error indicating insufficient privileges. Assuming the user has been

Question

Options

• ASELECT privilege on the 'CUSTOMERS' table.
• BUSAGE privilege on the `PUBLIC' schema.
• CREAD privilege on the 'CUSTOMERS' table.
• DUSAGE privilege on the 'SALES DB' database and SELECT privilege on the 'CUSTOMERS table.
• EUSAGE privilege on the FIJBLIC' schema and SELECT privilege on the 'CUSTOMERS table.

• A
  2% (1)
• B
  2% (1)
• C
  8% (4)
• D
  11% (6)
• E
  77% (41)

Explanation

In Snowflake, accessing a table requires traversing the full object hierarchy: database → schema → table. Since the user already has USAGE on the database, the two missing pieces are USAGE on the PUBLIC schema (to navigate into it) and SELECT on the CUSTOMERS table (to actually read rows) - exactly what option E provides.

Why the distractors fail:

• A - SELECT on the table alone is insufficient; without USAGE on the schema, Snowflake won't let the user resolve the table's path.
• B - Schema USAGE alone lets you "see" the schema but grants no ability to read table data; SELECT is still required.
• C - READ is not a valid Snowflake privilege; Snowflake uses SELECT for querying tables. This is a pure distractor.
• D - Re-granting USAGE on the database the user already has adds nothing, and critically it omits USAGE on the schema, leaving the schema layer unresolved.

Memory tip: Think of Snowflake privileges like locked doors in a hallway - you need a key for each door: Database (USAGE) → Schema (USAGE) → Table (SELECT). The question tells you the first door is already open, so you only need the schema key and the table key (option E).

No community discussion yet for this question.