- (Topic 6)
How many credits does a size 3X-Large virtual warehouse consume if it runs continuously for 2 hours?
Correct Answer:C
In Snowflake, the consumption of credits by a virtual warehouse is determined by its size and the duration for which it runs. A size 3X-Large virtual warehouse consumes 128 credits if it runs continuously for 2 hours. This consumption rate is based on the principle that larger warehouses, capable of providing greater computational resources and throughput, consume more credits per hour of operation. The specific rate of consumption is defined by Snowflake??s pricing model and the scale of the virtual warehouse.References:Snowflake Pricing Documentation
- (Topic 5)
If a virtual warehouse runs for 61 seconds, shut down, and then restart and runs for 30 seconds, for how many seconds is it billed?
Correct Answer:C
Snowflake bills virtual warehouse usage in one-minute increments, rounding up to the nearest minute for any partial minute of compute time used. If a virtual warehouse runs for 61 seconds and then, after being shut down, restarts and runs for an additional 30 seconds, the total time billed would be 120 seconds or 2 minutes. The first 61 secondsare rounded up to 2 minutes, and the subsequent 30 seconds are within a new minute, which is also rounded up to the nearest minute.
References:
✑ Snowflake Documentation: Virtual Warehouses Billing
- (Topic 6)
Authorization to execute CREATE
Correct Answer:A
In Snowflake, the authorization to executeCREATE <object>statements, such as creating tables, views, databases, etc., is determined by the role currently set as the user's primary role. The primary role of a user or session specifies the set of privileges(including creation privileges) that the user has. While users can have multiple roles, only the primary role is used to determine what objects the user can create unless explicitly specified in the session.
Reference: This is based on the principle of Role-Based Access Control (RBAC) in Snowflake, where roles are used to manage access permissions. The official Snowflake documentation on Understanding and Using Roles would be the best resource to verify this information: https://docs.snowflake.com/en/user-guide/security-access-control- overview.html#roles
- (Topic 6)
In addition to performing all the standard steps to share data, which privilege must be granted on each database referenced by a secure view in order to be shared?
Correct Answer:D
In addition to performing all the standard steps to share data, theUSAGEprivilege must be granted on each database referenced by a secure view in order to be shared. When sharing a database or specific objects like secure views, the receiving account needs to have theUSAGEprivilege on the database and schema to access the shared data. This privilege enables the receiving account to access the database and its schemas but does not allow for any DML operations. It's a prerequisite for accessing any objects within the database.
For a secure view to be part of a share, not only does the view itself need to be shared, but the underlying database (and schema, if applicable) must also be accessible to therecipients. GrantingUSAGEprivilege on the database ensures that the receiving account can access the database in a read-only mode to utilize the shared view.
References:
✑ Snowflake Documentation on Shares: Creating and Managing Shares
- (Topic 3)
What action can a user take to address query concurrency issues?
Correct Answer:C
To address query concurrency issues, a user can add additional clusters to the virtual warehouse. This allows for the distribution of queries across multiple clusters, reducing the load on any single cluster and improving overall query performance2.
- (Topic 5)
Which function should be used to insert JSON format string data inot a VARIANT field?
Correct Answer:C
To insert JSON formatted string data into a VARIANT field in Snowflake, the correct function to use isPARSE_JSON. ThePARSE_JSONfunction is specifically designed to interpret a JSON formatted string and convert it into a VARIANT type, which is Snowflake's flexible format for handling semi-structured data like JSON, XML, and Avro. This function is essential for loading and querying JSON data within Snowflake, allowing users to store and manage JSON data efficiently while preserving its structure for querying purposes. This function's usage and capabilities are detailed in the Snowflake documentation, providing users with guidance on how to handle semi-structured data effectively within their Snowflake environments.
References:
✑ Snowflake Documentation: PARSE_JSON