Answer: External Tokenization

The question asks about a Snowflake feature that substitutes sensitive data with randomly generated identifiers BEFORE loading data into Snowflake. External Tokenization (option A) is specifically designed for this purpose - it allows sensitive data to be tokenized externally before being loaded into Snowflake, replacing actual sensitive values with surrogate tokens. This prevents unauthorized access to the original sensitive data within Snowflake. The community discussion shows 100% consensus on answer A, with multiple users confirming this is correct and providing links to Snowflake documentation that specifically describes External Tokenization for this exact use case. Other options are less suitable: External Tables (B) are for querying external data without loading it, Materialized Views (C) are for pre-computed query results, and User-Defined Table Functions (D) are for custom transformations - none of these specifically handle tokenization of sensitive data before loading.

Author: LeetQuiz Editorial Team