**Architectural Logic**: View: Virtual; query runs at read time. No storage. Materialized view: Physical storage of query result; refreshed on schedule or on commit. **Why**: Views for abstraction, security, logic reuse. Materialized views for precomputed expensive aggregations,...
This medium-level SQL question appears frequently in data engineering interviews at companies like Presidio, Swiggy. While less common, it tests deeper understanding that distinguishes strong candidates.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Architectural Logic: View: Virtual; query runs at read time. No storage. Materialized view: Physical storage of query result; refreshed on schedule or on commit. Why: Views for abstraction, security, logic reuse. Materialized views for precomputed expensive aggregations, low-latency dashboards. Scalability: View scales with underlying tables. Materialized view scales with refresh strategy—incremental vs full. Cost: View has no storage cost; materialized view has storage + compute for refresh. Stale data trade-off: MV can be seconds to hours old. Use views for logic; MVs when query cost >> refresh cost.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer — FreeAccording to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 2 companies. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.