CompTIA N10-009 Traffic Types & Communication Patterns Guide

Traffic-pattern questions are distribution questions. CompTIA is usually testing whether you can match the communication method to the delivery need without creating unnecessary noise, wasted bandwidth, or the wrong scope of reachability.

Anycast: A routing model where one logical address is announced from multiple locations and the network delivers traffic to the closest path.

Broadcast domain: The set of devices that can receive the same Layer 2 broadcast traffic on a local segment or VLAN.

What CompTIA is really testing

The strongest answers usually depend on whether the traffic should go:

• one to one
• one to many
• one to the nearest available instance
• one to every host on the local segment

Keep the traffic types distinct

A simple traffic-behavior example

1ARP request -> broadcast on local segment
2Video stream to subscribed receivers -> multicast
3Web request to one server -> unicast
4Request to the nearest public resolver instance -> anycast

What to notice:

• not every one-to-many problem should become broadcast
• broadcast stays local to the broadcast domain instead of scaling cleanly everywhere
• anycast is about nearest or best path selection, not about every server receiving the same packet

Why scope matters

CompTIA often hides the right answer inside this question:

“How many receivers should get this traffic, and how far should it travel?”

• local discovery often points toward broadcast behavior
• scoped group delivery points more toward multicast
• ordinary application traffic is usually unicast
• resilient nearest-instance service often points toward anycast

Common traps

• using broadcast when the question is really about scoped delivery
• treating multicast like a security feature instead of a delivery model
• assuming anycast means every instance processes the packet
• forgetting that broadcast noise is limited by the local broadcast domain

What strong answers usually do

• match the traffic pattern to the actual distribution requirement
• keep local broadcast behavior separate from routed delivery logic
• recognize when anycast changes path selection and resilience behavior
• choose the narrowest delivery method that fits the use case

Decision order that usually wins

1. Classify the traffic as one-to-one, one-to-all in a local domain, one-to-many interested receivers, or best-nearest instance.
2. If ordinary client-server traffic is described, think unicast.
3. If the clue is local-domain flooding, think broadcast.
4. If the same logical service should be reachable through the nearest instance, think anycast.
5. Network+ usually rewards matching the communication pattern to the path behavior rather than overthinking the topology.

Quiz

Continue with 1.6 Media, Wireless & Links to keep the domain flow intact.