Easy To Download Snowflake ADA-C01 Exam Dumps Updated 74 Questions [Q20-Q39]

Share

Easy To Download Snowflake ADA-C01 Exam Dumps Updated 74 Questions

New Updated ADA-C01 Exam Questions 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
  • Interpret and make recommendations for data clustering
  • Manage DML locking and concurrency in Snowflake
Topic 3
  • Given a scenario, configure access controls
  • Set up and manage security administration and authorization
Topic 4
  • Given a scenario, manage databases, tables, and views
  • Manage organizations and access control
Topic 5
  • Implement and manage data governance in Snowflake
  • Data Sharing, Data Exchange, and Snowflake Marketplace
Topic 6
  • Set up and manage network and private connectivity
  • Given a scenario, manage Snowflake Time Travel and Fail-safe

 

NEW QUESTION # 20
A large international company with many operating regions requires data to be shared bi-directionally among all offices (head office to regional offices and regional offices among themselves). This company is a Snowflake account holder with European operations deployed in Microsoft Azure (single region) while North American regional offices are using AWS (single region) as their deployment cloud. This setup is required to comply with Personal Identifiable Information (PII) regulations in some of the European countries. The corporate head office is in Europe.
How can this data be shared bi-directionally, while MINIMIZING costs?

  • A. Use the PUT command to move files to an Amazon S3 bucket and Azure Blobs, and use an external file management application to move files within the corporate VPC.
  • B. Use data replication everywhere to reduce costs associated with same-region sharing.
  • C. Use bi-directional data sharing among offices in the same region and replication among offices across the continents.
  • D. Move all the Snowflake accounts to a single region, and implement data sharing.

Answer: C

Explanation:
According to the Snowflake documentation1, data sharing is a feature that allows sharing selected objects in a database in one account with other accounts in the same organization, without copying or transferring any data. Data sharing is supported across regions and across cloud platforms, but it requires enabling account database replication for both the source and target accounts2. Data replication is a feature that allows replicating objects from a source account to one or more target accounts in the same organization, providing read-only access for the replicated objects. Data replication is also supported across regions and across cloud platforms, but it incurs additional storage costs for the replicated data2. Therefore, the best way to share data bi-directionally among all offices, while minimizing costs, is to use data sharing among offices in the same region, which does not require replication or additional storage, and use replication among offices across the continents, which provides near real-time access to the shared data. Option A is incorrect because using data replication everywhere would increase the costs associated with additional storage and compute resources for the replicated data. Option B is incorrect because using the PUT command to move files to an Amazon S3 bucket and Azure Blobs, and using an external file management application to move files within the corporate VPC, would not leverage the benefits of Snowflake's data sharing and replication features, and would also incur additional costs and complexity for data transfer and synchronization. Option C is incorrect because moving all the Snowflake accounts to a single region would violate the PII regulations in some of the European countries, and would also incur additional costs and complexity for data migration and consolidation.


NEW QUESTION # 21
A team is provisioning new lower environments from the production database using cloning. All production objects and references reside in the database, and do not have external references.
What set of object references needs to be re-pointed before granting access for usage?

  • A. Sequences, storage integrations, views, secure views, and materialized views
  • B. Sequences, views, secure views, and materialized views
  • C. Sequences, views, and secure views
  • D. There are no object references that need to be re-pointed

Answer: A

Explanation:
According to the Snowflake documentation1, when an object in a schema is cloned, any future grants defined for this object type in the schema are applied to the cloned object unless the COPY GRANTS option is specified in the CREATE statement for the clone operation. However, some objects may still reference the source object or external objects after cloning, which may cause issues with access or functionality. These objects include:
* Sequences: If a table column references a sequence that generates default values, the cloned table may reference the source or cloned sequence, depending on where the sequence is defined. To avoid conflicts, the sequence reference should be re-pointed to the desired sequence using the ALTER TABLE command2.
* Storage integrations: If a stage or a table references a storage integration, the cloned object may still reference the source storage integration, which may not be accessible or valid in the new environment. To avoid errors, the storage integration reference should be re-pointed to the desired storage integration using the ALTER STAGE or ALTER TABLE command34.
* Views, secure views, and materialized views: If a view references another view or table, the cloned view may still reference the source object, which may not be accessible or valid in the new environment. To avoid errors, the view reference should be re-pointed to the desired object using the CREATE OR REPLACE VIEW command5.
1: Cloning Considerations | Snowflake Documentation 2: [ALTER TABLE | Snowflake Documentation] 3: [ALTER STAGE | Snowflake Documentation] 4: [ALTER TABLE | Snowflake Documentation] 5: [CREATE VIEW | Snowflake Documentation]


