ARA-C01 Snowflake Architecture Practice Question
What is the primary architectural advantage of using External Tables with the 'REFRESH' property instead of traditional data loading via COPY INTO?
⚠ Common exam trap
Many assume external tables improve query performance over COPY INTO, missing that their primary architectural benefit is querying data in place to avoid duplication and storage costs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
It allows for querying data in place without incurring Snowflake storage costs.
External tables allow Snowflake to query data directly from cloud storage without importing it into Snowflake's proprietary storage format. This is beneficial for data lake architectures where data must remain accessible to other tools. The REFRESH property ensures that the Snowflake metadata stays in sync with the files in the cloud bucket as they are added or removed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
External tables provide significantly faster query performance than internal tables.
Why it's wrong here
External tables are generally slower than internal tables because they cannot take advantage of Snowflake's proprietary micro-partitioning, optimized compression, and metadata-driven pruning. The data must be read from external storage and parsed on-the-fly, which introduces more latency compared to querying data stored natively within the Snowflake storage layer.
- ✓
It allows for querying data in place without incurring Snowflake storage costs.
Why this is correct
The main advantage of external tables is the ability to analyze data without moving it into Snowflake. This avoids duplicating data and eliminates Snowflake-specific storage charges, although users still pay for the underlying cloud provider storage and the compute credits used by the virtual warehouse to process the queries.
- ✗
External tables automatically support ACID transactions for updates and deletes.
Why it's wrong here
External tables are read-only from the perspective of Snowflake. You cannot perform DML operations like UPDATE, DELETE, or MERGE on an external table. To modify the data, you must change the underlying files in the cloud storage bucket, making them unsuitable for applications that require transactional consistency for data modifications.
- ✗
Using external tables eliminates the need for a Virtual Warehouse for queries.
Why it's wrong here
Regardless of whether data is in an internal or external table, a Virtual Warehouse is always required to provide the compute power needed to execute the SQL query. The warehouse reads the data from the external stage, processes it, and returns the result, consuming credits based on the warehouse size and duration.
About these practice questions
Courseiva writes every ARA-C01 question from scratch — 209 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This ARA-C01 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ARA-C01 exam.