A Snowflake Native App developer wants to externalize certain configuration values so that a consumer can adjust the app's behavior without modifying the app's code directly. Which of the following methods is the MOST appropriate for achieving this using the Snowflake Native App Framework?

• A. Defining parameters in the manifest file and using them within the application code.
• B. Hardcoding the configuration values directly into the SQL code.
• C. Using dynamic SQL to modify the application code at runtime based on environment variables.
• D. Using Snowflake variables and setting them at the session level.
• E. Storing the configuration values in a separate Snowflake table within the consumer account.

You are developing a Snowflake Native Application that needs to be deployed across multiple Snowflake accounts. The application includes a setup script that creates several tables and stored procedures. However, some consumers might have naming conflicts with the objects created by your setup script. Which of the following strategies can you use to minimize naming conflicts and ensure smooth application deployment? (Select all that apply)

• A. Dynamically generate object names within the setup script using the application's name and a random suffix.
• B. Utilize the 'CREATE OR REPLACE syntax for all objects in the setup script to overwrite any existing objects.
• C. Prefix all objects created by the setup script with a unique, application-specific identifier.
• D. Instruct consumers to drop any conflicting objects before installing the application.
• E. Package all application objects into a dedicated schema within the consumer's database.

You are developing a Snowflake Native App that performs complex data transformations and offers different pricing tiers based on usage. You plan to use Snowflake Usage Metering Events to track consumer usage. Which of the following is the MOST appropriate approach to track usage and associate it with the correct pricing tier in your setup script and application code?

• A. Call 'SYSTEM$METER USAGE with a dynamic event name that encodes the pricing tier and complexity of the transformation. Store the mapping of event names to pricing in a configuration table within your app.
  
• B. Avoid using 'SYSTEM$METER USAGE altogether and rely on Snowflake's built-in resource monitoring to track usage for billing.
• C. Call 'SYSTEM$METER USAGE without specifying an event name. Aggregate usage data based on query history in the consumer account to determine pricing.
• D. Call 'SYSTEM$METER USAGE with a fixed event name and quantity for each transformation, regardless of complexity or pricing tier.
• E. Create a view on the APP USAGMETERING_HISTORY view to capture usage data. Call 'SYSTEM$METER USAGE from with in the View.
  

You are developing a Snowflake Native Application that requires robust role-based access control. The application provides data transformation services to consumer accounts. You want to define distinct roles for different levels of access: 'TRANSFORMER_ADMIW (full control), 'TRANSFORMER USER (execute transformations), and 'TRANSFORMER OBSERVER (read-only access to metadata). In the setup script, which SQL statements are the MOST secure and efficient way to achieve this while adhering to Snowflake's recommended practices for application roles?

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

An organization is building a Snowflake Native App that performs complex data transformations. The transformation logic is encapsulated in a stored procedure. They want to allow consumer accounts to execute this stored procedure, but ONLY with the privileges of the application itself, preventing access to the consumer's data through the procedure. Which set of actions are required to achieve this?

• A. Create the stored procedure with the 'EXECUTE AS CALLER clause and grant the 'APPLY APPLICATION' privilege on the application package to the consumer's role.
• B. Create the stored procedure with the ' EXECUTE AS CALLER clause and grant the 'EXECUTE APPLICATION' privilege on the application instance to the consumer's role.
• C. Create the stored procedure with the ' EXECUTE AS OWNER' clause and grant the ' IMPORTED PRIVILEGES' on the application package to the consumer's role.
• D. Create the stored procedure with the ' EXECUTE AS OWNER clause and grant the ' EXECUTE APPLICATION' privilege on the application instance to the consumer's role.
• E. Create the stored procedure with the 'EXECUTE AS OWNER clause and grant the 'USAGE privilege on the application package to the consumer's role.