Which of the following are characteristics of how row access policies can be applied to external tables? (Choose three.)

Question

Options

• AAn external table can be created with a row access policy, and the policy can be applied to the
• BA row access policy can be applied to the VALUE column of an existing external table.
• CA row access policy cannot be directly added to a virtual column of an external table.
• DExternal tables are supported as mapping tables in a row access policy.
• EWhile cloning a database, both the row access policy and the external table will be cloned.
• FA row access policy cannot be applied to a view created on top of an external table.

• A
  75% (24)
• D
  16% (5)
• E
  3% (1)
• F
  6% (2)

Explanation

Snowflake external tables have specific behaviors with row access policies. Option A is correct: a row access policy can be specified at the time of external table creation (CREATE EXTERNAL TABLE ... WITH ROW ACCESS POLICY) and can also be added or replaced on an existing external table using ALTER TABLE. Option B is correct: the VALUE column is the single implicit column that stores the raw parsed data in an external table, and a row access policy can be applied to it. Option C is correct: virtual columns in an external table are derived expressions from the VALUE column (e.g., VALUE:field::type), and Snowflake does not allow row access policies to be attached directly to these virtual columns - the policy must be on the VALUE column or the table itself. Option D is incorrect: external tables are NOT supported as mapping tables inside a row access policy definition due to their read-only and external nature. Option E is incorrect: external tables cannot be cloned because cloning only applies to internal Snowflake storage - the underlying external data is outside Snowflake's control. Option F is incorrect: row access policies can be applied to views built on external tables.

No community discussion yet for this question.