Build fluency in the vocabulary of tracking objects as white, gray, or black to safely collect garbage concurrently with the application.
0 / 5 completed
1 / 5
A teammate explains that a concurrent garbage collector tracks each object as white, meaning unvisited, gray, meaning visited but its references not yet scanned, or black, meaning fully scanned, to safely reclaim memory while the application keeps running and mutating references. What algorithm is being described?
Tri-color marking is exactly this: every object is classified as white if unvisited, gray if visited but its outgoing references have not yet been scanned, or black if fully scanned along with all its references, and this invariant lets a concurrent collector safely reclaim only white objects at the end of a pass, even while the application mutates references during collection, as long as a write barrier prevents a black object from ever pointing directly to a white one. A DNS zone transfer is an unrelated concept about replicating name server records. This white-gray-black-invariant approach is exactly why tri-color marking underlies concurrent and incremental garbage collectors.
2 / 5
During a design review, the team relies on tri-color marking with a write barrier for a low-latency service that cannot tolerate long stop-the-world pauses, specifically so collection can proceed concurrently with the application mutating object references. Which capability does this provide?
Tri-color marking with a write barrier here provides safe concurrent collection despite the application mutating references mid-pass, since the write barrier prevents a black object from ever pointing directly to an unmarked white object, which would otherwise let a live object be mistakenly reclaimed. A stop-the-world collector that halts the application for the entire marking phase avoids that hazard by simply not letting the application run concurrently at all, at the cost of a longer pause. This safe-concurrent-mutation behavior is exactly why tri-color marking is favored for low-latency services.
3 / 5
In a code review, a dev notices a garbage collector marks objects reachable from the roots but has no write barrier to catch a black object later being mutated to point at a white object, while the application keeps running concurrently during marking. What does this represent?
This is a missed tri-color-marking safety requirement, since without a write barrier a black object can end up pointing at a white object that gets wrongly reclaimed. A cache eviction policy is an unrelated concept about discarded cache entries. This missing-write-barrier gap is exactly the kind of correctness hazard a reviewer flags once marking must remain safe while the application runs concurrently.
4 / 5
An incident report shows a service crashed with a use-after-free-style corruption because a concurrent collector reclaimed an object that a black object still referenced, since no write barrier caught the black-to-white reference created after that object was marked. What practice would prevent this?
Adding a proper write barrier to the tri-color-marking implementation ensures a mutation creating a black-to-white reference is caught and the white object is kept alive instead of being wrongly reclaimed. Continuing to run concurrent marking without any write barrier regardless of how many black-to-white references get created during mutation is exactly what caused the corruption described in this incident. This write-barrier-enforced-invariant approach is the standard fix once concurrent marking is confirmed to need it for safety.
5 / 5
During a PR review, a teammate asks why the team reaches for tri-color marking with a write barrier instead of a simple stop-the-world mark phase that halts the application entirely while scanning, given that stopping the world avoids any write-barrier complexity. What is the reasoning?
Tri-color marking trades write-barrier bookkeeping overhead on every reference mutation for the ability to collect concurrently without a long application pause, while stop-the-world marking is simpler but freezes the application for the full scan. This is exactly why tri-color marking is favored in low-latency, garbage-collected runtimes, while stop-the-world marking remains acceptable when brief full-application pauses are tolerable.
What does the "Tri-Color Marking Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to tri-color marking 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.