Free VMware 2V0-13.25 Actual Exam Questions - Question 1 Discussion
Foundation (VCF) environment with a management domain and multiple workload domains
deployed in two datacenters located in the same city.
During one of the initial workshops with stakeholders, the following information was identified:
The Recovery Time Objective (RTO) for workloads is 24 hours.
The management domain must remain continuously available with Recovery Point Objective (RPO)
of 0.
Hardware overhead should be minimized by utilizing standby resources that host test workloads
during normal operation.
Operational overhead should be minimized.
Latency between both datacenters is 2 ms.
Which design decision should the architect document to satisfy provided requirements?
It’s B. The stretched cluster handles zero RPO for management perfectly with that low latency, plus Live Recovery for workloads meets the 24-hour RTO without wasting hardware on standby resources.
B/D? The management domain needs zero RPO, so sync replication like in a stretched cluster makes sense. For workloads with 24-hour RTO, async replication could be enough and save resources. A and C seem less practical here.
B. The zero RPO for the management domain basically rules out async replication since that always risks some data loss. The vSAN stretched cluster keeps data in sync with minimal latency, fitting the 2 ms delay nicely, and Live Recovery for workloads balances resource use with the 24-hour RTO. Plus, this keeps operational overhead manageable by automating failover within the stretched cluster setup. Options A and C either don’t meet continuous availability or have too high an RTO, and D can’t fulfill zero RPO for management.
B/D? B fits the zero RPO need for management with a stretched cluster, while D covers async for workloads to save resources. A and C seem off for continuous availability needs.
Actually, option D can’t guarantee zero RPO for the management domain because asynchronous replication always risks some data loss. So it doesn’t fit their continuous availability need.
B The management domain needs zero RPO and continuous availability, which pretty much demands synchronous replication like a vSAN stretched cluster; async replication in D wouldn’t guarantee zero RPO for management.
I’m thinking option B deserves a closer look here too. The management domain needs zero RPO and continuous availability, which usually means synchronous replication—exactly what a vSAN stretched cluster provides. The 2 ms latency between datacenters seems low enough for this to work without major performance hits. Using Live Recovery for workload domains fits the 24-hour RTO and helps keep hardware overhead down by running test workloads on standby resources. But does the question confirm that the latency is stable enough for a stretched cluster, or could fluctuations make async replication sa
It’s D because asynchronous replication fits the 24-hour RTO for workloads and reduces hardware overhead by not requiring active standby for everything. Plus, it avoids the risk of latency spikes affecting management domain availability.
I’m going with B as well. The stretched cluster for the management domain fits the zero RPO need perfectly, and since latency is pretty low at 2 ms, synchronous replication should be stable. Plus, Live Recovery for workload domains handles the 24-hour RTO without needing full active-active. The other options seem off—A’s full redeploy feels risky for that RPO zero on management, and async replication in D won’t guarantee no data loss. C’s daily backups won’t meet the zero RPO or continuous availability required for management either.
It’s A because automating full redeployment keeps operational overhead low and uses test workloads on standby resources, matching the 24-hour RTO without needing costly constant replication.
I think option B fits best since it addresses zero RPO for management with a stretched cluster and uses Live Recovery for workloads to keep overhead low. The 2 ms latency supports synchronous replication well. B
Makes sense that the management domain needs zero RPO, so synchronous replication like in B fits best. Async in D wouldn't guarantee zero data loss for management. B is the solid choice here.
It’s D because the management domain requires zero RPO, meaning no data loss, which only synchronous or near-sync replication can guarantee. Since the latency is low but not zero, async replication still works for the workload domains with a 24-hour RTO. This approach avoids the heavier hardware demands of a stretched cluster, using standby resources efficiently for test workloads without constant active sync. So async replication balances minimal hardware overhead and the required RTO/RPO targets better than a fully stretched cluster setup.
B. The 2 ms latency supports a vSAN stretched cluster, which is crucial for zero RPO on the management domain. Live Recovery matches the 24-hour RTO and keeps overhead low for workload domains.
Probably B makes the most sense here since the 2 ms latency supports stretched clusters, which are needed for zero RPO on management. Live Recovery fits the 24-hour RTO for workloads and minimizes overhead.
Actually, D might not work since asynchronous replication can’t guarantee zero RPO for the management domain, which needs continuous availability without data loss. That rules out option D for the management part.
Maybe B fits since vSAN stretched clusters handle low latency well, but does the 2 ms delay definitely support a stretched cluster for the management domain here? Would be good to confirm that.