A company needs to have the following features available in its Snowflake account:
* 1. Support for Multi-Factor Authentication (MFA)
* 2. A minimum of 2 months of Time Travel availability
* 3. Database replication in between different regions
* 4. Native support for JDBC and ODBC
* 5. Customer-managed encryption keys using Tri-Secret Secure
* 6. Support for Payment Card Industry Data Security Standards (PCI DSS)
In order to provide all the listed services, what is the MINIMUM Snowflake edition that should be selected during account creation?

1. A. Standard
2. B. Enterprise
3. C. Business Critical
4. D. Virtual Private Snowflake (VPS)

Correct Answer: C
According to the Snowflake documentation1, the Business Critical edition offers the following features that are relevant to the question:
✑ Support for Multi-Factor Authentication (MFA): This is a standard feature available
in all Snowflake editions1.
✑ A minimum of 2 months of Time Travel availability: This is an enterprise feature that allows users to access historical data for up to 90 days1.
✑ Database replication in between different regions: This is an enterprise feature that enables users to replicate databases across different regions or cloud platforms1.
✑ Native support for JDBC and ODBC: This is a standard feature available in all Snowflake editions1.
✑ Customer-managed encryption keys using Tri-Secret Secure: This is a business critical feature that provides enhanced security and data protection by allowing customers to manage their own encryption keys1.
✑ Support for Payment Card Industry Data Security Standards (PCI DSS): This is a business critical feature that ensures compliance with PCI DSS regulations for handling sensitive cardholder data1.
Therefore, the minimum Snowflake edition that should be selected during account creation to provide all the listed services is the Business Critical edition.
References:
✑ Snowflake Editions | Snowflake Documentation

An Architect Is designing a data lake with Snowflake. The company has structured, semi- structured, and unstructured data. The company wants to save the data inside the data lake within the Snowflake system. The company is planning on sharing data among Its corporate branches using Snowflake data sharing.
What should be considered when sharing the unstructured data within Snowflake?

1. A. A pre-signed URL should be used to save the unstructured data into Snowflake in order to share data over secure views, with no time limit for the URL.
2. B. A scoped URL should be used to save the unstructured data into Snowflake in order to share data over secure views, with a 24-hour time limit for the URL.
3. C. A file URL should be used to save the unstructured data into Snowflake in order to share data over secure views, with a 7-day time limit for the URL.
4. D. A file URL should be used to save the unstructured data into Snowflake in order to share data over secure views, with the "expiration_time" argument defined for the URL time limit.

Correct Answer: D
According to the Snowflake documentation, unstructured data files can be shared by using a secure view and Secure Data Sharing. A secure view allows the result of a query to be accessed like a table, and a secure view is specifically designated for data privacy. A scoped URL is an encoded URL that permits temporary access to a staged file without granting privileges to the stage. The URL expires when the persisted query result period ends, which is currently 24 hours. A scoped URL is recommended for file administrators to give scoped access to data files to specific roles in the same account. Snowflake records information in the query history about who uses a scoped URL to
access a file, and when. Therefore, a scoped URL is the best option to share unstructured data within Snowflake, as it provides security, accountability, and control over the data access. References:
✑ Sharing unstructured Data with a secure view
✑ Introduction to Loading Unstructured Data

A Snowflake Architect is designing a multiple-account design strategy.
This strategy will be MOST cost-effective with which scenarios? (Select TWO).

1. A. The company wants to clone a production database that resides on AWS to a development database that resides on Azure.
2. B. The company needs to share data between two databases, where one must support Payment Card Industry Data Security Standard (PCI DSS) compliance but the other one does not.
3. C. The company needs to support different role-based access control features for the development, test, and production environments.
4. D. The company security policy mandates the use of different Active Directory instances for the development, test, and production environments.
5. E. The company must use a specific network policy for certain users to allow and block given IP addresses.

Correct Answer: BD
B. When dealing with PCI DSS compliance, having separate accounts can be beneficial because it enables strong isolation of environments that handle sensitive data from those that do not. By segregating the compliant from non-compliant resources, an organization can limit the scope of compliance, thus making it a cost-effective strategy.D. Different Active Directory instances can be managed more effectively and securely when separated into different accounts. This approach allows for distinct identity and access management policies, which can enforce security requirements and minimize the risk of access policy errors between environments.

An Architect needs to allow a user to create a database from an inbound share.
To meet this requirement, the user??s role must have which privileges? (Choose two.)

1. A. IMPORT SHARE;
2. B. IMPORT PRIVILEGES;
3. C. CREATE DATABASE;
4. D. CREATE SHARE;
5. E. IMPORT DATABASE;

Correct Answer: CE
According to the Snowflake documentation, to create a database from an inbound share, the user??s role must have the following privileges:
✑ The CREATE DATABASE privilege on the current account. This privilege allows
the user to create a new database in the account1.
✑ The IMPORT DATABASE privilege on the share. This privilege allows the user to import a database from the share into the account2. The other privileges listed are not relevant for this requirement. The IMPORT SHARE privilege is used to import
a share into the account, not a database3. The IMPORT PRIVILEGES privilege is used to import the privileges granted on the shared objects, not the objects themselves2. The CREATE SHARE privilege is used to create a share to provide data to other accounts, not to consume data from other accounts4.
References:
✑ CREATE DATABASE | Snowflake Documentation
✑ Importing Data from a Share | Snowflake Documentation
✑ Importing a Share | Snowflake Documentation
✑ CREATE SHARE | Snowflake Documentation

Which columns can be included in an external table schema? (Select THREE).

1. A. VALUE
2. B. METADATASROW_ID
3. C. METADATASISUPDATE
4. D. METADAT A$ FILENAME
5. E. METADATAS FILE_ROW_NUMBER
6. F. METADATASEXTERNAL TABLE PARTITION

Correct Answer: ADE
An external table schema defines the columns and data types of the data stored in an external stage. All external tables include the following columns by default:
✑ VALUE: A VARIANT type column that represents a single row in the external file.
✑ METADATA$FILENAME: A pseudocolumn that identifies the name of each staged data file included in the external table, including its path in the stage.
✑ METADATA$FILE_ROW_NUMBER: A pseudocolumn that shows the row number for each record in a staged data file.
You can also create additional virtual columns as expressions using the VALUE column and/or the pseudocolumns. However, the following columns are not valid for external tables and cannot be included in the schema:
✑ METADATASROW_ID: This column is only available for internal tables and shows
the unique identifier for each row in the table.
✑ METADATASISUPDATE: This column is only available for internal tables and shows whether the row was inserted or updated by a merge operation.
✑ METADATASEXTERNAL TABLE PARTITION: This column is not a valid column name and does not exist in Snowflake.
References: Introduction to External Tables, CREATE EXTERNAL TABLE