100% Accurate Answers! Mar-2026 ARA-C01 Actual Real Exam Questions [Q116-Q134]

QUESTION 116
An Architect executes the following query:
SELECT query_hash,
COUNT(*) AS query_count,
SUM(QH.EXECUTION_TIME) AS total_execution_time,
SUM((QH.EXECUTION_TIME / (1000 * 60 * 60)) * 8) AS c
FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY QH
WHERE warehouse_name = ‘WH_L’
AND DATE_TRUNC(‘day’, start_time) >= CURRENT_DATE() – 3
GROUP BY query_hash
ORDER BY c DESC
LIMIT 10;
What information does this query provide? (Select TWO).

It shows the total execution time and credit estimates for the 10 most expensive individual queries executed on WH_L over the last 3 days.

It shows the total execution time and credit estimates for the 10 most expensive query groups (identical or similar queries) executed on WH_L over the last 3 days.

It shows the total execution time and credit estimates for the 10 most frequently run query groups executed on WH_L over the last 3 days.

It calculates relative cost by converting execution time to minutes and multiplying by credits used.

It calculates relative cost by converting execution time to hours and multiplying by credits used.

QUESTION 117
What is a valid object hierarchy when building a Snowflake environment?

Account –> Database –> Schema –> Warehouse

Organization –> Account –> Database –> Schema –> Stage

Account –> Schema > Table –> Stage

Organization –> Account –> Stage –> Table –> View

Explanation
This is the valid object hierarchy when building a Snowflake environment, according to the Snowflake documentation and the web search results. Snowflake is a cloud data platform that supports various types of objects, such as databases, schemas, tables, views, stages, warehouses, and more. These objects are organized in a hierarchical structure, as follows:
* Organization: An organization is the top-level entity that represents a group of Snowflake accounts that are related by business needs or ownership. An organization can have one or more accounts, and can enable features such as cross-account data sharing, billing and usage reporting, and single sign-on across accounts12.
* Account: An account is the primary entity that represents a Snowflake customer. An account can have one or more databases, schemas, stages, warehouses, and other objects. An account can also have one or more users, roles, and security integrations. An account is associated with a specific cloud platform, region, and Snowflake edition34.
* Database: A database is a logical grouping of schemas. A database can have one or more schemas, and can store structured, semi-structured, or unstructured data. A database can also have properties such as retention time, encryption, and ownership56.
* Schema: A schema is a logical grouping of tables, views, stages, and other objects. A schema can have one or more objects, and can define the namespace and access control for the objects. A schema can also have properties such as ownership and default warehouse .
* Stage: A stage is a named location that references the files in external or internal storage. A stage can be used to load data into Snowflake tables using the COPY INTO command, or to unload data from Snowflake tables using the COPY INTO LOCATION command. A stage can be created at the account, database, or schema level, and can have properties such as file format, encryption, and credentials .
The other options listed are not valid object hierarchies, because they either omit or misplace some objects in the structure. For example, option A omits the organization level and places the warehouse under the schema level, which is incorrect. Option C omits the organization, account, and stage levels, and places the table under the schema level, which is incorrect. Option D omits the database level and places the stage and table under the account level, which is incorrect.
References:
* Snowflake Documentation: Organizations
* Snowflake Blog: Introducing Organizations in Snowflake
* Snowflake Documentation: Accounts
* Snowflake Blog: Understanding Snowflake Account Structures
* Snowflake Documentation: Databases
* Snowflake Blog: How to Create a Database in Snowflake
* [Snowflake Documentation: Schemas]
* [Snowflake Blog: How to Create a Schema in Snowflake]
* [Snowflake Documentation: Stages]
* [Snowflake Blog: How to Use Stages in Snowflake]

QUESTION 118
An Architect needs to design a Snowflake account and database strategy to store and analyze large amounts of structured and semi-structured data. There are many business units and departments within the company. The requirements are scalability, security, and cost efficiency.
What design should be used?

Create a single Snowflake account and database for all data storage and analysis needs, regardless of data volume or complexity.

Set up separate Snowflake accounts and databases for each department or business unit, to ensure data isolation and security.

Use Snowflake’s data lake functionality to store and analyze all data in a central location, without the need for structured schemas or indexes

Use a centralized Snowflake database for core business data, and use separate databases for departmental or project-specific data.

QUESTION 119
How can the Snowpipe REST API be used to keep a log of data load history?

Call insertReport every 20 minutes, fetching the last 10,000 entries.

Call loadHistoryScan every minute for the maximum time range.

