SnowflakeProfessional levelADA-C01Page 6 of 6

ADA-C01 exam dumps: questions 501 to 565 of 565

Page 6 of the free ADA-C01 question bank for the SnowPro® Advanced: Administrator exam. Questions 501 to 565 are listed below, the first 5 in full with answers and explanations. Back to page 1 for the exam overview and FAQ.

Question bank last updated April 2026

Start timed practice exam Questions 501 to 565

Free ADA-C01 practice questions

Questions 501 to 505 of 565

Pick an answer before you open the explanation. Each question also has its own page with a permalink.

ADA-C01 Question 501

Single answerManage Native Apps

A Snowflake administrator manages a consumer account where a Native App from Snowflake Marketplace has already been installed and is used by several analyst roles. The security team now requires the administrator to verify what privileges and objects the app has access to before approving an upgrade to a newer app version. Which action should the administrator take to review the app's granted permissions and references in a way that aligns with Native App management best practices?

A
Use SHOW APPLICATIONS and DESCRIBE APPLICATION on the installed app to review its metadata, including granted references and version details before upgrading.
B
Query ACCOUNT_USAGE.GRANTS_TO_ROLES for the app name, because Native Apps are managed only as role grants and do not expose application-level metadata.
C
Clone the application package into a separate database and inspect its setup script there, because installed Native Apps can only be reviewed by cloning the package.
D
Use SHOW DATABASES to locate the app objects, because Native Apps are exposed only as standard databases and their permissions are reviewed the same way as shared databases.

Show answer and explanation

Correct answer: A

Explanation

For Native Apps, Snowflake distinguishes between provider-side objects such as the APPLICATION PACKAGE and consumer-side installed APPLICATION objects. In a consumer account, administrators should use Native App management commands to inspect the installed app rather than treating it only as a database or only as a collection of grants. SHOW APPLICATIONS helps identify installed apps, and DESCRIBE APPLICATION is the key command for reviewing installed application details before operational actions such as upgrades. This aligns with Snowflake Native App Framework administration practices, where app lifecycle tasks like inspecting versions, references, and configuration are handled through application-level metadata rather than package cloning or generic database inspection.

A. Correct.
Correct. In the consumer account, an installed Native App is managed as an application object. SHOW APPLICATIONS lists installed apps, and DESCRIBE APPLICATION provides key metadata about the installed app, such as version-related information and details needed to assess configuration, including references and privileges the application requires or uses. This is the appropriate administrative path before approving an upgrade.
B. Incorrect.
Incorrect. Although grant-related views can help analyze some access patterns in Snowflake generally, a Native App is not administered only through standard role-grant inspection. Relying solely on ACCOUNT_USAGE.GRANTS_TO_ROLES misses application-specific metadata and does not provide the focused visibility administrators need for Native App review and upgrade readiness.
C. Incorrect.
Incorrect. Consumers do not manage installed Native Apps by cloning the provider's application package. Application packages are provider-side objects used to build and publish apps, not consumer-side objects used for normal review of installed apps. This option confuses provider development workflow with consumer administration.
D. Incorrect.
Incorrect. Native Apps are not reviewed solely as standard databases. While an app may create or expose objects internally, the installed unit is an application object with its own management commands. Using SHOW DATABASES would not provide the complete, app-specific permission and reference information needed for upgrade review.

ADA-C01 Question 502

Single answerManage Native Apps

A Snowflake administrator at a consumer account needs to deploy a Snowflake Native App from a private listing for a security analytics vendor. The vendor's app requires creating application objects in the consumer account and needs access to a specific events database after installation. The security team requires that the app receive only the minimum privileges needed, and they do not want to grant broad account-level access during installation. Which action should the administrator take to meet these requirements?

