SOL-C01 · Question #190
You are designing a Snowflake UDF to parse log files. The UDF needs to accept the log file content as a string argument and a configuration parameter that specifies the log format. Which of the…
The correct answer is E. Store the log format in a Snowflake secret and retrieve it using the SYSTEM$GET SECRET. Option E is the best solution. Storing the log format in a Snowflake secret offers the most secure and manageable approach. Secrets are designed to store sensitive configuration data, and SYSTEM$GET_SECRET ensures that the UDF can access the format without embedding it directly…
Question
You are designing a Snowflake UDF to parse log files. The UDF needs to accept the log file content as a string argument and a configuration parameter that specifies the log format. Which of the following approaches is MOST efficient and allows for easy updates to the log format without redeploying the UDF?
Options
- APass the log format as a string argument directly to the UDF. Parse the string within the UDF to
- BStore the log format in a separate table and use a Snowflake lookup within the UDF to retrieve the
- CUse a stage to store the log format definition as a JSON file. Read the file content from the stage
- DStore the log format in a named stage and create a function to retrieve the format from the stage
- EStore the log format in a Snowflake secret and retrieve it using the SYSTEM$GET SECRET
How the community answered
(20 responses)- B5% (1)
- C15% (3)
- D10% (2)
- E70% (14)
Explanation
Option E is the best solution. Storing the log format in a Snowflake secret offers the most secure and manageable approach. Secrets are designed to store sensitive configuration data, and SYSTEM$GET_SECRET ensures that the UDF can access the format without embedding it directly in the code. This allows for updates without redeploying the UDF. Options A, B, C, and D have drawbacks. Passing as a string (A) is inefficient and less secure. Table lookup (B) adds overhead. External tables/stages (C and D) are more complex and might not be necessary for simple configuration data.
Topics
Community Discussion
No community discussion yet for this question.