You have a Python script that uses Snowpark to connect to Snowflake. You want to ensure that the connection parameters, such as account identifier, username, password, and database, are securely manag

Question

Options

• AStore the connection parameters in a plain text file in a secure location on the server.
• BUtilize environment variables to store the connection parameters and access them from the Python
• CUse Snowflake's Secret object to store credentials, and use Snowpark to retrieve these secrets for
• DStore the connection parameters in a configuration file encrypted with a strong encryption
• EHardcode the parameters within the Python script, but obfuscate them using Base64 encoding.

• A
  12% (3)
• B
  84% (21)
• E
  4% (1)

Explanation

The goal is to avoid hardcoding sensitive credentials in source code. Option B (environment variables) is a widely accepted secure practice: credentials are set at the OS or container level, read at runtime, and never appear in the codebase. Option C (Snowflake Secret objects) is the native Snowflake approach-secrets are stored encrypted in Snowflake and retrieved programmatically by the Snowpark session, keeping credentials out of the script entirely. Option D (encrypted configuration file) adds a layer of security over a plain text file, making it a reasonable approach when properly implemented with key management. Option A (plain text file) is explicitly insecure-it provides no protection if the file is accessed. Option E (Base64 encoding) is not encryption; it is trivially reversible and provides zero security, making it a dangerous false sense of security.

No community discussion yet for this question.