Verified ADA-C01 Exam Dumps PDF [2024] Access using ActualVCE [Q27-Q50]

Verified ADA-C01 Exam Dumps PDF [2024] Access using ActualVCE

Try Best ADA-C01 Exam Questions from Training Expert ActualVCE

NEW QUESTION # 27
A data provider wants to share data from multiple databases with a data consumer account.
How can this be accomplished?

• A. The data provider needs to create a secure view and grant the REFERENCE_USAGE privilege on each database referenced by the secure view.
• B. The data provider needs to create a secure view and grant the USAGE privilege on each database referenced by the secure view.
• C. The data provider needs to create a secure view and must grant the REFERENCE_USAGE privilege on the database where the secure view is created.
• D. The data provider needs to create a secure view and grant the REFERENCE_USAGE privilege to a database role to include objects from multiple databases in a share

Answer: A

Explanation:
Explanation
Option B is the correct answer because it follows the steps described in the Snowflake documentation for sharing data from multiple databases using secure views. The data provider needs to grant the REFERENCE_USAGE privilege on each database that contains objects referenced by the secure view, and the USAGE privilege only on the database where the secure view is created. Option A is incorrect because it grants the USAGE privilege instead of the REFERENCE_USAGE privilege. Option C is incorrect because it grants the REFERENCE_USAGE privilege to a database role, which is not supported. Option D is incorrect because it grants the REFERENCE_USAGE privilege on the wrong database.

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

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

Answer: A

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 # 29
For Snowflake network policies, what will occur when the account_level and user_level network policies are both defined?

• A. The user_level policy will override the account_level policy.
• B. The account_level policy will override the user_level policy.
• C. A network policy error will be generated with no definitions provided.
• D. The user_level network policies will not be supported.

Answer: A

Explanation:
Explanation
According to the Network Policies documentation, a network policy can be applied to an account, a security integration, or a user. If there are network policies applied to more than one of these, the most specific network policy overrides more general network policies. The following summarizes the order of precedence:
*Account: Network policies applied to an account are the most general network policies. They are overridden by network policies applied to a security integration or user.
*Security Integration: Network policies applied to a security integration override network policies applied to the account, but are overridden by a network policy applied to a user.
*User: Network policies applied to a user are the most specific network policies. They override both accounts and security integrations.
Therefore, if both the account_level and user_level network policies are defined, the user_level policy will take effect and the account_level policy will be ignored. The other options are incorrect because:
*The account_level policy will not override the user_level policy, as explained above.
*The user_level network policies will be supported, as they are part of the network policyfeature.
*A network policy error will not be generated, as there is no conflict between the account_level and user_level network policies.

NEW QUESTION # 30
Which command can temporarily disable Multi-factor Authentication (MFA) for the Snowflake username user1 for 24 hours?

• A. alter user userl set TEMPORARY_MFA_BYPASS=1440;
• B. alter user userl set MINS_TO_BYPASS_MFA=1440;
• C. alter user userl set HOURS_TO_BYPASS_MFA=24;
• D. alter user userl set DISABLE_MFA=1440;

Answer: B

Explanation:
Explanation
According to the Snowflake documentation1, the MINS_TO_BYPASS_MFA property specifies the number of minutes to temporarily disable MFA for a user so that they can log in without the temporary token generated by the Duo Mobile application. After the time passes, MFA is enforced and the user cannot log in without the token. Therefore, to disable MFA for 24 hours, the value of this property should be set to 1440 minutes (24 x
60). Option B is incorrect because the DISABLE_MFA property is a boolean value that permanently disables MFA for a user, not a numeric value that specifies the duration. Option C is incorrect because there is no such property as TEMPORARY_MFA_BYPASS in Snowflake. Option D is incorrect because there is no such property as HOURS_TO_BYPASS_MFA in Snowflake.

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

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

Answer: C,D

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 # 32
In general, the monthly billing for database replication is proportional to which variables? (Select TWO).

• A. The frequency of the secondary database refreshes from the primary database
• B. The frequency of changes to the primary database as a result of data loading or DML operations
• C. The number of times data moves across regions and/or cloud service providers between the primary and secondary database accounts
• D. The amount of table data in the primary database that changes as a result of data loading or DML operations
• E. The number and size of warehouses defined in the primary account

