nerdexam
Snowflake

DEA-C02 · Question #16

A company is building a dashboard for thousands of Analysts. The dashboard presents the results of a few summary queries on tables that are regularly updated. The query conditions vary by topic…

The correct answer is B. Assign all queries to a multi-cluster virtual warehouse set to maximized mode. Monitor to. Maximized mode on a multi-cluster virtual warehouse is the right choice because it keeps all clusters running at full capacity at all times, eliminating the startup latency that would occur if clusters had to spin up on demand. Since the dashboard serves thousands of analysts…

Performance Optimization

Question

A company is building a dashboard for thousands of Analysts. The dashboard presents the results of a few summary queries on tables that are regularly updated. The query conditions vary by topic according to what data each Analyst needs. Responsiveness of the dashboard queries is a top priority, and the data cache should be preserved. How should the Data Engineer configure the compute resources to support this dashboard?

Options

  • AAssign queries to a multi-cluster virtual warehouse with economy auto-scaling. Allow the system
  • BAssign all queries to a multi-cluster virtual warehouse set to maximized mode. Monitor to
  • CCreate a virtual warehouse for every 250 Analysts. Monitor to determine how many of these
  • DCreate a size XL virtual warehouse to support all the dashboard queries. Monitor query runtimes

How the community answered

(21 responses)
  • A
    10% (2)
  • B
    81% (17)
  • C
    5% (1)
  • D
    5% (1)

Explanation

Maximized mode on a multi-cluster virtual warehouse is the right choice because it keeps all clusters running at full capacity at all times, eliminating the startup latency that would occur if clusters had to spin up on demand. Since the dashboard serves thousands of analysts with query conditions that vary per user, concurrent demand is high and unpredictable - maximized mode ensures every query hits a warm, available cluster, preserving the data cache across clusters and meeting the "responsiveness is top priority" requirement.

Why the distractors fail:

  • A (Economy auto-scaling): Economy mode prioritizes cost savings by delaying cluster spin-up, which introduces latency. This directly conflicts with the responsiveness requirement and risks cache loss during scale-up events.
  • C (One warehouse per 250 analysts): Creating separate warehouses fragments the cache across isolated resources, meaning each warehouse must rebuild its cache independently - undermining the "preserve the data cache" requirement and adding management overhead.
  • D (Single XL warehouse): A single warehouse, regardless of size, cannot scale horizontally to handle thousands of concurrent analysts without queuing. Queued queries kill responsiveness.

Memory tip: Think of Maximized = Max Speed, Max Concurrency. When the requirement says "responsiveness is top priority," that's the signal to maximize clusters - not economize or isolate them. Economy = cost priority; Maximized = performance priority.

Topics

#Multi-cluster Virtual Warehouses#Warehouse Maximized Mode#Performance Tuning#Concurrency Management

Community Discussion

No community discussion yet for this question.

Full DEA-C02 Practice