You're designing a Snowflake Native Application that leverages Snowpark Container Services (SPCS) and you are creating a CI/CD pipeline for deploying your application to multiple Snowflake regions. As part of the pipeline, you want to automate the creation of a Compute Pool. Which of the following approaches represents the MOST robust and repeatable method for creating the Compute Pool across all regions, considering factors like consistency and potential differences in available instance families?

• A. Use a Snowflake Script (SnowSQL) to create the Compute Pool, hardcoding the instance family and other parameters directly into the script.
• B. Compute Pools created are global objects, so the pool automatically exists across all regions.
• C. Use a Snowflake Script (SnowSQL) to create the Compute Pool, retrieving the available instance families dynamically using 'SYSTEM$GET_CP POLICY' and selecting the appropriate instance family based on regional availability. Store common configurations in environment variables.
• D. Create a Compute Pool in one region and then clone it to all other regions using the 'CREATE CLONE syntax.
• E. Manually create the Compute Pool in each region using the Snowflake web interface, ensuring the parameters are identical across all instances.

You are developing a Snowflake Native Application that relies on external functions (UDFs/UDTFs) for data processing. A new version of your application includes significant changes to these external functions, potentially affecting existing consumer data and queries. How should you manage the upgrade process to minimize disruption and ensure data integrity in consumer accounts? Assume consumers rely on your function names in their queries. Which of the following approach is MOST suitable?

• A. Rename all the external functions in the new version and instruct consumers to update their queries accordingly after the upgrade.
• B. Use release directives to direct users to an intermediate version that provides a compatibility layer for the external function changes. This layer translates calls to the old function names into calls to the new functions, allowing for a phased transition.
• C. Create new versions of the external functions with different names while maintaining the old functions in the new version. Consumers can then migrate to the new functions at their own pace. Use release directives to route new users to new functions.
• D. Develop wrapper functions in the new version that call the original external functions with the new logic applied. Consumers can then gradually migrate to the wrapper functions without immediately changing their queries.
• E. Update the external functions in place with the new logic. Snowflake's versioning will automatically handle any compatibility issues for existing queries.

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. Grant the development team direct access to the consumer's data warehouse to facilitate testing. Ensure proper auditing is enabled.
• B. Create a separate Snowflake account for testing and populate it with synthetic data that mimics the structure and characteristics of the consumer's data.
• C. Use Snowflake's data classification features to identify sensitive data and implement row-level security to restrict access to the development team.
• 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.

An application provider, 'SecureData Solutions', wants to implement an in-app share within their Snowflake Native App. They intend to share a specific, filtered subset of a provider-owned table with consumers to enhance app functionality without exposing the entire dataset. Which of the following steps are REQUIRED to properly configure and utilize this in-app share?

• A. Create a share in the provider account, grant usage on the database and schema containing the table to the share, and then grant SELECT privilege on the filtered view of the table directly to the share.
• B. Create a secure view on the provider-owned table with the desired filters, create a database role in the provider account, grant SELECT privilege on the secure view to this database role, create a share, and grant usage to the role. Lastly, grant OWNERSHIP on the SHARE to the application role.
• C. Create a secure view on the provider-owned table with the desired filters, create a share in the provider account, grant usage on the database and schema containing the secure view to the share, and then grant SELECT privilege on the secure view directly to the share. Lastly, grant OWNERSHIP on the SHARE to the application role.
• D. Create a database role in the provider account, grant SELECT privilege on the base table to the role, then create a SHARE and add the role to the SHARE as a privileged principal.
• E. Create a database role in the provider account, grant SELECT privilege on the filtered view of the table to this database role, and then create a share and grant usage to this role.

A Native Application is being developed that requires access to the consumer's Snowflake account for billing purposes. The application needs to record the query history of the consumer's account to estimate resource usage. Which is the MOST secure and efficient method for the Native App to access this data, minimizing the permissions granted to the app and considering the governance aspects?

• A. Grant the 'ACCOUNTADMIN' role to the Native App's service account. This provides full access to the account's query history.
• B. Create a stored procedure within the Native App that executes as the 'OWNER and queries the view. The stored procedure is granted to the Native App's service account with 'EXECUTE privileges.
• C. Use the 'READ SESSION' privilege to allow the application to read the current session context and infer the resource usage from it.
• D. Grant the ' MONITOR USAGE' privilege to the Native App's service account, allowing it to query the view.
• E. Grant the ' USAGE privilege on the 'SNOWFLAKE' database to the Native App's service account, allowing it to query all tables and views in that database.