NAS-C01試験無料問題集「Snowflake SnowPro Specialty - Native Apps 認定」

A. Create an API integration, implement a service (e.g., AWS Lambda) that queries the data and grant 'USAGE on the API Integration and appropriate permissions on the service to the Streamlit application's role.

B. Grant 'SELECT privilege directly on the protected table to the Streamlit application's role.

C. Use an external function (UDF) owned by the application to query the protected table and grant USAGE' privilege on the UDF to the Streamlit application's role.

D. Create a secure view on the protected table and grant 'SELECT privilege on the secure view to the Streamlit application's role.

E. Create a stored procedure with 'EXECUTE AS CALLER which queries the protected table and grant 'USAGE privilege on the procedure to the Streamlit application's role.

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

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. Install the 'requests' library on each Snowflake virtual warehouse used by the application.

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

A. Implement logging within the stored procedure to capture the execution flow and intermediate data values. Use 'SYSTEM$GET PREDECESSORS to track dependencies. Analyze the logs to identify the race condition. Use a session table rather than a temp table.

B. Isolate the portion of the stored procedure that writes to the temporary table into a separate stored procedure with 'EXECUTE AS CALLER privileges.

C. Use Snowflake's 'GET_DDL' function to retrieve the SQL definition of the consumer's query and analyze it for potential errors.

D. Implement a retry mechanism with exponential backoff in the stored procedure to handle potential concurrency issues when writing to the temporary table.

E. Replace the temporary table with a permanent table with appropriate locking mechanisms to prevent concurrent modifications. Consumers will need to be notified of a minor version update.

A. Regions are inherently globally available so it cannot be restricted. Include the EULA within the code of the application, forcing the user to acknowledge it through the code.

B. Use the Snowflake CLI to programmatically set the allowed regions using the 'snowflake marketplace application update' command. Include a link to an external website hosting the EULA in the listing description.

C. During listing creation, select the 'Custom EULA' option and provide the EULA text directly within the designated field. Configure the 'Availability' section to specify the allowed regions.

D. Configure the 'Availability' section of the listing to specify allowed regions. Upload the EULA as a PDF document within the 'Documentation' section.

E. Specify the allowed regions in the 'Availability' section of the listing. Upload a text file containing the EULA and mark it as 'Required Agreement' in the listing settings.

A. Create a patch version with bug fixes and create a new minor version with schema changes, and release it as an upgrade on the Marketplace.

B. Deprecate the existing version of the application and force all consumers to upgrade to the new version within 24 hours.

C. Create a new version of the application with the updated logic and schema, test it thoroughly, and then release it as an upgrade on the Marketplace.

D. Directly modify the application's code and schema in the production environment, then announce the changes to consumers.

E. Modify the existing application's code and schema, create a new listing for the updated version, and remove the old listing.

A. Package all necessary data within the application itself, eliminating the need for external data sources.

B. Utilize Snowflake's data replication feature to replicate the internal stages and associated data to regional Snowflake accounts.

C. Configure the application to access data in a central, globally accessible stage, regardless of the user's region.

D. Design the application to use external stages (e.g., AWS S3, Azure Blob Storage) in each region and implement logic to access the nearest stage based on the user's location.

E. Replicate the entire Snowflake account across all regions where the app is deployed.

A. 

B. 

C. 

D. 

E. 

A. The Streamlit application is not aware of the application package's Python environment. You need to set the environment variable within the Streamlit application to point to the directory containing 'my_module'.

B. Streamlit does not support custom Python modules within Snowflake Native Applications. You must use only built-in Python modules or those available through Anaconda.

C. The correct handler is not specified in the 'manifest.ymr file.

D. The 'my_module' is not located in the correct directory structure within the application package. Ensure it's placed in the 'src' directory (or the directory specified in 'package-name' in 'setup.py') and the directory structure mirrors the package structure required for import.

E. The 'my_module' is not included in the file for your application package. Add it to the 'packages' list in 'setup.py'.

A. Ensure the stage containing the Python file is explicitly referenced with 'OWNER' rights in the application manifest file.

B. Explicitly grant 'USAGE privilege on the stage to each role within the application that will execute the UDF in the 'setup.sqr script.

C. Grant the 'READ privilege on the stage to the schema in the provider account before building the application package.

D. Include the Python code for the UDF inline within the 'CREATE FUNCTION' statement, instead of referencing an external stage.

E. Grant on the stage and 'USAGE' on the database and schema containing the stage to the 'SNOWFLAKCORE.BUILTIN APP API' schema in the provider account before building the application package.

A. Store audit logs in an external stage, leveraging cloud storage. Implement periodic data loading from the stage into a Snowflake table for querying.

B. Store audit logs as JSON files in a variant column within a Snowflake table.

C. Store audit logs directly in a Snowflake table, leveraging clustering keys and partitioning for efficient querying and maintenance.

D. Send audit logs to a third-party logging service via external functions. Maintain a summary table within Snowflake containing aggregated audit data.

E. Write audit logs to a Snowflake queue. Configure a Snowpipe to load the data continuously into a Snowflake table.

A. CREATE VIEW app_db.internal_schema.consumer_view AS SELECT coll , c012 FROM app_db.internal_schema.sensitive_data; GRANT SELECT ON VIEW app_db.internal_schema.consumer_view TO ROLE consumer_role;

B. CREATE OR REPLACE SECURE VIEW app_db.internal_schema.consumer_view AS SELECT coll , c012 FROM app_db.internal_schema.sensitive_data; GRANT SELECT ON VIEW TO ROLE consumer_role;

C. CREATE OR REPLACE SECURE VIEW app_db.internal_schema.consumer_view AS SELECT coll , c012 FROM app_db.internal_schema.sensitive_data; GRANT SELECT ON VIEW TO ROLE consumer_role; REVOKE ALL PRIVILEGES ON VIEW app_db.internal_schema.consumer_view FROM ROLE PUBLIC;

D. CREATE OR REPLACE SECURE VIEW app_db.internal_schema.consumer_view AS SELECT coll , c012 FROM app_db.internal_schema.sensitive_data; GRANT ALL PRIVILEGES ON VIEW TO ROLE consumer_role;

E. CREATE OR REPLACE VIEW app_db.internal_schema.consumer_view AS SELECT coll , c012 FROM app_db.internal_schema.sensitive_data; GRANT ALL PRIVILEGES ON VIEW TO ROLE consumer_role;