Snowflake · DAA-C01
SnowPro Advanced: Data Analyst (DAA-C01) Practice Tests
Validates advanced skills in applying comprehensive data analysis principles using Snowflake, including data ingestion, advanced SQL, UDFs, and predictive and diagnostic analytics. Requires 1+ years of hands-on Snowflake experience and an active SnowPro Core certification.
Exam Details
Practice Questions
600
≈ 6 practice exams
Duration
115 minutes
Passing Score
750/1000
Difficulty
ProfessionalLast Updated
Jun 2026
Topics Covered
Data Ingestion and PreparationData TransformationAdvanced SQL Query DevelopmentSnowflake Built-in Functions and UDFsDescriptive and Diagnostic Data AnalysisPredictive Data AnalysisData Presentation and Business Requirements
SnowPro Advanced: Data Analyst (DAA-C01) Practice Exam Preparation
Use this DAA-C01 practice exam to prepare for SnowPro Advanced: Data Analyst (DAA-C01) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 600 questions for Snowflake DAA-C01, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as Data Ingestion and Preparation, Data Transformation, Advanced SQL Query Development, Snowflake Built-in Functions and UDFs, and Descriptive and Diagnostic Data Analysis. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
Exam Overview
The SnowPro® Advanced: Data Analyst (DAA-C01) certification is Snowflake's advanced-tier credential for data professionals who apply comprehensive analytical techniques within the Snowflake Data Cloud. The exam validates expertise across the full analytical workflow: acquiring and loading structured, semi-structured, and unstructured data; transforming and preparing it for analysis; writing and optimizing complex SQL; leveraging Snowflake built-in functions and user-defined functions (UDFs); and performing descriptive, diagnostic, and predictive analytics to surface business insights.
Unlike entry-level Snowflake certifications, this exam expects candidates to demonstrate production-grade fluency with Snowflake-specific features such as Snowsight dashboards, Time Travel, semi-structured data handling (JSON, Parquet, Avro, ORC, XML), query optimization via partition pruning and materialized views, and integration with BI tools including Tableau, Looker, and Power BI. Delivered by Pearson VUE, the exam consists of 65 scored multiple-choice and multiple-select questions to be completed in 115 minutes, with a passing score of 750 on a scaled 0–1000 range. The registration fee is $375 USD per attempt (a 20% regional discount applies in India).
Who Should Take This Exam
This certification is designed for working data professionals who spend the majority of their time querying, transforming, and analyzing data inside Snowflake. Relevant job titles include Data Analyst, Analytics Engineer, Business Intelligence Developer, ELT Developer, and BI Professional. Candidates typically have responsibility for building analytical pipelines, authoring complex SQL reports, creating dashboards in Snowsight or connected BI tools, and communicating data-driven findings to business stakeholders.
The exam is appropriate for those who have moved beyond foundational Snowflake usage and are ready to demonstrate advanced competency in forecasting, UDFs, and diagnostic analytics. It is not intended for platform administrators or data engineers focused primarily on infrastructure — those roles are better served by the SnowPro Advanced: Administrator or SnowPro Advanced: Data Engineer tracks.
Prerequisites
Snowflake requires candidates to hold an active SnowPro Core Certification before sitting for the DAA-C01 exam. The SnowPro Core validates foundational knowledge of Snowflake architecture, data loading, querying, and account management, and its concepts are assumed knowledge for the advanced exam. There is no formal academic prerequisite, but Snowflake recommends candidates have at least one year of hands-on, production-level experience working as a Data Analyst in the Snowflake Data Cloud.
Beyond the formal requirement, candidates should be fluent in advanced SQL (window functions, CTEs, recursive queries, analytic functions) and have practical experience with at least one scripting or programming language for UDF development (Python, JavaScript, or Java are common choices). Familiarity with data modeling concepts, semi-structured data formats (JSON, Parquet), and at least one BI or visualization tool is strongly recommended before attempting the exam.
Exam Format
The DAA-C01 exam consists of 65 questions in multiple-choice (single correct answer) and multiple-select (two or more correct answers) formats. Candidates have 115 minutes to complete the exam. It is delivered online through Pearson VUE, which supports both remote proctored (OnVUE) and in-person testing center formats. The exam is currently offered in English only.
Scoring uses a scaled system ranging from 0 to 1000; a minimum scaled score of 750 is required to pass. Snowflake does not publish a fixed percentage-correct passing threshold, as the scaled score accounts for question difficulty. There is no published limit on retake attempts, and each attempt requires the full $375 USD registration fee. Snowflake recommends downloading the official exam study guide from the certification page prior to registration, as it contains the most current domain objectives and any updates to exam content.
Skills Measured
- 1.Domain 1 – Data Ingestion and Preparation (approx. 15–20%): Retrieving structured (CSV), semi-structured (JSON, Parquet, Avro, ORC, XML), unstructured, and synthetically generated data; performing data discovery to assess available datasets and identify elements required for business goals; profiling data for quality, granularity, and completeness; enforcing data integrity constraints; and using Snowflake's COPY INTO, Snowpipe, and internal/external stages for data loading.
- 2.Domain 2 – Data Transformation (approx. 15–20%): Cleaning and reshaping raw data using SQL transformations and Snowflake's FLATTEN, PARSE_JSON, and LATERAL JOIN capabilities for semi-structured sources; designing and implementing scalable transformation pipelines; applying data normalization and denormalization techniques; and building reusable transformation logic using views, stored procedures, and tasks.
- 3.Domain 3 – Advanced SQL Query Development (approx. 20–25%): Writing and troubleshooting complex queries using window functions, CTEs, subqueries, and recursive SQL; optimizing query performance through partition pruning, clustering keys, materialized views, and result caching; handling data anomalies and NULLs; and interpreting query profiles in Snowsight to diagnose performance bottlenecks.
- 4.Domain 4 – Snowflake Built-in Functions and UDFs (approx. 15–20%): Applying date/time, string, numeric, conditional, and aggregate functions; working with semi-structured data functions (GET, GET_PATH, OBJECT_CONSTRUCT); creating and invoking scalar and tabular User-Defined Functions (UDFs) in SQL, Python, JavaScript, or Java; and using User-Defined Table Functions (UDTFs) for advanced analytical use cases.
- 5.Domain 5 – Descriptive and Diagnostic Data Analysis (approx. 10–15%): Summarizing datasets using statistical measures (mean, median, standard deviation, percentiles); identifying outliers, trends, and anomalies; using exploratory data analysis techniques within Snowflake; applying Snowflake's TABLESAMPLE for large-dataset profiling; and building descriptive reports and interactive dashboards in Snowsight.
- 6.Domain 6 – Predictive Data Analysis (approx. 10–15%): Applying time-series forecasting methods available natively in Snowflake (including Snowflake ML-powered forecasting functions); using regression techniques for predictive modeling; interpreting model outputs and communicating forecast uncertainty; and understanding when to leverage Snowpark for more advanced ML workflows.
- 7.Domain 7 – Data Presentation and Business Requirements (approx. 10–15%): Translating business questions into analytical requirements; exporting data in formats appropriate for downstream consumers (CSV, JSON, Parquet); connecting Snowflake to BI tools such as Tableau, Power BI, and Looker via Partner Connect or direct ODBC/JDBC; building stakeholder-facing dashboards and reports; and applying data storytelling principles to communicate insights effectively.
Study Tips
- Download and work through the official Snowflake SnowPro Advanced: Data Analyst Study Guide (available at learn.snowflake.com) before anything else — it defines the exact domain objectives and is the authoritative source for what will be tested.
- Build hands-on practice in a free Snowflake trial account: load semi-structured JSON and Parquet files using COPY INTO and Snowpipe, practice FLATTEN and PARSE_JSON queries, and profile the results in Snowsight's query editor to understand explain plans and partition pruning.
- Master window functions, CTEs, and analytic SQL — these appear heavily across multiple domains. Practice writing RANK, DENSE_RANK, LAG, LEAD, NTILE, and RATIO_TO_REPORT functions against realistic datasets, and focus on understanding when each is appropriate.
- Experiment with Snowflake's native ML forecasting functions (introduced in 2023–2024) and build at least one UDF in Python or JavaScript. The predictive analytics and UDF domains require applied experience that is difficult to gain through reading alone.
- Use Snowflake's free Hands-On Essentials and Data Warehousing Workshop labs on Snowflake University (learn.snowflake.com) to reinforce practical skills, and supplement with the Pluralsight SnowPro Advanced: Data Analyst learning path, which maps directly to DAA-C01 objectives.
- Review the SnowPro Core Certification study material as a baseline — the DAA-C01 builds on Core concepts such as micro-partitions, clustering, Time Travel, data sharing, and Snowflake architecture. Gaps in Core knowledge will surface during the advanced exam.
- Practice with timed mock exams (65 questions in 115 minutes ≈ 1.75 minutes per question). Focus especially on multiple-select questions, which require identifying all correct answers with no partial credit — a common source of lost points for candidates who know the material but rush.
Career Benefits
Earning the SnowPro Advanced: Data Analyst credential signals to employers that a candidate can operate independently at an advanced level on the Snowflake platform — a differentiated skill as Snowflake's market share in the cloud data warehouse space continues to grow across financial services, retail, healthcare, and technology sectors. Job titles commonly held by certified candidates include Senior Data Analyst, Analytics Engineer, BI Engineer, and Data Scientist, with US salaries for Snowflake-proficient analysts typically ranging from $95,000 to $145,000 depending on seniority, industry, and location.
The DAA-C01 sits within Snowflake's Advanced certification tier, positioning it above the SnowPro Core and SnowPro Associate credentials and alongside other Advanced specializations (Data Engineer, Architect, Administrator). Unlike vendor-neutral analytics certifications, the DAA-C01 directly validates platform-specific expertise that many employers explicitly list as a job requirement when Snowflake is the primary data platform. Holding both the SnowPro Core and an Advanced specialization is increasingly recognized as a strong signal of job-ready Snowflake proficiency in competitive data hiring pipelines.
Sample Questions
5 sample questions with answers and explanations. The full bank has 600 questions, enough for 6 full-length practice exams.
Preview — answers shown1. A data governance architect at Northwind Insurance applies a dynamic data masking policy to the SSN column of the CUSTOMERS base table. The policy returns the real SSN to users with ANALYST_ROLE or SECURITY_ADMIN and returns the masked value '***-**-XXXX' to all other roles. A business user holding ANALYST_ROLE runs a SELECT query against a non-secure view called CUSTOMER_SUMMARY, which includes the SSN column derived from the CUSTOMERS table. What value will the user see for the SSN column? (Select one!)
AThe masked value '***-**-XXXX', because non-secure views apply the most restrictive masking policy available to prevent privilege escalation through indirect table access
BAn error at query time, because dynamic data masking policies attached to base table columns are not evaluated when the column is accessed indirectly through a view definition
CThe real SSN value, because dynamic data masking evaluates the querying user's active role at query execution time and the policy applies consistently whether the column is accessed through a view or directly from the base table
DThe real SSN value only if CUSTOMER_SUMMARY is defined as a SECURE VIEW; for non-secure views, Snowflake defaults to the most restrictive mask to prevent unintended data exposure
Explanation
Dynamic data masking policies in Snowflake are evaluated at query execution time based on the active role of the user running the query, not the role of the view owner or policy owner. Because the querying user holds ANALYST_ROLE, which is explicitly granted unmasked access in the policy conditions, they receive the real SSN value. This evaluation is identical whether the user accesses the SSN column directly from the CUSTOMERS table or through the CUSTOMER_SUMMARY view — masking policies are bound to the column and enforced at all access paths. Non-secure views do not override or escalate masking policy behavior; the policy conditions are applied exactly as defined regardless of view type. Dynamic data masking does not produce errors when a masked column is accessed through a view. The SECURE VIEW designation controls whether a view's internal query definition is visible to users in query profiles and SHOW commands, not how masking policies are enforced during query execution.
2. Contoso's reporting team needs to generate a regional sales summary that shows totals for every possible combination of three dimensions — Region, Category, and Year — including the grand total and all partial subtotals such as Region alone, Category + Year, and Region + Category. They require all 8 grouping combinations produced automatically in a single query. Which SQL grouping construct should they use? (Select one!)
AGROUP BY CUBE(Region, Category, Year)
BGROUP BY GROUPING SETS ((Region, Category, Year), (Region, Category), (Region, Year))
CGROUP BY ALL
DGROUP BY ROLLUP(Region, Category, Year)
Explanation
CUBE(Region, Category, Year) generates all 2^3 = 8 possible grouping combinations: (Region, Category, Year), (Region, Category), (Region, Year), (Category, Year), (Region), (Category), (Year), and the grand total (). This is the correct choice when every cross-dimensional subtotal must appear in a single query. ROLLUP(Region, Category, Year) produces only 4 groupings in a strict left-to-right hierarchy — (Region, Category, Year), (Region, Category), (Region), and () — which omits cross-dimensional combinations such as (Category, Year) and (Category) alone. GROUPING SETS with only three entries generates exactly those three grouping sets and excludes the remaining required combinations. GROUP BY ALL is shorthand that groups by all non-aggregate columns in the SELECT list, producing one row per unique value combination but no multi-level subtotals or grand totals.
3. A senior developer at Litware Analytics is reviewing two SQL UDF definitions written by a junior team member. The first UDF, GET_ACCOUNT_TIER(), accepts an ACCOUNT_ID INTEGER and returns a VARCHAR by executing a SELECT statement that joins the ACCOUNTS and TIER_RULES tables to derive the tier name. The second UDF, LOG_LOOKUP_EVENT(), accepts the same INTEGER input and attempts to INSERT a row into an AUDIT_LOG table each time a lookup is performed. The developer needs to predict which functions will be created successfully. What is the correct outcome? (Select one!)
ABoth UDFs fail because any SQL UDF that performs I/O against Snowflake tables must be rewritten as a JavaScript or Python UDF to gain the necessary execution context and privileges
BGET_ACCOUNT_TIER fails at creation time because SQL UDF bodies must be pure scalar expressions that do not reference any base tables; LOG_LOOKUP_EVENT also fails because DML is unsupported
CBoth UDFs are created successfully; LOG_LOOKUP_EVENT defers the INSERT and executes it asynchronously after the calling query commits, ensuring audit records are eventually consistent
DGET_ACCOUNT_TIER is created successfully because SQL UDFs support SELECT expressions including table joins; LOG_LOOKUP_EVENT fails at creation time because SQL UDFs cannot contain DML operations such as INSERT, UPDATE, or DELETE
Explanation
Snowflake SQL UDF bodies support SELECT expressions, including complete SELECT statements that join multiple tables, filter rows, and return a single scalar value. GET_ACCOUNT_TIER is therefore valid and will be created and executed successfully, with the SELECT inlined into the calling query at runtime. In contrast, SQL UDF bodies explicitly cannot contain DDL statements or any DML statement other than SELECT. An INSERT operation inside a SQL UDF body causes the CREATE FUNCTION statement itself to fail with a compilation error at creation time, not at call time. To perform audit logging that requires writing rows to a table, the correct approach is a stored procedure, which supports full DML and procedural logic but must be invoked via CALL and cannot be embedded inline within a SELECT expression. JavaScript and Python UDFs provide more flexibility than SQL UDFs but are also subject to restrictions on direct DML execution without using the query execution APIs available in those runtimes.
4. A data modeling team at Contoso Analytics needs to build an automatically maintained pre-aggregated reporting layer that joins three dimension tables with a central fact table and applies GROUP BY aggregations. They are evaluating Snowflake materialized views versus dynamic tables for this use case. Which statement correctly explains why dynamic tables are the appropriate choice? (Select one!)
ADynamic tables support complex SQL including multi-table joins and aggregations, whereas materialized views are restricted to a single base table and do not support joins
BDynamic tables use INCREMENTAL refresh mode by default while materialized views always use FULL refresh, making dynamic tables consistently faster for all workloads
CDynamic tables are available in all Snowflake editions while materialized views require Business Critical Edition or higher
DDynamic tables are cached entirely in Snowflake memory for zero-latency access, while materialized views are persisted to cloud storage with higher read latency
Explanation
Materialized views in Snowflake are restricted to queries against a single base table — they do not support joins, making them unsuitable for multi-table aggregation pipelines. Dynamic tables overcome this limitation by supporting arbitrarily complex SQL including multi-table joins, aggregations, window functions, and nested CTEs, which makes them the correct choice for denormalized reporting layers built from normalized schemas. The claim that dynamic tables default to INCREMENTAL refresh mode is incorrect — the default is AUTO, where Snowflake selects between INCREMENTAL and FULL based on query characteristics; only INCREMENTAL is available when the query structure allows it. Dynamic tables are not memory-cached objects; they are persisted tables with computed data subject to TARGET_LAG refresh schedules (minimum 1 minute). Materialized views require Enterprise Edition and above, not Business Critical Edition specifically.
5. A data engineering team at Litware Financial builds a dynamic table that computes daily revenue summaries from an ORDERS source table. The source table is append-only, receiving only INSERT operations. The dynamic table is created with REFRESH_MODE = AUTO and TARGET_LAG = '10 minutes'. During monitoring, the team notices that each refresh completes in a few seconds, even though the ORDERS table contains billions of historical rows. Which two statements accurately explain why refreshes complete so quickly for this workload? (Select two!)
Multiple correct answersAWhen REFRESH_MODE is set to AUTO, Snowflake inspects both the transformation logic and the source table's change pattern; for append-only sources with incrementally computable transformations, it automatically selects INCREMENTAL refresh rather than FULL refresh
BAUTO mode defaults to FULL refresh for all dynamic tables containing GROUP BY or aggregation clauses, because Snowflake cannot guarantee correctness of partial aggregation results without re-scanning all historical data
CINCREMENTAL refresh drastically reduces compute time on append-only workloads by processing only the rows inserted since the previous refresh cycle, avoiding a full scan of the billions of historical rows in the ORDERS table
DSetting TARGET_LAG to values below 60 seconds enables sub-second refresh intervals, which inherently forces Snowflake to use micro-partition pruning and skip unchanged data blocks regardless of REFRESH_MODE
EConfiguring REFRESH_MODE = FULL on this same dynamic table would produce equivalent refresh performance to AUTO because Snowflake's query optimizer uses column-level statistics to skip unchanged micro-partitions in both modes
Explanation
When REFRESH_MODE is set to AUTO, Snowflake evaluates two factors: the SQL transformation definition and the nature of changes on the source table. For an append-only INSERT-only workload with a transformation that can be computed incrementally — such as grouped aggregations over newly inserted rows — Snowflake automatically selects INCREMENTAL refresh. This means each refresh cycle processes only the rows that arrived since the last successful refresh, which is why completion time is measured in seconds rather than minutes for a billions-row table. AUTO mode does not default to FULL refresh for GROUP BY queries; the decision is based on whether the aggregation can be computed correctly using only new data, and append-only sources with additive aggregations satisfy this condition. The minimum supported TARGET_LAG for a dynamic table is 1 minute — sub-minute values are not supported and will be rejected at creation time. FULL refresh mode always re-scans and recomputes the complete result set from all source rows on every cycle; micro-partition pruning applies to predicate filters but does not replicate the efficiency of true incremental processing, making FULL refresh significantly slower on large historical tables.
More Snowflake Practice Exams
SnowPro® Specialty: Snowpark (SPS-C01)
SPS-C01 · 599 questions
SnowPro Advanced: Administrator (ADA-C02)
ADA-C02 · 600 questions
SnowPro Advanced: Architect (ARA-C01)
ARA-C01 · 592 questions
SnowPro Advanced: Data Engineer (DEA-C02)
DEA-C02 · 597 questions
SnowPro® Advanced: Data Scientist (DSA-C03)
DSA-C03 · 600 questions
SnowPro Advanced: Security Engineer (SEA-C01)
SEA-C01 · 550 questions
$17.99
One-time access to this exam
600 questions (6 practice exams' worth)
Unlimited timed exam simulations
Yours forever — no subscription
Detailed explanations
Free preview stays available