Snowflake SnowPro Specialty - Native Apps Sample Questions:

1. You are developing a Snowflake Native App that needs to be configurable by the consumer during installation. You define parameters in the 'manifest.ymr file. During application installation, the consumer provides values for these parameters. How can you access these parameter values within your application's setup script ('setup.sql')?

A) Parameter values are automatically available as global variables within the 'setup.sqr script. You can reference them directly by their name as defined in the 'manifest.yml'.
B) You must use the 'GET_DDL' function to retrieve the parameter values from the application object definition. The returned DDL string will contain the parameter values, which you need to parse.
C) Parameter values are stored in a dedicated table automatically created by Snowflake during application installation. You can query this table using standard SQL to retrieve the parameter values.
D) Use the ' SYSTEM$GET PARAMETER function within the 'setup.sqr script, passing the parameter name as an argument. This function retrieves the current value of the specified parameter for the application.
E) Parameter values are passed as arguments to the 'setup.sqr script. You need to define input parameters in the script declaration and then access them by their position or name.

2. Consider a scenario where a Snowflake Native Application contains a task named "daily data sync'. This task needs to be executed in the consumer's account. To enable proper monitoring and governance within the consumer's account, the consumer wants to tag the executions of this task. Which of the following actions must the application provider take to ensure that the consumer can successfully tag the 'daily data sync' task executions without compromising the security of the application or requiring the consumer to have elevated privileges on the application database?

A) The provider must grant the APPLY MASKING POLICY privilege on the task to the consumer's account role, enabling the consumer to configure tags via masking policies.
B) The provider must grant the APPLY TAG privilege on the task to the consumer's account role. No other configuration is necessary.
C) The provider must grant the APPLY TAG privilege on the account to the consumer s account role.
D) The provider must grant the OWNERSHIP privilege on the task to the consumer's account role, allowing the consumer to set tags directly.
E) The provider cannot enable the consumer to tag the task executions without granting elevated privileges on the application database or compromising security; tagging is solely the provider's responsibility.

3. You are developing a Snowflake Native Application that uses a Stored Procedure to orchestrate complex data processing tasks. This stored procedure is defined within the application package. When testing in test mode, which of the following security considerations are paramount to ensure the procedure executes correctly and securely, without unintentionally granting excessive privileges to the consumer?

A) Ensure that any roles granted to the application role also have the necessary privileges to execute the stored procedure, and access the objects it interacts with. The stored procedure must be defined with 'EXECUTE AS CALLER.
B) Since the application is running in test mode, security is not a major concern. Granting all necessary privileges directly to the application role simplifies testing without compromising the consumer's security.
C) Define the stored procedure with the 'EXECUTE AS OWNER clause. This ensures the procedure always runs with the privileges of the application owner, regardless of the caller's permissions.
D) Create a dedicated service user specifically for the application and grant only the necessary privileges to this user. The stored procedure should then execute with the privileges of this service user using the 'EXECUTE AS CALLER clause. This allows granular access control.
E) Grant the 'EXECUTE' privilege on the stored procedure to the 'PUBLIC' role during test mode. This simplifies testing but should be revoked before publishing the application.

4. A Native App provider wants to implement comprehensive monitoring of their application's behavior within consumer accounts. They decide to use Event Tables to capture various application events. Which of the following strategies is the MOST appropriate for designing and managing Event Tables for this purpose? Select ALL that apply.

A) Create a single, generic Event Table with a VARIANT column for event-specific data to accommodate all event types.
B) Utilize dynamic table creation based on the type of event being recorded, ensuring optimal storage and query performance for each event type. Dynamic table creation is managed programmatically.
C) Create separate Event Tables for each distinct event type, with columns tailored to the specific data associated with each event.
D) Implement a data retention policy to automatically purge older events from the Event Tables, minimizing storage costs and improving query performance.
E) Use a centralized Event Table that is shared across all consumer accounts to simplify data aggregation and analysis.

5. You are responsible for managing the pricing plans for your Snowflake Native Application listed on the Marketplace. You want to offer a 'Premium' tier that includes additional features and resources. To achieve this, you need to modify the listing to include this new pricing option. Which of the following steps are NECESSARY and in the CORRECT order to successfully add the 'Premium' tier to your application's listing, ensuring existing customers are not negatively impacted? (Choose two options in their proper order)

A) 1. Update the Marketplace listing by adding the 'Premium' pricing tier with appropriate settings, but without modifying the application package. 2. Inform existing customers that the new pricing tier is available.
B) 1. Modify the existing application package in place to include the code changes supporting the 'Premium' features. 2. Update the Marketplace listing with the modified application and add the 'Premium' pricing tier with appropriate settings.
C) 1. Update the listing on the Marketplace with the new pricing tier. 2. Ensure backward compatibility for existing customers by implementing logic in the application to detect their current tier and maintain existing functionality.
D) 1. Create a new version of the application package in your provider account with the code changes supporting the 'Premium' features. 2. Update the Marketplace listing with the new version of the application and add the 'Premium' pricing tier with appropriate settings.
E) 1. Test new Pricing in a Sandbox environment with few consumers. 2. Deploy the new version to the consumer accounts.

Solutions: