The scenario requires a Layer 3 Data Center Interconnect (DCI) because the IP spaces are unique and no Layer 2 bridging is needed. EVPN Type 5 routes (IP Prefix routes) are specifically designed for this purpose, advertising IP prefixes between data centers without requiring MAC address learning across the DCI. To exchange these Type 5 routes, the border leaf nodes (DCI gateways) in each data center must establish an EVPN peering session, typically over an eBGP session across the IP backbone. This allows for efficient and scalable L3 connectivity between the separate routing domains of the data centers.

A. Configure a Type 2 EVPN route for each unique prefix.

Incorrect. Type 2 routes are for MAC/IP advertisements and are used for Layer 2 extension, which is explicitly not required in this scenario.

D. Configure peering for EVPN between all leaf nodes within each data center.

Incorrect. This describes intra-data center peering for the fabric's underlay/overlay, not the inter-data center peering required for DCI.

1. Juniper Networks, "EVPN User Guide". Section: "EVPN-VXLAN DC Interconnect". This guide details DCI models, specifying that for L3-only interconnects, Type 5 routes are used to exchange IP prefixes between border leaf gateways.

2. Juniper Networks, "Technology Deep Dive: Seamless EVPN-VXLAN Data Center Interconnect" (White Paper, 2020). Section: "L3 DCI Gateway Models". This paper explains that Type 5 routes provide a clean and scalable method for extending L3 connectivity between data centers. It also illustrates the eBGP peering between DCI gateway devices.

3. RFC 7432, "BGP MPLS-Based Ethernet VPN". Section 9, "IP Prefix Advertisement". While the RFC covers MPLS, the principles of the EVPN route types are defined here. Type 5 is defined for advertising IP prefixes.