You are developing a Snowflake Native Application that requires maintaining multiple live versions for different customer segments. Some customers need to stay on an older version for compatibility reasons, while new customers should use the latest version. How can you best manage these different versions using Snowflake Native App features?

• A. By creating separate Snowflake accounts for each customer segment, each with a different version of the application installed.
• B. By using streams and tasks to replicate data and logic between different versions of the application, ensuring data consistency.
• C. By creating separate application packages for each version and managing them independently, allowing consumers to choose which version to install. The 'APPLICATION ROLE is used to define application-level access.
• D. By leveraging the 'APPLICATION ROLE to control access to different versions using conditional logic within the application code.
• E. By implementing a custom versioning system within the application's stored procedures and functions, relying on consumer-provided parameters to determine which version of the logic to execute.

解説: (CertJuken メンバーにのみ表示されます)

You are developing a Snowflake Native Application that leverages a UDF to perform complex data transformations. During provider-side testing in test mode, you encounter an intermittent error within the UDF. Which of the following strategies are MOST effective in debugging this issue within the limitations of test mode, considering you cannot directly access the consumer's Snowflake account or granular execution logs?

• A. Implement rigorous input validation within the UDF to catch potential data inconsistencies that might be causing the error. Ensure informative error messages are returned for debugging purposes.
• B. Leverage Snowflake's query profiling tools on the provider side against the application's data-sharing objects to identify performance bottlenecks or unexpected behavior within the UDF's execution plan. (Assume data sharing objects are set up for provider side testing)
• C. Use the ALERT' functionality to send notifications to the provider's account whenever the UDF encounters the error, allowing for real-time monitoring of the application's behavior.
• D. Simulate the consumer environment as closely as possible on the provider side by creating a separate Snowflake account with similar data volumes and configurations, then install the application in test mode in that account.
• E. Utilize 'SYSTEM$LOG' within the UDF to output detailed execution information to the application's event table. Analyze these logs after triggering the error in test mode.

解説: (CertJuken メンバーにのみ表示されます)

A Snowflake Native App developer wants to externalize certain configuration values so that a consumer can adjust the app's behavior without modifying the app's code directly. Which of the following methods is the MOST appropriate for achieving this using the Snowflake Native App Framework?

• A. Defining parameters in the manifest file and using them within the application code.
• B. Using Snowflake variables and setting them at the session level.
• C. Hardcoding the configuration values directly into the SQL code.
• D. Using dynamic SQL to modify the application code at runtime based on environment variables.
• E. Storing the configuration values in a separate Snowflake table within the consumer account.

解説: (CertJuken メンバーにのみ表示されます)

You are building a Snowflake Native App that aggregates data across multiple consumer accounts. Your app needs to securely access data in each consumer's Snowflake account without requiring them to share their credentials directly. You are evaluating different options for secure data access. Which of the following strategies are viable and recommended to implement this, maximizing security and minimizing administrative overhead for the consumer?

• A. Utilize Snowflake's Native App data sharing capabilities where the provider app shares data products back to the consumer account and the consumer account can use this inside their apps.
  
• B. Use Snowflake Data Clean Rooms to allow the app to query data from the consumers accounts.
  
• C. Have consumers create and share a JWT (JSON Web Token) with your application. The JWT will be used to authenticate against their Snowflake instance via an external function.
  
• D. Implement a data sharing agreement where consumers create a share from their account and grant usage to your application's account using secure data sharing. The application account can then create a database from this share.
  
• E. Require consumers to grant SELECT privileges on their tables directly to the application's account. This necessitates the consumer to manage grants directly.
  

解説: (CertJuken メンバーにのみ表示されます)

A Snowflake Native Application developer is deploying a Snowpark Container Services service. The 'service.yamr file includes the following configuration snippet for defining the service's endpoint:

• A. Set 'useTls' to true under ports specification. No changes are required to the 'service.yaml' file.
• B. Configure the container application itself to handle TLS termination using a self-signed certificate. No changes are required in the 'service.yaml' file.
• C. Add a TLS certificate and key to the Kubernetes Secret referenced by the 'tls' field in the Ingress configuration. Also, update the port configuration to reflect port 443.
• D.
  
• E. Update the port configuration to use port 443 and set the protocol to 'TLS'. Snowflake automatically handles TLS termination for SPCS services on port 443.

解説: (CertJuken メンバーにのみ表示されます)