ARA-C01 · Question #40
A company has an external vendor who puts data into Google Cloud Storage. The company's Snowflake account is set up in Azure. What would be the MOST efficient way to load data from the vendor into Sno
The correct answer is B. Create an external stage on Google Cloud Storage and use the external table to load the data into. Snowflake supports cross-cloud external stages, meaning a Snowflake account hosted on Azure can create an external stage pointing to a Google Cloud Storage (GCS) bucket. Data can then be loaded using COPY INTO directly from GCS without moving files between cloud providers. This i
Question
A company has an external vendor who puts data into Google Cloud Storage. The company's Snowflake account is set up in Azure. What would be the MOST efficient way to load data from the vendor into Snowflake?
Options
- AAsk the vendor to create a Snowflake account, load the data into Snowflake and create a data
- BCreate an external stage on Google Cloud Storage and use the external table to load the data into
- CCopy the data from Google Cloud Storage to Azure Blob storage using external tools and load
- DCreate a Snowflake Account in the Google Cloud Platform (GCP), ingest data into this account
How the community answered
(61 responses)- A3% (2)
- B75% (46)
- C7% (4)
- D15% (9)
Explanation
Snowflake supports cross-cloud external stages, meaning a Snowflake account hosted on Azure can create an external stage pointing to a Google Cloud Storage (GCS) bucket. Data can then be loaded using COPY INTO directly from GCS without moving files between cloud providers. This is the most efficient approach because it eliminates the extra transfer step, reduces latency, and avoids additional infrastructure. Option A is impractical as it requires the vendor to set up Snowflake and configure data sharing. Option C unnecessarily copies data between clouds, adding cost and latency. Option D requires setting up and maintaining a second Snowflake account in GCP, adding significant overhead.
Topics
Community Discussion
No community discussion yet for this question.