2V0-13.24 · Question #89
An architect is designing a new VCF solution to meet the following requirements: - The solution must be deployed across two availability zones. - The physical hosts must be installed in a single…
The correct answer is D. A single NSX Overlay Transport Zone for all clusters to carry the traffic between the ESXi hosts. The VCF 5.2 design uses a Single Instance - Multiple Availability Zones topology (e.g., stretched cluster), requiring centralized management across two AZs, hosts in one rack per AZ, and workload mobility across AZs. The logical design focuses on high-level networking…
Question
An architect is designing a new VCF solution to meet the following requirements:
- The solution must be deployed across two availability zones.
- The physical hosts must be installed in a single rack per
availability zone.
- Workloads running in the cluster must be able to run on hosts in
either availability zone. The architect has decided that to meet these requirements, the solution will be deployed using the Single Instance - Multiple Availability Zones VCF Topology. When considering the design for the network, what should the architect include in the logical design to meet these requirements?
Options
- AA physical network fabric in a leaf-spine configuration with dual Cisco switches within each
- BA highly available gateway that supports the failure of an entire availability zone.
- CA 25-GbE port on each Top of Rack (ToR) switch connected to the ESXi host uplinks.
- DA single NSX Overlay Transport Zone for all clusters to carry the traffic between the ESXi hosts.
How the community answered
(54 responses)- A6% (3)
- B17% (9)
- C7% (4)
- D70% (38)
Explanation
The VCF 5.2 design uses a Single Instance - Multiple Availability Zones topology (e.g., stretched cluster), requiring centralized management across two AZs, hosts in one rack per AZ, and workload mobility across AZs. The logical design focuses on high-level networking architecture, not physical details. Let's evaluate: Option A: A physical network fabric in a leaf-spine configuration with dual Cisco switches within each availability zone A leaf-spine fabric enhances physical network scalability and redundancy, aligning with rack- based deployments. However, it's a physical design detail (switch topology), not a logical networking decision, per the VCF 5.2 Design Guide. Option B: A highly available gateway that supports the failure of an entire availability zone A gateway (e.g., NSX Edge Tier-0) with AZ failover supports North-South traffic resilience. While valuable, it doesn't directly enable workload mobility across AZs (East-West traffic), which is the core requirement. The VCF 5.2 Networking Guide treats gateways as supplementary, not foundational for stretched clusters. Option C: A 25-GbE port on each Top of Rack (ToR) switch connected to the ESXi host uplinks Specifying 25-GbE ports is a physical network detail (bandwidth, cabling), not a logical design element. The VCF 5.2 Design Guide relegates port speeds to physical implementation, not logical Option D: A single NSX Overlay Transport Zone for all clusters to carry the traffic between the In a stretched cluster topology, a single NSX Overlay Transport Zone enables VM mobility across AZs via overlay networks (e.g., Geneve). It ensures workloads can run on hosts in either AZ by providing a unified L2/L3 connectivity layer, managed by NSX. The VCF 5.2 Architectural Guide mandates a single Overlay TZ for stretched deployments to support vMotion and workload distribution, directly meeting the requirement.
Topics
Community Discussion
No community discussion yet for this question.