Aug 15, 2024 Newest ADA-C01 Exam Dumps – Achieve Success in Actual ADA-C01 Exam [Q15-Q39]

Share

Aug 15, 2024 Newest ADA-C01 Exam Dumps – Achieve Success in Actual ADA-C01 Exam

Updated Snowflake ADA-C01 Dumps – Check Free ADA-C01 Exam Dumps (2024)


Snowflake ADA-C01 Exam Syllabus Topics:

TopicDetails
Topic 1
  • Snowflake Security, Role-Based Access Control (RBAC), and User Administration
  • Disaster Recovery, Backup, and Data Replication
Topic 2
  • Manage and implement data sharing
  • Given a set of business requirements, establish access control architecture
Topic 3
  • Given a scenario, create and manage access control
  • Given a scenario, implement resource monitors
Topic 4
  • Set up and manage network and private connectivity
  • Given a scenario, manage Snowflake Time Travel and Fail-safe
Topic 5
  • Implement and manage data governance in Snowflake
  • Data Sharing, Data Exchange, and Snowflake Marketplace
Topic 6
  • Given a scenario, configure access controls
  • Set up and manage security administration and authorization

 

NEW QUESTION # 15
What are characteristics of Dynamic Data Masking? (Select TWO).

  • A. A single masking policy can be applied to columns with different data types.
  • B. A masking policy can be applied to the VALUE column of an external table.
  • C. A masking policy that is currently set on a table can be dropped.
  • D. The role that creates the masking policy will always see unmasked data in query results.
  • E. A single masking policy can be applied to columns in different tables.

Answer: A,E

Explanation:
Explanation
According to the Using Dynamic Data Masking documentation, Dynamic Data Masking is a feature that allows you to alter sections of data in table and view columns at query time using a predefined masking strategy. The following are some of the characteristics of Dynamic Data Masking:
*A single masking policy can be applied to columns in different tables. This means that you can write a policy once and have it apply to thousands of columns across databases and schemas.
*A single masking policy can be applied to columns with different data types. This means that you can use the same masking strategy for columns that store different kinds of data, such as strings, numbers, dates, etc.
*A masking policy that is currently set on a table can be dropped. This means that you can remove the masking policy from the table and restore the original data visibility.
*A masking policy can be applied to the VALUE column of an external table. This means that you can mask data that is stored in an external stage and queried through an external table.
*The role that creates the masking policy will always see unmasked data in query results. This is not true, as the masking policy can also apply to the creator role depending on the execution context conditions defined in the policy. For example, if the policy specifies that only users with a certain custom entitlement can see the unmasked data, then the creator role will also need to have that entitlement to see the unmasked data.


NEW QUESTION # 16
The ACCOUNTADMIN of Account 123 works with Snowflake Support to set up a Data Exchange. After the exchange is populated with listings from other Snowflake accounts, what roles in Account 123 are allowed to request and get data?

  • A. Any role with USAGE privilege on the Data Exchange
  • B. Any role that the listing provider has designated as authorized
  • C. Only the ACCOUNTADMIN role, and no other roles
  • D. Any role with IMPORT SHARE and CREATE DATABASE privileges

Answer: A

Explanation:
To request and get data from a Data Exchange, the role in Account 123 must have the USAGE privilege on the Data Exchange object. This privilege allows the role to view the listings and request access to the data. According to the Snowflake documentation, "To view the listings in a data exchange, a role must have the USAGE privilege on the data exchange object. To request access to a listing, a role must have the USAGE privilege on the data exchange object and the IMPORT SHARE privilege on the account." The other options are either incorrect or not sufficient to request and get data from a Data Exchange. Option A is incorrect, as the ACCOUNTADMIN role is not the only role that can request and get data, as long as other roles have the necessary privileges. Option C is incorrect, as the IMPORT SHARE and CREATE DATABASE privileges are not required to request and get data, but only to create a database from a share after the access is granted. Option D is incorrect, as the listing provider does not designate the authorized roles in Account 123, but only approves or denies the requests from Account 123.


