Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Snowflake ARA-C01 Exam - Topic 6 Question 50 Discussion

Actual exam question for Snowflake's ARA-C01 exam
Question #: 50
Topic #: 6
[All ARA-C01 Questions]

A company is using Snowflake in Azure in the Netherlands. The company analyst team also has data in JSON format that is stored in an Amazon S3 bucket in the AWS Singapore region that the team wants to analyze.

The Architect has been given the following requirements:

1. Provide access to frequently changing data

2. Keep egress costs to a minimum

3. Maintain low latency

How can these requirements be met with the LEAST amount of operational overhead?

Show Suggested Answer Hide Answer
Suggested Answer: B

:Option A is the best design to meet the requirements because it uses a materialized view on top of an external table against the S3 bucket in AWS Singapore.A materialized view is a database object that contains the results of a query and can be refreshed periodically to reflect changes in the underlying data1.An external table is a table that references data files stored in a cloud storage service, such as Amazon S32. By using a materialized view on top of an external table, the company can provide access to frequently changing data, keep egress costs to a minimum, and maintain low latency. This is because the materialized view will cache the query results in Snowflake, reducing the need to access the external data files and incur network charges. The materialized view will also improve the query performance by avoiding scanning the external data files every time.The materialized view can be refreshed on a schedule or on demand to capture the changes in the external data files1.

Option B is not the best design because it uses an external table against the S3 bucket in AWS Singapore and copies the data into transient tables.A transient table is a table that is not subject to the Time Travel and Fail-safe features of Snowflake, and is automatically purged after a period of time3. By using an external table and copying the data into transient tables, the company will incur more egress costs and operational overhead than using a materialized view. This is because the external table will access the external data files every time a query is executed, and the copy operation will also transfer data from S3 to Snowflake. The transient tables will also consume more storage space in Snowflake and require manual maintenance to ensure they are up to date.

Option C is not the best design because it copies the data between providers from S3 to Azure Blob storage to collocate, then uses Snowpipe for data ingestion.Snowpipe is a service that automates the loading of data from external sources into Snowflake tables4. By copying the data between providers, the company will incur high egress costs and latency, as well as operational complexity and maintenance of the infrastructure. Snowpipe will also add another layer of processing and storage in Snowflake, which may not be necessary if the external data files are already in a queryable format.

Option D is not the best design because it uses AWS Transfer Family to replicate data between the S3 bucket in AWS Singapore and an Azure Netherlands Blob storage, then uses an external table against the Blob storage.AWS Transfer Family is a service that enables secure and seamless transfer of files over SFTP, FTPS, and FTP to and from Amazon S3 or Amazon EFS5. By using AWS Transfer Family, the company will incur high egress costs and latency, as well as operational complexity and maintenance of the infrastructure. The external table will also access the external data files every time a query is executed, which may affect the query performance.


by Martina at May 05, 2025, 10:24 AM

Limited Time Offer

25%

Off

Get Premium ARA-C01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Essie
4 months ago
A is definitely the way to go for minimizing costs.
upvoted 0 times
...
Krissy
4 months ago
Surprised that D is even an option, seems like extra steps!
upvoted 0 times
...
William
4 months ago
Option A seems like the best choice for low overhead.
upvoted 0 times
...
Goldie
4 months ago
C sounds complicated, not sure it's worth the effort.
upvoted 0 times
...
Dorthy
4 months ago
I disagree, B might be more efficient for frequent changes.
upvoted 0 times
...
Melissa
5 months ago
I feel like option D could be a good choice since it involves replication, but I’m not sure how that impacts operational overhead compared to the others.
upvoted 0 times
...
Eleni
5 months ago
I’m a bit confused about the egress costs. Would copying data to Azure Blob storage really minimize those costs?
upvoted 0 times
...
Lynelle
5 months ago
I think option B sounds familiar; it might help with low latency since it keeps the data accessible without too much overhead.
upvoted 0 times
...
Ryan
5 months ago
I remember we discussed external tables in class, but I'm not sure if using a materialized view is the best option for frequently changing data.
upvoted 0 times
...
Ashley
6 months ago
I think I've got a good handle on this. Option C seems like the best approach, as it allows for efficient data ingestion using Snowpipe while keeping the data within the Azure ecosystem.
upvoted 0 times
...
Adria
6 months ago
Option D looks promising, as it leverages the AWS Transfer Family to replicate the data between the S3 bucket and Azure Blob storage. This could help maintain low latency and minimize operational overhead.
upvoted 0 times
...
Kayleigh
6 months ago
I'm a bit confused by the different cloud providers involved. I'll need to carefully review the options to determine the most efficient and cost-effective solution.
upvoted 0 times
...
Darnell
6 months ago
Hmm, the key here is minimizing operational overhead while meeting the requirements. I'm leaning towards option C, as it seems to address the need for frequent data updates and low egress costs.
upvoted 0 times
...
Enola
6 months ago
This question seems straightforward, but I want to make sure I fully understand the requirements before selecting an answer.
upvoted 0 times
...
Roxane
10 months ago
You know, Option A with the materialized view might not be a bad idea. That could give us the frequent data access we need without too much overhead. Worth considering, for sure.
upvoted 0 times
Alysa
9 months ago
Yeah, I agree. It seems like a practical option to meet the requirements with minimal operational overhead.
upvoted 0 times
...
Moon
9 months ago
Option A with the materialized view sounds like a good solution. It could help with frequent data access.
upvoted 0 times
...
...
Venita
10 months ago
Haha, Option D with the AWS Transfer Family? Sounds like a complicated workaround just to get the data where we need it. I'd rather keep it simple and go with Option B.
upvoted 0 times
Lindsey
8 months ago
Let's go with Option B then, it's the least amount of operational overhead.
upvoted 0 times
...
Ezekiel
9 months ago
Yeah, keeping it simple is usually the best way to go.
upvoted 0 times
...
Laurel
9 months ago
I agree, Option B seems like a simpler approach to meet the requirements.
upvoted 0 times
...
Aliza
10 months ago
Option D with AWS Transfer Family seems like a complex solution.
upvoted 0 times
...
...
Barney
10 months ago
I'm not sure about Option C. Copying the data between providers seems like it could get messy and increase the operational overhead. We should try to minimize that as much as possible.
upvoted 0 times
Ashleigh
10 months ago
B) Use an external table against the S3 bucket in AWS Singapore and copy the data into transient tables.
upvoted 0 times
...
Avery
10 months ago
A) Use a materialized view on top of an external table against the S3 bucket in AWS Singapore.
upvoted 0 times
...
...
Franchesca
11 months ago
But wouldn't using external tables against the S3 bucket in AWS Singapore be more cost-effective?
upvoted 0 times
...
Sue
11 months ago
I prefer option D, replicating data between providers could be more reliable.
upvoted 0 times
...
Anjelica
11 months ago
Option B looks like the way to go. Keeping the data in the external table and copying it into transient tables should provide the frequently changing data access and low latency we need.
upvoted 0 times
Holley
10 months ago
Agreed. It seems like the most efficient way to handle the data analysis process.
upvoted 0 times
...
Melita
10 months ago
That sounds like a good solution. It should meet all the requirements without too much operational overhead.
upvoted 0 times
...
Charlene
10 months ago
B) Use an external table against the S3 bucket in AWS Singapore and copy the data into transient tables.
upvoted 0 times
...
...
Elvis
11 months ago
I agree with Franchesca, using Snowpipe for data ingestion seems efficient.
upvoted 0 times
...
Franchesca
11 months ago
I think option C sounds like a good solution.
upvoted 0 times
...

Save Cancel