Which Snowflake feature allows a user to substitute a randomly generated identifier for sensitive data, in order to prevent unauthorized users access to the data, before loading it into Snowflake?

The correct answer is A. External Tokenization. External Tokenization (A) is the Snowflake feature that enables substituting sensitive values (such as credit card numbers, SSNs, or other PII) with randomly generated tokens BEFORE the data is loaded into Snowflake. This is done via an API integration with a third-party…

Data Protection and Data Sharing

Question

Options

AExternal Tokenization
BExternal Tables
CMaterialized Views
DUser-Defined Table Functions (UDTF)

How the community answered

(27 responses)

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

Explanation

External Tokenization (A) is the Snowflake feature that enables substituting sensitive values (such as credit card numbers, SSNs, or other PII) with randomly generated tokens BEFORE the data is loaded into Snowflake. This is done via an API integration with a third-party tokenization provider (e.g., Protegrity, Voltage). Only authorized roles can detokenize (retrieve the original value) by calling an external function that connects back to the tokenization service. This is distinct from Dynamic Data Masking, which masks data at query time after it is already stored. External Tables (B) read data from external stages but perform no masking. Materialized Views (C) are pre-computed query results. UDTFs (D) are table-valued functions - not a data protection mechanism.

Topics

#External Tokenization#Data Protection#Sensitive Data#Data Security

Community Discussion

No community discussion yet for this question.

Full COF-C02 Practice