Prepare with Snowflake NAS-C01 exam torrent, pass for sure

You're developing a Snowpark Container Services application. Your 'service.yaml' file defines a service named 'data_processor'. You want to create a service endpoint, 'ingest_endpoint' , that is secured and accessible only by authorized consumers of your Snowflake Native Application. Select the TWO SQL statements that, when used together, will correctly create and bind the service endpoint, ensuring proper OAuth authentication and authorization.

• A. CREATE OR REPLACE SERVICE ENDPOINT ingest_endpoint FOR SERVICE data_processor WITH AUTHENTICATION TYPE = SNOWFLAKE_JWT;
• B. ALTER SERVICE data_processor ADD ENDPOINT ingest_endpoint WITH AUTHENTICATION TYPE = OAUTH;
• C. BIND SERVICE ENDPOINT ingest_endpoint FOR SERVICE data_processor WITH AUTHENTICATION TYPE = NONE TO APPLICATION PACKAGE;
• D. CREATE SERVICE ENDPOINT ingest_endpoint FOR SERVICE data_processor WITH AUTHENTICATION TYPE = OAUTH;
• E. BIND SERVICE ENDPOINT ingest_endpoint FOR SERVICE data_processor WITH AUTHENTICATION TYPE = OAUTH TO APPLICATION PACKAGE;

A Snowflake Native App developer is building an application package that contains multiple versions. They want to ensure that a consumer upgrading from version 1.0 to version 2.0 MUST execute a specific set of SQL scripts as part of the upgrade process to migrate existing application dat a. Which Snowflake Native App feature should they leverage to achieve this?

• A. Snowflake Pipes to load and transform the existing data.
• B. Application Role-Based Access Control (RBAC)
• C. Snowflake Streams and Tasks to monitor the application version and trigger the migration scripts automatically.
• D. A post-install script defined in the setup script.
• E. A version change handler defined within the application package.

You have a Snowflake Native Application that utilizes a managed table. After upgrading your application to version 2.0, some users report that they are missing data in the managed table. After investigation, you realize version 2.0 changed the schema of the managed table and also did not properly migrate all the data from old format into new format. Which of the following steps should be taken to address the missing data after upgrading a Snowflake Native Application?

• A. Manually insert the missing data into the managed table in each consumer's account, contacting affected users to coordinate the data entry.
• B. Rollback all users to version 1.0 and then perform the schema migration directly on the consumer's account using custom SQL scripts.
• C. Create a new version 2.1. Within version 2.1's setup script, dynamically detect if the application is an upgrade from 1.0 and, if so, execute the data migration script to transfer data from the old schema to the new schema.
• D. Since managed tables are fully managed by Snowflake, contact Snowflake support to initiate a data recovery process in each affected consumer account.
• E. Create a new version 2.1 that includes a data migration script to transfer data from the old schema (as it existed in version 1.0) to the new schema in version 2.0. Use release directives to upgrade affected users to version 2.1 after staging.

You've installed a Snowflake Native Application that provides advanced data analytics. The application requires a consumer-defined function (UDF), 'MASK SENSITIVE DATA, to be created in their account and used by the application. The application's setup script includes logic to check for the UDF's existence, but you want to ensure the application gracefully handles the case where the consumer has not yet created the UDF. Which of the following strategies can you implement to improve the application's resilience and provide a better user experience in this scenario? Select all that apply.

• A. Implement error handling within the application's code to catch the 'SQL compilation error: UDF does not exists exception. Provide a user-friendly error message and instructions on how to create the UDF.
• B. Within the application's SQL code, use the 'TRY FUNCTION' function to call 'MASK SENSITIVE DATA'. If the UDF does not exist, 'TRY FUNCTION' will return 'NULL' instead of raising an error.
• C. In the application's setup script, create a placeholder UDF with the same name and signature as 'MASK SENSITIVE DATA' that returns 'NULL'. The application logic can then handle 'NULL' values appropriately until the consumer provides the actual UDF.
• D. Require the consumer to create the UDF before installing the application. The application setup script should fail if the UDF is not found, preventing installation.
• E. Dynamically generate the application code using a stored procedure, only including the parts of the code that rely on if the function exists. Use 'SYSTEM$GET PRIVILEGES()' to check existence.

You are developing a Snowflake Native Application that requires specific roles to be assigned to consumers upon installation. Your setup script needs to automatically create these roles if they don't exist and grant appropriate privileges on application objects. Which of the following approaches is the MOST secure and efficient way to achieve this, assuming you want to minimize the attack surface?

• A. Instruct consumers to manually create the roles and grant privileges after installation, providing them with a separate documentation file containing the necessary SQL commands.
• B. Use a UDF to create the roles and grant privileges. This UDF should be owned by the application and be executed with CALLER's rights.
• C. Dynamically generate SQL statements within the setup script based on a configuration table stored within the application package, then execute these statements to create the roles and grant privileges.
• D. Hardcode the role names in the setup script and create them using a stored procedure executed with the 'OWNER privilege. Then, grant the necessary privileges to those roles.
• E. Use a 'CREATE ROLE IF NOT EXISTS' statement within the setup script, followed by 'GRANT statements using the 'APPLICATION' keyword to avoid granting privileges directly to the role within the provider account.