Snowflake DAA-C01 Practice Test Questions Answers

This error occurs due to a misunderstanding of how Snowflake resolves object names and the location of the Shared Snowflake Database. In Snowflake, the ACCOUNT_USAGE schema is a collection of views that provide comprehensive historical data about account activities, including credit consumption, storage, and query history. These views are stored within the system-defined database named SNOWFLAKE.

When the Data Analyst executes the query shown in the image, they are operating within the database context of DB1 and the schema context of PUBLIC. Because the query references ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY without a fully qualified name, the Snowflake compiler attempts to resolve the object starting from the current database context. Consequently, it looks for a schema named ACCOUNT_USAGE inside DB1. As the error message correctly indicates, Schema 'DB1.ACCOUNT_USAGE' does not exist.

To fix this, the Analyst has two options:

Fully Qualify the Object Name: Modify the query to reference the full path: FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY. This is the most common best practice as it allows the query to run regardless of the user's current session context.

Change the Context: Use the command USE DATABASE SNOWFLAKE; before running the query. This changes the session's database context so that ACCOUNT_USAGE can be found.

It is a common misconception (represented in Option A) that only an ACCOUNTADMIN can access these views. While access is restricted by default, the ACCOUNTADMIN can grant IMPORTED PRIVILEGES on the SNOWFLAKE database to other roles, such as a Data Analyst role. However, the specific error shown is a namespace resolution error, not a permission-denied error (which would typically say "Insufficient privileges"). Therefore, changing the context or fully qualifying the name is the direct solution to this specific failure.

The GENERATOR table function is used in Snowflake to produce a synthetic result set, typically for testing or creating dummy data. However, the GENERATOR function requires at least one of two parameters to be explicitly set to a positive value to produce any rows: ROWCOUNT or TIMELIMIT.

In the provided query, the user has set TIMELIMIT => NULL. In Snowflake's SQL implementation for the GENERATOR function, NULL is treated as a zero or an undefined limit. Furthermore, since the ROWCOUNT parameter is omitted, it defaults to zero. Because neither a positive duration nor a positive row count has been specified, the generator engine has no instruction on how many rows to build.

Evaluating the Results:

Option A is a distractor; while one might think NULL means "no limit" (infinity), the GENERATOR function is designed to be finite and safe.

Option B is incorrect; the number 12 inside the RANDOM(12) function is merely a seed value for the random number generator, ensuring the output is reproducible. It has no impact on the number of rows produced by the FROM clause.

Option C is incorrect; 10 is just a boundary for the UNIFORM function.

Option D is the 100% correct answer. Because the query specifies TIMELIMIT => NULL and fails to provide a ROWCOUNT, Snowflake will execute the query successfully but return a result set containing 0 rows. This is a common "trick" question in the Data Analysis domain to test an analyst's familiarity with table function parameters.

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.

In Snowsight, the Scorecard chart type is specifically designed to highlight a single key metric (the "Value") and optionally compare it against a static or dynamic benchmark (the "Comparison"). This visualization is a core component of the Data Presentation and Data Visualization domain, as it provides an immediate "at-a-glance" status for high-level KPIs.

1. Interpreting the Scorecard Components:

Primary Value: The large, bold number (38) represents the actual value calculated by the underlying query. In this scenario, it is the company's average employee age.

Secondary Metric (The Percentage): When a scorecard is configured with a comparison value, Snowsight automatically calculates the percentage difference between the primary value and that comparison.

Visual Indicators: The green upward arrow indicates that the primary value is higher than the comparison value. If the value were lower, the arrow would point downward and typically appear in red.

2. The Mathematical Calculation:

The 12% shown in the exhibit is the result of the percentage change formula:

Evaluating the Options:

Options A and D are incorrect because they misidentify the large number (38) as the "comparison." In Snowflake's UI, the large number is always the primary metric being tracked, not the target it is being measured against.

Option B is incorrect because the percentage in a scorecard represents relative difference, not a statistical measure like standard deviation.

Option C is the 100% correct interpretation. It correctly identifies 38 as the current company value and 12% as the calculated difference from the industry benchmark of 34. This level of visual literacy is expected of a SnowPro Advanced: Data Analyst to ensure dashboard insights are communicated accurately to stakeholders.

In Snowflake, table relationships established via constraints are managed at the metadata level. When a table that is referenced by a foreign key is renamed, Snowflake automatically maintains the integrity of that relationship by updating the internal metadata pointers.

Unlike some legacy database systems where a rename might break hardcoded references, Snowflake's architecture ensures that the Foreign Key in the son table remains valid. After executing ALTER TABLE mother RENAME TO father;, the constraint son_fk will be automatically updated by the system to reference the new table name, father. If you were to run a SHOW TRANSACTIONS or GET_DDL command on the son table after the rename, you would see that the REFERENCES clause now points to father(id).

Evaluating the Options:

Options A and B are incorrect because Snowflake is designed to prevent "orphaned" constraints during standard DDL operations like renaming. The relationship is preserved.

Option C is incorrect because Snowflake's query optimizer can still utilize these constraints for query rewrite and join elimination optimizations, provided the constraints are defined, regardless of the table's current name.

Option D is the 100% correct answer. This automatic update behavior is a core feature of Snowflake's metadata-driven approach to Data Transformation and Data Modeling, allowing for flexible schema evolution without breaking existing relational structures.