Refer to the exhibit. There is a connectivity issue between Customer-1 and Customer-2. File servers between the customers cannot send critical data. R3 routes are missing from the routing table on the

Question

Exhibits

Options

• ABidirectional Forwarding Detection must be applied to the upstream facing BGP interfaces
• BThe operator must ensure that all prefixes have the same next-hop from PE1 and PE2 for BGP PIC
• CA reserved BGP community of 1:10 must be used to denote the PIC feature set to the routing protocol
• DBGP import export policies must be applied on all devices for the routes needing BGP for PIC

• A
  74% (20)
• B
  15% (4)
• C
  4% (1)
• D
  7% (2)

Explanation

The scenario describes R3 routes missing from Customer-1's routing table despite all interfaces being up, pointing to a redistribution or route filtering misconfiguration on R2. R2 sits between the two customer segments and is responsible for propagating routes between them. The exhibit's configuration option A shows the correct configuration for R2-likely fixing a missing or incorrectly applied redistribution statement, route-map, or distribute-list. The other options either reference unrelated features (BFD, BGP PIC communities, import/export policies) that do not apply to this basic connectivity and route propagation problem between the two customer networks.

No community discussion yet for this question.