The correct answer is B. In a named file format .

When data is regularly loaded or unloaded using the same format settings, Snowflake recommends defining those settings in a named file format. This avoids repeating the same file format options in every COPY command and reduces operational overhead.

Why B is correct:

A named file format stores reusable format options, such as file type and formatting behavior. For semi-structured data, named file formats can define options for formats such as JSON, Avro, ORC, Parquet, or XML.

Example:

CREATE FILE FORMAT my_json_format

TYPE = JSON

COMPRESSION = AUTO;

COPY INTO @my_stage/output/

FROM my_table

FILE_FORMAT = my_json_format;

Why the other options are incorrect:

A. A table definition defines table columns and properties, not unload formatting options.

C. A named stage can include a file format reference, but the reusable copy/file parsing settings themselves are defined in a named file format.

D. Copy options can be specified directly in the COPY command, but that is less efficient for repeated, similarly formatted unload operations.

Official Snowflake documentation reference:

Snowflake documentation explains that named file formats are reusable database objects that define format options for loading and unloading data.

The correct answer is A. A staged file needs to be unloaded to a local machine .

The Snowflake GET command is used to download files from an internal Snowflake stage to a local file system. It is commonly used after data has been unloaded from a table into an internal stage and the user wants to retrieve those staged files locally.

Why A is correct:

The GET command downloads files from a Snowflake internal stage to a local directory.

Example:

GET @my_stage file:///tmp/data/;

This command downloads files from the internal stage @my_stage to the local /tmp/data/ directory.

Why the other options are incorrect:

B. Loading a local file onto a stage is done with the PUT command, not GET.

C. Opening query results in a third-party tool is not the purpose of the GET command.

D. Permanently deleting files from a Snowflake stage is done with the REMOVE command, not GET.

Official Snowflake documentation reference:

Snowflake documentation describes the GET command as the command used to download data files from a Snowflake stage to a local directory or folder.

When unloading data using the COPY INTO < location > command, Snowflake offers options to compress files. The default behavior is governed by the COMPRESSION parameter. Setting COMPRESSION = AUTO allows Snowflake to automatically use its default compression algorithm, which is GZIP for most formats like CSV.

In addition to performing all the standard steps to share data, theUSAGEprivilege must be granted on each database referenced by a secure view in order to be shared. When sharing a database or specific objects like secure views, the receiving account needs to have theUSAGEprivilege on the database and schema to access the shared data. Thisprivilege enables the receiving account to access the database and its schemas but does not allow for any DML operations. It ' s a prerequisite for accessing any objects within the database.

For a secure view to be part of a share, not only does the view itself need to be shared, but the underlying database (and schema, if applicable) must also be accessible to the recipients. GrantingUSAGEprivilege on the database ensures that the receiving account can access the database in a read-only mode to utilize the shared view.

The correct answer is B. Iceberg table .

Snowflake Secure Data Sharing allows providers to share supported database objects with other Snowflake accounts. Supported objects include tables, secure views, secure materialized views, secure UDFs, and certain other supported table types. Snowflake-managed Iceberg tables can be shared in supported configurations.

Why B is correct:

An Iceberg table is a supported table object in Snowflake and can be shared using Secure Data Sharing, subject to Snowflake’s supported Iceberg table sharing requirements.

Why the other options are incorrect:

A. Event tables are used to store logging and tracing event data. They are not the expected shareable object in this question.

C. Temporary tables exist only within the session that created them and cannot be shared with other accounts.

D. Stored procedures are not standard objects shared through Secure Data Sharing in the same way as tables and secure views.

Official Snowflake documentation reference:

Snowflake documentation lists supported objects for Secure Data Sharing and describes sharing supported table objects, including Iceberg tables where supported.

The correct answer is B. Loading and unloading data .

SnowSQL is Snowflake’s command-line client. It is used to connect to Snowflake, execute SQL statements, run SQL scripts, and perform data loading and unloading operations.

Why B is correct:

SnowSQL supports data loading and unloading workflows. For example, users can use SnowSQL to run PUT, GET, and COPY commands.

Example loading workflow:

PUT file:///local/path/data.csv @my_stage;

COPY INTO my_table

FROM @my_stage

FILE_FORMAT = (TYPE = CSV);

Example unloading workflow:

COPY INTO @my_stage/output/

FROM my_table;

GET @my_stage/output/ file:///local/path/output/;

Why the other options are incorrect:

A. Dashboards are usually developed in BI tools or applications, not SnowSQL.

C. Snowflake Native Apps are developed and managed using Snowflake Native App Framework tools and Snowflake CLI, not primarily SnowSQL.

D. Monitoring transformation activity is usually done through Snowflake views, query history, task history, event tables, or monitoring features, not as the primary purpose of SnowSQL.

Official Snowflake documentation reference:

Snowflake documentation describes SnowSQL as the command-line client for connecting to Snowflake and executing SQL queries, including data loading and unloading commands.

The ORGADMIN role in Snowflake is designed to manage organization-level activities. This role can perform several tasks that span across multiple accounts within the organization.

View Usage Information:The ORGADMIN role can view usage statistics and billing information for all accounts within the organization.

-- Example: Viewing usage information

SELECT *

FROM organization_usage_history;

Enable Database Replication:The ORGADMIN role has the authority to enable and manage database replication for accounts within the organization.

-- Example: Enabling database replication

ALTER DATABASE my_database ENABLE REPLICATION TO ACCOUNT other_account;

Snowflake ' s Data Exchange allows data providers to publish data that is accessible only to users they explicitly invite. This mechanism ensures that only approved users or Snowflake accounts have access, adding a layer of security and control. Invited users can query the shared data directly within their Snowflake account without requiring data copies, reducing redundancy and enhancing data accessibility within controlled boundaries. This selective sharing feature is part of Snowflake’s secure data-sharing capabilities.

When a user is granted a custom role , they inherit only the privileges assigned to that role . This is aligned with the principle of least privilege in RBAC.

The correct answers are A. SHOW USERS and B. DESCRIBE USER .

Snowflake user metadata includes information related to MFA enrollment and configuration. To inspect user-level properties, administrators can use SHOW USERS or DESCRIBE USER.

Why A is correct:

SHOW USERS returns information about users in the account. Its output can include user properties that indicate MFA status or related authentication details.

Why B is correct:

DESCRIBE USER returns detailed properties for a specific user. This can be used to inspect whether MFA has been enabled for that user.

Example:

DESCRIBE USER my_user;

Why the other options are incorrect:

C. SHOW PARAMETERS displays parameters, not user MFA enrollment status.

D. SHOW USER FUNCTIONS lists user-defined functions, not Snowflake users.

E. SHOW CONNECTIONS displays connection objects and does not indicate MFA status for a specific user.

Official Snowflake documentation reference:

Snowflake documentation describes SHOW USERS and DESCRIBE USER as commands for viewing user metadata and user properties.

Fail-safe is a non-configurable feature in Snowflake that provides an additional layer of data protection beyond Time Travel. Time Travel allows users to access historical data within a configurable period (up to 90 days), while Fail-safe provides an additional 7-day period during which Snowflake retains historical data to recover from significant data loss or corruption incidents. This period is not accessible by users but can be used by Snowflake support to assist in data recovery efforts.

The official Snowflake function that converts a JSON null value inside a VARIANT to a SQL NULL is STRIP_NULL_VALUE .

Important correction:

The provided answer C. TRY_CAST is not the best official answer. TRY_CAST attempts to cast a string expression to another data type and returns SQL NULL if the cast fails. It is not the Snowflake function specifically used to convert a JSON null value in a VARIANT to SQL NULL.

Why the listed options are not correct:

A. CAST converts values between data types, but it is not the specific Snowflake function documented for stripping a JSON null value from a VARIANT.

B. TO_CHAR converts values to a character string. It does not specifically convert a JSON null value to SQL NULL.

C. TRY_CAST returns SQL NULL when a cast fails, but it is not the documented function for converting a VARIANT JSON null to SQL NULL.

D. TO_BINARY converts compatible values to binary and is unrelated to JSON null handling.

Correct Snowflake function:

STRIP_NULL_VALUE( < variant_expression > )

This function returns SQL NULL if the input is a JSON null value.

Official Snowflake documentation reference:

Snowflake documentation describes STRIP_NULL_VALUE as the function that removes a JSON null value from a VARIANT value and returns SQL NULL.