2V0-13.25 · Question #85
An architect is expanding an existing private cloud infrastructure based on VMware Cloud Foundation (VCF). the requirement is to deploy two additional instances of VCF at two separate datacenters…
The correct answer is B. Deploy an additional VCF fleet in datacenter B and an additional VCF instance within the existing. According to the VMware Cloud Foundation 9.0.1 Network Latency and Fleet Expansion Guidelines, the maximum supported latency between VCF instances in a fleet is 100ms round-trip (refer to VCF- NET-REQD-LAT-006). Any latency exceeding this threshold can impact VCF Operations…
Question
An architect is expanding an existing private cloud infrastructure based on VMware Cloud Foundation (VCF). the requirement is to deploy two additional instances of VCF at two separate datacenters within the existing private cloud with minimal additional footprint.
- Datacenter A is 90 miles from the existing VCF fleet instance with a
network round trip time of 90ms.
- Datacenter B is 120 miles from the existing VCF fleet instance with a
network round trip time of 120ms. Which design decision would meet the requirement for this expansion?
Options
- ADeploy two additional VCF instances within the existing VCF fleet, one each in datacenters A and
- BDeploy an additional VCF fleet in datacenter B and an additional VCF instance within the existing
- CDeploy two additional VCF fleets, one for each VCF instance in datacenters A and B.
- DDeploy an additional VCF fleet in datacenter A and an additional VCF instance within the existing
How the community answered
(39 responses)- A23% (9)
- B59% (23)
- C13% (5)
- D5% (2)
Explanation
According to the VMware Cloud Foundation 9.0.1 Network Latency and Fleet Expansion Guidelines, the maximum supported latency between VCF instances in a fleet is 100ms round-trip (refer to VCF- NET-REQD-LAT-006). Any latency exceeding this threshold can impact VCF Operations synchronization, NSX Federation communication, and lifecycle management tasks. In this scenario, Datacenter A (90ms RTT) is within the 100ms limit, whereas Datacenter B (120ms RTT) exceeds it. Therefore, Datacenter A can host a new VCF instance within the existing VCF fleet, maintaining fleet-level manageability and minimal footprint. Datacenter B, on the other hand, requires a separate VCF fleet due to latency exceeding the supported limit. This design ensures operational continuity while minimizing hardware footprint by using a hybrid deployment strategy - a fleet instance in Datacenter A and a standalone fleet in Datacenter B.
Topics
Community Discussion
No community discussion yet for this question.