Answer: B,D

Explanation:
Explanation
Snowflake charges for database replication based on two categories: data transfer and compute resources1.
Data transfer costs depend on the amount of data that is transferred from the primary database to the secondary database across regions and/or cloud service providers2. Compute resource costs depend on the use of Snowflake-provided compute resources to copy data between accounts across regions1. Both data transfer and compute resource costs are proportional to the frequency and amount of changes to the primary database as a result of data loading or DML operations3.
Therefore, the answer is A and B. The other options are not directly related to the replication billing, as the frequency of secondary database refreshes does not affect the amount of data transferred or copied4, and the number and size of warehouses defined in the primary account do not affect the replication process5.

NEW QUESTION # 33
A Snowflake customer is experiencing higher costs than anticipated while migrating their data warehouse workloads from on-premises to Snowflake. The migration workloads have been deployed on a single warehouse and are characterized by a large number of small INSERTs rather than bulk loading of large extracts. That single warehouse has been configured as a single cluster, 2XL because there are many parallel INSERTs that are scheduled during nightly loads.
How can the Administrator reduce the costs, while minimizing the overall load times, for migrating data warehouse history?

• A. The INSERTS should be converted to several tables to avoid contention on large tables that slows down query processing.
• B. There should be another 2XL warehouse deployed to handle a portion of the load queries.
• C. The 2XL warehouse should be changed to 4XL to increase the number of threads available for parallel load queries.
• D. The warehouse should be kept as a SMALL or XSMALL and configured as a multi-cluster warehouse to handle the parallel load queries.

Answer: D

Explanation:
Explanation
According to the Snowflake Warehouse Cost Optimization blog post, one of the strategies to reduce the cost of running a warehouse is to use a multi-cluster warehouse with auto-scaling enabled. This allows the warehouse to automatically adjust the number of clusters based on the concurrency demand and the queue size. A multi-cluster warehouse can also be configured with a minimum and maximum number of clusters, as well as a scaling policy to control the scaling behavior. This way,the warehouse can handle the parallel load queries efficiently without wasting resources or credits. The blog post also suggests using a smaller warehouse size, such as SMALL or XSMALL, for loading data, as it can perform better than a larger warehouse size for small INSERTs. Therefore, the best option to reduce the costs while minimizing the overall load times for migrating data warehouse history is to keep the warehouse as a SMALL or XSMALL and configure it as a multi-cluster warehouse to handle the parallel load queries. The other options are incorrect because:
*A. Deploying another 2XL warehouse to handle a portion of the load queries will not reduce the costs, but increase them. It will also introduce complexity and potential inconsistency in managing the data loading process across multiple warehouses.
*B. Changing the 2XL warehouse to 4XL will not reduce the costs, but increase them. It will also provide more compute resources than needed for small INSERTs, which are not CPU-intensive but I/O-intensive.
*D. Converting the INSERTs to several tables will not reduce the costs, but increase them. It will also create unnecessary data duplication and fragmentation, which will affect the query performance and data quality.

NEW QUESTION # 34
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
  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;
• B. 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;
• C. 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;
• D. 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;

Answer: A

Explanation:
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 # 35
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 EAST
  Command: ALTER DATABASE PROD_AWS_WEST REFRESH;
• B. Location : AWS_WEST
  Command : ALTER DATABASE PROD AWS WEST REFRESH;
• C. Location : AWS_WEST
  Command : REFRESH DATABASE PROD_AWS WEST REFRESH;
• D. Location : AWS_EAST
  Command : REFRESH DATABASE PROD_AWS_WEST REFRESH;

Answer: C

Explanation:
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 # 36
A retailer uses a TRANSACTIONS table (100M rows, 1.2 TB) that has been clustered by the STORE_ID column (varchar(50)). The vast majority of analyses on this table are grouped by STORE_ID to look at store performance.
There are 1000 stores operated by the retailer but most sales come from only 20 stores. The Administrator notes that most queries are currently experiencing poor pruning, with large amounts of bytes processed by even simple queries.
Why is this occurring?