NEW QUESTION # 17
When does auto-suspend occur for a multi-cluster virtual warehouse?

  • A. When the minimum number of clusters is running and there is no activity for the specified period of time.
  • B. After a specified period of time when an additional cluster has started on the maximum number of clusters specified for a warehouse.
  • C. Auto-suspend does not apply for multi-cluster warehouses.
  • D. When there has been no activity on any cluster for the specified period of time.

Answer: A

Explanation:
According to the Multi-cluster Warehouses documentation, auto-suspend is a feature that allows a warehouse to automatically suspend itself after a specified period of inactivity. For a multi-cluster warehouse, auto-suspend applies to the entire warehouse, not to individual clusters. Therefore, auto-suspend occurs when the minimum number of clusters is running and there is no activity for the specified period of time. The other options are incorrect because:
* A. Auto-suspend does not occur when there has been no activity on any cluster for the specified period of time. This would imply that each cluster has its own auto-suspend timer, which is not the case. The warehouse has a single auto-suspend timer that is reset by any activity on any cluster.
* B. Auto-suspend does not occur after a specified period of time when an additional cluster has started on the maximum number of clusters specified for a warehouse. This would imply that the auto-suspend timer is affected by the number of clusters running, which is not the case. The auto-suspend timer is only affected by the activity on the warehouse, regardless of the number of clusters running.
* D. Auto-suspend does apply for multi-cluster warehouses, as explained above. It is a feature that can be enabled or disabled for any warehouse, regardless of the number of clusters.


NEW QUESTION # 18
DatabaseA has a single schema called Schema1. This schema contains many tables and views. The ANALYST role has privileges to select from all objects in DatabaseA. Schema1. The SYSADMIN role clones DatabaseA to DatabaseA_clone.
What privileges does the ANALYST role have on tables and views in DatabaseA_clone? (Select TWO).

  • A. SELECT on all tables, and only secure views in DatabaseA_clone. Schemal
  • B. SELECT on all tables, and only non-secure views in DatabaseA_clone. Schemal
  • C. SELECT on all tables and views in DatabaseA_clone. Schema1
  • D. USAGE on the database DatabaseA_clone. Schemal
  • E. USAGE on the schema DatabaseA clone

Answer: B,C

Explanation:
Explanation
According to the Snowflake documentation, when a database or schema is cloned, the clone inherits all granted privileges on the clones of all child objects contained in the source object, such as tables and views.
However, the clone of the container itself does not inherit the privileges granted on the source container.
Therefore, the ANALYST role will have SELECT privilege on all tables and views in DatabaseA_clone.Schema1, but not USAGE privilege on the database or schema. The type of view (secure or non-secure) does not affect the cloning of privileges.


NEW QUESTION # 19
Which masking policy will mask a column whenever it is queried through a view owned by a role named MASKED_VIEW_ROLE?

  • A. create or replace masking policy maskString as (val string) returns string -> case when current_role() in ('MASKED_VIEW_ROLE') then ' ********* ' else val end;
  • B. create or replace masking policy maskstring as (val string) returns string -> case when is_role_in_session ('MASKED_VIEW_ROLE') then ' ** else val end;
    *,
  • C. create or replace masking policy maskstring as (val string) returns string -> case when invoker_role() in ('MASKED_VIEW_ROLE') then else val end;
    ' **
  • D. create or replace masking policy maskString as (val string) returns string -> case when array_contains ('MASKED_VIEW_ROLE' :: variant, parse_json (current_available_roles ())) then
    '*
    else val
    end;
    ** '

Answer: B

Explanation:
Explanation
A masking policy is a SQL expression that transforms the data in a column based on the role that queries the column1. The is_role_in_session function returns true if the specified role is in the current session2. Therefore, the masking policy in option A will mask the column data with asterisks whenever it is queried through a view owned by the MASKED_VIEW_ROLE3. The other options use different functions that do not check the ownership of the view, but rather the current role, the invoker role, or the available roles in the session45.
These functions may not return the desired result if the role that owns the view is different from the role that queries the view.


