You are developing a Snowflake Native Application that manages customer accounts. In version 1.0, you had a table named 'CUSTOMER_ACCOUNTS with columns 'ACCOUNT D', 'CUSTOMER NAME, and 'EMAIL'. You are now releasing version 2.0, which requires adding a new column 'PHONE NUMBER to the 'CUSTOMER ACCOUNTS table, but you need to ensure backward compatibility and allow seamless upgrades for existing installations. Which of the following approaches within the 'setup.sqr file is the MOST robust and reliable to implement this schema change without disrupting existing users?

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

You are designing a Snowflake Native Application that requires managing application roles and permissions. Which of the following best practices should be followed regarding application roles and permissions in a Snowflake Native Application?

• A. Define granular application roles with specific permissions, and provide documentation to the consumer on how to grant these roles to their users.
• B. Use the 'EXECUTE AS OWNER clause for all stored procedures to avoid granting explicit privileges to the application roles.
• C. Grant all necessary privileges to the 'APPLICATION' role during setup, as this simplifies permission management for consumers.
• D. Avoid using application roles altogether and rely solely on the consumer's existing roles and permissions.
• E. Bundle all application logic within a single stored procedure owned by the 'APPLICATION' role.

A Snowflake Native Application developer, Bob, is using Snowsight to manage access to the application. He has created a custom role, , and wants to grant this role the ability to grant and revoke privileges on all objects within the application's schema, app_data'. Which of the following Snowsight actions (or sequence of actions) is the MOST effective and secure way to achieve this?
(Assume Bob is logged in as a user with 'ACCOUNTADMIN' role).

• A. Grant the the 'APPLY MASKING POLICY privilege globally at the account level using Snowsight.
• B. In Snowsight, write and execute the following SQL command:
• C. Within Snowsight, navigate to the application database, select 'Grant Privileges', and grant the 'USAGE' privilege to the .
• D. Within Snowsight, navigate to the 'app_data' schema, select 'Grant Privileges', and grant the 'OWNERSHIP' privilege to the .
• E. Within Snowsight, navigate to the 'app_data' schema, select 'Grant Privileges', grant the 'USAGE privilege to the and then individually grant 'SELECT, 'INSERT, 'UPDATE' , and "DELETE privileges on each table and view within the schema.

A Native App provider has created an application package and wants to control the versions of the application available to different consumers. They need to ensure that a specific consumer account, 'CUSTOMER R, only has access to version '1.0' of the application. Which of the following steps are necessary to achieve this?

• A. When creating the authorization grant for for the APPLICATION ROLE, specify VERSION = '1.01.
• B. Create a new application package specifically for 'CUSTOMER A' and only include version '1.0' in that package.
• C. Specify the version '1.0' when creating the share object for 'CUSTOMER_A'.
• D. No specific steps are required. By default, consumers will automatically receive the latest version of the application.
• E. The provider must first create a new version of the application package containing only version 1 .C , and then create an authorization grant for the role to CUSTOMER A that includes version '1.0'

You are responsible for managing the pricing plans for your Snowflake Native Application listed on the Marketplace. You want to offer a 'Premium' tier that includes additional features and resources. To achieve this, you need to modify the listing to include this new pricing option. Which of the following steps are NECESSARY and in the CORRECT order to successfully add the 'Premium' tier to your application's listing, ensuring existing customers are not negatively impacted? (Choose two options in their proper order)

• A. 1. Update the listing on the Marketplace with the new pricing tier. 2. Ensure backward compatibility for existing customers by implementing logic in the application to detect their current tier and maintain existing functionality.
• B. 1. Update the Marketplace listing by adding the 'Premium' pricing tier with appropriate settings, but without modifying the application package. 2. Inform existing customers that the new pricing tier is available.
• C. 1. Create a new version of the application package in your provider account with the code changes supporting the 'Premium' features. 2. Update the Marketplace listing with the new version of the application and add the 'Premium' pricing tier with appropriate settings.
• D. 1. Test new Pricing in a Sandbox environment with few consumers. 2. Deploy the new version to the consumer accounts.
• E. 1. Modify the existing application package in place to include the code changes supporting the 'Premium' features. 2. Update the Marketplace listing with the modified application and add the 'Premium' pricing tier with appropriate settings.