Match a job Paths Subjects Questions Quizzes Pricing
Overview Read Practice

Practice — Data Engineering in Production (5 questions)

Pro content

Sign up free, then start a 14-day Pro trial — no card needed.

Advanced Open Free

Diagnosing and Preventing a Runaway Warehouse Cost Spike Permalink →

Finance flags that your team's Snowflake bill for last month is 4x the usual amount. You pull WAREHOUSE_METERING_HISTORY and find that a single warehouse, ANALYTICS_XL, was active nearly continuously for 11 days straight, even overnight and on weekends, at an X-LARGE size. Nobody remembers scheduling anything unusual. Digging further, you find an engineer ran a one-off backfill on that warehouse 11 days ago, manually resized it to X-LARGE "to make it finish faster," and the warehouse's AUTO_SUSPEND was set to 3600 (one hour) months earlier "because cold starts were annoying during a demo."

  1. Explain exactly how these two settings combined to produce an 11-day near-continuous billing window, not just "auto-suspend was too long."
  2. Propose the concrete configuration and process fixes — not just "be more careful" — that prevent this specific failure mode from recurring, for this warehouse and others like it.
  3. Design a detection mechanism that would have caught this within hours instead of a full billing cycle later, and explain what signal it watches for.

Share this question

Advanced Open Pro

Prod Credentials Leaked Into a Dev Environment

Unlock this question →
Advanced Open Pro

Designing Slim CI for a Slow, Expensive dbt Project

Unlock this question →
Advanced Open Pro

A 3am Pipeline Failure With No Usable Runbook

Unlock this question →
Advanced Open Pro

A Metric Changed Meaning and Nobody Downstream Was Told

Unlock this question →

We use cookies for product analytics to improve OmniAtlas. See our Privacy Policy.