You're packaging a Snowflake Native App and need to define the minimum Snowflake version required for installation. You also want to specify an optional PARAMETER that users can configure during installation to customize the app's behavior. Which section of the manifest file allows you to achieve this?

• A. The 'deployment.sql' file where you define the app's deployment settings.
• B. The 'metadata.json' file, which only contains descriptive information about the app.
• C. The 'setup.sqrl' file, where you define SQL commands to be executed during app installation.
• D. The 'application.yaml' file under the 'configuration' section, where you can specify and define PARAMETERS with their types and default values.
• E. The 'privileges.sql' file, where you define the privileges required by the application.

You are developing a Snowflake Native App that requires accessing sensitive user data within the consumer's account. To ensure data privacy and security, you need to implement appropriate access controls. Which of the following approaches is the MOST secure and recommended way to grant your app access to this data, assuming the data is stored in a table named 'user_data' ?

• A. Using a stored procedure with 'EXECUTE AS CALLER that accesses the 'user_data' table. Grant 'EXECUTE privilege on the stored procedure to the application role.
• B. Granting 'SELECT privilege directly on the 'user_data' table to the application role provided by Snowflake Native App Framework.
• C. Creating a custom role in the consumer account with 'SELECT privilege on the 'user_data' table and granting that role to the application.
• D. Granting 'USAGE privilege on the 'user_data' table directly to the application role provided by Snowflake Native App Framework.
• E. Defining a secure view that filters the table based on the application role and granting 'SELECT privilege on the secure view to the application role provided by Snowflake Native App Framework.

You have successfully deployed your Snowflake Native Application Package to an external stage (AWS S3), but consumers are reporting they are not receiving updates after you deploy new versions to the external stage. You have verified that the IAM role, Snowflake integration, and S3 bucket policy are correctly configured. What steps should you take to troubleshoot and resolve this issue?

• A. Consumers must manually refresh their installed application instance using the command 'ALTER APPLICATION REFRESH;' after a new package version is deployed.
• B. Grant the APPLICATION ROLE to the SNOWFLAKE DEPLOYMENT role on the application package. This allows the deployment process to automatically update the consumer instances.
• C. Verify that the SNOWFLAKE DEPLOYMENT role has been granted ownership of the Integration object used for accessing the external stage.
• D. Ensure the S3 bucket has versioning enabled. Snowflake relies on S3 versioning to detect new application package versions.
• E. Execute the 'ALTER APPLICATION PACKAGE REFRESH' command after each deployment to the external stage. This explicitly informs Snowflake to refresh the application package metadata.

You are developing a Snowflake Native Application that utilizes a custom stage for storing large intermediate datasets during processing. Your CI/CD pipeline involves automated testing in a dedicated testing account. To ensure proper isolation and prevent interference with production data, how should you configure the stage path within your application package version definition, considering the stage name might differ between development and test environments?

• A. Utilize Snowflake's and 'CURRENT functions in conjunction with conditional logic within the application to derive the stage path based on the environment.
• B. Use a Snowflake Secret to store the stage path and retrieve it dynamically during application installation. The secret's value will be environment-specific.
• C. Employ a versioned configuration file (e.g., YAML) within the application package. The CI/CD pipeline should replace placeholders in the configuration file with environment-specific stage paths before creating the version.
• D. Define the stage path as a parameter in the application installation script. When installing the application in each environment, pass the correct stage path as an argument.
• E. Hardcode the stage name and path directly within the setup script of the version. This approach is simple and ensures consistent access across environments.