NEW QUESTION # 22
What access control policy will be put into place when future grants are assigned to both database and schema objects?

  • A. Database privileges will take precedence over schema privileges.
  • B. An access policy combining both the database object and the schema object will be used, with the most permissive policy taking precedence.
  • C. An access policy combining both the database object and the schema object will be used, with the most restrictive policy taking precedence.
  • D. Schema privileges will take precedence over database privileges.

Answer: D

Explanation:
When future grants are defined on the same object type for a database and a schema in the same database, the schema-level grants take precedence over the database level grants, and the database level grants are ignored4. This behavior applies to privileges on future objects granted to one role or different roles4. Future grants allow defining an initial set of privileges to grant on new (i.e. future) objects of a certain type in a database or a schema3. As soon as the new objects are created inside the database or schema, the predefined set of privileges are assigned to the object automatically without any manual intervention3.


NEW QUESTION # 23
A Snowflake Administrator has a multi-cluster virtual warehouse and is using the Snowflake Business Critical edition. The minimum number of clusters is set to 2 and the maximum number of clusters is set to 10. This configuration works well for the standard workload, rarely exceeding 5 running clusters. However, once a month the Administrator notes that there are a few complex long-running queries that are causing increased queue time and the warehouse reaches its maximum limit at 10 clusters.
Which solutions will address the issues happening once a month? (Select TWO).

  • A. Examine the complex queries and determine if they can be made more efficient using clustering keys or materialized views.
  • B. Increase the multi-cluster maximum to 20 or more clusters.
  • C. Use a task to increase the cluster size for the time period that the more complex queries are running and another task to reduce the size of the cluster once the complex queries complete.
  • D. Increase the minimum number of clusters started in the multi-cluster configuration to 5.
  • E. Have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload.

Answer: C,E

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 A is a possible solution to address the issues happening once a month, as it allows the administrator to use a task to increase the cluster size for the time period that the more complex queries are running and another task to reduce the size of the cluster once the complex queries complete. This way, the warehouse can have more resources available to handle the complex queries without reaching the maximum limit of 10 clusters, and then return to the normal cluster size to save costs. Option B is another possible solution to address the issues happening once a month, as it allows the administrator to have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload. This way, the warehouse can isolate the complex queries from the standard workload and avoid queue time and resource contention. Option C is not a recommended solution to address the issues happening once a month, as it would increase the costs and complexity of managing the multi-cluster warehouse, and may not solve the underlying problem of inefficient queries. Option D is a good practice to improve the performance of the queries, but it is not a direct solution to address the issues happening once a month, as it requires analyzing and optimizing the complex queries using clustering keys or materialized views, which may not be feasible or effective in all cases. Option E is not a recommended solution to address the issues happening once a month, as it would increase the costs and waste resources by starting more clusters than needed for the standard workload.


NEW QUESTION # 24
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 IMPORT SHARE and CREATE DATABASE privileges
  • B. Any role that the listing provider has designated as authorized
  • C. Only the ACCOUNTADMIN role, and no other roles
  • D. Any role with USAGE privilege on the Data Exchange

Answer: D

Explanation:
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 # 25
An Administrator has a warehouse which is intended to have a credit quota set for 3000 for each calendar year. The Administrator needs to create a resource monitor that will perform the following tasks:
1. At 80% usage notify the account Administrators.
2. At 100% usage suspend the warehouse and notify the account Administrators.
3. At 120% stop all running executions, suspend the warehouse, and notify the account Administrators.
Which SQL command will meet these requirements?

  • A. create or replace resource monitor RM1 with credit_quota=3000
    start_timestamp = '2022-01-01 00:00 CET'
    triggers on 80 percent do notify
    on 100 percent do suspend
    on 120 percent do suspend_immediate;
    alter warehouse WH1 set resource_monitor = RM1;
  • B. create or replace resource monitor RM1 with credit_quota=3000
    frequency = yearly
    triggers on 80 percent do notify
    on 100 percent do suspend
    on 120 percent do suspend_immediate;
    alter warehouse WH1 set resource_monitor = RM1;
  • C. create or replace resource monitor RM1 with credit_quota=3000
    start_timestamp = '2022-01-01 00:00 CET'
    triggers on 80 percent do notify
    on 100 percent do notify and suspend
    on 120 percent do notify and suspend_immediate;
    alter warehouse WH1 set resource monitor = RM1;
  • D. create or replace resource monitor RM1 with credit_quota=3000
    frequency = yearly
    start_timestamp = '2022-01-01 00:00 CET'
    triggers on 80 percent do notify
    on 100 percent do suspend
    on 120 percent do suspend_immediate;
    alter warehouse WH1 set resource monitor = RM1;

