In a Data Center deployment, what is the key functional difference between configuring a BGP neighbor as a "Core Peer" versus an "Edge Peer"?

The key functional difference between a BGP Core Peer and an Edge Peer in Palo Alto Networks SD-WAN lies in the automatic route redistribution policy. Routes learned from a peer designated as "Core" are considered internal to the data center and are automatically advertised and redistributed throughout the SD-WAN fabric to all other sites. Conversely, routes learned from an "Edge" peer, typically a service provider, are used for local routing decisions at that site (e.g., for internet or private WAN egress) and are not automatically redistributed to other sites in the overlay network.

A. This describes a common use case but not the core functional difference. The reason they are used this way is because of the underlying route redistribution behavior described in option B.
C. Both Core and Edge peer types support eBGP and iBGP. The choice between eBGP and iBGP is determined by the Autonomous System (AS) number configuration, not the peer type.
D. This is an inaccurate generalization. An Edge Peer can connect to either the internet or an MPLS provider, and a Core Peer is for the LAN side, not directly for internet connectivity.

1. Palo Alto Networks Prisma SD-WAN Administrator's Guide 6.2: In the section "Configure BGP," under "BGP Peers," the guide specifies the behavior of different peer types. It states: "Routes learned from a Core peer are automatically advertised to all other sites in the SD-WAN fabric." For Edge peers, it implies that routes are used locally and not automatically advertised. (Reference: Prisma SD-WAN Administrator's Guide, section on BGP configuration).

2. Palo Alto Networks Prisma SD-WAN Design and Operation (EDU-330) Student Guide: This courseware details SD-WAN architecture. In the module covering routing and data center integration, it explains that Core BGP peers are used to learn prefixes from the DC core that need to be advertised to remote branch sites. It contrasts this with Edge peers, whose learned routes (like a default route from an ISP) are kept local to the site. (Reference: EDU-330 Student Guide, Module on Advanced Routing with BGP).