Choose NAS-C01 most accurate study material

A Snowflake Native App provider is developing an application that requires a consumer to execute stored procedures owned by the application. These procedures need to access data within the application's container. Which of the following sets of actions are required for a consumer to successfully execute these stored procedures?

• A. The provider must grant the EXECUTE MANAGED PROCEDURE privilege to the consumer's account and the consumer must be granted USAGE on the application package.
• B. No special actions are required. Consumers can execute any stored procedure within a Native App once the application is installed.
• C. The provider must create a custom role within the application package with the EXECUTE privilege on the stored procedures, and the consumer must be granted authorization to assume that role.
• D. The provider must grant the EXECUTE privilege on the application package and the consumer must create a local role that inherits privileges from the application.
• E. The consumer must be granted the EXECUTE privilege on each stored procedure individually.

You are preparing to deploy a Snowflake Native Application to the Snowflake Marketplace. You have implemented versioning using the 'VERSION' clause in your setup script. Your application relies on a specific shared data source that is only available in the AWS us- west-2 region. To ensure that consumers in other regions can still install and use your application, you decide to offer different versions with region-specific logic. Which of the following approaches is the MOST effective and recommended to manage region-specific configurations and data sharing across multiple versions of your Snowflake Native Application?

• A. Create separate application packages for each region, containing region-specific configurations and data sharing setups. This ensures consumers only install the version relevant to their region.
• B. Implement a build process that generates region-specific setup scripts based on environment variables using a CI/CD pipeline. Each version of the application will then contain the right setup script based on the target region.
• C. Implement conditional logic within the application's stored procedures to check the current region and adjust data sharing and execution accordingly using Package all configurations within a single version.
• D. Use the 'PATCH' clause during application deployment to selectively modify the configuration based on the target region. Deploy the same application package to all regions.
• E. Use separate schemas within the application package for each region, and configure application roles with permissions to only access schemas relevant to their region. No changes to code logic are required.

You are developing a Snowflake Native Application and wish to publish an application package to an external staging location (e.g., AWS S3). You have already created the application package in Snowflake. What are the necessary steps and considerations to ensure the application package is securely and correctly deployed to the external stage, making it accessible to consumers?

• A. Create an IAM role in AWS with appropriate permissions to access the S3 bucket. Create a Snowflake integration object referencing the IAM role. Use the CREATE APPLICATION PACKAGE command with the EXTERNAL STAGE parameter pointing to the Snowflake integration object.
• B. Grant the SNOWFLAKE DEPLOYMENT application role the CREATE STAGE privilege on the external stage. Then, use the CREATE APPLICATION PACKAGE command with the EXTERNAL STAGE parameter pointing to the external stage location.
• C. Grant the ACCOUNTADMIN role to the SNOWFLAKE DEPLOYMENT application role and use the TOKEN function to create credentials. Use these credentials to upload the application package files to the external stage.
• D. Create an APPLICATION PACKAGE, then grant CREATE APPLICATION privilege on the package to SNOWFLAKE DEPLOYMENT role and use the SYSTEM$GENERATE_SCIM_ACCESS_TOKEN function to create credentials. Use these credentials to upload the application package files to the external stage.
• E. Use the PUT command to directly upload the application package files to the external stage. Then, create an APPLICATION using the CREATE APPLICATION command, referencing the uploaded files in the stage using the EXTERNAL_STAGE parameter.

You are designing a Snowflake Native Application that utilizes Snowpark Container Services to provide a data enrichment service for customer dat a. This service requires the application to securely store and manage API keys and other sensitive configuration data. Which of the following methods offers the MOST secure and compliant approach for managing these secrets within the context of a Snowflake Native Application deployed in the customer's environment?

• A. Storing the API keys directly within the container's environment variables during the container build process.
• B. Leveraging Snowflake secrets to securely store and manage the API keys. The container retrieves the secrets at runtime using the Snowflake API or Snowpark.
• C. Encrypting the API keys using a symmetric key and storing them in a Snowflake table. The container retrieves and decrypts the keys at runtime.
• D. Hardcoding the API keys within the application's source code. The source code is obfuscated to make it difficult to extract the keys.
• E. Storing the API keys in an external key management system (KMS) and granting the container access to the KMS using its assigned service account.

You are developing a Snowflake Native Application that requires access to an external API to enrich data within the consumer's account. You need to implement secure authentication and authorization to this external API. Which of the following methods provide the MOST secure and compliant approach for storing and managing the API credentials within your Snowflake Native Application package, while minimizing the risk of exposure to the consumer?

• A. Store the API credentials as environment variables within the Snowflake function code that calls the API. These variables are automatically encrypted by Snowflake.
• B. Store the API credentials as a secret within Snowflake's Secret Management feature, referencing the secret from within your application's functions. Grant access to the secret through the application role.
• C. Store the API credentials in a secure configuration table within your application package, encrypted using a symmetric key managed by Snowflake's KMS.
• D. Prompt the consumer to provide the API credentials during the application installation process, storing them in a secure configuration table within their account and referencing them from your application through secure views.
• E. Store the API credentials as plain text within the setup script, as this script is only executed once during installation and is not accessible to consumers.