Call insertReport every 8 minutes for a 10-minute time range.

Call loadHistoryScan every 10 minutes for a 15-minutes range.

QUESTION 120
What conditions should be true for a table to consider search optimization

The table size is at least 100 GB

The table is not clustered OR The table is frequently queried on columns other than the primary cluster key

The table can be of any size

QUESTION 121
Bytes spilled to remote storage in query profile indicates volume of data spilled to remote disk

TRUE

FALSE

QUESTION 122
A company is storing large numbers of small JSON files (ranging from 1-4 bytes) that are received from IoT devices and sent to a cloud provider. In any given hour, 100,000 files are added to the cloud provider.
What is the MOST cost-effective way to bring this data into a Snowflake table?

An external table

A pipe

A stream

A copy command at regular intervals

QUESTION 123
A Snowflake Architect is setting up database replication to support a disaster recovery plan. The primary database has external tables.
How should the database be replicated?

Create a clone of the primary database then replicate the database.

Move the external tables to a database that is not replicated, then replicate the primary database.

Replicate the database ensuring the replicated database is in the same region as the external tables.

Share the primary database with an account in the same region that the database will be replicated to.

QUESTION 124
Who can provide permission to EXECUTE TASK?

ACCOUNTADMIN

THE TASK OWNER

SYSADMIN

QUESTION 125
An Architect uses COPY INTO with the ON_ERROR=SKIP_FILE option to bulk load CSV files into a table called TABLEA, using its table stage. One file named file5.csv fails to load. The Architect fixes the file and re-loads it to the stage with the exact same file name it had previously.
Which commands should the Architect use to load only file5.csv file from the stage? (Choose two.)

COPY INTO tablea FROM @%tablea RETURN_FAILED_ONLY = TRUE;

COPY INTO tablea FROM @%tablea;

COPY INTO tablea FROM @%tablea FILES = (‘file5.csv’);

COPY INTO tablea FROM @%tablea FORCE = TRUE;

COPY INTO tablea FROM @%tablea NEW_FILES_ONLY = TRUE;

COPY INTO tablea FROM @%tablea MERGE = TRUE;

QUESTION 126
When loading data into a table that captures the load time in a column with a default value of either CURRENT_TIME() or CURRENT_TIMESTAMP() what will occur?

All rows loaded using a specific COPY statement will have varying timestamps based on when the rows were inserted.

Any rows loaded using a specific COPY statement will have varying timestamps based on when the rows were read from the source.

Any rows loaded using a specific COPY statement will have varying timestamps based on when the rows were created in the source.

All rows loaded using a specific COPY statement will have the same timestamp value.

QUESTION 127
A new user user_01 is created within Snowflake. The following two commands are executed:
Command 1-> show grants to user user_01;
Command 2 ~> show grants on user user 01;
What inferences can be made about these commands?

Command 1 defines which user owns user_01
Command 2 defines all the grants which have been given to user_01

Command 1 defines all the grants which are given to user_01 Command 2 defines which user owns user_01

Command 1 defines which role owns user_01
Command 2 defines all the grants which have been given to user_01

Command 1 defines all the grants which are given to user_01
Command 2 defines which role owns user 01

QUESTION 128
Below are the rest APIs provided by Snowpipe

insertFiles

insertReport

loadData

QUESTION 129
A company is storing large numbers of small JSON files (ranging from 1-4 bytes) that are received from IoT devices and sent to a cloud provider. In any given hour, 100,000 files are added to the cloud provider.
What is the MOST cost-effective way to bring this data into a Snowflake table?

An external table

A pipe

A stream

A copy command at regular intervals

Explanation
* A pipe is a Snowflake object that continuously loads data from files in a stage (internal or external) into a table. A pipe can be configured to use auto-ingest, which means that Snowflake automatically detects new or modified files in the stage and loads them into the table without any manual intervention1.
* A pipe is the most cost-effective way to bring large numbers of small JSON files into a Snowflake table, because it minimizes the number of COPY commands executed and the number of micro-partitions created. A pipe can use file aggregation, which means that it can combine multiple small files into a single larger file before loading them into the table. This reduces the load time and the storage cost of the data2.
* An external table is a Snowflake object that references data files stored in an external location, such as Amazon S3, Google Cloud Storage, or Microsoft Azure Blob Storage. An external table does not store the data in Snowflake, but only provides a view of the data for querying. An external table is not a cost-effective way to bring data into a Snowflake table, because it does not support file aggregation, and it requires additional network bandwidth and compute resources to query the external data3.
* A stream is a Snowflake object that records the history of changes (inserts, updates, and deletes) made to a table. A stream can be used to consume the changes from a table and apply them to another table or a task. A stream is not a way to bring data into a Snowflake table, but a way to process the data after it is loaded into a table4.
* A copy command is a Snowflake command that loads data from files in a stage into a table. A copy command can be executed manually or scheduled using a task. A copy command is not a cost-effective way to bring large numbers of small JSON files into a Snowflake table, because it does not support file aggregation, and it may create many micro-partitions that increase the storage cost of the data5.
References: : Pipes : Loading Data Using Snowpipe : External Tables : Streams : COPY INTO <table>

