Snowflake NAS-C01 real dump : SnowPro Specialty - Native Apps

You have a Snowflake Native Application listed on the Marketplace. You need to update the application to add a new feature, which requires changes to both the application code and the database schema within the application package. You want to ensure a seamless upgrade experience for existing consumers, minimizing downtime and data loss. What is the MOST appropriate strategy for deploying this update?

• A. Create a new version of the application package. Include a setup script that detects the existing version of the application and performs any necessary schema migrations or data transformations. Announce the new version and instruct consumers to manually upgrade.
• B. Modify the existing application package directly with the updated code and schema. This will automatically update the application for all consumers.
• C. Create a new version of the application package with the updated code and schema. Consumers will automatically be upgraded to the new version upon release.
• D. Create a new version of the application package. Implement a Snowpark Python stored procedure within the new version that handles schema migrations and data transformations. This procedure should be automatically executed during the upgrade process.
• E. Create a new version of the application package. Before releasing, use a feature flag system to gradually roll out the new feature to a subset of consumers, monitoring for any issues before a full release.

A Snowflake Native App provider wants to ensure that even future roles created in their provider account will NOT automatically have access to the application database , which was created without the "MANAGED ACCESS' property initially. After creating a security audit suggested it to be with managed access. Which of the following steps BEST secures the app database?
Note multiple options may be needed

• A. GRANT OWNERSHIP ON DATABASE TO ROLE application_role;
• B. REVOKE USAGE ON DATABASE FROM ROLE PUBLIC;
• C. DROP DATABASE CREATE DATABASE WITH MANAGED ACCESS;
• D. ALTER DATABASE SET MANAGED ACCESS = TRUE;
• E. REVOKE ALL PRIVILEGES ON DATABASE FROM PUBLIC;

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

You are preparing to list your Snowflake Native Application on the Snowflake Marketplace. You want to restrict its availability to specific Snowflake regions and also require consumers to agree to a custom End User License Agreement (EULA) before installation. Which steps are essential during the listing creation process to achieve this?

• A. Configure the 'Availability' section of the listing to specify allowed regions. Upload the EULA as a PDF document within the 'Documentation' section.
• B. During listing creation, select the 'Custom EULA' option and provide the EULA text directly within the designated field. Configure the 'Availability' section to specify the allowed regions.
• C. Use the Snowflake CLI to programmatically set the allowed regions using the 'snowflake marketplace application update' command. Include a link to an external website hosting the EULA in the listing description.
• D. Regions are inherently globally available so it cannot be restricted. Include the EULA within the code of the application, forcing the user to acknowledge it through the code.
• E. Specify the allowed regions in the 'Availability' section of the listing. Upload a text file containing the EULA and mark it as 'Required Agreement' in the listing settings.