NEW QUESTION # 20
An Administrator has a table named SALES_DATA which needs some edits, but the Administrator does not want to change the main table data. The Administrator decides to make a transient copy of this table and wants the transient table to have all the same permissions as the original table.
How can the Administrator create the transient table so it inherits the same permissions as the original table, and what considerations need to be made concerning the requirements? (Select TWO).

  • A. Use the following SQL command:
    create transient table TRANSIENT_SALES_DATA as select * from SALES_DATA;
  • B. Use the following SQL commands:
    create transient table TRANSIENT_SALES_DATA like SALES_DATA copy grants; insert into TRANSIENT_SALES_DATA select * from SALES_DATA;
  • C. Transient tables will be purged at the end of the user session and do not have any Fail-safe period.
  • D. Use the following SQL command:
    create transient table TRANSIENT SALES DATA as select * from SALES_DATA copy grants;
  • E. Transient tables will persist until explicitly dropped and contribute to overall storage costs.

Answer: D,E

Explanation:
Explanation
According to the Snowflake documentation1, the COPY GRANTS option can be used to copy all privileges, except OWNERSHIP, from the existing table to the new transient table. This option also preserves any future grants defined for the object type in the schema. Option A is incorrect because it does not copy any grants from the original table. Option C is incorrect because it does not copy the data from the original table, only the structure and grants. Option E is incorrect because transient tables are not session-based and do not have a Fail-safe period, but they do have a Time Travel retention period2.
1: CREATE TABLE | Snowflake Documentation 2: Working with Temporary and Transient Tables | Snowflake Documentation


NEW QUESTION # 21
A company has many users in the role ANALYST who routinely query Snowflake through a reporting tool.
The Administrator has noticed that the ANALYST users keep two
small clusters busy all of the time, and occasionally they need three or four clusters of that size.
Based on this scenario, how should the Administrator set up a virtual warehouse to MOST efficiently support this group of users?

  • A. Create a multi-cluster warehouse with MIN_CLUSTERS set to 2. Set the warehouse to auto-resume and auto-suspend, and give USAGE privileges to the ANALYST role. Allow the warehouse to auto-scale.
  • B. Create a standard X-Large warehouse, which is equivalent to four small clusters. Set the warehouse to auto-resume and auto-suspend, and give USAGE privileges to the ANALYST role.
  • C. Create a multi-cluster warehouse with MIN_CLUSTERS set to 1. Give MANAGE privileges to the ANALYST role so this group can start and stop the warehouse, and increase the number of clusters as needed.
  • D. Create four virtual warehouses (sized Small through XL) and set them to auto-suspend andauto-resume.
    Have users in the ANALYST role select the appropriate warehouse based on how many queries are being run.

Answer: A

Explanation:
Explanation
According to the Snowflake documentation1, a multi-cluster warehouse is a virtual warehouse that consists of multiple clusters of compute resources that can scale up or down automatically to handle the concurrency and performance needs of the queries submitted to the warehouse. A multi-cluster warehouse has a minimum and maximum number of clusters that can be specified by the administrator. Option B is the most efficient way to support the group of users, as it allows the administrator to create a multi-cluster warehouse with MIN_CLUSTERS set to 2, which means that the warehouse will always have two clusters running to handle the standard workload. The warehouse can also auto-scale up to the maximum number of clusters (which can be set according to the peak workload) when there is a spike in demand, and then scale down when the demand decreases. The warehouse can also auto-resume and auto-suspend, which means that the warehouse will automatically start when a query is submitted and automatically stop after a period of inactivity. The administrator can also give USAGE privileges to the ANALYST role, which means that the users can use the warehouse to execute queries and load data, but not modify or operate the warehouse. Option A is not efficient, as it requires the users to manually start and stop the warehouse, and increase the number of clusters as needed, which can be time-consuming and error-prone. Option C is not efficient, as it creates a standard X-Large warehouse, which is equivalent to four small clusters, which may be more than needed for the standard workload, and may not be enough for the peak workload. Option D is not efficient, as it creates four virtual warehouses of different sizes, which can be confusing and cumbersome for the users to select the appropriate warehouse based on how many queries are being run, and may also result in wasted resources and costs.


