A global company needs to securely share its sales and Inventory data with a vendor using a Snowflake account.
The company has its Snowflake account In the AWS eu-west 2 Europe (London) region. The vendor's Snowflake account Is on the Azure platform in the West Europe region. How should the company's Architect configure the data share?
The correct way to securely share data with a vendor using a Snowflake account on a different cloud platform and region is to create a share, add objects to the share, and add a consumer account to the share for the vendor to access. This way, the company can control what data is shared, who can access it, and how long the share is valid. The vendor can then query the shared data without copying or moving it to their own account. The other options are either incorrect or inefficient, as they involve creating unnecessary reader accounts, users, roles, or database replication.
https://learn.snowflake.com/en/certifications/snowpro-advanced-architect/
An Architect has designed a data pipeline that Is receiving small CSV files from multiple sources. All of the files are landing in one location. Specific files are filtered for loading into Snowflake tables using the copy command. The loading performance is poor.
What changes can be made to Improve the data loading performance?
According to the Snowflake documentation, the data loading performance can be improved by following some best practices and guidelines for preparing and staging the data files. One of the recommendations is to aim for data files that are roughly 100-250 MB (or larger) in size compressed, as this will optimize the number of parallel operations for a load. Smaller files should be aggregated and larger files should be split to achieve this size range. Another recommendation is to use a multi-cluster warehouse for loading, as this will allow for scaling up or out the compute resources depending on the load demand. A single-cluster warehouse may not be able to handle the load concurrency and throughput efficiently. Therefore, by creating a multi-cluster warehouse and merging smaller files to create bigger files, the data loading performance can be improved.Reference:
Data Loading Considerations
Preparing Your Data Files
Planning a Data Load
Company A would like to share data in Snowflake with Company B. Company B is not on the same cloud platform as Company A.
What is required to allow data sharing between these two companies?
According to the SnowPro Advanced: Architect documents and learning resources, the requirement to allow data sharing between two companies that are not on the same cloud platform is to set up data replication to the region and cloud platform where the consumer resides. Data replication is a feature of Snowflake that enables copying databases across accounts in different regions and cloud platforms. Data replication allows data providers to securely share data with data consumers across different regions and cloud platforms by creating a replica database in the consumer's account. The replica database is read-only and automatically synchronized with the primary database in the provider's account.Data replication is useful for scenarios where data sharing is not possible or desirable due to latency, compliance, or security reasons1. The other options are incorrect because they are not required or feasible to allow data sharing between two companies that are not on the same cloud platform. Option A is incorrect because creating a pipeline to write shared data to a cloud storage location in the target cloud provider is not a secure or efficient way of sharing data. It would require additional steps to load the data from the cloud storage to the consumer's account, and it would not leverage the benefits of Snowflake's data sharing features. Option B is incorrect because ensuring that all views are persisted is not relevant for data sharing across cloud platforms. Views can be shared across cloud platforms as long as they reference objects in the same database.Persisting views is an option to improve the performance of querying views, but it is not required for data sharing2. Option D is incorrect because Company A and Company B do not need to agree to use a single cloud platform.Data sharing is possible across different cloud platforms using data replication or other methods, such as listings or auto-fulfillment3.Reference:Replicating Databases Across Multiple Accounts | Snowflake Documentation,Persisting Views | Snowflake Documentation,Sharing Data Across Regions and Cloud Platforms | Snowflake Documentation
How do Snowflake databases that are created from shares differ from standard databases that are not created from shares? (Choose three.)
According to the SnowPro Advanced: Architect documents and learning resources, the ways that Snowflake databases that are created from shares differ from standard databases that are not created from shares are:
Shared databases are read-only. This means that the data consumers who access the shared databases cannot modify or delete the data or the objects in the databases.The data providers who share the databases have full control over the data and the objects, and can grant or revoke privileges on them1.
Shared databases cannot be cloned. This means that the data consumers who access the shared databases cannot create a copy of the databases or the objects in the databases.The data providers who share the databases can clone the databases or the objects, but the clones are not automatically shared2.
Shared databases are not supported by Time Travel. This means that the data consumers who access the shared databases cannot use the AS OF clause to query historical data or restore deleted data.The data providers who share the databases can use Time Travel on the databases or the objects, but the historical data is not visible to the data consumers3.
The other options are incorrect because they are not ways that Snowflake databases that are created from shares differ from standard databases that are not created from shares. Option B is incorrect because shared databases do not need to be refreshed in order for new data to be visible.The data consumers who access the shared databases can see the latest data as soon as the data providers update the data1. Option E is incorrect because shared databases will not have the PUBLIC or INFORMATION_SCHEMA schemas without explicitly granting these schemas to the share.The data consumers who access the shared databases can only see the objects that the data providers grant to the share, and the PUBLIC and INFORMATION_SCHEMA schemas are not granted by default4. Option F is incorrect because shared databases cannot be created as transient databases. Transient databases are databases that do not support Time Travel or Fail-safe, and can be dropped without affecting the retention period of the data.Shared databases are always created as permanent databases, regardless of the type of the source database5.Reference:Introduction to Secure Data Sharing | Snowflake Documentation,Cloning Objects | Snowflake Documentation,Time Travel | Snowflake Documentation,Working with Shares | Snowflake Documentation,CREATE DATABASE | Snowflake Documentation
The following DDL command was used to create a task based on a stream:

