Palo Alto Networks SD-WAN Engineer — Question 6

A network engineer isle to ping and traceroute from SD-WAN branch IP 192.168.1.123 to servers in primary data center – DC1, but is unable to ping or traceroute to a server 10.2.2.22 in the newly configured secondary data center, DC2.
The DC2 ION device is advertising the branch IP subnet 192.168.1.0/24 to the DC2 core via eBGP Core Peer. The DC2 data center site has site prefix 10.2.2.0/23 configured.
Which configuration will resolve the issue in this scenario?

Answer options

• A. The default 0.0.0.0/0 static route to the DC2 ION pointing to the DC2 next hop.
• B. Reconfigure eBGP Core Peer to iBGP Core Peer.
• C. Reconfigure eBGP Core Peer as Edge Peer type.
• D. Remove site prefix 10.2.2.0/23 from DC2 site configuration.

Correct answer: C

Explanation

The correct answer, C, is appropriate because configuring the eBGP Core Peer as an Edge Peer type allows proper routing for the branch subnet to the DC2 servers. Option A would not resolve the routing issue as it does not align the peer types correctly. Option B would not be suitable because changing to iBGP does not address the specific connectivity issue with the Edge configuration. Option D would lead to the loss of address space needed for the servers in DC2.