Answer: D

Explanation:
Option B is the correct SQL command to create a resource monitor that meets the requirements. It sets the credit quota to 3000, the frequency to yearly, the start timestamp to January 1, 2022, and the triggers to notify and suspend the warehouse at the specified thresholds. Option A is incorrect because it does not specify the frequency. Option C is incorrect because it does not specify the frequency and it uses notify and suspend instead of suspend and suspend_immediate. Option D is incorrect because it does not specify the start timestamp. For more information about resource monitors, see Working with Resource Monitors and CREATE RESOURCE MONITOR.


NEW QUESTION # 26
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_CLIENT
  • C. CURRENT_ROLE
  • D. CURRENT_USER

Answer: D

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 # 27
A user has enrolled in Multi-factor Authentication (MFA) for connecting to Snowflake. The user informs the Snowflake Administrator that they lost their mobile phone the previous evening.
Which step should the Administrator take to allow the user to log in to the system, without revoking their MFA enrollment?

  • A. Instruct the user to connect to Snowflake using SnowSQL, which does not support MFA authentication.
  • B. Alter the user and set DISABLE_MFA to true, which will suspend the MFA requirement for 24 hours.
  • C. Alter the user and set MINS TO BYPASS MFA to a value that will disable MFA long enough for the user to log in.
  • D. Instruct the user to append the normal URL with /?mode=mfa_bypass&code= to log on.

Answer: C

Explanation:
The MINS_TO_BYPASS_MFA property allows the account administrator to temporarily disable MFA for a user who has lost their phone or changed their phone number1. The user can log in without MFA for the specified number of minutes, and then re-enroll in MFA using their new phone1. This does not revoke their MFA enrollment, unlike the DISABLE_MFA property, which cancels their enrollment and requires them to re-enroll from scratch1. The other options are not valid ways to bypass MFA, as SnowSQL does support MFA authentication2, and there is no such URL parameter as /?mode=mfa_bypass&code= for Snowflake3


NEW QUESTION # 28
A team of developers created a new schema for a new project. The developers are assigned the role DEV_TEAM which was set up using the following statements:
USE ROLE SECURITYADMIN;
CREATE ROLE DEV TEAM;
GRANT USAGE, CREATE SCHEMA ON DATABASE DEV_DB01 TO ROLE DEV_TEAM;
GRANT USAGE ON WAREHOUSE DEV_WH TO ROLE DEV_TEAM;
Each team member's access is set up using the following statements:
USE ROLE SECURITYADMIN;
CREATE ROLE JDOE_PROFILE;
CREATE USER JDOE LOGIN NAME = 'JDOE' DEFAULT_ROLE='JDOE_PROFILE';
GRANT ROLE JDOE_PROFILE TO USER JDOE;
GRANT ROLE DEV_TEAM TO ROLE JDOE_PROFILE;
New tables created by any of the developers are not accessible by the team as a whole.
How can an Administrator address this problem?

  • A. Set up the new schema as a managed-access schema.
  • B. Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
  • C. Assign ownership privilege to DEV_TEAM on the newly-created schema.
  • D. Set up future grants on the newly-created schemas.

Answer: D

Explanation:
Explanation
According to the Snowflake documentation1, future grants are a way to automatically grant privileges on future objects of a specific type that are created in a database or schema. By setting up future grants on the newly-created schemas, the administrator can ensure that any tables created by the developers in those schemas will be accessible by the DEV_TEAM role, without having to grant privileges on each table individually. Option A is incorrect because assigning ownership privilege to DEV_TEAM on the newly-created schema does not grant privileges on the tables in the schema, only on the schema itself. Option B is incorrect because assigning usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE does not affect the access to the tables in the schemas, only the ability to use the warehouse.
Option D is incorrect because setting up the new schema as a managed-access schema does not grant privileges on the tables in the schema, but rather requires explicit grants for each table.


NEW QUESTION # 29
A company has set up a new Snowflake account. An Identity Provider (IdP) has been configured for both Single Sign-On (SSO) and SCIM provisioning.
What maintenance is required to ensure that the SCIM provisioning process continues to operate without errors?

  • A. The Administrator must issue a POST RENEW call to the REST API at least once every six months.
  • B. The IdP service account requires a new RSA key pair to be generated every six months.
  • C. The OAuth Bearer Tokens have a lifespan of six months and must be regenerated prior to expiration.
  • D. The IdP Administrator must issue a REFRESH transaction at least once every six months to synchronize all users and roles.

Answer: C