QUESTION 130
What considerations need to be taken when using database cloning as a tool for data lifecycle management in a development environment? (Select TWO).

Any pipes in the source are not cloned.

Any pipes in the source referring to internal stages are not cloned.

Any pipes in the source referring to external stages are not cloned.

The clone inherits all granted privileges of all child objects in the source object, including the database.

The clone inherits all granted privileges of all child objects in the source object, excluding the database.

Database cloning is a feature of Snowflake that allows creating a copy of a database, schema, table, or view without consuming any additional storage space. Database cloning can be used as a tool for data lifecycle management in a development environment, where developers and testers can work on isolated copies of production data without affecting the original data or each other1.
However, there are some considerations that need to be taken when using database cloning in a development environment, such as:
* Any pipes in the source are not cloned. Pipes are objects that load data from a stage into a table continuously. Pipes are not cloned because they are associated with a specific stage and table, and cloning them would create duplicate data loading and potential conflicts2.
* The clone inherits all granted privileges of all child objects in the source object, including the database.
Privileges are the permissions that control the access and actions that can be performed on an object.
When a database is cloned, the clone inherits all the privileges that were granted on the source database and its child objects, such as schemas, tables, and views. This means that the same roles that can access and modify the source database can also access and modify the clone, unless the privileges are explicitly revoked or modified3.
The other options are not correct because:
* B. Any pipes in the source referring to internal stages are not cloned. This is a subset of option A, which states that any pipes in the source are not cloned, regardless of the type of stage they refer to.
* C. Any pipes in the source referring to external stages are not cloned. This is also a subset of option A, which states that any pipes in the source are not cloned, regardless of the type of stage they refer to.
* E. The clone inherits all granted privileges of all child objects in the source object, excluding the database. This is incorrect, as the clone inherits all granted privileges of the source object, including the database.
References:
* 1: Database Cloning | Snowflake Documentation
* 2: Pipes | Snowflake Documentation
* 3: Access Control Privileges | Snowflake Documentation

QUESTION 131
An Architect needs to grant a group of ORDER_ADMIN users the ability to clean old data in an ORDERS table (deleting all records older than 5 years), without granting any privileges on the table. The group’s manager (ORDER_MANAGER) has full DELETE privileges on the table.
How can the ORDER_ADMIN role be enabled to perform this data cleanup, without needing the DELETE privilege held by the ORDER_MANAGER role?

Create a stored procedure that runs with caller’s rights, including the appropriate “> 5 years” business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

Create a stored procedure that can be run using both caller’s and owner’s rights (allowing the user to specify which rights are used during execution), and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

Create a stored procedure that runs with owner’s rights, including the appropriate “> 5 years” business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

This scenario would actually not be possible in Snowflake – any user performing a DELETE on a table requires the DELETE privilege to be granted to the role they are using.

QUESTION 132
An Architect needs to grant a group of ORDER_ADMIN users the ability to clean old data in an ORDERS table (deleting all records older than 5 years), without granting any privileges on the table. The group’s manager (ORDER_MANAGER) has full DELETE privileges on the table.
How can the ORDER_ADMIN role be enabled to perform this data cleanup, without needing the DELETE privilege held by the ORDER_MANAGER role?

Create a stored procedure that runs with caller’s rights, including the appropriate “> 5 years” business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

Create a stored procedure that can be run using both caller’s and owner’s rights (allowing the user to specify which rights are used during execution), and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

Create a stored procedure that runs with owner’s rights, including the appropriate “> 5 years” business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

This scenario would actually not be possible in Snowflake – any user performing a DELETE on a table requires the DELETE privilege to be granted to the role they are using.

QUESTION 133
Data sharing is supported only between provider and consumer accounts in same region

TRUE

FALSE

QUESTION 134
An Architect needs to allow a user to create a database from an inbound share.
To meet this requirement, the user’s role must have which privileges? (Choose two.)

Leave a Reply Cancel reply