NEW QUESTION # 22
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?

  • A. CURRENT ACCOUNT
  • B. CURRENT_USER
  • C. CURRENT_CLIENT
  • D. CURRENT_ROLE

Answer: B

Explanation:
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.


NEW QUESTION # 23
A company has implemented Snowflake replication between two Snowflake accounts, both of which are running on a Snowflake Enterprise edition. The replication is for the database APP_DB containing only one schema, APP_SCHEMA. The company's Time Travel retention policy is currently set for 30 days for both accounts. An Administrator has been asked to extend the Time Travel retention policy to 60 days on the secondary database only.
How can this requirement be met?

  • A. Set the data retention policy on the primary database to 60 days.
  • B. Set the data retention policy on the schemas in the secondary database to 60 days.
  • C. Set the data retention policy on the primary database to 30 days and the schemas to 60 days.
  • D. Set the data retention policy on the secondary database to 60 days.

Answer: D

Explanation:
Explanation
According to the Replication considerations documentation, the Time Travel retention period for a secondary database can be different from the primary database. The retention period can be set at the database, schema, or table level using the DATA_RETENTION_TIME_IN_DAYS parameter. Therefore, to extend the Time Travel retention policy to 60 days on the secondary database only, the best option is to set the data retention policy on the secondary database to 60 days using the ALTER DATABASE command. The other options are incorrect because:
*B. Setting the data retention policy on the schemas in the secondary database to 60 days will not affect the database-level retention period, which will remain at 30 days. The most specific setting overrides the more general ones, so the schema-level setting will apply to the tables in the schema, but not to the database itself.
*C. Setting the data retention policy on the primary database to 30 days and the schemas to 60 days will not affect the secondary database, which will have its own retention period. The replication process does not copy the retention period settings from the primary to the secondary database, so they can be configured independently.
*D. Setting the data retention policy on the primary database to 60 days will not affect the secondary database, which will have its own retention period. The replication process does not copy the retention period settings from the primary to the secondary database, so they can be configured independently.


NEW QUESTION # 24
Which Snowflake objects can be managed using SCIM integration? (Select TWO).

  • A. Users
  • B. Warehouses
  • C. Shares
  • D. Stages
  • E. Roles

Answer: A,E

Explanation:
Explanation
A SCIM security integration allows the automated management of user identities and groups (i.e. roles) by creating an interface between Snowflake and a third-party Identity Provider (IdP)1. Snowflake supports SCIM integration with Okta, Azure, and custom SCIM clients2. SCIM integration does not support managing other Snowflake objects, such as stages, warehouses, or shares3. Therefore, the answer is B. Users and D. Roles.


NEW QUESTION # 25
What roles can be used to create network policies within Snowflake accounts? (Select THREE).

  • A. SECURITYADMIN
  • B. ACCOUNTADMIN
  • C. SYSADMIN
  • D. ORGADMIN
  • E. Any role with the global permission of CREATE NETWORK POLICY
  • F. Any role that owns the database where the network policy is created

Answer: A,B,E