Assuming MY_WH is set to auto_suspend -- 60 and used exclusively for this task, which statement is true?
The warehouse MY_WH will only be active when there are results in the stream. This is because the task is created based on a stream, which means that the task will only be executed when there are new data in the stream. Additionally, the warehouse is set to auto_suspend - 60, which means that the warehouse will automatically suspend after 60 seconds of inactivity. Therefore, the warehouse will only be active when there are results in the stream.Reference:
[CREATE TASK | Snowflake Documentation]
[Using Streams and Tasks | Snowflake Documentation]
[CREATE WAREHOUSE | Snowflake Documentation]
Rachel Hernandez
8 days agoLaura Turner
22 days agoAmanda Lewis
11 days agoAndrew Roberts
17 days agoAngela Sanchez
5 days agoKristofer
1 month agoGlendora
2 months agoFrancine
2 months agoShannon
2 months agoJohnson
2 months agoKallie
3 months agoValentin
3 months agoLajuana
3 months agoWillie
3 months agoWalker
4 months agoGenevive
4 months agoSkye
4 months agoParis
5 months agoNoe
5 months agoLizette
5 months agoAlex
5 months agoColton
6 months agoBobbye
6 months agoHayley
6 months agoTherese
6 months agoAyesha
7 months agoWinifred
7 months agoHerman
7 months agoArthur
7 months agoBernardine
8 months agoDanica
8 months agoLeeann
8 months agoSusana
8 months agoTy
8 months agoSocorro
8 months agoKimberlie
10 months agoLashawnda
10 months agoMyra
11 months agoGene
11 months agoCyndy
11 months agoIlene
1 year agoLenora
1 year agoMargery
1 year agoNan
1 year agoRosendo
1 year agoOlga
1 year agoAlex
1 year agoOretha
1 year agoAileen
1 year agoKati
1 year agoCarole
1 year agoGraciela
1 year agoFausto
1 year agoNickole
1 year agoShayne
1 year agoCory
1 year agoTruman
1 year agoKayleigh
1 year agoYoko
1 year agoJulian
1 year agoEttie
1 year agoElliott
2 years agoZana
2 years agoRolande
2 years agoJohnetta
2 years agoJolanda
2 years agoPatrick
2 years agoNoble
2 years agoWade
2 years agoHollis
2 years agoArminda
2 years agoLayla
2 years agoMable
2 years agoRozella
2 years agoThaddeus
2 years agoOlive
2 years agoGianna
2 years agoGerman
2 years agoJaclyn
2 years agoDorathy
2 years agoBelen
2 years agoLindsey
2 years agoRickie
2 years agoGennie
2 years agoStephania
2 years ago