Free Snowflake ADA-C01 Exam Dumps May 2026

To retrieve a list of schemas deleted within the last 2 days from the DB1 database, you need a metadata view that includes historical data, including dropped (deleted) objects.

Let's review the options:

B. SNOWFLAKE.ACCOUNT_USAGE.SCHEMATA

This is the correct choice because:

It includes metadata for all schemas, even deleted ones, within the retention period.

It contains a DELETED column and a DELETED_ON timestamp column.

You can filter rows with:

sql

CopyEdit

SELECT *

FROM SNOWFLAKE.ACCOUNT_USAGE.SCHEMATA

WHERE DELETED IS TRUE

AND DELETED_ON >= DATEADD(DAY, -2, CURRENT_TIMESTAMP())

AND CATALOG_NAME = 'DB1';

A. SHOW SCHEMAS IN DATABASE DB1;

Only shows current (active) schemas --- does not include deleted schemas.

C. DB1.INFORMATION_SCHEMA.SCHEMATA

Like option A, this view only includes active schemas in the current database.

No info on deleted schemas is retained.

D. SNOWFLAKE.ACCOUNT_USAGE.DATABASES

This metadata view tracks databases, not individual schemas.

SnowPro Administrator Reference:

SNOWFLAKE.ACCOUNT_USAGE.SCHEMATA documentation

Metadata includes both active and deleted schemas (within retention window).

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.

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.

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.