Snowflake Updated DAA-C01 Exam Questions and Answers by inaya

In Snowsight (Snowflake's web interface), Data Analysts can create interactive dashboards and worksheets using Filters. When you define a filter (such as a Date Range or a list of Regions), you must assign it a SQL Keyword.

This "SQL Keyword" acts as a variable placeholder within your SQL code. For example, if you create a filter for "Customer Region" and set the SQL keyword to :my_region, you can then write a query like: SELECT * FROM sales WHERE region = :my_region. When a user interacts with the UI and selects "North America" from the dropdown, Snowsight automatically injects "North America" into every instance where :my_region appears in the worksheet's SQL.

Evaluating the Options:

Option A is incorrect because the keyword is a label/variable, not the underlying function code.

Option C and Option D are incorrect as they confuse the data source of the filter values with the reference name used in the SQL code.

Option B is the correct answer. The SQL Keyword is specifically the identifier (prefixed with a colon in the code) that allows the analyst to link the UI element (the filter) to the execution logic of the query. This is a fundamental skill for the Data Presentation and Data Visualization domain, ensuring reports are dynamic and user-friendly.

In the Snowflake data loading hierarchy, understanding the order of precedence for file format options is critical for troubleshooting and automation. Snowflake allows you to define file format options (such as CSV delimiter, header settings, or compression type) at multiple levels: as a standalone named File Format object, within a Stage definition, or directly inside a COPY INTO statement.

When data is loaded, Snowflake evaluates these definitions based on a specific override logic. The COPY INTO statement sits at the top of this hierarchy. This means that any file format options or named file formats explicitly called out in the COPY INTO command will override any conflicting settings defined at the stage or table level. For example, if a stage is defined to expect comma-separated files, but the COPY INTO command specifies a pipe delimiter, Snowflake will use the pipe delimiter for that specific load operation.

Evaluating the Options:

Options A, B, and C are incorrect because while they provide default behaviors for specific objects or namespaces, they are considered "lower-level" configurations.

Option D is the 100% correct answer. The COPY INTO statement provides the final, explicit instruction to the query engine. This design allows Data Analysts to use general-purpose stages for various file types by simply specifying the unique format requirements at the time of the execution, providing maximum flexibility in the Data Ingestion workflow.

Snowsight, the modern web interface for Snowflake, introduces robust collaboration features through shared worksheets. Understanding the synchronization and versioning logic is critical for the Data Presentation and Data Visualization domain.

When a worksheet is shared with collaborators, Snowflake enables real-time collaboration (Option D). This means that as one user types or modifies SQL code, those changes are immediately visible to all other users who have the worksheet open. This functionality is similar to co-authoring in modern document editors, allowing data teams to debug or develop complex queries synchronously without the need for manual copy-pasting or constant screen sharing.

Furthermore, Snowflake manages the execution history of shared worksheets through a structured versioning system (Option C). If multiple users are interacting with the same worksheet, Snowflake does not overwrite a single "master" state during execution. Instead, every time a user executes the worksheet (or a portion of it), Snowflake creates a new version of the worksheet content associated with that specific run. This ensures that the code used to generate a particular result set is preserved and tied to that specific Query ID in the history.

Evaluating the Options:

Option A is incorrect because while users can see current edits, viewing a full, navigable history of "past versions" is not a standard feature in the same way it is in dedicated version control systems like Git.

Option B is incorrect as worksheet sharing is restricted to users within the same Snowflake account. Sharing across accounts requires the use of Data Shares or Private Listings.

Option E is incorrect because Snowflake preserves the history rather than overwriting it, allowing analysts to audit who ran what code and when.

Options C and D are the 100% correct answers. They define the synchronous and persistent nature of Snowsight collaboration, ensuring that teams can work together effectively while maintaining an immutable trail of executions.

In Snowflake, a Stored Procedure is the primary object used for procedural logic and the encapsulation of multiple SQL statements. Unlike standard functions that are typically restricted to returning a single value or a table based on an input, Stored Procedures are designed to perform administrative tasks, wrap complex business logic, and execute a sequence of operations—such as DDL (Data Definition Language) and DML (Data Manipulation Language) commands—within a single callable object.

Modular code development is facilitated by Stored Procedures because they allow analysts and developers to write logic once and reuse it across various workflows. For example, a procedure can be written to truncate a staging table, call a COPY INTO command, and then execute several INSERT statements into a final fact table. This "wrapper" approach ensures consistency, as any change to the logic only needs to be updated in the procedure definition rather than in every script or task that uses it.

Evaluating the Options:

Option B is incorrect because a Materialized View is a pre-computed result set used to improve query performance; it does not "encapsulate a series of statements" for procedural execution.

Option C is incorrect because while User-Defined Functions (UDFs) provide reusability, they are generally intended for calculations or data transformations that return a result. They are much more restricted than procedures; for instance, a UDF cannot execute DDL commands like CREATE TABLE.

Option D is incorrect because a Common Table Expression (CTE) is a temporary named result set defined within the execution scope of a single SELECT, INSERT, UPDATE, or DELETE statement. It is not a persistent database object and cannot be reused across different sessions or scripts.

Option A is the correct answer. Snowflake Stored Procedures can be written in multiple languages (JavaScript, Snowflake Scripting/SQL, Python, Java, or Scala), providing the flexibility needed for sophisticated, modular automation in a data pipeline.