You are managing a Snowflake Marketplace listing for your native application. You need to update the application logic and schem a. Which of the following actions is the correct sequence to perform the update in a non-breaking way for existing consumers?

• A. Deprecate the existing version of the application and force all consumers to upgrade to the new version within 24 hours.
• B. Create a patch version with bug fixes and create a new minor version with schema changes, and release it as an upgrade on the Marketplace.
• C. Modify the existing application's code and schema, create a new listing for the updated version, and remove the old listing.
• D. Directly modify the application's code and schema in the production environment, then announce the changes to consumers.
• E. Create a new version of the application with the updated logic and schema, test it thoroughly, and then release it as an upgrade on the Marketplace.

You're building a Streamlit application within a Snowflake Native App that uses the Permissions API (hypothetical) to control access to sensitive dat a. Your security team has mandated that any changes to data access privileges must be audited. How can you effectively log all privilege grant and revoke operations performed via the Permissions API within your Streamlit application running inside Snowflake, assuming you are given the hypothetical 'PermissionsClient' and methods as below?

• A. Use Snowflake's native logging capabilities in the application's setup script, logging directly to the Snowflake event log. However, these logs may require a system administrator to interpret and extract.
• B. Leverage Snowflake's built-in 'QUERY _ HISTORY' view to track all SQL commands executed by the Streamlit application. Filter for 'GRANT and 'REVOKE statements to identify privilege changes. Replicate to external storage for retention.
• C. Implement a custom logging function that captures the API calls and their parameters. Use a try-except block around each API call, logging the details to a separate audit table in Snowflake, and pushing logs to external SIEM tools.
• D. Rely solely on the Permissions API's built-in audit trails, assuming it automatically logs all operations to a system table accessible only by Snowflake administrators.
• E. Configure Snowflake's event tables for security to track privilege grants and revokes. Create a Streamlit function that fetches and displays these audit events within the application's admin panel. Push data into separate staging area.

You are developing a Snowflake Native Application and want to implement comprehensive cost monitoring for your application's resource consumption within a consumer's Snowflake account. Which of the following approaches provide the MOST effective and granular cost visibility for both you (as the provider) and your consumers?

• A. Leverage Snowflake's Resource Monitor feature to set budget limits for the entire consumer account and receive alerts when these limits are exceeded. This provides a general overview of spending but lacks application-specific granularity.
• B. Implement custom logging within your application to track resource usage (e.g., CPU time, data scanned) for each function or query. Aggregate and analyze these logs to generate cost reports for consumers.
• C. Rely solely on Snowflake's global account-level cost dashboards and resource monitors to track overall Snowflake usage, including the resources consumed by your application. Analyze these dashboards manually to identify potential cost optimization opportunities.
• D. Combine Snowflake's query history (accessed via the ACCOUNT_USAGE schema) with custom tagging of resources and queries within your application. This allows you to attribute resource consumption to specific application features and provide detailed cost breakdowns for consumers.
• E. Utilize Snowflake's query history and function within your application to capture query execution statistics. Create views or tables to summarize resource consumption metrics for specific application components.

A provider is developing a Snowflake Native App. They have created a database named 'app_db' using 'CREATE DATABASE app_db WITH MANAGED ACCESS;'. Subsequently, they need to create a schema within this database and grant specific privileges on the schema's objects to a role 'app_admin' . Which of the following SQL statements are valid and necessary to set this up securely and effectively?

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

A financial services company is developing a Snowflake Native App. It needs to securely access external market data via an API and store the processed results in a consumer-provided table. Considering security best practices and the Snowflake Native App Framework limitations, which of the following approaches represents the MOST secure and recommended implementation for this scenario?

• A. Utilize a Java UDF with the 'network access' capability to call the external API directly from within the UDF. Store the processed data directly into a consumer- provided table by using the application role with INSERT privilege granted by consumer.
• B. Employ a Snowflake external function, configured with a service account, which invokes an API integration stored in the provider account. The external function returns the data, which is then inserted into a consumer-owned table using a stored procedure and INSERT statements, where the application role has been granted the necessary INSERT privilege.
• C. Use a Snowflake external function with an API integration, configured with a service account that has the necessary permissions to access the API. Store the processed data in a consumer-provided table using stored procedures and INSERT statements using the application role.
• D. Utilize a Python UDF with the 'external network access' capability to call the external API directly from within the UDF. Store the processed data directly into a consumer-provided table by using the application role. API key is stored in snowflake secret.
• E. Use a Snowflake external function with an API integration that passes the API key as a parameter. Store the processed data in a consumer-provided table using dynamic SQL.