• A. Sales across stores are not uniformly distributed.
• B. The cardinality of the stores to transaction count ratio is too low to use the STORE_ID as a clustering key.
• C. The table is not big enough to take advantage of the clustering key.
• D. The STORE_ID should be numeric.

Answer: A

Explanation:
Explanation
According to the Snowflake documentation1, clustering keys are most effective when the data is evenly distributed across the key values. If the data is skewed, such as in this case where most sales come from only
20 stores out of 1000, then the micro-partitions will not be well-clustered and the pruning will be poor. This means that more bytes will be scanned by queries, even if they filter by STORE_ID. Option A is incorrect because the data type of the clustering key does not affect the pruning. Option B is incorrect because the table is large enough to benefit from clustering, if the data was more balanced. Option D is incorrect because the cardinality of the clustering key is not relevant for pruning, as long as the key values are distinct.
1: Considerations for Choosing Clustering for a Table | Snowflake Documentation

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

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

Answer: B

Explanation:
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 # 38
An Administrator receives data from a Snowflake partner. The partner is sharing a dataset that contains multiple secure views. The Administrator would like to configure the data so that only certain roles can see certain secure views.
How can this be accomplished?

• A. Create views over the incoming shared database and apply the desired RBAC onto these views.
• B. Apply RBAC directly onto the partner's shared secure views.
• C. Clone the data and insert it into a company-owned share and apply the desired RBAC on the new tables.
• D. Individually grant imported privileges onto the schema in the share.

Answer: A

Explanation:
Explanation
According to the Snowflake documentation1, secure views are only exposed to authorized users who have been granted the role that owns the view. Therefore, applying RBAC directly onto the partner's shared secure views (option A) is not possible, as the administrator does not own those views. Individually granting imported privileges onto the schema in the share (option B) is also not feasible, as the privileges granted on the schema do not apply to existing secure views, only tofuture ones2. Cloning the data and inserting it into a company-owned share (option C) is not recommended, as it would create unnecessary duplication of data and increase storage costs. The best option is to create views over the incoming shared database and apply the desired RBAC onto these views (option D). This way, the administrator can control the access to the data based on the roles in their account, without modifying the original data or views from the partner.

NEW QUESTION # 39
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 found in the BLOCKED_IP_LIST of bar_policy.
• B. No, because 3.3.3.10 is not found in the ALLOWED_IP_LIST of foo_policy.
• C. Yes, because 3.3.3.10 is found in the ALLOWED_IP_LIST of foo_policy.
• D. Yes, because 3.3.3.10 is found in the ALLOWED_IP_LIST of bar_policy.

Answer: A

Explanation:
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 # 40
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. Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
• B. Set up the new schema as a managed-access schema.
• C. Set up future grants on the newly-created schemas.
• D. Assign ownership privilege to DEV_TEAM on the newly-created schema.

Answer: C

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 # 41
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 data replication everywhere to reduce costs associated with same-region sharing.
• B. Use bi-directional data sharing among offices in the same region and replication among offices across the continents.
• C. Move all the Snowflake accounts to a single region, and implement data sharing.
• D. 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.

Answer: B

Explanation:
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 # 42
A Snowflake Administrator created a role ROLE_MANAGED_ACCESS and a schema SCHEMA_MANAGED_ACCESS as follows:
USE ROLE SECURITYADMIN;
CREATE ROLE ROLE_MANAGED_ACCESS;
GRANT ROLE ROLE_MANAGED_ACCESS TO ROLE SYSADMIN;
GRANT USAGE ON WAREHOUSE COMPUTE_WH TO ROLE ROLE_MANAGED_ACCESS;
GRANT ALL privileges ON DATABASE WORK TO ROLE ROLE_MANAGED_ACCESS;
USE ROLE ROLE_MANAGED_ACCESS;
CREATE SCHEMA SCHEMA_MANAGED_ACCESS WITH MANAGED ACCESS;
USE ROLE SECURITYADMIN;
GRANT SELECT, INSERT ON FUTURE TABLES IN SCHEMA SCHEMA MANAGED ACCESS to ROLE_MANAGED_ACCESS; The Administrator now wants to disable the managed access on the schema.
How can this be accomplished?

