A Snowflake Native App developer wants to externalize certain configuration values so that a consumer can adjust the app's behavior without modifying the app's code directly. Which of the following methods is the MOST appropriate for achieving this using the Snowflake Native App Framework?

• A. Defining parameters in the manifest file and using them within the application code.
• B. Storing the configuration values in a separate Snowflake table within the consumer account.
• C. Hardcoding the configuration values directly into the SQL code.
• D. Using dynamic SQL to modify the application code at runtime based on environment variables.
• E. Using Snowflake variables and setting them at the session level.

You are developing a Snowflake Native Application that processes financial transactions. You want to implement a robust version management strategy. You have created versions 'v1_0', 'V1 _ 1', and 'v2 Version has a critical bug fix and needs to be prioritized for immediate deployment to specific consumer accounts that reported issues, while contains significant feature enhancements and is undergoing phased rollout. What is the most efficient and secure way to manage these releases in Snowflake?

• A. Option E
• B. Option A
• C. Option B
• D. Option D
• E. Option C

A provider is developing a Snowflake Native Application that uses a managed task to perform critical data transformations. The provider wants to ensure the managed task is only ever executed when the application is in a 'RUNNING' state. They have defined a secure view which returns a single row and a column named 'status' of type VARCHAR. The provider intends to use the 'EXECUTE MANAGED TASK' privilege in conjunction with a user-defined function (UDF) to control task execution. Which of the following approaches, utilizing a UDF and the 'EXECUTE MANAGED TASK' privilege, will correctly and securely prevent the managed task from running unless the application status is 'RUNNING'? Assume the UDF is created with the 'SECURE keyword.

• A. Create a UDF that returns TRUE only if 'SELECT status FROM app_db.app_schema.app_status_view' returns 'RUNNING'. Then, in the managed task definition, use the WHEN clause with the UDF. Grant 'EXECUTE MANAGED TASK' on the managed task and 'SELECT on the to the application role.
• B. create a UDF that executes if 'SELECT status FROM app_db.app_schema.app_status_view' does not return 'RUNNING'. Grant 'EXECUTE MANAGED TASK' on the managed task to the application role. Do not grant SELECT on the view.
• C. Create a UDF that executes ' if 'SELECT status FROM app_db.app_schema.app_status_view' returns 'RUNNING'. Grant 'EXECUTE MANAGED TASK' on the managed task to the application role. Grant SELECT on the view.
• D. Create a UDF that executes 'SYSTEM$TASK SUSPEND('app_db.app_schema.my_managed_task'Y if 'SELECT status FROM app_db.app_schema.app_status_view' does not return 'RUNNING', otherwise executes Grant 'EXECUTE MANAGED TASK' on the managed task to the application role. Grant 'SELECT on the view.
• E. Create a UDF that returns TRUE only if 'SELECT status FROM app_db.app_schema.app_status_view' returns 'RUNNING'. Then, in the managed task definition, use the WHEN clause with the UDF. Grant 'EXECUTE MANAGED TASK' on the managed task to the application role. Do not grant SELECT on the view.

A data provider wants to distribute a Snowflake Native Application that includes a secure view 'PROVIDER DB.PUBLIC.SALES SUMMARY' which aggregates sales dat a. They want to allow consumers of the application to query this view, but prevent them from accessing the underlying base tables. Which minimum set of privileges must be granted on the 'SALES SUMMARY view to enable this, assuming the application role is 'APP ROLE and the installing account doesn't want to use 'imported privileges' ?

• A. GRANT SELECT ON VIEW PROVIDER DB.PUBLIC.SALES SUMMARY TO SHARE WITH APP ROLE;
• B. GRANT USAGE ON DATABASE PROVIDER DB TO ROLE APP ROLE; GRANT USAGE ON SCHEMA PROVIDER DPUBLIC TO ROLE APP ROLE; GRANT SELECT ON VIEW PROVIDER DB.PUBLIC.SALES SUMMARY TO ROLE APP ROLE;
• C. GRANT ALL PRIVILEGES ON VIEW PROVIDER DB.PUBLISALES SUMMARY TO ROLE APP ROLE;
• D. GRANT REFERENCES ON VIEW PROVIDER DB.PUBLIC.SALES SUMMARY TO ROLE APP ROLE;
• E. GRANT SELECT ON VIEW PROVIDER DB.PUBLIC.SALES SUMMARY TO ROLE APP ROLE;

You are developing a Snowflake Native Application that processes sensitive dat a. During the application lifecycle management, including version updates, what steps should you take to ensure the data security and privacy of the consumers' data, especially considering that your development team might need access to a subset of the data for testing?

• A. Use Snowflake's data classification features to identify sensitive data and implement row-level security to restrict access to the development team.
• B. Grant the development team direct access to the consumer's data warehouse to facilitate testing. Ensure proper auditing is enabled.
• C. Create a separate Snowflake account for testing and populate it with synthetic data that mimics the structure and characteristics of the consumer's data.
• D. Utilize Snowflake's external functions to process the data in a secure enclave outside of Snowflake, minimizing the risk of data exposure. Ensure external functions called are encrypted.
• E. Implement data masking and anonymization techniques to create a sanitized test dataset derived from the consumer's data. Provide the development team with access only to the masked data, via data sharing from the producer to consumer account.