Which actions are considered breaking changes to data that is shared with consumers in the Snowflake Marketplace? (Select TWO).
According to the Snowflake documentation1, breaking changes are changes that affect the schema or structure of the shared data, such as dropping or renaming a column or a table. These changes may cause errors or unexpected results for the consumers who query the shared data. Deleting data from a table, unpublishing the data listing, or adding region availability to the listing are not breaking changes, as they do not alter the schema or structure of the shared data.
1: Managing Data Listings in Snowflake Data Marketplace | Snowflake Documentation
What is a characteristic of Snowflake's transaction locking and concurrency modeling?
According to the Snowflake documentation1, Snowflake uses a multi-version concurrency control (MVCC) model, which means that each transaction operates on a consistent snapshot of the database at a point in time. This allows queries and DML statements to run concurrently without blocking each other, as they do not modify the same data. Therefore, a deadlock, which occurs when concurrent transactions are waiting on resources that are locked by each other, cannot happen in Snowflake. Option B is incorrect because queries and DML statements do not block each other in Snowflake, unless they are explicitly started transactions and multiple statements in each transaction2. Option C is incorrect because transaction locking in Snowflake is enforced at the partition level, not the row or table level3. Option D is incorrect because queries executed within a given transaction do not see that transaction's uncommitted changes, but only the committed changes that occurred before the transaction started1.
Which tasks can be performed by the ORGADMIN role? (Select THREE).
A user with the ORGADMIN role can perform the following tasks1:
* Create one or more accounts in the organization.
* View a list of all regions enabled for the organization.
* View usage information for all accounts in the organization.
Option C is incorrect because creating secure views on application tables is not a function of the ORGADMIN role, but rather a function of the roles that have access to the tables and schemas within the accounts. Option E is incorrect because performing zero-copy cloning on account data is not a function of the ORGADMIN role, but rather a function of the roles that have the CLONE privilege on the objects within the accounts. Option F is incorrect because creating a reader account to share data with another organization is not a function of the ORGADMIN role, but rather a function of the roles that have the CREATE SHARE privilege on the objects within the accounts.
An Administrator has a user who needs to be able to suspend and resume a task based on the current virtual warehouse load, but this user should not be able to modify the task or start a new run.
What privileges should be granted to the user to meet these requirements? (Select TWO).
The user needs the OPERATE privilege on the task to suspend and resume it, and the USAGE privilege on the database and schema containing the task to access it1.The EXECUTE TASK privilege is not required for suspending and resuming a task, only for triggering a new run1. The OWNERSHIP privilege on the task or the database and schema would allow the user to modify or drop the task, which is not desired.
When adding secure views to a share in Snowflake, which function is needed to authorize users from another account to access rows in a base table?
According to the Working with Secure Views documentation, secure views are designed to limit access to sensitive data that should not be exposed to all users of the underlying table(s). When sharing secure views with another account, the view definition must include a function that returns the identity of the user who is querying the view, such as CURRENT_USER, CURRENT_ROLE, or CURRENT_ACCOUNT. These functions can be used to filter the rows in the base table based on the user's identity. For example, a secure view can use the CURRENT_USER function to compare the user name with a column in the base table that contains the authorized user names. Only the rows that match the user name will be returned by the view. The CURRENT_CLIENT function is not suitable for this purpose, because it returns the IP address of the client that is connected to Snowflake, which is not related to the user's identity.
Stephen Campbell
8 days agoTiffany Howard
24 days agoCharles Murphy
17 days agoJennifer Peterson
6 days agoGary Garcia
20 days agoDeborah Turner
3 days agoEdward Young
11 hours agoDarnell
1 month agoFrance
2 months agoSusana
2 months agoMiesha
2 months agoPamella
2 months agoAntonio
3 months agoCammy
3 months agoSage
3 months agoEvelynn
4 months agoWilliam
4 months agoAleisha
4 months agoCarisa
4 months agoVirgina
5 months agoEmilio
5 months agoAmie
5 months agoTijuana
5 months agoHelga
6 months agoStefany
6 months agoJosephine
6 months agoEleonore
6 months agoRory
7 months agoAlaine
7 months agoCyndy
7 months agoArlyne
7 months agoWillard
8 months agoDominga
8 months agoFelicia
8 months agoLouvenia
8 months agoCraig
10 months agoEdwin
11 months agoNieves
1 year agoDaniel
1 year agoBrande
1 year agoTamar
1 year agoAdria
1 year agoJerilyn
1 year agoLindsey
1 year agoSunny
1 year agoLatia
1 year agoMike
2 years agoJaime
2 years agoSylvie
2 years agoGilma
2 years agoPeggie
2 years agoReid
2 years agoMarge
2 years agoErasmo
2 years agoKenda
2 years agoCarey
2 years agoJerilyn
2 years agoEden
2 years agoSanjuana
2 years agoNicolette
2 years agoYoko
2 years agoLou
2 years agoFreida
2 years agoArthur
2 years agoTamar
2 years agoChristiane
2 years agoLai
2 years ago