350-401 · Question #175
What mechanism does PIM use to forward multicast traffic?
The correct answer is A. PIM sparse mode uses a pull model to deliver multicast traffic.. PIM Multicast Forwarding Mechanisms Option A is correct because PIM Sparse Mode (PIM-SM) operates on a pull model, meaning traffic is only forwarded to routers that have explicitly requested it by joining a multicast group - traffic flows toward receivers on demand, not by defaul
Question
What mechanism does PIM use to forward multicast traffic?
Options
- APIM sparse mode uses a pull model to deliver multicast traffic.
- BPIM dense mode uses a pull model to deliver multicast traffic.
- CPIM sparse mode uses receivers to register with the RP.
- DPIM sparse mode uses a flood and prune model to deliver multicast traffic.
How the community answered
(33 responses)- A88% (29)
- B3% (1)
- C3% (1)
- D6% (2)
Explanation
PIM Multicast Forwarding Mechanisms
Option A is correct because PIM Sparse Mode (PIM-SM) operates on a pull model, meaning traffic is only forwarded to routers that have explicitly requested it by joining a multicast group - traffic flows toward receivers on demand, not by default.
Why the distractors are wrong:
- Option B is incorrect because it's PIM Dense Mode (PIM-DM) that uses flood and prune (a push model), not a pull model - PIM-DM floods traffic everywhere first, then prunes branches with no receivers.
- Option C is partially true (sources register with the RP, not receivers), but the statement is misleading - sources register with the Rendezvous Point (RP), while receivers join using IGMP; this alone doesn't describe the forwarding mechanism.
- Option D is incorrect because flood and prune describes PIM Dense Mode, not Sparse Mode.
Memory Tip: Think of the words themselves - "Sparse" means few/scattered, so routers only pull traffic where needed (pull = sparse). "Dense" means packed/everywhere, so traffic floods everywhere first (flood = dense). Sparse = Pull; Dense = Push (flood & prune).
Topics
Community Discussion
No community discussion yet for this question.