Build fluency in the vocabulary of ICE candidate negotiation.
0 / 5 completed
1 / 5
A teammate explains that a video-calling app gathers several possible network paths for each peer, a direct host address, a server-reflexive address discovered via STUN, and a relayed address via TURN as a fallback, then tries each candidate pair in priority order until it finds one that actually establishes a connection through both peers' NATs and firewalls. What is being described?
ICE (Interactive Connectivity Establishment) candidate negotiation is exactly what is described here. A DNS zone transfer is an unrelated concept about replicating name server records. Understanding ICE candidate negotiation is exactly why it comes up so often in real engineering discussions of this kind of problem.
2 / 5
During a design review, the team adopts ICE candidate negotiation, specifically to gain a concrete benefit. Which capability does this provide?
ICE candidate negotiation here provides a reliable connection despite unpredictable NAT and firewall configurations, since multiple candidate paths are gathered and tried in priority order until one actually works. Assuming a direct connection between each peer's local host address will always succeed, with no fallback if a NAT or firewall blocks it is the alternative this avoids. This behavior is exactly why ICE candidate negotiation is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a system relies on assuming a direct connection between each peer's local host address will always succeed, with no fallback if a NAT or firewall blocks it, instead of using ICE candidate negotiation. What does this represent?
This is a missed ICE candidate negotiation-opportunity, since ICE candidate negotiation would provide a reliable connection despite unpredictable NAT and firewall configurations, since multiple candidate paths are gathered and tried in priority order until one actually works. 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 video calls between users on two different restrictive corporate networks consistently failed to connect because the app only ever attempted a direct host-to-host connection with no fallback path. What practice would prevent this?
Gathering host, server-reflexive, and relayed ICE candidates and trying each pair in priority order instead of assuming only a direct connection will work. 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 ICE candidate negotiation instead of assuming a direct connection between each peer's local host address will always succeed, with no fallback if a NAT or firewall blocks it. What is the reasoning?
ICE negotiation trades the overhead of gathering and testing multiple candidate paths, including a TURN relay, for a connection that succeeds across a much wider range of NAT and firewall configurations, while assuming only a direct connection keeps the code simpler but fails outright whenever either peer sits behind a restrictive NAT or firewall. This is exactly why ICE candidate negotiation is favored in scenarios that call for it, while the alternative remains acceptable in simpler cases that don't.
What does the "ICE candidate negotiation Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to ice candidate negotiation 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.