Explanation:
According to the Snowflake documentation1, the authentication process for SCIM provisioning uses an OAuth Bearer token and this token is valid for six months. Customers must keep track of their authentication token and can generate a new token on demand. If the token expires, the SCIM provisioning process will fail. Therefore, the token must be regenerated before it expires. The other options are not required for SCIM provisioning.


NEW QUESTION # 30
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 second query includes a CURRENT_DATE () function.
  • B. The queries are executed with two different roles.
  • C. The queries are executed with two different virtual warehouses.
  • D. The second query includes a CURRENT_TIMESTAMP () function.

Answer: C

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 # 31
Which statement allows this user to access this Snowflake account from a specific IP address (192.168.1.100) while blocking their access from anywhere else?

  • A. CREATE NETWORK POLICY ADMIN_POLICY
    ALLOWED IP LIST = ('192.168.1.100')
    BLOCKED_IP_LIST = ('0.0.0.0/0');
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';
  • B. CREATE NETWORK POLICY ADMIN_POLICY
    ALLOWED_IP_LIST = ('192.168.1.100');
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';
    User ABC is the only user with an ACCOUNTADMIN role.
  • C. CREATE NETWORK POLICY ADMIN POLICY
    ALLOWED_IP_LIST = ('192.168.1.100');
    ALTER ROLE ACCOUNTADMIN SET NETWORK_POLICY = 'ADMIN_POLICY';
  • D. CREATE OR REPLACE NETWORK POLICY ADMIN_POLICY
    ALLOWED_IP_LIST = ('192.168. 1. 100/0') ;
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';

Answer: A

Explanation:
Explanation
Option C creates a network policy that allows only the IP address 192.168.1.100 and blocks all other IP addresses using the CIDR notation 0.0.0.0/01. It then applies the network policy to the user ABC, who has the ACCOUNTADMIN role. This ensures that only this user can access the Snowflake account from the specified IP address, while blocking their access from anywhere else. Option A does not block any other IP addresses, option B applies the network policy to the role instead of the user, and option D uses an invalid CIDR notation.


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

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

Answer: B,D,F

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 # 33
Which statement allows this user to access this Snowflake account from a specific IP address (192.168.1.100) while blocking their access from anywhere else?

  • A. CREATE NETWORK POLICY ADMIN_POLICY
    ALLOWED IP LIST = ('192.168.1.100')
    BLOCKED_IP_LIST = ('0.0.0.0/0');
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';
  • B. CREATE NETWORK POLICY ADMIN_POLICY
    ALLOWED_IP_LIST = ('192.168.1.100');
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';
    User ABC is the only user with an ACCOUNTADMIN role.
  • C. CREATE NETWORK POLICY ADMIN POLICY
    ALLOWED_IP_LIST = ('192.168.1.100');
    ALTER ROLE ACCOUNTADMIN SET NETWORK_POLICY = 'ADMIN_POLICY';
  • D. CREATE OR REPLACE NETWORK POLICY ADMIN_POLICY
    ALLOWED_IP_LIST = ('192.168. 1. 100/0') ;
    ALTER USER ABC SET NETWORK_POLICY = 'ADMIN_POLICY';

Answer: A

Explanation:
Option C creates a network policy that allows only the IP address 192.168.1.100 and blocks all other IP addresses using the CIDR notation 0.0.0.0/01. It then applies the network policy to the user ABC, who has the ACCOUNTADMIN role. This ensures that only this user can access the Snowflake account from the specified IP address, while blocking their access from anywhere else. Option A does not block any other IP addresses, option B applies the network policy to the role instead of the user, and option D uses an invalid CIDR notation.


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

  • A. Users must be granted REPLICATIONADMIN privileges in order to enable replication.
  • B. Databases created from shares can be replicated.
  • C. The ALTER DATABASE ... ENABLE REPLICATION TO ACCOUNTS command must be issued from the primary account.
  • D. To start replication run the ALTER DATABASE ... REFRESH command on the account where the secondary database resides.
  • E. Replication can only occur within the same cloud provider.
  • F. 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.

Answer: B,C,F

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 # 35
A Snowflake Administrator has a multi-cluster virtual warehouse and is using the Snowflake Business Critical edition. The minimum number of clusters is set to 2 and the maximum number of clusters is set to 10. This configuration works well for the standard workload, rarely exceeding 5 running clusters. However, once a month the Administrator notes that there are a few complex long-running queries that are causing increased queue time and the warehouse reaches its maximum limit at 10 clusters.
Which solutions will address the issues happening once a month? (Select TWO).

  • A. Increase the multi-cluster maximum to 20 or more clusters.
  • B. Examine the complex queries and determine if they can be made more efficient usingclustering keys or materialized views.
  • C. Use a task to increase the cluster size for the time period that the more complex queries are running and another task to reduce the size of the cluster once the complex queries complete.
  • D. Increase the minimum number of clusters started in the multi-cluster configuration to 5.
  • E. Have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload.

