You are packaging a Snowflake Native App and need to ensure that consumer accounts can only access specific data views you've created within your application schem a. You want to prevent consumers from directly querying the underlying tables. Which of the following security measures, when implemented together, BEST achieve this objective? (Choose two)

• A. Grant 'SELECT' privilege on the underlying tables to the 'application role' within the application package.
• B. Use secure views to expose data, ensuring data access is controlled through the view's definition.
• C. Do not grant any privileges on the underlying tables to the 'application role' within the application package.
• D. Grant "OWNERSHIP' on the views to the 'application role' within the application package.
• E. Grant 'SELECT privilege only on the views to the 'application role' within the application package.

You are developing a Snowflake Native Application with a custom setup script. Within the setup script, you need to perform different actions based on whether the application is being installed for the first time in a consumer's account, or if it's an upgrade from a previous version. Which of the following functions or techniques can you reliably use within the setup script to determine if the current execution is a fresh installation vs. an upgrade? (Assume the app version is maintained and accessible as a variable 'current_version' .)

• A. Query the 'INFORMATION_SCHEMAPPLICATIONS' view to check if the application name already exists in the consumer's account.
• B. Use the table 'APPLICATION_REGISTRY' function to check for an existing entry for the application in the current account.
• C. Check if the current version is '1.0', assuming the initial version of the application will always be '1.0'.
• D. Use 'SYSTEM$GET_PREVIOUS_VERSION()' function inside the setup script. If it returns NULL, it is the first install.
• E. Attempt to read a known persistent setting from the application's metadata. If the setting exists, it's an upgrade; otherwise, it's a fresh install. (Requires metadata setup in a previous version)

You are developing a Snowflake Native App that processes streaming data from a Kafka topic. The app needs to continuously ingest data, perform real-time transformations, and store the results in a Snowflake table within the app's managed database. Which Snowflake feature(s) and approach(es) are BEST suited for implementing this data ingestion and processing pipeline within the Native App?

• A. Use Snowflake Pipes to continuously ingest data from the Kafka topic into a staging table and then use stored procedures to periodically transform and load the data into the target table.
• B. Leverage Snowflake Snowpipe Streaming to ingest data directly from the Kafka topic into the target table, combined with Snowflake Tasks to handle any required data transformations.
• C. Employ a combination of Snowflake Snowpipe Streaming for data ingestion and Dynamic Tables for continuous, incremental data transformations within the application's managed database.
• D. Use a Snowflake Stream to capture changes in the Kafka topic and then use a Snowflake Task to periodically merge these changes into the target table.
• E. Implement a custom Kafka consumer within a Java User-Defined Function (UDF) to read data from the Kafka topic and directly insert it into the target table.

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.