• A. USE ROLE ROLE MANAGED_ACCESS;
  DROP SCHEMA WORK. SCHEMA_MANAGED_ACCESS;
  CREATE SCHEMA SCHEMA_MANAGED_ACCESS;
  Then recreate all needed objects.
• B. USE ROLE ROLE_MANAGED_ACCESS;
  DROP SCHEMA WORK. SCHEMA MANAGED_ACCESS;
  CREATE SCHEMA SCHEMA_MANAGED_ACCESS WITHOUT MANAGED ACCESS;
  Then recreate all needed objects.
• C. ALTER SCHEMA SCHEMA MANAGED ACCESS DISABLE MANAGED ACCESS;
• D. REVOKE SELECT, INSERT ON FUTURE TABLES IN SCHEMA SCHEMA_MANAGED_ACCESS FROM ROLE_MANAGED_ACCESS; ALTER SCHEMA SCHEMA MANAGED ACCESS DISABLE MANAGED ACCESS;

Answer: C

Explanation:
Explanation
According to the Snowflake documentation1, you can change a managed access schema to a regular schema using the ALTER SCHEMA statement with the DISABLE MANAGED ACCESS keywords. This will disable the managed access feature on the schema and revert the access control to the default behavior. Option B is incorrect because dropping and recreating the schema will also delete all the objects and metadata in the schema, which is not necessary to disable the managed access. Option C is incorrect because revoking the privileges on the future tables from the role is not required to disable the managed access. Option D is incorrect because there is no WITHOUT MANAGED ACCESS option in the CREATE SCHEMA statement.

NEW QUESTION # 43
When a role is dropped, which role inherits ownership of objects owned by the dropped role?

• A. The SYSADMIN role
• B. The role executing the command
• C. The role above the dropped role in the RBAC hierarchy
• D. The SECURITYADMIN role

Answer: C

Explanation:
Explanation
According to the Snowflake documentation1, when a role is dropped, ownership of all objects owned by the dropped role is transferred to the role that is directly above the dropped role in the role hierarchy. This is to ensure that there is always a single owner for each object in the system.
1: Drop Role | Snowflake Documentation

NEW QUESTION # 44
What is required for stages, without credentials, to limit data exfiltration after a storage integration and associated stages are created?

• A. ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION = true;
  ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION FOR STAGE_OPERATION = true;
  ALTER ACCOUNT my_account SET
  PREVENT_UNLOAD_TO_INLINE_URL = true;
• B. ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION = true;
  ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_OPERATION = true;
  ALTER ACCOUNT my_account SET
  PREVENT_UNLOAD_TO_INLINE_URL = false;
• C. ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION = false;
  ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_OPERATION = false;
  ALTER ACCOUNT my_account SET
  PREVENT_UNLOAD_TO_INLINE_URL = true;
• D. ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION = false;
  ALTER ACCOUNT my_account SET
  REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_OPERATION = false;
  ALTER ACCOUNT my_account SET
  PREVENT_UNLOAD_TO_INLINE_URL = false;

Answer: A

Explanation:
Explanation
According to the Snowflake documentation1, stages without credentials are a way to create external stages that use storage integrations to access data files in cloud storage without providing any credentials to Snowflake.
Storage integrations are objects that define a trust relationship between Snowflake and a cloud provider, allowing Snowflake to authenticate and authorize access to the cloud storage. To limit data exfiltration after a storage integration and associated stages are created, the following account-level parameters can be set:
*REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION: This parameter enforces that all external stages must be created using a storage integration. This prevents users from creating external stages with inline credentials or URLs that point to unauthorized locations.
*REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_OPERATION: This parameter enforces that all operations on external stages, such as PUT, GET, COPY, and LIST, must use a storage integration. This prevents users from performing operations on external stages with inline credentials or URLs that point to unauthorized locations.
*PREVENT_UNLOAD_TO_INLINE_URL: This parameter prevents users from unloading data from Snowflake tables to inline URLs that do not use a storage integration. This prevents users from exporting data to unauthorized locations.
Therefore, the correct answer is option D, which sets all these parameters to true. Option A is incorrect because it sets PREVENT_UNLOAD_TO_INLINE_URL to false, which allows users to unload data to inline URLs that do not use a storage integration. Option B is incorrect because it sets both REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_CREATION and REQUIRE_STORAGE_INTEGRATION_FOR_STAGE_OPERATION to false, which allows users to create and operate on external stages without using a storage integration. Option C is incorrect because it sets all the parameters to false, which does not enforce any restrictions on data exfiltration.

