In an application-centric design, the creation of additional EPGs under one bridge domain is possible. This allows for greater flexibility in managing and segmenting network traffic for different applications or services within the same bridge domain.

References  :=  Network Centric to ACI Centric Migration - Cisco

 In Cisco ACI, contracts define the policies for communication between EPGs (Endpoint Groups). For a client in WebClient EPG to establish an HTTP connection toward a server in WebServer EPG, the contract must allow the initiation of communication from WebClient to WebServer. Since HTTP uses port 80, the destination port (DST Port) should be set to 80 as per standard HTTP communications. The option “Apply Both Direction DISABLED” means that only the initiator of the connection (in this case, WebClient EPG) can send traffic unless specified otherwise by another contract or filter. The “Reverse Port Filter ENABLED” allows return traffic from WebServer EPG back to WebClient EPG on dynamically allocated source ports used by WebClient when initiating the connection. This combination ensures that clients can initiate an HTTP request and receive responses from servers.  References : = Implementing Cisco Application Centric Infrastructure Official Cert Guide

The Endpoint Group (EPG) scope is the correct choice to meet the requirements for the e-commerce software in a Cisco ACI fabric. By selecting the EPG scope, contracts can be reused within the same Virtual Routing and Forwarding (VRF) context, reducing the overall number of contracts. Additionally, it ensures that the e-commerce software communicates only with software EPGs that are part of the same Application Network Profile (ANP), while preventing communication with applications in different ANPs.  References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

Graphical user interface Description automatically generated

 In a scenario where an organization deploys active-active data centers with active-standby firewalls in each data center within a Cisco ACI Multi-Pod environment, maintaining traffic symmetry through firewalls is crucial for consistent security policy enforcement and avoiding asymmetric routing issues. Enabling Pod ID Aware Redirection allows for intelligent redirection of traffic based on pod identification numbers so that return traffic can be directed back through the same path it originated from, thus maintaining symmetry even in complex multi-pod deployments.  References : Implementing Cisco Application Centric Infrastructure Official Cert Guide

The protocol used for exchanging MAC/IP address information for endpoints between spine switches in different pods within a Cisco Multi-Pod solution is MP-BGPEVPN (Multiprotocol BGP Ethernet VPN). This protocol facilitates scalable communication between separate locations by allowing MAC/IP address information sharing across pods.  References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

Before associating a schema with a newly configured site in Cisco ACI Multi-Site Orchestrator, it’s essential to  configure a provider . This establishes a communication link between the orchestrator and the sites, enabling proper deployment and management of objects across multiple sites.

 For a Cisco ACI leaf switch to correctly learn the remote endpoint MAC, the VXLAN packet received from the Cisco ACI spine must include  bridge domain  information.  The bridge domain contains the Layer 2 forwarding context, which allows the leaf switch to learn and associate the MAC address with the correct bridge domain 3 .

References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

To limit IP address learning in BD1 when VM1 is incorrectly attached to a PortGroup, enabling the Enforce Subnet Check is the correct action. This feature ensures that only IP addresses belonging to the defined subnets under the bridge domain are learned, preventing incorrect IP data from being disseminated across the network.  References  := ( Implementing Cisco Application Centric Infrastructure Official Cert Guide )

 In a Cisco ACI Multi-Pod environment that is expanding, spine headend replication should be configured to ensure efficient forwarding of BUM (Broadcast, Unknown unicast, Multicast) traffic across the IPN (Inter-Pod Network). This configuration optimizes the control plane scaling and ensures that BUM traffic is handled effectively, maintaining network performance and stability.

References : Implementing Cisco Application Centric Infrastructure Official Cert Guide