6 exercises — fill in the blanks in a network design recommendation report, then write a clear 3-sentence design justification from given requirements.
0 / 6 completed
1 / 6
Fill in the blank in this network design recommendation: "We recommend a ____ topology with a redundant core for this branch network, so each branch connects only to headquarters, keeping the design simple to manage while still tolerating a single link failure."
Hub-and-spoke — each branch (spoke) connects only to a central location (hub), rather than to every other branch. This is simpler to manage and scales more easily than a full mesh, at the cost of longer paths for branch-to-branch traffic.
Common network topology vocabulary: • Hub-and-spoke: central point, simple, scalable, but hub is a critical dependency • Full mesh: every node connects to every other node — lowest latency between any two points, but complex and expensive to scale • Partial mesh: a middle ground — critical sites are meshed, less critical sites use hub-and-spoke • Redundant core: the core (hub) itself has duplicate paths/devices so a single failure there does not take down the whole network
Justifying a topology choice in a design document always pairs the choice with the reasoning: "we recommend X because [traffic pattern / cost / operational complexity]."
2 / 6
Fill in the blank: "The ____ sits between the public internet and the internal network, hosting internet-facing services like the web server and mail relay, so that a compromise there does not directly expose the internal LAN."
DMZ (demilitarised zone) — a network segment positioned between the public internet and the trusted internal network, used to host services that must be reachable from the internet (web servers, mail relays, VPN concentrators) while keeping them isolated from sensitive internal systems.
Design principle behind the DMZ: if an internet-facing service is compromised, the attacker lands in the DMZ, not directly on the internal network — firewall rules between the DMZ and internal network are typically very restrictive, permitting only the specific traffic those DMZ services genuinely need (e.g., the web server may only reach the internal database on one specific port).
Phrase pattern for a design doc: "Public-facing services live in the DMZ; the firewall permits only the minimum required traffic from the DMZ into the internal network, and denies all DMZ-initiated traffic to internal systems by default."
3 / 6
Fill in the blank: "To keep broadcast traffic contained and separate departments logically without running additional cabling, we will divide the office network into several ____ — one for engineering, one for finance, one for guest Wi-Fi."
VLANs (Virtual Local Area Networks) — logically separate broadcast domains on the same physical switching infrastructure, used to segment traffic by department, function, or security requirement without needing separate physical networks.
Segmentation vocabulary: • VLAN: logical Layer 2 segmentation on shared switches • Segmentation: the broader practice of dividing a network into smaller, isolated zones to limit the blast radius of a compromise or fault • Micro-segmentation: very fine-grained segmentation, often down to individual workloads, common in modern data centre and cloud security designs • Inter-VLAN routing: a router or Layer 3 switch that permits (and controls, via ACLs) traffic between VLANs
Design justification phrase: "guest Wi-Fi is placed on its own VLAN with no route to internal VLANs, so a compromised guest device cannot reach internal systems."
4 / 6
Fill in the blank: "For this critical application, we designed the network with ____ so that if the primary firewall fails, the secondary automatically takes over the active role within seconds, with no manual intervention."
Failover / High availability (HA) — a design where a redundant standby device automatically takes over if the primary fails, minimising downtime. "Failover" describes the event/action itself; "HA" describes the overall design property.
Redundancy and availability vocabulary: • Redundancy: having a spare/duplicate component so a single failure does not cause an outage • Failover: the automatic (or manual) switch from a failed primary component to a standby • HA pair / active-passive: two devices, one actively handling traffic, one on standby ready to take over • Active-active: both devices handle traffic simultaneously, sharing the load, with each able to absorb the other's traffic if one fails • Single point of failure (SPOF): a component whose failure would bring down the whole system — a design goal is usually to eliminate these for critical paths
Design phrase: "the firewall pair runs in active-passive HA mode with sub-second failover, eliminating the firewall as a single point of failure."
5 / 6
Which sentence best presents a network design recommendation to a non-technical stakeholder, framing the requirement, the topology, and the justification clearly?
A strong design recommendation for a non-technical audience states: the business requirement ("reliable access to the shared inventory system"), the proposed solution in plain terms ("a dedicated encrypted link... with a backup internet-based connection"), and the justification tied back to the requirement ("keeps the inventory system reachable even during a link outage") — without leading with jargon like "OSPF" or "area 0" that has no meaning to the audience.
Structure for presenting a network design to stakeholders: 1. Requirement: what business outcome does this design need to achieve? 2. Proposed topology (in plain language): what are we building, described in terms of what it does, not just what it's called 3. Justification: why this approach specifically satisfies the requirement (cost, reliability, simplicity) 4. Trade-offs acknowledged: what this design does NOT solve, or what it costs, so expectations are set correctly
Save the protocol-level detail (OSPF, BGP, VLAN IDs) for the technical design document aimed at engineers, not the stakeholder summary.
6 / 6
Production exercise: Given these requirements — "The company is opening a new branch office. It needs internet access, secure connectivity back to headquarters, and must not be able to reach the finance VLAN at headquarters" — which 3-sentence design justification best addresses all three requirements clearly?
This answer addresses all three stated requirements, one per sentence, with justification: (1) internet access — via local ISP, explaining WHY (keeps browsing off the VPN); (2) secure connectivity to HQ — site-to-site IPsec VPN, correctly named; (3) finance VLAN isolation — an explicit deny rule, tied directly back to "no business need", which is the standard justification pattern for a least-privilege access decision.
Production pattern for a design justification: [Requirement] → [Specific mechanism] → [Why this mechanism satisfies the requirement], repeated for each requirement, in plain but technically accurate language.
The wrong options fail for identifiable reasons: option A is too vague and offers no mechanism; option C introduces jargon (BGP/OSPF/full mesh/WPA3) that doesn't match the stated requirements and is disproportionate for a single new branch; option D ignores the explicit segmentation requirement entirely, which would be a serious security gap if actually implemented.
What does the "Network Design Communication — Networking Language Exercises" exercise cover?
Practise network design vocabulary in English: topology, redundancy, failover, HA, VLAN, segmentation, DMZ, and presenting and justifying network design decisions clearly.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Network Design Communication — Networking Language Exercises"?
This exercise has 6 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Networking Language exercises?
Browse the full Networking Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.