Answer: C,E

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 A is a possible solution to address the issues happening once a month, as it allows the administrator to use a task to increase the cluster size for the time period that the more complex queries are running and another task to reduce the size of the cluster once the complex queries complete. This way, the warehouse can have more resources available to handle the complex queries without reaching the maximum limit of 10 clusters, and then return to the normal cluster size to save costs. Option B is another possible solution to address the issues happening once a month, as it allows the administrator to have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload. This way, the warehouse can isolate the complex queries from the standard workload and avoid queue time and resource contention. Option C is not a recommended solution to address the issues happening once a month, as it would increase the costs and complexity of managing the multi-cluster warehouse, and may not solve the underlying problem of inefficient queries. Option D is a good practice to improve the performance of the queries, but it is not a direct solution to address the issues happening once a month, as it requires analyzing and optimizing the complex queries using clustering keys or materialized views, which may not be feasible or effective in all cases. Option E is not a recommended solution to address the issues happening once a month, as it would increase the costs and waste resources by starting more clusters than needed for the standard workload.


NEW QUESTION # 36
What role or roles should be used to properly create the object required to setup OAuth 2.0 integration?

  • A. ACCOUNTADMIN and SYSADMIN
  • B. ACCOUNTADMIN and SECURITYADMIN
  • C. ACCOUNTADMIN only
  • D. Any role with GRANT USAGE on SECURITY INTEGRATION

Answer: C

Explanation:
Explanation
According to the Using OAuth 2.0 with Snowflake - Blog, only the ACCOUNTADMIN role can create and manage integrations, so an administrator must assume that role when creating a security integration for OAuth.
The other roles do not have the necessary privileges to create the object required to setup OAuth 2.0 integration.


NEW QUESTION # 37
A Snowflake account is configured with SCIM provisioning for user accounts and has bi-directional synchronization for user identities. An Administrator with access to SECURITYADMIN uses the Snowflake UI to create a user by issuing the following commands:
use role USERADMIN;
create or replace role DEVELOPER_ROLE;
create user PTORRES PASSWORD = 'hello world!' MUST_CHANGE_PASSWORD = FALSE default_role = DEVELOPER_ROLE; The new user named PTORRES successfully logs in, but sees a default role of PUBLIC in the web UI. When attempted, the following command fails:
use DEVELOPER_ROLE;
Why does this command fail?

  • A. The DEVELOPER_ROLE needs to be granted to SYSADMIN before user PTORRES will be able to use the role.
  • B. The new role can only take effect after USERADMIN has logged out.
  • C. USERADMIN needs to explicitly grant the DEVELOPER_ROLE to the new USER.
  • D. The new role will only take effect once the identity provider has synchronized by way of SCIM with the Snowflake account.

Answer: C

Explanation:
Explanation
According to the Snowflake documentation1, creating a user with a default role does not automatically grant that role to the user. The user must be explicitly granted the role by the role owner or a higher-level role.
Therefore, the USERADMIN role, which created the DEVELOPER_ROLE, needs to explicitly grant the DEVELOPER_ROLE to the new user PTORRES using the GRANT ROLE command. Otherwise, the user PTORRES will not be able to use the DEVELOPER_ROLE and will see the default role of PUBLIC in the web UI. Option A is incorrect because the DEVELOPER_ROLE does not need to be granted to SYSADMIN before user PTORRES can use the role. Option B is incorrect because the new role can take effect immediately after it is created and granted to the user, and does not depend on the USERADMIN role logging out. Option D is incorrect because the new role will not be affected by the identity provider synchronization, as it is created and managed in Snowflake.


NEW QUESTION # 38
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, Create Stream
  • B. Database: Usage
    Schema: Usage, Create Stream
    Table: Select
  • C. Database: Usage, Create Stream
    Schema: Usage
    Table: Select
  • D. Database: Usage
    Schema: Usage
    Table: Select

Answer: A


NEW QUESTION # 39
......

Updated Free Snowflake ADA-C01 Test Engine Questions with 74 Q&As: https://www.examboosts.com/Snowflake/ADA-C01-practice-exam-dumps.html

The Best SnowPro Advanced: Administrator ADA-C01 Professional Exam Questions: https://drive.google.com/open?id=167yYu3PAZX4AkNSEumZpL2lE_nI4p86k