Snowflake SnowPro Specialty - Native Apps - NAS-C01 模擬練習

A.

B.

C.

D.

E.

A. Package the data extraction logic directly into the Native App using User-Defined Functions (UDFs) that establish secure connections to each consumer account using separate credentials stored securely within the application package.

B. Grant SELECT privileges directly to the application role on all relevant tables in the consumer accounts.

C. Utilize secure data sharing with data clean rooms, exposing the required datasets via views on each data clean room.

D. Create a shared database from each consumer account containing views over the required tables, granting SELECT privileges on these views to the application role.

E. Implement a data access service within the Native App that uses external functions to query data from consumer accounts, relying on network policies for security.

A. Use Snowflake's built-in resource monitors to proactively track application consumption and alert consumers when they approach predefined spending limits.

B. Implement a tiered pricing model based on data volume processed, compute resources consumed, or number of users accessing the application. Offer a free basic tier with limited functionality.

C. Offer a free trial period with limited functionality to allow potential consumers to evaluate the application before committing to a paid subscription.

D. Provide detailed cost estimation documentation outlining the expected costs for different usage scenarios and data volumes.

E. Refrain from providing any cost-related information upfront to encourage broader adoption, deferring cost discussions until after installation and usage.

A. Create a series of external functions that are called when the application's data changes. These functions will call an external notification service that alerts consumers.

B. Grant SELECT privileges on the managed tables directly to consumer accounts, using secure views to filter data.

C. Leverage Snowflake's event tables (using EVENT TABLES) to capture significant data changes, then create an API function using 'CREATE FUNCTION' with 'RETURNS TABLE' in the application package to expose these events to consumers through a secure share. Implement RBAC within the API function to manage access.

D. Use Snowflake Streams and Tasks within the provider account to continuously monitor the managed tables and create events that are pushed to a shared data lake. Consumers then access the data lake.

E. Implement a Python UDF that queries the managed tables and sends email notifications to consumers whenever a threshold is breached.

A. The statement will execute successfully, returning the session ID of the current session in which the stored procedure is running, provided the caller has USAGE privilege on the database.

B. The statement will execute successfully, but the 'session_id' will always be null as the 'READ SESSION' privilege does not apply within stored procedures.

C. The statement will execute successfully, returning the session ID of the current session in which the stored procedure is running, provided the Native App has the 'READ SESSION' privilege (implicitly or explicitly).

D. The statement will execute successfully, returning the session ID of the user who installed the Native Application.

E. The statement will fail because the READ SESSION' privilege is not automatically granted to stored procedures. You must explicitly grant the privilege to the stored procedure's owner.

A. Write a Python script leveraging the Snowflake Connector for Python to upload the files using multi-threading or asynchronous operations.

B. Use the Snowflake Visual Studio Code (VS Code) extension's built-in file upload feature, which automatically handles parallel uploads.

C. Use the 'PUT ' command with the 'PARALLEL' option enabled in SnowSQL.

D. Utilize Snowflake's internal staging using 'PUT command on Internal stage for smaller file and external stage for larger file and then copy the larger file from external to internal by referencing file URL.

E. Compress the files into a single ZIP archive before uploading using the 'PUT' command.

A. Install the 'requests' library on each Snowflake virtual warehouse used by the application.

B. Create a stage to store the Anaconda packages and reference them when calling the UDF from Streamlit.

C. Specify the library in the 'imports' clause when creating the UDF using the opackageS decorator. For example:

D. Use 'snowflake.ingest.SimplelngestManager' to manage the library dependencies within the application's metadata.

E. Import the library directly in the UDF code using 'import requests'. Snowflake automatically handles external dependencies.

A. Raise a support ticket with the provider through the Snowflake Marketplace. Include example queries, input data, and the expected vs. actual results to facilitate their debugging process. Further, Query data using different warehouse sizes to see if concurrency is a factor.

B. Use on the provider's account to establish a secure connection and directly debug the provider's stored procedures.

C. Contact Snowflake Support and provide them with a detailed description of the issue and relevant query examples. Snowflake Support can access the provider's environment and investigate.

D. Utilize the 'DEBUG' procedure exposed by the application (if any) to step through the risk calculation logic with specific input values.

E. Examine the 'INSTALLATION INFORMATION' view in the application's database to check for provider-published error messages or status updates related to data quality issues. Use queries to identify patterns in the inconsistent results.

A. Granting SELECT privilege directly on the underlying tables in the app's data schema to the consumer's role.

B. Creating stored procedures with the 'EXECUTE AS OWNER privilege and granting USAGE on the schema to the consumer's role. The stored procedures handle all data access logic.

C. Creating stored procedures with the 'EXECUTE AS CALLER privilege and granting USAGE on the schema to the consumer's role. The stored procedures handle all data access logic.

D. Granting OWNERSHIP on the app's data schema to the consumer's role, allowing them full control over the data.

E. Creating secure views on top of the underlying tables and granting SELECT privilege on these views to the consumer's role, while ensuring consumers can only access the exposed view.

A. Use Snowflake Secrets to store the API key securely and grant access to the APPLICATION role. Then, access the secret within your Stored Procedure or UDF.

B. Store the API key in a separate configuration file uploaded to a stage, encrypting the file with a symmetric key hardcoded in the application.

C. Store the API key directly in the application code as a constant variable.

D. Store the API key in a secure vault (e.g., HashiCorp Vault) and use an external function to retrieve the key at runtime. Implement appropriate authentication and authorization for the external function.

E. Store the API key as an environment variable in the Snowflake environment.

A. Create a Snowflake external table that directly reads data from the external source. Mount this external table within the container service and perform sentiment analysis directly on the external data.

B. Configure a Snowflake Task to periodically load data from the event table into an internal stage and then trigger the Snowpark Container Service to process the data from the stage.

C. Use a Snowflake Stream on the event table and continuously poll the Stream from within the Snowpark Container Service using the Snowpark API.

D. Implement a Snowpipe pipeline that continuously loads data from an external stage into the event table. Then use a database trigger on the event table to invoke a stored procedure that calls the Snowpark Container Service.

E. Utilize Snowflake Event Tables and subscribe the Snowpark Container Service to the event table. Process incoming events using a Snowpark Python function within the container, leveraging its ability to handle concurrent requests.