NEW QUESTION # 26
The following commands were executed:
Grant usage on database PROD to role PROD_ANALYST;
Grant usage on database PROD to role PROD_SUPERVISOR;
Grant ALL PRIVILEGES on schema PROD. WORKING to role PROD_ANALYST;
Grant ALL PRIVILEGES on schema PROD. WORKING to role PROD_SUPERVISOR;
Grant role PROD ANALYST to user A;
Grant role PROD SUPERVISOR to user B;
What authority does each user have on the WORKING schema?

  • A. Tables created by either user A or user B will be visible to both users.
  • B. Both user A and user B can create tables in the PROD. WORKING schema.
  • C. All existing tables in schema PROD. WORKING will be visible to both users.
  • D. Only user B can create tables, because all privileges were transferred to PROD_SUPERVISOR.

Answer: B


NEW QUESTION # 27
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?

  • A. CURRENT ACCOUNT
  • B. CURRENT_USER
  • C. CURRENT_CLIENT
  • D. CURRENT_ROLE

Answer: B

Explanation:
Explanation
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.


NEW QUESTION # 28
DatabaseA has a single schema called Schema1. This schema contains many tables and views. The ANALYST role has privileges to select from all objects in Database A. Schema1.
The SYSADMIN role clones DatabaseA to DatabaseA_clone.
What privileges does the ANALYST role have on tables and views in DatabaseA_clone? (Select TWO).

  • A. SELECT on all tables, and only secure views in DatabaseA_clone. Schemal
  • B. SELECT on all tables, and only non-secure views in DatabaseA_clone. Schemal
  • C. SELECT on all tables and views in DatabaseA_clone. Schema1
  • D. USAGE on the database DatabaseA_clone. Schemal
  • E. USAGE on the schema DatabaseA clone

Answer: B,C

Explanation:
According to the Snowflake documentation, when a database or schema is cloned, the clone inherits all granted privileges on the clones of all child objects contained in the source object, such as tables and views. However, the clone of the container itself does not inherit the privileges granted on the source container. Therefore, the ANALYST role will have SELECT privilege on all tables and views in DatabaseA_clone.Schema1, but not USAGE privilege on the database or schema. The type of view (secure or non-secure) does not affect the cloning of privileges.


NEW QUESTION # 29
An organization's sales team leverages this Snowflake query a few times a day:
SELECT CUSTOMER ID, CUSTOMER_NAME, ADDRESS, PHONE NO
FROM CUSTOMERS
WHERE LAST UPDATED BETWEEN TO_DATE (CURRENT_TIMESTAMP) AND (TO_DATE (CURRENT_TIMESTAMP) -7); What can the Snowflake Administrator do to optimize the use of persisted query results whenever possible?

  • A. Wrap the query in a User-Defined Function (UDF) to match syntax execution.
  • B. Leverage the CURRENT_DATE function for date calculations.
  • C. Assign everyone on the sales team to the same security role.
  • D. Assign everyone on the sales team to the same virtual warehouse.

Answer: B

Explanation:
According to the web search results from my predefined tool search_web, one of the factors that affects the reuse of persisted query results is the exact match of the query syntax1. If the query contains functions that return different values for successive runs, such as CURRENT_TIMESTAMP, then the query will not match the previous query and will not benefit from the cache. To avoid this, the query should use functions that return consistent values for the same day, such as CURRENT_DATE, which returns the current date without the time component2. Option A is incorrect because wrapping the query in a UDF does not guarantee the syntax match, as the UDF may also contain dynamic functions. Option B is incorrect because the virtual warehouse does not affect the persisted query results, which are stored at the account level1. Option C is incorrect because the security role does not affect the persisted query results, as long as the role has the necessary privileges to access the tables and views used in the query1.
1: Using Persisted Query Results | Snowflake Documentation 2: Date and Time Functions | Snowflake Documentation


NEW QUESTION # 30
A company has many users in the role ANALYST who routinely query Snowflake through a reporting tool.
The Administrator has noticed that the ANALYST users keep two
small clusters busy all of the time, and occasionally they need three or four clusters of that size.
Based on this scenario, how should the Administrator set up a virtual warehouse to MOST efficiently support this group of users?

  • A. Create a multi-cluster warehouse with MIN_CLUSTERS set to 2. Set the warehouse to auto-resume and auto-suspend, and give USAGE privileges to the ANALYST role. Allow the warehouse to auto-scale.
  • B. Create a standard X-Large warehouse, which is equivalent to four small clusters. Set the warehouse to auto-resume and auto-suspend, and give USAGE privileges to the ANALYST role.
  • C. Create a multi-cluster warehouse with MIN_CLUSTERS set to 1. Give MANAGE privileges to the ANALYST role so this group can start and stop the warehouse, and increase the number of clusters as needed.
  • D. Create four virtual warehouses (sized Small through XL) and set them to auto-suspend and auto-resume.Have users in the ANALYST role select the appropriate warehouse based on how many queries are being run.

Answer: A

Explanation:
Explanation
According to the Snowflake documentation1, a multi-cluster warehouse is a virtual warehouse that consists of multiple clusters of compute resources that can scale up or down automatically to handle the concurrency and performance needs of the queries submitted to the warehouse. A multi-cluster warehouse has a minimum and maximum number of clusters that can be specified by the administrator. Option B is the most efficient way to support the group of users, as it allows the administrator to create a multi-cluster warehouse with MIN_CLUSTERS set to 2, which means that the warehouse will always have two clusters running to handle the standard workload. The warehouse can also auto-scale up to the maximum number of clusters (which can be set according to the peak workload) when there is a spike in demand, and then scale down when the demand decreases. The warehouse can also auto-resume and auto-suspend, which means that the warehouse will automatically start when a query is submitted and automatically stop after a period of inactivity. The administrator can also give USAGE privileges to the ANALYST role, which means that the users can use the warehouse to execute queries and load data, but not modify or operate the warehouse. Option A is not efficient, as it requires the users to manually start and stop the warehouse, and increase the number of clusters as needed, which can be time-consuming and error-prone. Option C is not efficient, as it creates a standard X-Large warehouse, which is equivalent to four small clusters, which may be more than needed for the standard workload, and may not be enough for the peak workload. Option D is not efficient, as it creates four virtual warehouses of different sizes, which can be confusing and cumbersome for the users to select the appropriate warehouse based on how many queries are being run, and may also result in wasted resources and costs.


NEW QUESTION # 31
What are characteristics of data replication in Snowflake? (Select THREE).

  • A. Users must be granted REPLICATIONADMIN privileges in order to enable replication.
  • B. Users can have unlimited primary databases and they can be replicated to an unlimited number of accounts if all accounts are within the same organization.
  • C. Replication can only occur within the same cloud provider.
  • D. Databases created from shares can be replicated.
  • E. The ALTER DATABASE ... ENABLE REPLICATION TO ACCOUNTS command must be issued from the primary account.
  • F. To start replication run the ALTER DATABASE ... REFRESH command on the account where the secondary database resides.

Answer: B,D,E

Explanation:
* Option A is correct because the ALTER DATABASE ... ENABLE REPLICATION TO ACCOUNTS command must be issued from the primary account that owns the database to be replicated1.
* Option B is incorrect because users must be granted REPLICATIONGRANTER privileges in order to enable replication1.
* Option C is incorrect because to start replication, the ALTER DATABASE ... REFRESH command must be run on the primary database, not the secondary database1.
* Option D is incorrect because replication can occur across different cloud providers, as well as across regions2.
* Option E is correct because databases created from shares can be replicated, as long as the share is active and the database is not dropped or altered1.
* Option F is correct because users can have unlimited primary databases and they can be replicated to an unlimited number of accounts if all accounts are within the same organization1.


NEW QUESTION # 32
What are the MINIMUM grants required on the database, schema, and table for a stream to be properly created and managed?

  • A. Database: Usage
    Schema: Usage
    Table: Select
  • B. Database: Usage
    Schema: Usage
    Table: Select, Create Stream
  • C. Database: Usage, Create Stream
    Schema: Usage
    Table: Select
  • D. Database: Usage
    Schema: Usage, Create Stream
    Table: Select

Answer: B


NEW QUESTION # 33
In which scenario will use of an external table simplify a data pipeline?

  • A. When accessing a Snowflake table from a relational database
  • B. When accessing a Snowflake table from an external database within the same region
  • C. When accessing a Snowflake table that references data files located in cloud storage
  • D. When continuously writing data from a Snowflake table to external storage

Answer: C

Explanation:
According to the Introduction to External Tables documentation, an external table is a Snowflake feature that allows you to query data stored in an external stage as if the data were inside a table in Snowflake. The external stage is not part of Snowflake, so Snowflake does not store or manage the stage. This simplifies the data pipeline by eliminating the need to load the data into Snowflake before querying it. External tables can access data stored in any format that the COPY INTO <table> command supports, such as CSV, JSON, AVRO, ORC, or PARQUET. The other scenarios do not involve external tables, but rather require data loading, unloading, or federation.


NEW QUESTION # 34
What roles can be used to create network policies within Snowflake accounts? (Select THREE).

  • A. SECURITYADMIN
  • B. ACCOUNTADMIN
  • C. SYSADMIN
  • D. ORGADMIN
  • E. Any role with the global permission of CREATE NETWORK POLICY
  • F. Any role that owns the database where the network policy is created

Answer: A,B,E

Explanation:
Network policies are used to restrict access to the Snowflake service and internal stages based on user IP address1. To create network policies, a role must have the global permission of CREATE NETWORK POLICY2. By default, the system-defined roles of SECURITYADMIN and ACCOUNTADMIN have this permission3. However, any other role can be granted this permission by an administrator4. Therefore, the answer is B, C, and E. The other options are incorrect because SYSADMIN and ORGADMIN do not have the CREATE NETWORK POLICY permission by default3, and network policies are not tied to specific databases5.


NEW QUESTION # 35
A Snowflake Administrator is investigating why a query is not re-using the persisted result cache.
The Administrator found the two relevant queries from the SNOWFLAKE. ACCOUNT_USAGE.
QUERY_HISTORY view:

Why is the second query re-scanning micro-partitions instead of using the first query's persisted result cache?

  • A. The queries are executed with two different virtual warehouses.
  • B. The queries are executed with two different roles.
  • C. The second query includes a CURRENT_TIMESTAMP () function.
  • D. The second query includes a CURRENT_DATE () function.

Answer: A

Explanation:
Explanation
The inclusion of the CURRENT_TIMESTAMP() function in the second query prevents it from re-using the first query's persisted result cache because this function makes each execution unique due to the constantly changing timestamp. According to the Snowflake documentation, "The query does not include non-reusable functions, which return different results for successive runs of the same query. UUID_STRING, RANDOM, and RANDSTR are good examples of non-reusable functions." The CURRENT_TIMESTAMP() function is another example of a non-reusable function, as it returns the current date and time at the start of query execution, which varies for each run. Therefore, the second query is not identical to the first query, and the result cache is not reused. The other options are either incorrect or irrelevant to the question. Option B is incorrect, as the CURRENT_DATE() function is a reusable function, as it returns the same value for all queries executed within the same day. Option C is irrelevant, as the virtual warehouse used to execute the query does not affect the result cache reuse. Option D is also irrelevant, as the role used to execute the query does not affect the result cache reuse, as long as the role has the necessary access privileges for all the tables used in the query.


NEW QUESTION # 36
A company enabled replication between accounts and is ready to replicate data across regions in the same cloud service provider.
The primary database object is : PROD_AWS_EAST. Location : AWS_EAST
The secondary database object is : PROD_AWS_WEST. Location : AWS_WEST
What command and account location is needed to refresh the data?

  • A. Location : AWS_WEST
    Command : ALTER DATABASE PROD AWS WEST REFRESH;
  • B. Location : AWS_EAST
    Command : REFRESH DATABASE PROD_AWS_WEST REFRESH;
  • C. Location : AWS_WEST
    Command : REFRESH DATABASE PROD_AWS WEST REFRESH;
  • D. Location : AWS EAST
    Command: ALTER DATABASE PROD_AWS_WEST REFRESH;

