Snowflake SnowPro Specialty - Native Apps Sample Questions:

1. A data analytics company, 'Data Insights Pro', develops a Snowflake Native Application that provides advanced data visualizations. They want to publish this application on the Snowflake Marketplace as a public listing. Which of the following steps are required in addition to the standard application creation and packaging, specifically focusing on the public listing aspects? Assume the necessary roles and privileges are already granted.

A) Ensure that the application is compatible with all Snowflake regions before publishing to a public listing.
B) Submit the application package to Snowflake for security and compliance review before making it available on the Marketplace.
C) Define a pricing model using Snowflake's monetization features and configure the listing visibility to 'Public'.
D) Implement robust application usage monitoring and metering to ensure accurate billing if a commercial model is used.
E) Create a detailed listing description, including features, benefits, and example use cases, and define the support channels.

2. You are designing a Snowflake Native Application that requires granular control over the privileges granted to different application roles. You want to follow the principle of least privilege. You have the following requirements: Application roles , and app_read_only'. What is the most effective strategy to implement this using definer's rights?

A) Create stored procedures owned by the application, with each stored procedure explicitly granting the required privileges to the corresponding role. Consumers must then grant USAGE on these procedures to their desired roles.
B) Create separate schemas for each application role, placing objects with different privileges into these schemas. Then, grant the appropriate privileges on each schema to the corresponding application role.
C) Grant all privileges on all application objects to the 'app_admin' role and rely on the consumer to manage privilege inheritance for other roles.
D) Create views for each application role, granting SELECT privilege on the necessary tables to each view. Then, grant SELECT privilege on the appropriate view to each application role.
E) Create stored procedures owned by the application, with each stored procedure performing actions within the app. Grant OWNERSHIP on each stored procedure to the application admin. Consumers must then grant USAGE on these procedures to their desired roles.

3. You are developing a Snowflake Native Application that relies on external Python packages. You've successfully added the necessary packages to the stage associated with your application package using 'snowflake-cli' during development. However, when testing the application in a consumer account, you encounter errors indicating that these packages are not found. What are the most likely reasons for this issue and how can you resolve them?

A) The 'snowflake.yml' file does not correctly specify the stage where the Python packages are located. Update the 'snowflake.yml' file to include the correct stage URL and ensure the application's setup script creates the stage and uploads the packages.
B) The consumer account does not have access to the Snowflake Marketplace where the packages are hosted. Request the consumer to enable access to the required marketplace listings.
C) The packages were not correctly added to the stage. Verify that the packages are in the stage specified in the 'snowflake.yml' file, and that the application has the necessary permissions to read from the stage within the setup script.
D) The consumer account's Python environment is incompatible with the packages used by the application. Instruct the consumer to update their Python environment to match the application's requirements.
E) The stage is not automatically shared with the consumer account as part of the application package. Ensure that your setup script includes a step to create a share and grant usage on the stage to the consumer account.

4. A Native App developer is using Snowflake's Event Tables for tracing the execution of their application. They have noticed a significant performance overhead when event logging is enabled, particularly for high-volume UDFs. Which of the following strategies would be MOST effective in mitigating the performance impact of event logging while still capturing valuable tracing information?

A) Increase the frequency of event table flushes to reduce the number of events buffered in memory. This minimizes memory pressure and write latency.
B) Reduce the number of columns captured in the event tables to minimize the amount of data being written. Store all tracing data in a single large event table to simplify querying.
C) Implement sampling or conditional logging within the UDFs, only logging events for a subset of executions or when specific conditions are met. Utilize asynchronous logging techniques where appropriate to offload logging operations.
D) Disable event logging entirely for high-volume UDFs to eliminate the performance overhead.
E) Write event data directly to an external cloud storage system (e.g., AWS S3, Azure Blob Storage) bypassing Snowflake's Event Tables altogether.

5. You are creating a Snowflake Native App using the Native Apps Framework. Your application needs to perform a task that must execute on a regular schedule (e.g., daily data refresh). Which Snowflake feature(s) can you leverage to achieve this, and what considerations are important when using them within the Native App context?

A) You should implement an external scheduler (e.g., AWS Lambda, Azure Functions) that triggers a Snowflake Stored Procedure via the Snowflake API. The Stored Procedure should be owned by the APPLICATION role.
B) Snowflake Streams should be used to track data changes and trigger the refresh process. The Stream must be defined in the application package, and a separate task can be configured to consume the stream data.
C) Snowflake Pipes are the preferred method for scheduled data ingestion within Native Apps, as they are designed for continuous data loading from external sources.
D) Use Snowflake Alerts with a cron schedule to trigger a stored procedure owned by the APPLICATION role. The procedure executes any scheduled task.
E) Snowflake Tasks can be used directly within the Native App, but you must ensure the task definition is part of the application package and the task is resumed upon installation in the consumer account. The task must use the APPLICATION role.

Solutions: