Snowflake SnowPro Specialty - Native Apps Sample Questions:

1. A data engineer, Alice, is developing a Snowflake Native Application that exposes a stored procedure, 'calculate_aggregate' , within the application schema 'app_schema'. She initially granted privilege on the application database to the 'analyst_role' and EXECUTE privilege on 'calculate_aggregate' to the same role. Later, due to a security audit, she needs to revoke the 'EXECUTE privilege from 'analyst_role' but wants to ensure users assigned to 'analyst_role' can still access other objects in the application database (but not execute this specific stored procedure). Which of the following actions achieves this goal MOST efficiently and securely?

A)

B)

C)

D)

E)

2. You are publishing a Snowflake Native Application to the Marketplace. You've completed initial testing, and the application appears to function as expected. However, the security scan consistently fails with a 'Data Exfiltration' error. The application includes a stored procedure that aggregates data from several tables within the application container and writes the results to an external stage using the 'COPY INTO' command. Review the following code snippet:

Which of the following changes is MOST likely to resolve the 'Data Exfiltration' error during the security scan?

A) Encrypt the data written to the external stage using client-side encryption with a key managed by the application provider.
B) Require the consumer to explicitly grant the application usage privilege on a secure external stage controlled by the consumer, and modify the procedure to validate the stage's existence and permissions before exporting data.
C) Remove the 'GRANT EXECUTE privilege on the 'export_data' procedure from the 'app_public' role.
D) Modify the stored procedure to only export data to a table within the application container instead of an external stage.
E) Implement row-level security policies on the 'aggregated_data' table to restrict access to sensitive rows.

3. 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) 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.
B) 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.
C) 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.
D) 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.
E) 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.

4. You are managing the release of a new version (v2.0) of your Snowflake Native Application that introduces significant schema changes to shared tables accessed by consumer accounts. To minimize disruption during the upgrade, you want to implement a phased rollout while ensuring backward compatibility for consumers who haven't yet upgraded. Which of the following strategies would allow you to achieve this goal effectively? (Select TWO)

A) Implement API versioning within your application code and provide compatibility layers to handle requests from consumers running older versions.
B) Create views on top of the new schema in v2.0 that emulate the old schema from vl .0. Grant consumers 'USAGE' on these views until they upgrade.
C) Create separate versions of the shared tables for vl .0 and v2.0, using views to present a unified interface. Grant consumer 'USAGE on view after upgrading.
D) Publish v2.0 without any schema changes and rely on consumers to manually migrate their data to new tables after upgrading.
E) Use dynamic SQL within stored procedures to conditionally access either the old or new schema based on the consumer's account ID, identified through a custom configuration table.

5. You are designing a Snowflake Native Application that allows consumer accounts to customize certain aspects of its behavior. Specifically, the application needs to support consumer-defined thresholds for alerting, stored as parameters. You want to allow consumers to set these thresholds through the 'ALTER APPLICATION' command. How can you achieve this MOST effectively while ensuring that these parameters are securely managed and accessible within your application code?

A) Use 'ALTER APPLICATION' to modify session variables, which are then accessible within the application code via 'SYSTEM$GET_VARIABLE'.
B) Define parameters within the application manifest (manifest.yml) with mutable set to True. Use the SYSTEM$GET PARAMETER function within your application logic to retrieve these consumer-configurable values.
C) Define parameters within the application manifest (manifest.yml) with mutable set to True. Use the APPLICATION PARAMETER function within your application logic to retrieve these consumer-configurable values.
D) Define parameters using the 'USING' clause during application deployment in the provider account. Then, use 'ALTER APPLICATION' to modify these parameters in the consumer account.
E) Use 'ALTER APPLICATION' to directly modify values within a consumer-managed table, reading values from that table in your stored procedures.

Solutions: