Snowflake ARA-C01 Exam With Confidence Using Practice Dumps

The object type level at which the APPLY MASKING POLICY, APPLY ROW ACCESS POLICY and APPLY SESSION POLICY privileges can be granted is global. These are account-level privileges that control who can apply or unset these policies on objects such as columns, tables, views, accounts, or users. These privileges are granted to the ACCOUNTADMIN role by default, and can be granted to other roles as needed. The other options are incorrect because they are not the object type level at which these privileges can be granted. Database, schema, and table are lower-level object types that do not support these privileges. References: Access Control Privileges | Snowflake Documentation, Using Dynamic Data Masking | Snowflake Documentation, Using Row Access Policies | Snowflake Documentation, Using Session Policies | Snowflake Documentation

This question tests several core Snowflake semi-structured data concepts that are explicitly part of the SnowPro Architect exam scope: working with VARIANT data, array handling, and the use of LATERAL FLATTEN. The activities element in the JSON structure is an array, meaning it must be flattened before individual attributes such as activityNumber and winner can be accessed. Option A is invalid because it attempts to directly reference fields inside an array without flattening it.

Option B correctly uses LATERAL FLATTEN on json:activities, which produces one row per activity. The alias p.value represents each array element, allowing access to activityNumber and winner. The IFF expression then compares the activity’s winner value with leader.number. When they match, the query returns leader.name.default; otherwise, it returns follower.name.default. Casting the result to VARCHAR ensures a proper scalar output.

Option C is incorrect because it attempts to return full JSON objects (leader or follower) rather than the nested name.default value. Option D uses OUTER => TRUE, which is unnecessary in this case because the activities array is guaranteed to exist; while it would still work, Snowflake exam questions typically expect the most precise and minimal correct solution.

The correct answer is D because the CURRENT_TIME function returns the current timestamp at the start of the statement execution, not at the time of the record insertion. Therefore, if the load operation takes some time to complete, the CURRENT_TIME value may be earlier than the actual load time.

Option A is incorrect because the parameter setup mismatches do not affect the timestamp values. The parameters are used to control the behavior and performance of the load operation, such as the file format, the error handling, the purge option, etc.

Option B is incorrect because the Snowflake timezone parameter and the cloud provider’s parameters are independent of each other. The Snowflake timezone parameter determines the session timezone for displaying and converting timestamp values, while the cloud provider’s parameters determine the physical location and configuration of the storage and compute resources.

Option C is incorrect because the localtimestamp and systimestamp functions are not relevant for the Snowpipe load operation. The localtimestamp function returns the current timestamp in the session timezone, while the systimestamp function returns the current timestamp in the system timezone. Neither of them reflect the actual load time of the records. References:

Snowflake Documentation: Loading Data Using Snowpipe: This document explains how to use Snowpipe to continuously load data from external sources into Snowflake tables. It also describes the syntax and usage of the COPY INTO command, which supports various options and parameters to control the loading behavior.

Snowflake Documentation: Date and Time Data Types and Functions: This document explains the different data types and functions for working with date and time values in Snowflake. It also describes how to set and change the session timezone and the system timezone.

Snowflake Documentation: Querying Metadata: This document explains how to query the metadata of the objects and operations in Snowflake using various functions, views, and tables. It also describes how to access the copy history information using the COPY_HISTORY function or the COPY_HISTORY view.