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.
  

You are developing a subscription-based Snowflake Native Application that offers tiered pricing (Basic, Premium, Enterprise) based on resource consumption (e.g., compute hours, data storage). Consumers select their desired tier during the subscription process. Your application needs to dynamically adjust resource limits based on the selected tier. Which combination of the following actions should you take to correctly implement this?

• A. Create separate resource monitors for each tier and associate the consumer's account with the appropriate resource monitor based on their selected tier during application installation.
• B. Use 'ALTER WAREHOUSE commands within the application to dynamically adjust warehouse sizes based on the selected tier, after retrieving the selected tier information via the application's configuration metadata.
• C. Implement role-based access control (RBAC) using different roles for each tier, granting each role appropriate privileges for data access and compute resources. Assign users to roles based on their subscription tier.
• D. Store tier-specific resource limits (e.g., compute hours, data storage limits) in a configuration table within the application. Implement stored procedures that enforce these limits during runtime using custom logic.
• E. Leverage Snowflake's data governance features, creating row access policies for each tier and assigning them based on the consumer's subscription status

You are developing a Snowflake Native App that performs data transformations. The core logic is implemented in a series of stored procedures. You need to implement versioning for your app to allow for future updates and rollbacks. Which of the following steps are REQUIRED to properly implement versioning for a Snowflake Native App?

• A. Increment the 'version' attribute in the 'MANIFEST.yml' file for each new release.
• B. Tag each release in your version control system with the corresponding version number.
• C. Use the 'ALTER APPLICATION' command to update the app's version in the consumer's account.
• D. Update the 'version' attribute in the 'setup.sqr file, if one exists.
• E. Create a separate branch in your version control system for each version of the app.

Consider the following snippet from a Snowflake Native App manifest file (application.yaml):

Which of the following statements are TRUE regarding how these parameters can be accessed and used within the application's SQL code?

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

You are developing a Native Application that needs to access data from a consumer's table. The data contains personally identifiable information (PII), and your application requires explicit consent from the consumer to access this dat a. You have implemented a consent mechanism within your application's UI. Which of the following steps are NECESSARY to ensure compliance with data privacy regulations when accessing the consumer's data?

• A. Grant the SELECT privilege on the table directly to the application's service account after the consumer provides consent.
• B. Implement a secure view that filters the PII data unless the consumer's consent flag is set to TRUE in a separate consent table. Grant SELECT on the secure view to the application's service account.
• C. Use Snowflake's dynamic data masking policies on the PII columns and grant the application's service account the APPLY MASKING POLICY privilege. Revoke the UNMASK privilege from the application's service account.
• D. Implement a row access policy on the table based on the consumer's consent flag, ensuring the application only sees data for consumers who have granted consent. Grant the SELECT privilege on the table to the application.
• E. Implement a stored procedure that checks the consumer's consent flag. If consent is granted, the stored procedure retrieves and returns the requested data. Grant EXECUTE TASK privilege on the stored procedure to the application's service account.