Noos
PT EN
RAN-DBDEA-00164
Ranvier · DBDEA

Exam DBDEA Topics: troubleshooting Difficulty: medium

An analytics team serves executive dashboards from a Medium SQL warehouse. During the morning peak, individual dashboard queries take over a minute, and the query profile shows that each query itself is resource-hungry, with high CPU and memory use per node; only a handful of queries run concurrently. The team wants each query to run faster. What should they change on the warehouse?

Options (Reading Mode) Click to filter discussion →
  1. A. Create one dedicated warehouse per dashboard and manually route refreshes to whichever is idle
  2. B. Increase the warehouse size so every query runs with more memory and CPU per node
  3. C. Lengthen the auto-stop delay so the warehouse stays warm between dashboard refreshes
  4. D. Recreate the warehouse from scratch, because its size is fixed at creation and cannot be edited
Reveal answer

Correct answer: Increase the warehouse size so every query runs with more memory and CPU per node

Reference: https://docs.databricks.com/aws/en/compute/sql-warehouse/warehouse-behavior

02 — The Myelin Layer · Canonical Discussion

Where the exam tries to trick you — and how those who passed solved it.

0 Passed

contributed to this question

Answer Distractor Matrix Click an option to filter or open its dissection.
✦ Consolidated Synthesis (Wiki) rev. #1 (baseline) · CC BY-SA 4.0
Start synthesis for this question →

No community synthesis consolidated for this question yet. Below is the verifiable official starting point — if you passed the exam, open the option dissection.

Official Answer (B): Increase the warehouse size so every query runs with more memory and CPU per node

Ranvier · DBDEA

Contribute to this Question

Your contribution builds your Orbital Sheath

Peer contributions

No public contribution yet. Be the first who passed to explain why the distractors trick candidates — your contribution builds your Orbital Sheath.