Build fluency in the vocabulary of organizing a data lakehouse into progressively refined layers.
0 / 5 completed
1 / 5
A teammate explains that a data lakehouse organizes tables into three successive layers, a bronze layer holding raw, unmodified ingested data, a silver layer holding cleaned and conformed data with types and schemas validated, and a gold layer holding business-level aggregates ready for reporting, so each layer's data quality builds progressively on the one before it. What data-lakehouse layering pattern is being described?
The medallion architecture organizes a data lakehouse into three successive layers: a bronze layer holding raw, unmodified ingested data exactly as it arrived, a silver layer holding cleaned, validated, and conformed data with consistent types and schemas, and a gold layer holding business-level aggregates ready for reporting and analytics, so each layer's data quality builds progressively on the layer before it and a downstream failure never corrupts the original raw data. A DNS zone transfer is an unrelated concept about replicating name server records. This raw-then-cleaned-then-aggregated-layers approach is exactly why the medallion architecture is a widely adopted pattern in modern data lakehouse platforms like Databricks for giving every downstream consumer a clear, progressively refined layer to build on.
2 / 5
During a design review, the team adopts medallion architecture for a lakehouse ingesting raw event data from a dozen upstream systems, specifically so a schema-validation bug discovered downstream never corrupts or requires re-ingesting the original raw source data. Which capability does this provide?
Medallion architecture here provides reprocessable, layered data quality, since the raw bronze layer is preserved untouched and any downstream silver or gold transformation bug can be fixed by simply reprocessing from bronze. Cleaning and transforming the raw data in place with no preserved raw copy, so a transformation bug permanently corrupts the only copy of the ingested data is the alternative this avoids. This behavior is exactly why medallion architecture is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a data pipeline transforms and cleans raw ingested data in place with no separate untouched raw copy preserved, so a schema-validation bug in the cleaning step permanently corrupts the only copy of the data instead of leaving an unmodified bronze layer to reprocess from. What does this represent?
This is a missed medallion architecture-opportunity, since a medallion architecture would preserve the raw bronze layer untouched, letting a transformation bug be fixed by reprocessing instead of permanently losing the original data. 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 data team discovered a schema-validation bug had silently corrupted several months of transformed data, and recovery was impossible because the raw ingested data had been overwritten in place with no preserved untouched copy. What practice would prevent this?
Adopting a medallion architecture so raw ingested data is preserved untouched in a bronze layer, letting a downstream transformation bug be fixed by simply reprocessing from bronze. 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 medallion architecture instead of a single-layer pipeline that cleans and transforms data in place. What is the reasoning?
a medallion architecture trades the storage cost of keeping a full untouched raw copy and the pipeline complexity of three layers for the ability to safely reprocess from raw data after any downstream bug, while a single-layer pipeline is simpler and cheaper to store but permanently loses the original data once it is transformed in place. This is exactly why medallion architecture is favored when the raw data is expensive or impossible to re-fetch from its original source, while a single-layer pipeline that cleans and transforms data in place remains acceptable when storage cost is tightly constrained and the raw source can always be cheaply re-fetched if needed.
What does the "Medallion Architecture Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to medallion architecture 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.