Backend · Mid-level · Theory

In which cases would you deliberately denormalize a database schema, and what's the price you pay for it?

~4 min by voice

How to approach it

This checks whether you understand why normalization exists and can step away from it deliberately: with a concrete motive, a price (things going out of sync, more expensive writes) and a mechanism for keeping data consistent, not just "we duplicate it so it's faster".

Have you seen this question in a real interview?

Answers0

Avg. score—

Strong—

Practiced0

Topics

sql data modeling

Similar questions

What are slowly changing dimensions, SCDs, and what types do you know? Junior A query that used to run in milliseconds now takes seconds after the table grew to tens of millions of rows. How would you investigate, and what can you do about it? Mid-level What are a primary key and a foreign key? And how would you model a many-to-many relationship, for example students and courses? Junior You join the orders table with the payments table, and the total revenue in the report suddenly grows almost threefold. How would you look for the cause, and how would you fix it? Mid-level You're designing a sales data mart for BI. Would you choose a star or a snowflake schema, and how would you decide what one row in the fact table represents? Mid-level

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Best with headphones · ~4 min