Which kind of traffic is supported in an MVPN Extranet?

Question

Options

• APIM dense mode with Reverse Path Forwarding
• BPIM dense mode
• CPIM sparse mode
• DBidirectional PIM

• A
  6% (1)
• B
  12% (2)
• C
  82% (14)

Explanation

PIM sparse mode (C) is correct because MVPN Extranet deployments rely on explicit join mechanisms and controlled multicast distribution across VPN boundaries - exactly what sparse mode provides through its shared-tree and shortest-path-tree model. PIM dense mode (B) is eliminated because it uses flood-and-prune behavior that is unsuitable for MPLS/VPN environments where traffic must be tightly controlled. Option A (dense mode with RPF) fails for the same reason - adding RPF doesn't resolve the fundamental incompatibility of dense mode's flooding behavior with extranet architectures. Bidirectional PIM (D) is excluded because its shared bidirectional tree model lacks the source-specific routing granularity required for extranet multicast across separate VPN routing domains.

Memory tip: Think "Sparse = Selective" - MVPN Extranets need selective, explicit-join multicast, not the broadcast-first approach of dense or bidir modes.

No community discussion yet for this question.