Snowflake SnowPro Specialty - Native Apps : NAS-C01

You are developing a Snowflake Native Application that needs to track usage metrics within consumer accounts. Specifically, you want to log the number of times a particular function within your application is called, and also store certain operational statistics. Which of the following storage options are available to you within the application package to persist these metrics, and what are their implications?
(Select TWO)

• A. Leveraging external stages (e.g., AWS S3) to store the metrics. The application would need the necessary IAM roles and stage configuration.
• B. Creating permanent tables within the application package using the 'APPLICATION' schema. These tables persist across installations and updates.
• C. Utilizing User-Defined Functions (UDFs) with external network access to push metrics to an external logging service.
• D. Using temporary tables within the application. These tables are automatically dropped at the end of the session.
• E. Using the 'APPLICATION' schema to create persistent internal stages. Data written to these stages will persist across installations and updates.

Consider the following Snowflake Native Application design scenario: You are building a data enrichment application. This application requires a consumer to grant usage on a specific database in their account. The application will then use a user-defined function (UDF) to access and enrich the dat a. To minimize the risk of data exposure and adhere to best practices, which of the following approaches should you take when designing the UDF?

• A. Create the UDF with the 'SECURE keyword and implement granular access control within the UDF code, restricting access based on the application role.
• B. Create the UDF with the EXTERNAL_ACCESS' keyword to explicitly allow it to access data outside of the application package.
• C. Create the UDF with the 'VOLATILE' keyword to ensure it only runs when explicitly called, limiting the potential for unintended data access.
• D. Create the UDF with the 'IMMUTABLE keyword to prevent any data modification within the consumer's database.
• E. Create the UDF without any special keywords, relying solely on the consumer's permissions to control data access.

You are developing a Snowflake Native App that requires specific database privileges to be granted to the application role during installation. Which sections of the 'manifest.yml' file are primarily responsible for defining these required privileges, and how does Snowflake interpret and enforce them during the installation process?

• A. The 'setup.script' section defines the privileges needed. The application setup code must explicitly grant these privileges using 'GRANT statements to a specific application role. Snowflake does not automatically grant any privileges, so you have full control over permission management.
• B. The 'application.initial_version.privileges' section defines the privileges needed. Snowflake automatically grants these privileges to the application role defined in 'application.initial_version.role' before the setup script runs. This ensures the application has the necessary permissions to create objects and execute code within the consumer's account.
• C. The 'application.initial_version.parameters' section. While parameters can control behavior, they do not define or manage privileges. Privileges must be manually configured by the consumer post-installation.
• D. A combination of the 'application.initial_version.privileges' and 'setup.script' sections. 'application.initial_version.privileges' defines initial static privileges, while 'setup.script' can grant additional privileges dynamically during installation if needed. Snowflake ensures that all specified privileges are granted before the application is fully operational.
• E. The 'application.initial_version.artifacts' section is used to define the privileges. Snowflake parses this section to identify required privileges and grants them dynamically to the application role whenever a function or procedure is called that requires them.

You are the provider of a Snowflake Native Application built with Scal
a. Consumers are reporting that a specific UDF, 'calculate_risk' , occasionally returns incorrect results for certain input datasets. You suspect an issue with the UDF's logic but struggle to reproduce the problem in your development environment. Given that you cannot directly access the consumer's data, what are the most effective strategies for diagnosing this issue?

• A. Modify the UDF to include a 'debug' mode that performs additional checks and assertions. The consumer can enable this mode to collect diagnostic information and report any failures back to the provider. Consumer shares the error logs/code
• B. Implement logging within the 'calculate_risk' UDF to capture input parameters and output values for a sample of executions. Store these logs in a secure table accessible only to the provider, subject to data governance policies. Utilize Snowflake's masking policies to mask the sensitive data and allow the provider to see only masked version, not the actual sensitive data.
• C. Request the consumer to execute the UDF with the problematic datasets and provide the resulting incorrect output. Then, use Snowflake's query history and lineage features to trace the data flow and identify potential issues in the UDF's logic.
• D. Request the consumer to provide anonymized sample data that triggers the issue. Use this data in your development environment to debug the UDF.
• E. Implement comprehensive unit tests for the 'calculate_risk' UDF, covering a wide range of input values and edge cases. Ensure these tests pass before deploying new versions of the application.

You are preparing to list your Snowflake Native Application on the Snowflake Marketplace. You've developed the application and implemented security measures. Which of the following steps are essential best practices for ensuring a successful and secure listing on the Snowflake Marketplace?

• A. Avoid documenting any limitations or potential issues with the application to present a flawless image to potential consumers. Only provide limited pricing information to create a sense of urgency to potential consumer
• B. Clearly communicate the application's security model, including data encryption methods, access controls, and any reliance on consumer-side security configurations. Undergo and document regular security audits and penetration tests of the application.
• C. Implement robust error handling and logging mechanisms to provide consumers with informative error messages and aid in troubleshooting. Include mechanisms for securely collecting and storing application usage metrics (if required), ensuring compliance with privacy regulations.
• D. Include a prominently displayed disclaimer stating that the application is provided "as is" and the provider assumes no liability for any damages arising from its use. Only provide basic installation instructions. It is the end user's responsibility to know how to use the application.
• E. Thoroughly document the application's functionality, installation instructions, configuration options, and any known limitations. Provide clear and concise pricing information and support contact details.