You are developing a Snowflake Native Application that needs to securely access data in a consumer's account. The application requires the consumer to grant specific privileges to a custom role created and managed within the application package. Which of the following steps are absolutely essential for correctly configuring the application package to ensure this secure data access, and how should the setup script handle the privilege granting?

• A. Utilize a service account to access the data, providing the service account's credentials as part of the application setup. The application will then use the service account to access the consumer's data.
• B. Create a share from the provider account to the consumer account, granting the consumer read access to the application package's data. Then, use a setup script to grant ownership of the data to the application role after installation.
• C. Define the required privileges in the application package manifest (snowflake.yml). Ensure that the setup script includes commands to grant the specific privileges on the consumer's data to the application's custom role, using 'GRANT ON TO ROLE within an EXECUTE IMMEDIATE statement in the setup script. The setup script should also define the application role.
• D. Grant the 'USAGE privilege on the consumer's database and schema to the application's role within the setup script. This implicitly allows the application to read all data within that schema.
• E. The consumer must manually grant the necessary privileges to the application's role after the application is installed, as the application package cannot automatically modify the consumer's security settings.

You are developing a Snowflake Native Application that uses a custom Python handler to perform data transformations. This handler requires access to a third-party Python package not included in the standard Anaconda environment provided by Snowflake. To ensure the application functions correctly on consumer accounts, what steps must you take? (Select all that apply)

• A. Create a stage and upload the python package(s). Then in the Python UDF code, reference the python package from the stage.
• B. Use the SALTER FUNCTION' command after installation on the consumer's account to add the required Python package to the function definition. This option is not possible.
• C. Instruct consumers to manually install the necessary Python package using 'pip install' in a Snowflake Snowpark Python worksheet after installing the application.
• D. Specify the Python package as a dependency in the application's setup script using a install command.
• E. Include the required Python package in the application package as a zip file using the 'CREATE or REPLACE FUNCTION' command with the 'imports' clause.

Consider the following setup script snippet for a Snowflake Native Application:

What is the primary purpose of the 'WHERE NOT EXISTS' clause in the 'INSERT' statement within this setup script?

• A. To ensure that the 'INSERT statement only executes if the table is empty.
• B. To prevent duplicate rows with the same 'param_name' from being inserted into the 'app_data.configuration' table during subsequent installations or upgrades of the application.
• C. To optimize the performance of the 'INSERT statement by avoiding unnecessary insertions when the configuration parameter already exists.
• D. To handle potential errors that may occur if the 'api_endpoint' parameter is already defined in the consumer's account.
• E. To guarantee that the 'app_data.configuration' table always contains the latest version of the 'api_endpoint' parameter, overwriting any existing value.

Consider a Snowflake Native App that dynamically creates tables within the consumer's account using stored procedures. The application role is 'APP ROLE. After installation, the application needs to automatically grant 'SELECT privilege on all newly created tables in a specific schema CAPP DATA SCHEMA) to a consumer-defined role (CONSUMER ROLE). Which of the following approaches is the most secure and efficient way to achieve this? Assume the application cannot know the names of tables in advance.

• A. Include code in the stored procedure that creates the table to immediately grant SELECT privilege to CONSUMER_ROLE.
• B. Manually create tables outside of the application and grant the privileges.
• C. Grant future grants on the schema for 'SELECT privilege to the 'CONSUMER_ROLE when tables are created.
• D. Use a task that runs periodically to discover new tables and grant SELECT privilege to CONSUMER_ROLE.
• E. Grant OWNERSHIP on to the APP_ROLE with the GRANT OPTION, then have the application create the tables. The CONSUMER ROLE will then have implicit access.

You are developing a Snowflake Native Application that utilizes Snowpark Container Services (SPCS). Your application requires a Compute Pool configured with autoscaling capabilities to handle fluctuating workloads. However, you want to minimize costs when the application is idle. Which of the following considerations are MOST important when defining the 'MIN NODES' and 'MAX NODES' parameters for your Compute Pool, along with the 'AUTO RESUME setting?

• A. Setting to 0 allows the Compute Pool to scale down completely when idle, eliminating costs. 'AUTO_RESUME should be set to TRUE to automatically start the pool when a new request is received.
• B. The optimal configuration depends on the balance between cost and performance. A higher 'MIN_NODES' value provides faster initial response times but incurs higher costs when idle. 'AUTO RESUME should be set to TRUE if you want the pool to automatically restart based on incoming requests.
• C. Compute Pool autoscaling is managed entirely by the underlying container orchestration system and Snowflake only provides basic resource allocation. The 'MIN NODES' and 'MAX NODES parameters are advisory only.
• D. The 'AUTO_RESUME parameter is irrelevant as the compute pool automatically scales based on current workload. should be set to the expected average workload.
• E. Setting to a non-zero value ensures that some resources are always available, leading to faster response times for initial requests. 'AUTO RESUME' should be set to FALSE to prevent unnecessary resource usage.