Because multicast data forwarding relies on routing table entries, problems such as loops and suboptimal paths will not occur during the forwarding process.

Question

Options

• ATRUE
• BFALSE

• A
  20% (5)
• B
  80% (20)

Explanation

B is correct because multicast routing does use routing table entries (specifically multicast routing tables built by protocols like PIM), but this does not inherently prevent loops or suboptimal paths. Multicast forwarding relies on mechanisms like RPF (Reverse Path Forwarding) checks to attempt loop prevention, but misconfigurations, protocol failures, or Reverse Path Forwarding failures can still cause loops and suboptimal forwarding trees.

Why A is wrong: The statement assumes that "routing table entries = guaranteed correct forwarding," which is a false equivalence. Unicast routing tables can have loops too (e.g., routing protocol convergence issues), and multicast is no different - the presence of a table entry doesn't guarantee its correctness or optimality.

Memory tip: Think of a routing table as a map, not a GPS with traffic avoidance. A map can have outdated roads or circular routes drawn on it - just having one doesn't mean your path is loop-free or optimal. Multicast needs additional mechanisms (like RPF and proper protocol tuning) to actually achieve that.

No community discussion yet for this question.