New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware 2V0-13.25 Exam - Topic 4 Question 5 Discussion

Actual exam question for VMware's 2V0-13.25 exam
Question #: 5
Topic #: 4
[All 2V0-13.25 Questions]

An architect is designing a Business Continuity Disaster Recovery (BCDR) strategy for a Virtual Cloud 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?

Show Suggested Answer Hide Answer
Suggested Answer: B

To ensure zero RPO and high availability for the management domain, the best-fit design is to use a vSAN Stretched Cluster. With a 2ms latency and shared witness site, this design enables synchronous replication and automatic failover, ensuring no data loss (RPO 0) and minimal downtime.

For the workload domains where 24-hour RTO is acceptable, Live Recovery (leveraging replication and automation like Site Recovery Manager or Aria Automation Orchestrator) can be used to minimize operational effort and still meet recovery timelines. This strategy also aligns with minimizing hardware overhead by using the standby test infrastructure as failover capacity.


VMware Cloud Foundation Multisite Design Guide -- Stretched Clusters and Disaster Recovery

VMware vSAN Stretched Cluster Architecture Design

Contribute your Thoughts:

0/2000 characters
Dorsey
11 days ago
Option D could lead to data loss. Asynchronous replication isn't ideal here.
upvoted 0 times
...
An
16 days ago
I feel like option C won't meet the RTO requirement effectively.
upvoted 0 times
...
Andree
22 days ago
Option A seems risky. Redeploying the entire environment takes time.
upvoted 0 times
...
Josefa
27 days ago
I think option B is the best choice. vSAN stretched cluster ensures high availability.
upvoted 0 times
...
Daren
1 month ago
Asynchronous replication might not cut it for the management domain's RPO of 0.
upvoted 0 times
...
Maryann
1 month ago
2 ms latency? Really? That seems too good to be true.
upvoted 0 times
...
Dorothy
1 month ago
Daily backups? That won't meet the 24-hour RTO.
upvoted 0 times
...
Nell
2 months ago
I agree, vSAN stretched cluster is the way to go!
upvoted 0 times
...
Rebecka
2 months ago
Option B sounds solid for keeping the management domain up.
upvoted 0 times
...
Tamar
2 months ago
I recall that asynchronous replication could introduce latency issues, so I’m hesitant about option D for the management domain, especially with its strict RPO.
upvoted 0 times
...
Lashaunda
2 months ago
I practiced a similar question where we had to balance RTO and RPO, and I think using backups like in option C could work, but it might not meet the 24-hour RTO.
upvoted 0 times
...
Laine
2 months ago
I'm not entirely sure, but I feel like option B with the vSAN stretched cluster might be the best fit since it addresses the continuous availability requirement.
upvoted 0 times
...
Yuki
2 months ago
I remember discussing RTO and RPO in class, and I think the management domain's RPO of 0 means it needs to be highly available.
upvoted 0 times
...
Val
3 months ago
Agreed! The RPO of 0 for the management domain is crucial.
upvoted 0 times
...
Ivan
3 months ago
Option C is a good backup plan, but it won't help with the continuous availability requirement for the management domain.
upvoted 0 times
...
Raymon
4 months ago
Haha, Option A is like starting over from scratch every time there's an issue. Not very efficient!
upvoted 0 times
...
Tina
4 months ago
Option D is too risky with the 24-hour RTO requirement. Asynchronous replication may not be fast enough.
upvoted 0 times
...
Lawana
4 months ago
I agree, the stretched cluster and Live Recovery approach looks like the best fit here.
upvoted 0 times
...
Brent
4 months ago
Option B seems like the most comprehensive solution to meet the given requirements.
upvoted 0 times
...
Ronny
5 months ago
This is a tricky one. I'm not super familiar with VCF, but from the details provided, it sounds like we need a highly available and resilient solution. The low latency between datacenters opens up some interesting options. I'm leaning towards option D, as the async replication could give us the flexibility we need to meet the RTO and RPO requirements.
upvoted 0 times
...
Desirae
5 months ago
Okay, I think I've got a handle on this. The management domain needs zero RPO, so that rules out option C. And since the latency is low, a stretched cluster for the management domain seems like the way to go, along with async replication for the workloads. That should satisfy the RTO and minimize overhead. I'll go with option B.
upvoted 0 times
...
Quentin
5 months ago
Hmm, I'm a bit confused by the latency requirement. Does that mean we need to keep the datacenters in the same city? And what exactly is a "VCF environment" - is that like a VMware thing? I'll need to brush up on my cloud infrastructure knowledge for this one.
upvoted 0 times
...
Margurite
5 months ago
This looks like a pretty straightforward BCDR question. I'd probably start by focusing on the key requirements - continuous availability for the management domain, 24-hour RTO for workloads, and minimizing hardware/operational overhead.
upvoted 0 times
Joye
3 months ago
Agreed! vSAN stretched cluster sounds perfect for that.
upvoted 0 times
...
Mohammad
3 months ago
I think option B is the best choice. Continuous availability is crucial.
upvoted 0 times
...
Princess
3 months ago
Backups are good, but they don't ensure continuous availability like option B.
upvoted 0 times
...
...

Save Cancel