Free Access Snowflake.NAS-C01.v2026-05-24.q101 Practice Test (Page 16)

Question 71

A Snowflake Native Application, leveraging Snowpark Container Services (SPCS), is designed to perform complex data transformations on data residing within the customer's Snowflake account. The transformations require significant computational resources, and the container occasionally encounters resource constraints, leading to performance degradation. Which of the following strategies can you employ to optimize resource utilization and ensure the container runs efficiently within the customer's SPCS environment?

A.Increase the size of the virtual warehouse associated with the SPCS compute pool. This directly provides more computational resources to the container.

B.Optimize the container image by removing unnecessary dependencies and libraries, reducing its overall size and startup time.

C.Implement horizontal scaling within the container by deploying multiple replicas of the application and distributing the workload among them using a load balancer. The consumer must configure the number of replicas.

D.Rewrite the data transformation logic to utilize Snowflake's built-in SQL functions and stored procedures whenever possible. Move the transformation workload out of the container.

E.Increase the memory and CPU limits specified in the 'spec.yaml' file for the Snowpark Container Services deployment. This provides the container with more resources within the allocated compute pool.

Question 72

You are developing a Snowflake Native Application that utilizes a custom stage for storing large intermediate datasets during processing. Your CI/CD pipeline involves automated testing in a dedicated testing account. To ensure proper isolation and prevent interference with production data, how should you configure the stage path within your application package version definition, considering the stage name might differ between development and test environments?

A.Hardcode the stage name and path directly within the setup script of the version. This approach is simple and ensures consistent access across environments.

B.Use a Snowflake Secret to store the stage path and retrieve it dynamically during application installation. The secret's value will be environment-specific.

C.Employ a versioned configuration file (e.g., YAML) within the application package. The CI/CD pipeline should replace placeholders in the configuration file with environment-specific stage paths before creating the version.

D.Utilize Snowflake's and 'CURRENT functions in conjunction with conditional logic within the application to derive the stage path based on the environment.

E.Define the stage path as a parameter in the application installation script. When installing the application in each environment, pass the correct stage path as an argument.

Question 73

You are managing the release of a new version (v2.0) of your Snowflake Native Application that introduces significant schema changes to shared tables accessed by consumer accounts. To minimize disruption during the upgrade, you want to implement a phased rollout while ensuring backward compatibility for consumers who haven't yet upgraded. Which of the following strategies would allow you to achieve this goal effectively? (Select TWO)

A.Create views on top of the new schema in v2.0 that emulate the old schema from vl .0. Grant consumers 'USAGE' on these views until they upgrade.

B.Use dynamic SQL within stored procedures to conditionally access either the old or new schema based on the consumer's account ID, identified through a custom configuration table.

C.Publish v2.0 without any schema changes and rely on consumers to manually migrate their data to new tables after upgrading.

D.Implement API versioning within your application code and provide compatibility layers to handle requests from consumers running older versions.

E.Create separate versions of the shared tables for vl .0 and v2.0, using views to present a unified interface. Grant consumer 'USAGE on view after upgrading.

Question 74

After publishing your Snowflake Native Application on the Marketplace, you discover that a critical security vulnerability has been identified in a third-party library included in your application package. You need to quickly address this issue and push an updated version to your consumers. What is the recommended sequence of steps to remediate this vulnerability with minimal disruption to your users?

A.1. Deprecate the current version of the application. 2. Develop and test a new version with the updated library. 3. Publish the new version to the Marketplace. 4. Announce the new version to consumers.

B.1. Create a patch for the existing application. 2. Deploy the patch to all consumer accounts. 3. Notify consumers of the updated patch.

C.1. Develop and test a new version with the updated library. 2. Publish the new version as a private listing to selected consumers for testing. 3. Once validated, publish the new version to the Marketplace. 4. Deprecate the vulnerable version. 5. Announce the new version to consumers.

D.1. Immediately unlist the current version of the application. 2. Develop and test a new version with the updated library. 3. Publish the new version to the Marketplace. 4. Announce the new version to consumers.

E.1. Develop and test a new version with the updated library. 2. Publish the new version to the Marketplace. 3. Deprecate the vulnerable version. 4. Announce the new version to consumers.

Question 75

You are managing a Snowflake Native Application that allows consumers to configure certain aspects of its behavior through a dedicated configuration table. The application logic relies on specific values within this table to function correctly. During a new version deployment, you need to ensure that existing consumer configurations are migrated to the new version's configuration table structure without disrupting the application's availability. Which of the following strategies would you use to perform a zero-downtime configuration migration?

A.Drop the existing configuration table and recreate it with the new schema during the application upgrade process. The application will automatically adapt to the new schema once the upgrade is complete.

B.Implement a parallel migration strategy. Create a new configuration table with the new schema alongside the existing one. Update the application code to read from both tables concurrently, prioritizing the new table if values are present. Schedule a background job to migrate data from the old table to the new table. Once the migration is complete and verified, switch the application to solely read from the new table and eventually drop the old one.

C.Rename the existing configuration table to a backup name. Create a new configuration table with the new schema. The application will start using the new empty table, and consumers can manually reconfigure their settings.

D.Perform an in-place alteration of the existing configuration table to match the new schema. This might involve adding, dropping, or renaming columns. Update the application code to reflect these changes. If you need to rename tables, then use SALTER TABLE ... RENAME to minimize downtime.

E.Deploy the new application version with a feature flag that disables the configuration table dependency. Run a script in the background to migrate the data to the new table and then flip the feature flag to enable the new configuration.

Latest Upload: 131Databricks.Databricks-Generative-AI-Engineer-Associate.v2026-08-18.q40; 137SAP.C_CR125_2601.v2026-08-17.q28; 179Salesforce.Field-Service-Consultant.v2026-08-17.q134; 150Oracle.1Z0-1170.v2026-08-16.q64; 157Oracle.1Z1-1170.v2026-08-16.q64; 193Juniper.JN0-336.v2026-08-13.q60; 327EMC.NCP-AII.v2026-08-13.q200; 205CIRO.RSE.v2026-08-12.q41; 175CrowdStrike.CCSE-204.v2026-08-12.q50; 162ISQI.CT-GenAI.v2026-08-11.q14

Question 71

Question 72

Question 73

Question 74

Question 75

Download PDF File