nerdexam
Cisco

300-620 · Question #321

What is a characteristic of a Cisco ACI Multi-Pod?

The correct answer is A. It manages the configuration of different Cisco ACI pods using a single common Cisco APIC cluster.. Cisco ACI Multi-Pod allows for managing the configuration of multiple distinct ACI pods as a single logical fabric using a single, common Cisco APIC cluster.

Multi-Pod and Multi-Site

Question

What is a characteristic of a Cisco ACI Multi-Pod?

Options

  • AIt manages the configuration of different Cisco ACI pods using a single common Cisco APIC cluster.
  • BIt eliminates the need to deploy multicast in the Layer 3 network that interconnects the pods.
  • CA VPNv4 address family is used to exchange endpoint information between spines.
  • DSpines use BGP peering with IPN to send out the TEP pool prefix for the local pod.

How the community answered

(50 responses)
  • A
    86% (43)
  • B
    8% (4)
  • C
    2% (1)
  • D
    4% (2)

Why each option

Cisco ACI Multi-Pod allows for managing the configuration of multiple distinct ACI pods as a single logical fabric using a single, common Cisco APIC cluster.

AIt manages the configuration of different Cisco ACI pods using a single common Cisco APIC cluster.Correct

A fundamental characteristic of Cisco ACI Multi-Pod is its ability to manage several physically separated ACI pods as one cohesive logical fabric, all under the control and orchestration of a single, unified Cisco APIC cluster.

BIt eliminates the need to deploy multicast in the Layer 3 network that interconnects the pods.

Cisco ACI Multi-Pod deployments actually require multicast (PIM) within the Inter-Pod Network (IPN) to efficiently handle broadcast, unknown unicast, and multicast (BUM) traffic across pods.

CA VPNv4 address family is used to exchange endpoint information between spines.

While endpoint information exchange between spines in Multi-Pod uses MP-BGP with the EVPN address family, which relies on VPNv4 address families for L3 routes, stating 'VPNv4 address family' alone is less precise and not the primary defining characteristic of Multi-Pod compared to the single APIC cluster management.

DSpines use BGP peering with IPN to send out the TEP pool prefix for the local pod.

Spines typically use an Interior Gateway Protocol (IGP) like OSPF or ISIS to peer with the IPN to establish reachability for TEP pool prefixes, rather than BGP to send out the TEP pool prefix directly to the IPN.

Concept tested: ACI Multi-Pod architecture; APIC cluster management

Source: https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/5x/multi-pod/cisco-aci-multi-pod-config-guide-501.html#_Toc22956291

Topics

#ACI Multi-Pod#APIC cluster#fabric architecture

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice