Learn the vocabulary of preserving dimension history in a data warehouse as attributes change over time.
0 / 5 completed
1 / 5
A teammate explains that a data warehouse's customer dimension table stores a new row with a start and end date every time a customer's address changes, rather than overwriting the existing row, so a historical sales fact can still be joined against the exact address that was on file at the time of that sale. What data-warehouse modeling technique is being described?
A slowly changing dimension, most commonly implemented as type 2, inserts a new row with a start and end date every time a tracked attribute like a customer's address changes, rather than overwriting the existing row in place, so a historical fact row can still be joined against the dimension values that were actually true at the time that fact occurred, preserving history instead of only ever reflecting the current state. A DNS zone transfer is an unrelated concept about replicating name server records. This insert-a-new-dated-row-per-change approach is exactly why slowly changing dimensions are the standard data-warehouse technique for preserving historical accuracy when a dimension's attributes change over time.
2 / 5
During a design review, the team adopts slowly changing dimension for a sales-reporting warehouse that must show which region a customer's address was in at the time of each historical sale, specifically even after that customer has since moved to a different region. Which capability does this provide?
Slowly changing dimension here provides historically accurate joins between fact and dimension data, since each dimension row is stamped with the date range during which it was actually true. Overwriting the customer dimension row in place on every address change, so every past sale ends up joined against the customer's current address instead of the address that was on file at the time of that sale is the alternative this avoids. This behavior is exactly why slowly changing dimension is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a customer dimension table overwrites a customer's address in place every time it changes, so a historical sales report ends up joining every past sale against the customer's current address instead of the address on file at the time of that sale, and the team has no dimension-history technique in place. What does this represent?
This is a missed slowly changing dimension-opportunity, since a slowly changing dimension would preserve a dated row for the old address instead of overwriting it and losing the historical join. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows a regional sales report was found to be silently wrong for months, because the customer dimension table overwrote each customer's address in place on every change, causing every historical sale to join against the customer's current address instead of the address at the time of the sale. What practice would prevent this?
Implementing the customer dimension as a slowly changing dimension, so each address change inserts a new dated row instead of overwriting the existing one, preserving the correct historical join. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team reaches for slowly changing dimension instead of overwriting the dimension row in place on every change. What is the reasoning?
a slowly changing dimension trades additional storage and join complexity, since a fact table must join on the correct date-bounded row, for historically accurate reporting, while overwriting in place is simpler to query but silently loses the ability to report accurately on past periods once an attribute changes. This is exactly why slowly changing dimension is favored when historical accuracy of past reports must be preserved as dimension attributes change, while overwriting the dimension row in place on every change remains acceptable when only the current state ever needs to be reported and historical accuracy after a change does not matter.
What does the "Slowly Changing Dimension Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to slowly changing dimension vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.