A
Install the app using a role with ACCOUNTADMIN, because Native Apps require full account-level privileges to create application objects and request data access.
B
Install the app, then grant the app access only to the required events database or specific objects through application roles and privileges requested by the app.
C
Create the app in a reader account first, validate requested privileges there, and then promote it into the consumer account to avoid granting access directly.
D
Clone the events database into the application container so the app can read the cloned data without any additional grants after installation.

Show answer and explanation

Correct answer: B

Explanation

The best answer is to install the app and then explicitly grant only the required access to the app for the events database or specific underlying objects. In Snowflake Native Apps, consumers retain control over what the installed application can access in their account. This is a key security property of the Native App Framework: the app can request privileges or references, but the consumer decides whether to grant them. From an administrator perspective, the correct pattern is to follow least-privilege access, review what the app requests, and grant only the minimum necessary permissions after installation rather than defaulting to ACCOUNTADMIN-level access. This aligns with Snowflake documentation and best practices for managing Native Apps, application roles, and consumer-controlled privilege grants.

A. Incorrect.
Incorrect. Native Apps do not inherently require broad ACCOUNTADMIN access simply because they create application objects. While a sufficiently privileged role is needed to install and manage the application package in the consumer account, best practice is to avoid unnecessary account-level privileges and grant only the permissions the app actually needs. Using ACCOUNTADMIN as a blanket requirement violates least-privilege principles.
B. Correct.
Correct. This approach aligns with how Snowflake Native Apps are managed in consumer accounts. After installation, the consumer can grant the application access to specific databases, schemas, or objects that the app requests, rather than granting broad privileges upfront. This supports least privilege and allows the administrator to control exactly what data the app can use.
C. Incorrect.
Incorrect. Reader accounts are not used as a staging area for Native App validation in this way. A reader account is a special Snowflake account managed by a provider for data sharing use cases, not a mechanism for testing or promoting Native Apps into another consumer account. This option reflects a common misunderstanding between data sharing constructs and Native App lifecycle management.
D. Incorrect.
Incorrect. An installed Native App does not gain unrestricted ability to duplicate consumer data into its own context just to avoid grants. Cloning a consumer database into an application's managed objects is not the standard or intended security model for granting app data access. Native Apps typically rely on explicit consumer grants to shared content or referenced objects.

ADA-C01 Question 503

Select 2Domain 6.0: Disaster Recovery, Backup, and Data Replication (9%)

A company runs a business-critical Snowflake application in AWS us-east-1 and maintains a secondary account in AWS us-west-2 for disaster recovery. The primary account contains a database with several schemas, tables, and secure views. The DR requirement is to keep the secondary account nearly current and, during a regional outage, allow reporting workloads to resume quickly with minimal data loss. The administrator is configuring database replication and failover groups. Which TWO actions are required to meet this requirement?

A
Add the database to a failover group and periodically refresh the failover group in the secondary account so replicated objects stay current.
B
Enable replication for the database and include the database in a replication or failover configuration between the primary and secondary accounts.
C
Create a database clone in the secondary account; cross-region clones automatically stay synchronized with the source database.
D
Promote the secondary database to read/write before the first replication refresh so that applications can pre-stage writes in the DR region.
E
Configure application clients to use the secondary account only after the replicated database or failover group has been failed over or promoted during an outage.

Show answer and explanation

Correct answers: B, E

Explanation

Snowflake disaster recovery across regions/accounts is based on replication and failover, not on continuously synchronized clones. For databases, administrators configure replication from a primary database to a secondary database in another account/region and periodically refresh the secondary to control recovery point objectives. For broader account-level DR, failover groups can replicate supported objects such as databases and certain account objects needed for operational continuity. Secondary replicated databases are read-only until they are promoted or failed over, so applications must be redirected to the DR account after failover during an outage. This aligns with Snowflake best practices for business continuity: define replication scope, schedule refreshes to meet RPO, and document failover procedures including client redirection and role/object validation. See Snowflake documentation on database replication, replication groups/failover groups, and failover/promotion behavior for secondary databases.