NEW QUESTION # 45
An Administrator wants to delegate the administration of a company's data exchange to users who do not have access to the ACCOUNTADMIN role.
How can this requirement be met?

• A. Grant imported privileges on data exchange EXCHANGE_NAME to ROLE_NAME;
• B. Grant modify on data exchange EXCHANGE_NAME to ROLE_NAME;
• C. Grant usage on data exchange EXCHANGE_NAME to ROLE_NAME;
• D. Grant ownership on data exchange EXCHANGE_NAME to ROLE NAME;

Answer: B

Explanation:
Explanation
According to the [GRANT MODIFY] documentation, the MODIFY privilege on a data exchange allows a role to perform administrative tasks on the data exchange, such as inviting members, approving profiles, and reviewing listings. This privilege can be granted by the ACCOUNTADMIN role or a role that already has the MODIFY privilege on the data exchange. Therefore, to delegate the administration of a company's data exchange to users who do not have access to the ACCOUNTADMIN role, the best option is to grant the MODIFY privilege on the data exchange to a role that the users can assume. The other options are incorrect because:
*A. There is no such privilege as IMPORTED PRIVILEGES in Snowflake. The correct privilege name is IMPORT SHARE, which allows a role to create a database from a share. This privilege is not related to the administration of a data exchange, but to the consumption of shared data.
*C. There is no such privilege as OWNERSHIP in Snowflake. The correct privilege name is OWNED BY, which indicates the role that owns an object and has full control over it. However, this privilege cannot be granted or revoked, but only transferred by the current owner to another role using the GRANT OWNERSHIP command. Therefore, this option is not feasible for delegating the administration of a data exchange.
*D. The USAGE privilege on a data exchange allows a role to access the data exchange and view the available data listings. This privilege does not allow a role to perform administrative tasks on the data exchange, such as inviting members, approving profiles, and reviewing listings. Therefore, this option is not sufficient for delegating the administration of a data exchange.

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

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

Answer: B,C,F

Explanation:
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 # 47
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 will only take effect once the identity provider has synchronized by way of SCIM with the Snowflake account.
• C. The new role can only take effect after USERADMIN has logged out.
• D. USERADMIN needs to explicitly grant the DEVELOPER_ROLE to the new USER.

Answer: D

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 # 48
What SCIM integration types are supported in Snowflake? (Select THREE).

• A. Amazon Web Services (AWS)
• B. Google Cloud Platform (GCP)
• C. Azure Active Directory (Azure AD)
• D. Duo Security Provisioning Connector
• E. Custom
• F. Okta

Answer: C,E,F

Explanation:
Explanation
According to the Snowflake documentation1, Snowflake supports SCIM 2.0 to integrate Snowflake with Okta and Microsoft Azure AD, which both function as identity providers. Snowflake also supports identity providers that are neither Okta nor Microsoft Azure (i.e. Custom). Therefore, theSCIM integration types that are supported in Snowflake are Okta, Custom, and Azure AD. Option A is incorrect because Amazon Web Services (AWS) is not a SCIM identity provider. Option B is incorrect because Google Cloud Platform (GCP) is not a SCIM identity provider. Option F is incorrect because Duo Security Provisioning Connector is not a SCIM identity provider.

NEW QUESTION # 49
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 append the normal URL with /?mode=mfa_bypass&code= to log on.
• 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 connect to Snowflake using SnowSQL, which does not support MFA authentication.

Answer: C

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

Latest 100% Passing Guarantee - Brilliant ADA-C01 Exam Questions PDF: https://www.actualvce.com/Snowflake/ADA-C01-valid-vce-dumps.html

Practice Examples and Dumps & Tips for 2024 Latest ADA-C01 Valid Tests Dumps: https://drive.google.com/open?id=1H_ODRbmDVA7GKIleik7dmeG27rIpE1Cl