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 5V0-31.23 Exam - Topic 3 Question 13 Discussion

Actual exam question for VMware's 5V0-31.23 exam
Question #: 13
Topic #: 3
[All 5V0-31.23 Questions]

A large research facility has implemented VMware Cloud Foundation (VCF) in their environment. For their R&D VI Workload Domain to host their Virtual Machines, they use DHCP for their NSX Host Overlay Network TEPs, a dedicated vSAN Storage Policy for the cluster, and vSphere Lifecycle Manager images. For better resiliency, the administrator wants to stretch the cluster.

What will stop the administrator from creating a stretched cluster?

Show Suggested Answer Hide Answer
Suggested Answer: D

In a VMware Cloud Foundation (VCF) environment, creating a stretched cluster requires specific configurations for the NSX Host Overlay Network Tunnel Endpoints (TEPs). For stretched clusters, static IP addresses are required for the TEPs to ensure stable, predictable network connectivity across sites. Since this cluster uses DHCP for the NSX Host Overlay Network TEPs, it does not meet the requirements for a stretched cluster configuration.


Contribute your Thoughts:

0/2000 characters
Sarah
2 months ago
I thought DHCP was the issue, but I guess not?
upvoted 0 times
...
Erick
2 months ago
Definitely, it's a limitation for sure!
upvoted 0 times
...
Oliva
3 months ago
The vSAN Storage Policy shouldn't block it either.
upvoted 0 times
...
Florencia
3 months ago
Surprised that Workload Management is the dealbreaker!
upvoted 0 times
...
Tamekia
3 months ago
Stretched clusters can't be enabled with Workload Management.
upvoted 0 times
...
Veronique
3 months ago
I vaguely remember that vSphere Lifecycle Manager images shouldn't prevent stretched clusters, but I could be mixing it up with another topic.
upvoted 0 times
...
Agustin
4 months ago
I practiced a question similar to this, and I feel like DHCP for NSX TEPs could be a concern, but I need to double-check that.
upvoted 0 times
...
Stevie
4 months ago
I think the dedicated vSAN Storage Policy might be a problem too, but I can't recall the specifics on how it affects stretched clusters.
upvoted 0 times
...
Misty
4 months ago
I remember something about Workload Management potentially causing issues with stretched clusters, but I'm not entirely sure if that's the main blocker here.
upvoted 0 times
...
Misty
4 months ago
I've got a good feeling about this one. The key is to identify which of the given configurations would prevent the administrator from creating a stretched cluster.
upvoted 0 times
...
Monte
4 months ago
Okay, let's see. The question mentions a few specific configurations, so I'll need to analyze how those might impact the ability to stretch the cluster.
upvoted 0 times
...
Paulina
5 months ago
Hmm, I'm a bit confused about the details here. I'll need to review the VCF documentation to understand the constraints around stretched clusters.
upvoted 0 times
...
Lauryn
5 months ago
This seems like a tricky question. I'll need to think through the VMware Cloud Foundation (VCF) requirements carefully.
upvoted 0 times
...
Keneth
10 months ago
Ah, the vSphere Lifecycle Manager images. It's like trying to stretch a rubber band that's already tangled up in a knot. Nope, not gonna work.
upvoted 0 times
Casie
9 months ago
C: It's like trying to untangle a knot, impossible.
upvoted 0 times
...
Bettina
9 months ago
B: Yeah, that's a roadblock for stretching the cluster.
upvoted 0 times
...
Thurman
10 months ago
A: The cluster uses vSphere Lifecycle Manager images.
upvoted 0 times
...
...
Florencia
10 months ago
Workload Management, really? That's like adding more plates to a juggling act. Let's keep it simple and go with B.
upvoted 0 times
Barrett
9 months ago
D) The cluster uses DHCP for the NSX Host Overlay Network TEPs.
upvoted 0 times
...
Regenia
9 months ago
B) The cluster uses dedicated vSAN Storage Policy.
upvoted 0 times
...
Marylyn
10 months ago
A) The cluster is enabled for Workload Management.
upvoted 0 times
...
Lashanda
10 months ago
B) The cluster uses dedicated vSAN Storage Policy.
upvoted 0 times
...
...
Stanford
10 months ago
D, for sure. DHCP for the NSX Host Overlay Network TEPs? That's like trying to herd cats across a minefield. Good luck with that, buddy.
upvoted 0 times
Glendora
10 months ago
Yeah, using DHCP for TEPs sounds like a disaster waiting to happen. Definitely not a good idea for a stretched cluster.
upvoted 0 times
...
Marguerita
10 months ago
D, for sure. DHCP for the NSX Host Overlay Network TEPs? That's like trying to herd cats across a minefield. Good luck with that, buddy.
upvoted 0 times
...
...
Frederic
11 months ago
Hmm, I'd say the dedicated vSAN Storage Policy is the culprit here. I mean, who stretches a cluster with vSAN? That's like trying to stretch a rubber band that's already at its limit.
upvoted 0 times
...
Laila
11 months ago
But what about option A, enabling Workload Management? Could that also be a reason for not creating a stretched cluster?
upvoted 0 times
...
Jacob
11 months ago
I agree with Layla. Using DHCP for the TEPs might cause issues with stretching the cluster.
upvoted 0 times
...
Layla
11 months ago
I think the administrator can't create a stretched cluster because of option D, using DHCP for the NSX Host Overlay Network TEPs.
upvoted 0 times
...

Save Cancel