nerdexam
Cisco

300-620 · Question #179

A customer must deploy three Cisco ACI based data centers. Each site must be separated from the others. Which characteristic of Cisco ACI Multi-Pod makes it unsuitable for this deployment?

The correct answer is B. requires all pods to share the same Cisco APIC cluster. Cisco ACI Multi-Pod is unsuitable for deploying completely separated data centers because all pods within a Multi-Pod deployment must share a single APIC cluster.

Multi-Pod and Multi-Site

Question

A customer must deploy three Cisco ACI based data centers. Each site must be separated from the others. Which characteristic of Cisco ACI Multi-Pod makes it unsuitable for this deployment?

Options

  • Acreates a virtual pod in the remote location
  • Brequires all pods to share the same Cisco APIC cluster
  • Chas distance and scale limitations
  • Dplaces leaf switches in the remote site that belong to the same fabric as at the headquarters site

How the community answered

(38 responses)
  • A
    3% (1)
  • B
    87% (33)
  • C
    3% (1)
  • D
    8% (3)

Why each option

Cisco ACI Multi-Pod is unsuitable for deploying completely separated data centers because all pods within a Multi-Pod deployment must share a single APIC cluster.

Acreates a virtual pod in the remote location

Multi-Pod connects distinct physical pods, it does not create a 'virtual pod' in the remote location; this statement inaccurately describes Multi-Pod functionality.

Brequires all pods to share the same Cisco APIC clusterCorrect

Cisco ACI Multi-Pod unifies multiple geographically distributed pods under a single APIC cluster, creating one large logical fabric. If the requirement is for each data center to be entirely separated with its own independent management plane, Multi-Pod is unsuitable due to this shared APIC cluster characteristic.

Chas distance and scale limitations

While Multi-Pod does have distance and scale limitations, the primary reason it's unsuitable for 'separated' sites is the mandatory shared APIC cluster, which violates the separation requirement.

Dplaces leaf switches in the remote site that belong to the same fabric as at the headquarters site

Placing leaf switches in a remote site that belong to the same fabric as the headquarters site is a characteristic of Multi-Pod, not a reason for its unsuitability for separated data centers.

Concept tested: Cisco ACI Multi-Pod shared APIC cluster

Source: https://www.cisco.com/c/en/us/td/docs/dcn/aci/apic/6x/aci-multi-pod/cisco-aci-multi-pod-fabric-with-remote-leaf-deployment-guide-60x/multi-pod-introduction.html

Topics

#Multi-Pod#Multi-Site#APIC cluster#data center separation#architecture comparison

Community Discussion

No community discussion yet for this question.

Full 300-620 Practice