Answer: C

Explanation:
The REFRESH DATABASE command is used to refresh a secondary database with the latest data and metadata from the primary database1. The command must be executed in the target account where the secondary database resides2. Therefore, the answer is A, as the location is AWS_WEST and the command is REFRESH DATABASE PROD_AWS_WEST REFRESH. The other options are incorrect because they either use the wrong location, the wrong command, or the wrong database name.


NEW QUESTION # 37
Which tasks can be performed by the ORGADMIN role? (Select THREE).

  • A. Create a reader account to share data with another organization.
  • B. Perform zero-copy cloning on account data.
  • C. Create secure views on application tables within the organization.
  • D. View usage information for all accounts in the organization.
  • E. Create one or more accounts in the organization.
  • F. View a list of all regions enabled for the organization.

Answer: D,E,F

Explanation:
Explanation
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.


NEW QUESTION # 38
A user with the proper role issues the following commands when setting up and activating network policies:
CREATE OR REPLACE NETWORK POLICY foo_policy
ALLOWED_IP_LIST = ( '1.1.1.0/24', '2.2.2.0/24' , '3.3. 3. 0/24' )
BLOCKED IP LIST = ( '1.1.1.1')
COMMENT = 'Account level policy';
ALTER ACCOUNT SET NETWORK_POLICY=FOO_POLICY;
CREATE OR REPLACE NETWORK POLICY bar_policy
ALLOWED_IP_LIST = ('3.3.3.0/24')
BLOCKED IP LIST = ('3.3.3.10')
COMMENT = 'user level policy';
ALTER USER userl SET NETWORK_POLICY=BAR_POLICY;
Afterwards, user1 attempts to log in to Snowflake from IP address 3.3.3.10.
Will the login be successful?

  • A. No, because 3.3.3.10 is not found in the ALLOWED_IP_LIST of foo_policy.
  • B. No, because 3.3.3.10 is found in the BLOCKED_IP_LIST of bar_policy.
  • C. Yes, because 3.3.3.10 is found in the ALLOWED_IP_LIST of bar_policy.
  • D. Yes, because 3.3.3.10 is found in the ALLOWED_IP_LIST of foo_policy.

Answer: B

Explanation:
According to the Snowflake documentation1, network policies are a feature that allows restricting access to your account based on user IP address. A network policy can be applied to an account, a user, or a security integration, and can specify a list of allowed IP addresses and a list of blocked IP addresses. If there are network policies applied to more than one of these, the most specific network policy overrides more general network policies. In this case, the user1 has a network policy (bar_policy) applied to them, which overrides the account-level network policy (foo_policy). The bar_policy allows access only from the IP range 3.3.3.0/24, and blocks access from the IP address 3.3.3.10. Therefore, the user1 will not be able to log in to Snowflake from IP address 3.3.3.10, as it is found in the BLOCKED_IP_LIST of bar_policy. Option A is incorrect because the ALLOWED_IP_LIST of bar_policy does not override the BLOCKED_IP_LIST of bar_policy. Option C is incorrect because the ALLOWED_IP_LIST of foo_policy does not apply to user1, as it is overridden by the user-level network policy. Option D is incorrect because the ALLOWED_IP_LIST of foo_policy does not matter, as it is overridden by the user-level network policy.


NEW QUESTION # 39
......

Actual ADA-C01 Exam Recently Updated Questions with Free Demo: https://www.itcertmagic.com/Snowflake/real-ADA-C01-exam-prep-dumps.html

Valid ADA-C01 exam with Snowflake Real Exam Questions: https://drive.google.com/open?id=1jjeuaqQVc6ryxSFjaLahVBfS-Htm7bao