What action should be taken if a large number of concurrent queries are queued in a virtual warehouse?
Scale-up by resizing the warehouse.
Scale-out with a multi-cluster warehouse.
Disable auto-suspend on the warehouse.
Enable auto-resume on the warehouse.
A JSON document is stored in the source_colum of type VARIANT. The document has an array called elements. The array contains the name key that has a string value How can a Snowflake user extract the name from the first element?
Source_column.element[1]:name
Source_column.element[0]:name
Source_column.element[1].name
Source_column.element[0]:name
In Snowflake, when dealing with semi-structured data such as a JSON document stored in a VARIANT column, the proper syntax to extract a value is to use the column name followed by the path to the specific element. Since arrays in JSON are zero-indexed, the first element is referenced with [0]. Therefore, to extract the name from the first element of the elements array, the correct syntax is Source_column:elements[0].name.References: Snowflake Documentation on Semi-Structured Data
Which typos of charts does Snowsight support? (Select TWO).
Area charts
Bar charts
Column charts
Radar charts
Scorecards
Snowsight, Snowflake’s user interface for executing and analyzing queries, supports various types of visualizations to help users understand their data better. Among the supported types, area charts and bar charts are two common options. Area charts are useful for representing quantities through the use of filled areas on the graph, often useful for showing volume changes over time. Bar charts, on the other hand, are versatile for comparing different groups or categories of data. Both chart types are integral to data analysis, enabling users to visualize trends, patterns, and differences in their data effectively.References: Snowflake Documentation on Snowsight Visualizations
If a virtual warehouse is suspended, what happens to the warehouse cache?
The cache is dropped when the warehouse is suspended and is no longer available upon restart.
The warehouse cache persists for as long the warehouse exists, regardless of its suspension status.
The cache is maintained for up to two hours and can be restored If the warehouse Is restarted within this limit.
The cache is maintained for the auto suspend duration and can be restored it the warehouse 15 restarted within this limit.
When a virtual warehouse in Snowflake is suspended, the cache is dropped and is no longer available upon restart. This means that all cached data, including results and temporary data, are cleared from memory. The purpose of this behavior is to conserve resources while the warehouse is not active. Upon restarting the warehouse, it will need to reload any data required for queries from storage, which may result in a slower initial performance until the cache is repopulated. This is a critical consideration for managing performance and cost in Snowflake.
Which privilege is required for a user to be able to view a resource monitor?
USAGE
SELECT
MONITOR
OPERATE
The following settings are configured:
THE MIN_DATA_RETENTION_TIME_IN_DAYS is set to 5 at the account level.
THE DATA_RETENTION_TIME_IN_DAYS is set to 2 at the object level.
For how many days will the data be retained at the object level?
2
3
5
7
The settings shown in the image indicate that the data retention time in days is configured at two different levels: the account level and the object level. At the account level, the MIN_DATA_RETENTION_TIME_IN_DAYS is set to 5 days, and at the object level, the DATA_RETENTION_TIME_IN_DAYS is set to 2 days. Since the object level setting has a lower value, it takes precedence over the account level setting for the specific object. Therefore, the data will be retained for 2 days at the object level.References: Snowflake Documentation on Data Retention Policies
What is the expiration period tor a file URL used to access unstructured data in cloud storage?
The remainder of the session
An unlimited amount of time
The length of time specified in the expiration_time argument
The same length of time as the expiration period for the query results cache
When will Snowflake charge credits for the use of the Cloud Services layer?
Credits will be charged whenever the Cloud Services layer is used.
Credits will be charged only when running a Snowflake-provisioned compute warehouse comfute_wh.
Credits will be charged when the daily consumption of cloud services resources exceeds Wo of the daily warehouse usage.
Credits will be charged only when a virtual warehouse consumes serverless compute services.
Who can access the data published in a Data Exchange?
Only the data provider who published the data
Any Snowflake user, regardless of their role or permissions
Any user who has been provided with a unique Data Exchange URL
Only the users that the data provider has invited to the Data Exchange
Snowflake's Data Exchange allows data providers to publish data that is accessible only to users they explicitly invite. This mechanism ensures that only approved users or Snowflake accounts have access, adding a layer of security and control. Invited users can query the shared data directly within their Snowflake account without requiring data copies, reducing redundancy and enhancing data accessibility within controlled boundaries. This selective sharing feature is part of Snowflake’s secure data-sharing capabilities.
STION NO: 17
How can a data provider validate that a secure view is configured to display only the data the provider wishes to expose?
Log in to the data consumer account and check if the secure view data is appearing as expected.
Create a data share for a test data consumer account and check if the secure view data is appearing as expected.
Query the secure view from a consumer account by setting the share_restrictions parameter.
Simulate querying the secure view by setting the simulated_data_sharing_consumer session parameter.
The most effective way for a data provider to validate secure view configurations is to create a data share for a test data consumer account. This method allows the provider to review and confirm that only the intended data is accessible in the secure view. Secure views are designed to mask or restrict data visibility, so creating a test share replicates the consumer's experience and ensures data security before sharing with actual consumers.
While unloading data into a stage, how can the user ensure that the output will be a single file?
Use the copy option files=single.
Use the COPY Option SINGLE=TRUE .
Use the get option SINGLE-TRUE.
Use the GET option FILES-SINGLE.
To ensure that the output will be a single file when unloading data into a stage, you should use the COPY option SINGLE=TRUE. This option specifies that the result of the COPY INTO command should be written to a single file, rather than multiple files.
References:
Snowflake Documentation: COPY INTO
Who can create network policies within Snowflake? (Select TWO).
SYSADMIN only
ORCADMIN only
SECURITYADMIN or higher roles
A role with the CREATE NETWORK POLICY privilege
A role with the CREATE SECURITY INTEGRATION privilege
In Snowflake, network policies define the allowed IP address ranges from which users can connect to Snowflake, enhancing security by restricting access based on network location. The creation and management of network policies require sufficient privileges. Specifically, a user with the SECURITYADMIN role or any role with higher privileges, such as ACCOUNTADMIN, can create network policies. Additionally, a custom role can be granted the CREATE NETWORK POLICY privilege, enabling users assigned to that role to also create network policies. This approach allows for flexible and secure management of network access to Snowflake.References: Snowflake Documentation on Network Policies
What should be considered when deciding to use a secure view? (Select TWO).
No details of the query execution plan will be available in the query profiler.
Once created there is no way to determine if a view is secure or not.
Secure views do not take advantage of the same internal optimizations as standard views.
It is not possible to create secure materialized views.
The view definition of a secure view is still visible to users by way of the information schema.
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 not is incorrect because metadata about whether a view is secure can be retrieved from the INFORMATION_SCHEMA views or by using the SHOW VIEWS command.
D. It is not possible to create secure materialized views is 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 schema is 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.
Which Snowflake object is supported by both database replication and replication groups?
Pipes
Users
Stages
Materialized views
Secured Data Sharing is allowed for which Snowflake database objects? (Select TWO).
Tables
User-Defined Table Functions (UDTFs)
Secure views
Stored procedures
Worksheets
Snowflake allows secure data sharing for specific database objects to ensure data is shared securely and efficiently. The primary objects that can be shared securely are tables and secure views.
Tables: Share actual data stored in tables.
Secure Views: Share derived data while protecting the underlying table structures and any sensitive information.
References:
Snowflake Documentation: Introduction to Secure Data Sharing
Snowflake Documentation: Creating Secure Views
A Snowflake user is trying to load a 125 GB file using SnowSQL. The file continues to load for almost an entire day. What will happen at the 2< hour mark?
The file will continue to load until all contents arc loaded.
The tile will slop loading and all data up to that point will be committed.
The file loading could be aborted without any portion of the file being committed.
The file's number of allowable hours to load can be programmatically controlled to load easily into Snowflake
When attempting to load large files, such as a 125 GB file, into Snowflake using SnowSQL, the process might encounter limitations related to the maximum execution time for queries or data loading operations. If the loading process exceeds this time limit (typically around 24 hours), it could be aborted without committing any part of the file to the database. This behavior is designed to prevent indefinite resource consumption and to maintain system stability, emphasizing the need for optimizing data load operations, possibly through file segmentation or parallel loading strategies.References: Snowflake Documentation on Data Loading Considerations
What optional properties can a Snowflake user set when creating a virtual warehouse? (Select TWO).
Auto-suspend
Cache size
Default role
Resource monitor
Storage size
When creating a virtual warehouse in Snowflake, users have the option to set several properties to manage its behavior and resource usage. Two of these optional properties are Auto-suspend and Resource monitor.
Auto-suspend: This property defines the period of inactivity after which the warehouse will automatically suspend. This helps in managing costs by stopping the warehouse when it is not in use.
CREATE WAREHOUSE my_warehouse
WITH WAREHOUSE_SIZE = 'XSMALL'
AUTO_SUSPEND = 300; -- Auto-suspend after 5 minutes of inactivity
Resource monitor: Users can assign a resource monitor to a warehouse to control and limit the amount of credit usage. Resource monitors help in setting quotas and alerts for warehouse usage.
CREATE WAREHOUSE my_warehouse
WITH WAREHOUSE_SIZE = 'XSMALL'
RESOURCE_MONITOR = 'my_resource_monitor';
References:
Snowflake Documentation: Creating Warehouses
Snowflake Documentation: Resource Monitors
What virtual warehouse configuration should be used when processing a large number of complex queries?
Use the auto-resume feature.
Run the warehouse in auto-scale mode.
Increase the size of the warehouse.
Increase the number of warehouse clusters.
To handle a large number of complex queries, configuring the warehouse in auto-scale mode by increasing the number of warehouse clusters is recommended. This setup allows Snowflake to dynamically add clusters as demand increases, ensuring better performance and concurrency. Increasing the number of clusters provides scalability for concurrent users and heavy workloads, improving response times without impacting individual query performance.
Given the statement template below, which database objects can be added to a share?(Select TWO).
GRANT
Secure functions
Stored procedures
Streams
Tables
Tasks
In Snowflake, shares are used to share data across different Snowflake accounts securely. When you create a share, you can include various database objects that you want to share with consumers. According to Snowflake's documentation, the types of objects that can be shared include tables, secure views, secure materialized views, and streams. Secure functions and stored procedures are not shareable objects. Tasks also cannot be shared directly. Therefore, the correct answers are streams (C) and tables (D).
To share a stream or a table, you use the GRANT statement to grant privileges on these objects to a share. The syntax for sharing a table or stream involves specifying the type of object, the object name, and the share to which you are granting access. For example:
GRANT SELECT ON TABLE my_table TO SHARE my_share; GRANT SELECT ON STREAM my_stream TO SHARE my_share;
These commands grant the SELECT privilege on a table named my_table and a stream named my_stream to a share named my_share. This enables the consumer of the share to access these objects according to the granted privileges.
When used with the UNLOAD command, which parameter specifies the destination of unloaded data?
COPY INTO