How can an administrator check for updates (for example, SCIM API requests) sent to Snowflake by the identity provider?
Correct Answer: D
To monitor updates, such as SCIM API requests sent to Snowflake by the identity provider, an administrator can use theREST EVENT HISTORYfeature. This feature allows administrators to query historical data about REST API calls made to Snowflake, including those related to user and role management through SCIM (System for Cross-domain Identity Management). TheREST EVENT HISTORYtable function returns information about REST API calls made over a specified period. It is particularly useful for auditing and monitoring purposes, especially when integrating Snowflake with third-party identity providers that use SCIM for automated user provisioning and deprovisioning. An example query to check for SCIM API requests might look like this: SELECT*FROMTABLE(information_schema.rest_event_history(date_range_start=>dateadd('hours',-1,current_ ='SCIM'; This query returns details on SCIM API requests made in the last hour, including the request type, the identity provider's details, and the outcome of each request. Reference: Snowflake Documentation on REST EVENT HISTORY (https://docs.snowflake.com/en/sql-reference/functions/rest_event_history.html)
Question 312
True or False: A Virtual Warehouse can be resized while suspended.
Correct Answer: A
Virtual Warehouses in Snowflake can indeed be resized while they are suspended. Resizing a warehouse involves changing the number of compute resources (servers) allocated to it, which can be done to adjust performance and cost. When a warehouse is suspended, it is not currently running any queries, but its definition and metadata remain intact, allowing for modifications like resizing. Reference: https://docs.snowflake.com/en/user-guide/warehouses-tasks.html#effects-of-resizing-a-suspended-warehouse
Question 313
How can a Snowflake user access a JSON object, given the following table? (Select TWO).
Correct Answer: A,C
To access a JSON object in Snowflake, dot notation is used where the path to the object is specified after the column name containing the JSON data. Both lowercase and uppercase can be used for attribute names, so both "name" and "Name" are valid. References: [COF-C02] SnowPro Core Certification Exam Study Guide
Question 314
True or False: Loading data into Snowflake requires that source data files be no larger than 16MB.
Correct Answer: B
By default, COPY INTO location statements separate table data into a set of output files to take advantage of parallel operations. The maximum size for each file is set using the MAX_FILE_SIZE copy option. The default value is 16777216 (16 MB) but can be increased to accommodate larger files. The maximum file size supported is 5 GB for Amazon S3, Google Cloud Storage, or Microsoft Azure stages. To unload data to a single output file (at the potential cost of decreased performance), specify the SINGLE = true copy option in your statement. You can optionally specify a name for the file in the path.
Question 315
What should be considered when deciding to use a secure view? (Select TWO).
Correct Answer: A,C
When deciding to use a secure view, several considerations come into play, especially concerning security and performance: A;No details of the query execution plan will be available in the query profiler: Secure views are designed to prevent the exposure of the underlying data and the view definition to unauthorized users. Because of this, the detailed execution plans for queries against secure views are not available in the query profiler. This is intended to protect sensitive data from being inferred through the execution plan. C:Secure views do not take advantage of the same internal optimizations as standard views: Secure views, by their nature, limit some of the optimizations that can be applied compared to standard views. This is because they enforce row-level security and mask data, which can introduce additional processing overhead and limit the optimizer's ability to apply certain efficiencies that are available to standard views. B:Once created, there is no way to determine if a view is secure or notis incorrect because metadata about whether a view is secure can be retrieved from the INFORMATION_SCHEMA views or by using theSHOW VIEWScommand. D:It is not possible to create secure materialized viewsis incorrect because the limitation is not on the security of the view but on the fact that Snowflake currently does not support materialized views with the same dynamic data masking and row-level security features as secure views. E:The view definition of a secure view is still visible to users by way of the information schemais incorrect because secure views specifically hide the view definition from users who do not have the privilege to view it, ensuring that sensitive information in the definition is not exposed. Reference: Snowflake Documentation on Secure Views (https://docs.snowflake.com/en/user-guide/views-secure.html)
