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?

1. A. Create a pipeline to write shared data to a cloud storage location in the target cloud provider.
2. B. Ensure that all views are persisted, as views cannot be shared across cloud platforms.
3. C. Setup data replication to the region and cloud platform where the consumer resides.
4. D. Company A and Company B must agree to use a single cloud platform: Data sharing is only possible if the companies share the same cloud provider.

Correct Answer: C
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. References: Replicating Databases Across Multiple Accounts | Snowflake Documentation, Persisting Views | Snowflake Documentation, Sharing Data Across Regions and Cloud Platforms | Snowflake Documentation

An Architect entered the following commands in sequence:

USER1 cannot find the table.
Which of the following commands does the Architect need to run for USER1 to find the tables using the Principle of Least Privilege? (Choose two.)

1. A. GRANT ROLE PUBLIC TO ROLE INTERN;
2. B. GRANT USAGE ON DATABASE SANDBOX TO ROLE INTERN;
3. C. GRANT USAGE ON SCHEMA SANDBOX.PUBLIC TO ROLE INTERN;
4. D. GRANT OWNERSHIP ON DATABASE SANDBOX TO USER INTERN;
5. E. GRANT ALL PRIVILEGES ON DATABASE SANDBOX TO ROLE INTERN;

Correct Answer: BC
✑ According to the Principle of Least Privilege, the Architect should grant the minimum privileges necessary for the USER1 to find the tables in the SANDBOX database.
✑ The USER1 needs to have USAGE privilege on the SANDBOX database and the SANDBOX.PUBLIC schema to be able to access the tables in the PUBLIC schema. Therefore, the commands B and C are the correct ones to run.
✑ The command A is not correct because the PUBLIC role is automatically granted to every user and role in the account, and it does not have any privileges on the SANDBOX database by default.
✑ The command D is not correct because it would transfer the ownership of the SANDBOX database from the Architect to the USER1, which is not necessary and violates the Principle of Least Privilege.
✑ The command E is not correct because it would grant all the possible privileges on the SANDBOX database to the USER1, which is also not necessary and violates the Principle of Least Privilege.
References: : Snowflake - Principle of Least Privilege : Snowflake - Access Control Privileges : Snowflake - Public Role : Snowflake - Ownership and Grants

An Architect needs to design a data unloading strategy for Snowflake, that will be used with the COPY INTO command.
Which configuration is valid?

1. A. Location of files: Snowflake internal locatio
2. B. File formats: CSV, XM
3. C. File encoding: UTF-8. Encryption: 128-bit
4. D. Location of files: Amazon S3. File formats: CSV, JSO
5. E. File encoding: Latin-1 (ISO-8859). Encryption: 128-bit
6. F. Location of files: Google Cloud Storag
7. G. File formats: Parque
8. H. File encoding: UTF-8· Compression: gzip
9. I. Location of files: Azure ADL
10. J. File formats: JSON, XML, Avro, Parquet, OR
11. K. Compression: bzip2. Encryption: User-supplied key

Correct Answer: C
For the configuration of data unloading in Snowflake, the valid option among the provided choices is "C." This is because Snowflake supports unloading data into Google Cloud Storage using the COPY INTO <location> command with specific configurations. The configurations listed in option C, such as Parquet file format with UTF-8 encoding and gzip compression, are all supported by Snowflake. Notably, Parquet is a columnar storage file format, which is optimal for high-performance data processing tasks in Snowflake. The UTF-8 file encoding and gzip compression are both standard and widely used settings that are compatible with Snowflake??s capabilities for data unloading to cloud storage platforms.References:
✑ Snowflake Documentation on COPY INTO command
✑ Snowflake Documentation on Supported File Formats
✑ Snowflake Documentation on Compression and Encoding Options

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

1. A. Call insertReport every 20 minutes, fetching the last 10,000 entries.
2. B. Call loadHistoryScan every minute for the maximum time range.
3. C. Call insertReport every 8 minutes for a 10-minute time range.
4. D. Call loadHistoryScan every 10 minutes for a 15-minutes range.

Correct Answer: D
The Snowpipe REST API provides two endpoints for retrieving the data load history: insertReport and loadHistoryScan. The insertReport endpoint returns the status of the files that were submitted to the insertFiles endpoint, while the loadHistoryScan endpoint returns the history of the files that were actually loaded into the table by Snowpipe. To keep a log of data load history, it is recommended to use the loadHistoryScan endpoint, which provides more accurate and complete information about the data ingestion process. The loadHistoryScan endpoint accepts a start time and an end time as parameters, and returns the files that were loaded within that time range. The maximum time range that can be specified is 15 minutes, and the maximum number of files that can be returned is 10,000. Therefore, to keep a log of data load history, the best option is to call the loadHistoryScan endpoint every 10 minutes for a 15-minute time range, and store the results in a log file or a table. This way, the log will capture all the files that were loaded by Snowpipe, and avoid any gaps or overlaps in the time range. The other options are incorrect because:
✑ Calling insertReport every 20 minutes, fetching the last 10,000 entries, will not
provide a complete log of data load history, as some files may be missed or duplicated due to the asynchronous nature of Snowpipe. Moreover, insertReport only returns the status of the files that were submitted, not the files that were loaded.
✑ Calling loadHistoryScan every minute for the maximum time range will result in too
many API calls and unnecessary overhead, as the same files will be returned multiple times. Moreover, the maximum time range is 15 minutes, not 1 minute.
✑ Calling insertReport every 8 minutes for a 10-minute time range will suffer from the
same problems as option A, and also create gaps or overlaps in the time range. References:
✑ Snowpipe REST API
✑ Option 1: Loading Data Using the Snowpipe REST API
✑ PIPE_USAGE_HISTORY

What are some of the characteristics of result set caches? (Choose three.)

1. A. Time Travel queries can be executed against the result set cache.
2. B. Snowflake persists the data results for 24 hours.
3. C. Each time persisted results for a query are used, a 24-hour retention period is reset.
4. D. The data stored in the result cache will contribute to storage costs.
5. E. The retention period can be reset for a maximum of 31 days.
6. F. The result set cache is not shared between warehouses.

Correct Answer: BCF
In Snowflake, the characteristics of result set caches include persistence of data results for 24 hours (B), each use of persisted results resets the 24-hour retention period (C), and result set caches are not shared between different warehouses (F). The result set cache is specifically designed to avoid repeated execution of the same query within this timeframe, reducing computational overhead and speeding up query responses. These caches do not contribute to storage costs, and their retention period cannot be extended beyond the default duration nor up to 31 days, as might be misconstrued.References: Snowflake Documentation on Result Set Caching.