You are tasked with developing a Snowflake Native Application that allows consumers to securely access and analyze data from an external API. Your application needs to handle API authentication using OAuth 2.0, refresh tokens automatically, and provide a user- friendly interface for consumers to configure the API connection. Which of the following steps are CRITICAL for ensuring secure and seamless integration with the external API within your Snowflake Native Application?

• A. Embed the OAuth 2.0 client library directly into your application's code and handle token management within the application logic.
• B. Utilize Snowflake's Secret objects to securely store the client ID and client secret. Use the object within your Snowflake Native App to make the application consumer-configurable.
• C. Use Snowflake's External Functions to call an API Gateway to obtain authentication tokens and then make calls to External API.
• D. Store the client ID and client secret directly within the application's setup script.
• E. Require consumers to manually configure the OAuth 2.0 connection details (client ID, client secret, token endpoint, etc.) within their Snowflake account and then pass these details as parameters to your application's functions.

You are managing the release of a new version (v2.0) of your Snowflake Native Application that introduces significant schema changes to shared tables accessed by consumer accounts. To minimize disruption during the upgrade, you want to implement a phased rollout while ensuring backward compatibility for consumers who haven't yet upgraded. Which of the following strategies would allow you to achieve this goal effectively? (Select TWO)

• A. Create separate versions of the shared tables for vl .0 and v2.0, using views to present a unified interface. Grant consumer 'USAGE on view after upgrading.
• B. Create views on top of the new schema in v2.0 that emulate the old schema from vl .0. Grant consumers 'USAGE' on these views until they upgrade.
• C. Use dynamic SQL within stored procedures to conditionally access either the old or new schema based on the consumer's account ID, identified through a custom configuration table.
• D. Implement API versioning within your application code and provide compatibility layers to handle requests from consumers running older versions.
• E. Publish v2.0 without any schema changes and rely on consumers to manually migrate their data to new tables after upgrading.

When designing the architecture of a Snowflake Native App, which of the following architectural considerations and trade-offs should you carefully evaluate to optimize performance, security, and cost-effectiveness? (Select all that apply)

• A. Using secured API integration to call the external APIs to get real time details in the app to make the app more useful.
• B. Choosing the appropriate data access model (e.g., UDFs, stored procedures, Snowpark) based on the specific use case and performance requirements, considering the overhead associated with each approach.
• C. Implementing robust error handling and logging mechanisms to facilitate debugging and monitoring of the application's behavior in both the provider and consumer environments.
• D. Minimizing data transfer between the provider and consumer accounts by leveraging Snowpark and UDFs for data processing within the consumer's environment.
• E. Storing all application data within the provider account and accessing it directly from the consumer account using data sharing to avoid data duplication.

You're developing a Snowflake Native App. Part of your application logic involves using a UDF (User-Defined Function) to perform complex calculations on data residing in a table within the consumer's Snowflake account. Which of the following statements correctly describes how you would package and deploy this UDF within your Native App using the application package?

• A. The UDF definition must be created as an external function, pointing to an external API endpoint that your application controls, enabling the UDF logic to be executed outside of the consumer's Snowflake environment.
• B. The UDF definition must be created directly within the consumer's account after the application is installed, as UDFs cannot be included in the application package.
• C. You must create the UDF within a schema in your application package, and grant USAGE privilege on the schema to the application role. The consumer will automatically be granted EXECUTE privilege on the UDF.
• D. You must create the UDF within a schema in your application package. No additional privileges need to be granted, as the application role automatically has all necessary privileges within the application's namespace.
• E. You must create the UDF within a schema in your application package, and grant USAGE privilege on the schema to the application role. The application code can then execute the UDF without any further privilege grants within the consumer account, and the UDF can be called from SQL or other UDFs using unqualified names.

A Native Application provider wants to grant the 'SELECT privilege on a view, 'CUSTOMER DATA, in a shared database 'SALES DATA DB' to consumers installing their application. The provider also wants to ensure that future views created in 'SALES DATA DB' are automatically accessible to the application. Which of the following SQL statements, executed by the provider, achieves this with the LEAST amount of privilege escalation risk?

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