A. Incorrect.
Incorrect. A failover group is refreshed from the primary side after objects are added and replication is configured; the statement is misleading because the required foundational step is enabling replication for supported objects and configuring the replication/failover relationship between accounts. Also, failover groups are used to replicate a broader set of account objects, while databases themselves are replicated as primary/secondary databases. Simply saying to 'add the database to a failover group and refresh in the secondary account' is not the correct required action as stated.
B. Correct.
Correct. To use Snowflake cross-region disaster recovery, the database must be configured for replication to a secondary account. Depending on what needs protection, administrators use database replication and/or failover groups for supported account objects. This is the core requirement for keeping the secondary nearly current with periodic refreshes from the primary.
C. Incorrect.
Incorrect. A clone is a point-in-time copy and does not provide ongoing synchronization across regions or accounts. Cloning is useful for fast copies inside Snowflake, but it is not a disaster recovery mechanism for keeping a secondary region continuously updated.
D. Incorrect.
Incorrect. A replicated secondary database is read-only until a failover or promotion occurs. You cannot pre-stage writes to the secondary before failover. This option reflects a common misconception that secondary replicas can be used as active-active writable databases.
E. Correct.
Correct. During normal operation, replicated secondary databases remain read-only. In a regional outage, workloads can resume in the DR account only after administrators perform the appropriate failover/promotion process and redirect clients there. Updating client connectivity is a necessary operational step to actually use the DR environment.

ADA-C01 Question 504

Select 2Domain 6.0: Disaster Recovery, Backup, and Data Replication (9%)

A company runs a business-critical Snowflake deployment in AWS us-east-1 and must meet a disaster recovery objective that allows analytics workloads to be resumed in another region with minimal administrative effort. The source account contains several databases, including one shared from a different provider account and one database with an external stage that points to an S3 bucket in us-east-1. The Snowflake administrator configures account replication to a secondary account in AWS us-west-2 and performs regular refreshes. During a regional outage, the team plans to fail over to the secondary account. Which TWO statements correctly describe what the administrator should expect after failover?

A
Primary databases that are included in the replication configuration can become writable in the secondary account after failover.
B
The shared database that originated from another provider account will be fully replicated and available for failover in the secondary account.
C
The external stage definition may exist after replication, but access depends on the target region having connectivity and appropriate access to the referenced S3 location.
D
Virtual warehouses from the primary account will be replicated so compute capacity is immediately available after failover without additional setup.
E
Historical query results cache from the primary account will be replicated so identical queries in the failover account can reuse the same cached results.

Show answer and explanation

Correct answers: A, C

Explanation

Snowflake disaster recovery relies on replication and failover capabilities for supported account and database objects, but administrators must distinguish between replicated metadata/data and non-replicated operational components. After failover, replicated databases become writable in the secondary account, enabling business continuity. However, inbound shared databases are not treated as fully owned primary databases for replication/failover, so they should not be assumed to appear as failover-ready copies. External stages require special attention because Snowflake can replicate object definitions, but the underlying external storage remains in the cloud provider account and region originally configured; access, network reachability, and IAM permissions must still work from the failover environment. Also, warehouses and result cache are not replicated, so DR planning should include provisioning compute in the target account and validating dependencies on external storage. These expectations align with Snowflake documentation on replication and failover, limitations for shared data, and the behavior of external stages and compute resources in cross-region disaster recovery designs.

