Refer to the exhibit. An engineer must allow IP mobility between Site1 and Site2 in a Cisco ACI Multi- Site orchestrator. The design must meet these requirements: - A disaster recovery (DR) solution…

Defining a unique bridge domain subnet per site would prevent IP mobility between sites without re-IP, as each site would have its own distinct Layer 3 subnet, which contradicts the requirement for no re-IP.

Configuring STP between Cisco ACI fabrics is generally not recommended or supported for inter-fabric Layer 2 stretched links; ACI handles its own loop prevention within the fabric and relies on IP routing for inter-fabric communication or specific MAC address move handling for L2 stretch.

Deploying a local EPG for Site1 and Site2 is a standard way to define endpoints within each site, but it doesn't inherently provide the L2 stretching capability for IP mobility or address BUM traffic management between sites.

Disabling Inter-site BUM Traffic is essential to prevent broadcast storms across stretched Layer 2 networks in a Multi-Site deployment, which is a critical requirement for network stability. This ensures that unknown unicast, broadcast, and multicast traffic does not traverse the inter-site link unnecessarily, addressing the requirement to avoid broadcast storms.

Applying the L2 Stretch feature within Cisco ACI Multi-Site Orchestrator enables the extension of a Layer 2 network (Bridge Domain) across different ACI fabrics, allowing IP mobility between sites without having to re-IP application servers during a disaster recovery event and without requiring vMotion.