A. Correct.
Correct. With database or account replication and failover groups, replicated databases in the secondary account are read-only until failover occurs. After failover/promoting the secondary, the replicated objects become writable in the failover target, which is the core mechanism used to resume operations during a disaster recovery event.
B. Incorrect.
Incorrect. A database that is itself obtained through data sharing from another account is not replicated as if it were a primary database owned by the source account. Replication covers eligible objects owned in the source account, but inbound shared databases are not fully replicated for failover in this manner. This is a common misconception when organizations mix native shares with replicated databases.
C. Correct.
Correct. Replication can include metadata for supported objects, but external stages depend on the external cloud storage location and the related credentials/integration setup being usable from the failover environment. Because the stage points to an S3 bucket in us-east-1, the administrator must consider cross-region access, permissions, and whether the bucket remains reachable during the outage. Replication does not magically relocate the external data.
D. Incorrect.
Incorrect. Virtual warehouses are compute resources and are not replicated as part of database/account replication for disaster recovery. In the failover account, warehouses must be created or otherwise made available separately. Candidates often confuse replicated data-plane metadata with compute infrastructure.
E. Incorrect.
Incorrect. Persisted query results and cache state are not replicated for disaster recovery. Even if the same SQL is executed after failover, result reuse depends on conditions in the target account at that time, not on cache copied from the source account. Query history and execution context are not a substitute for replicated databases.

ADA-C01 Question 505

Single answer6.1 Manage data replication.

A global company uses Snowflake in AWS us-east-1 as its primary region and AWS eu-west-1 as its disaster recovery region. The administrators created a failover group to replicate several databases and account objects to the secondary account. During a DR test, analysts in eu-west-1 report that one critical database is missing, even though scheduled replication for the failover group is succeeding. The security team also notices that a newly created network policy was not present in the secondary account. Which action is the MOST appropriate to ensure both the missing database and the new network policy are included in future replications?

A
Modify the existing failover group to include the missing database and the NETWORK POLICIES object type, then continue or trigger replication for that failover group.
B
Create a database replication group for the missing database, because failover groups cannot replicate databases and account objects together.
C
Run a manual refresh on the secondary account, because failover groups automatically include all newly created databases and account objects after the first replication.
D
Promote the secondary account to primary, add the missing database and network policy there, and then fail back so the original primary account inherits those objects.

Show answer and explanation

Correct answer: A

Explanation

This scenario tests practical administration of Snowflake replication and failover groups. For disaster recovery across regions/accounts, failover groups are used to replicate supported databases and supported account objects together. A key operational detail is that replication is scope-based: only the databases and account object types defined in the failover group are replicated. If administrators add a new database later, or expect supported account objects such as network policies to appear in the secondary account, they must ensure those items are included in the failover group configuration. After altering the failover group, the next scheduled replication or an explicit refresh will copy the newly included objects. This aligns with Snowflake documentation on replication and failover groups, which distinguishes between database replication and failover groups and emphasizes that only explicitly included supported objects are replicated.

A. Correct.
Correct. In Snowflake, a failover group is the mechanism used to replicate and fail over supported databases together with supported account objects. Objects are replicated only if they are explicitly included in the failover group definition. If a new database or supported account object type such as network policies was not included, administrators must alter the failover group to add them, and then allow the next scheduled refresh or trigger replication. This directly addresses both symptoms in the scenario.
B. Incorrect.
Incorrect. This reflects a common misunderstanding. Failover groups are specifically designed to replicate collections of supported databases and account objects together for business continuity and disaster recovery. Creating a separate database replication group is not the right fix for a scenario already using a failover group for coordinated replication of databases plus account-level objects.
C. Incorrect.
Incorrect. Failover groups do not automatically expand to include every newly created database or every supported account object unless those objects or object types are part of the group's definition. A replication refresh only updates the objects already configured for replication; it does not discover and add out-of-scope objects automatically.
D. Incorrect.
Incorrect. Failing over or promoting the secondary account does not solve a configuration scoping problem. Replication scope must be defined on the failover group. Adding objects on the secondary during a DR event is not the normal method for fixing omitted replication content, and it can complicate recovery planning.

Timed practice exam

Take a ADA-C01 practice test under exam conditions

65 questions in 115 minutes, drawn from this bank, with a score report and a per-question review when you finish.

Start timed exam

ADA-C01 practice questions 501 to 565 of 565

Every question has a page with the answer and explanation. Numbers are stable, so you can bookmark or share them. The bank is split into 6 pages of up to 100 questions.