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-15.25 Exam - Topic 5 Question 6 Discussion

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

An administrator is attempting to activate a new vSphere Supervisor for use with VMware Cloud Foundation (VCF) Automation on a newly deployed cluster. In the VMware vSphere client, when going through the vSphere Supervisor activation having selected VCF Networking with VPC, the Virtual Private Cloud (VPC) Connectivity Profile dropdown is empty on the workload network page. The administrator verified that a Virtual Private Cloud (VPC) Connectivity Profile exists in NSX.

What is the cause of the issue?

Show Suggested Answer Hide Answer
Suggested Answer: C

When activating a vSphere Supervisor using VCF Networking with VPC, the Supervisor Workload Network must use a VPC Connectivity Profile. These profiles are scoped to an NSX Project, and cannot be consumed from the Default Project.

VCF Automation requires that:

A custom NSX Project be used for VPC networking integrations.

The Default Project cannot host Connectivity Profiles or VPC constructs intended for Supervisor activation.

Even though the administrator verified that a VPC Connectivity Profile exists in NSX, the Supervisor wizard will not display it if:

The VPC Connectivity Profile belongs to a different project, or

The current selection is the Default Project, which blocks visibility.

This exact behavior---empty VPC Connectivity Profile dropdown---is documented when attempting Supervisor activation under the Default NSX Project.

Option A (T0 active/active) affects North-South routing but does not hide VPC profiles. Option B (Supervisor HA mode) does not impact network profile selection. Option D (missing default VPC) is incorrect because the wizard is complaining about availability of Connectivity Profiles, not VPC instances.


Contribute your Thoughts:

0/2000 characters
Nikita
3 days ago
I bet the administrator forgot to pay the VPC subscription fee. That's why it's not working.
upvoted 0 times
...
Leah
8 days ago
The default VPC is probably on vacation. That's why it's not showing up.
upvoted 0 times
...
Stacey
13 days ago
C) The selected NSX Project is the Default Project.
upvoted 0 times
...
Von
19 days ago
D) The default VPC has not been created.
upvoted 0 times
...
Markus
24 days ago
I’m leaning towards option D, but I’m not completely confident. I know the default VPC is crucial for connectivity, but I need to double-check that.
upvoted 0 times
...
Crista
29 days ago
I feel like the active/active mode of the TO gateway might be relevant here, but I can't recall the specifics on how that affects VPC profiles.
upvoted 0 times
...
Tambra
1 month ago
I think I encountered a similar question in practice, and it was related to the NSX Project settings. Could the Default Project be causing the issue?
upvoted 0 times
...
Chauncey
1 month ago
I remember something about VPC profiles needing to be properly configured in NSX, but I'm not sure if the default VPC has to be created first.
upvoted 0 times
...
Natalie
1 month ago
This question is testing our understanding of VMware Cloud Foundation and NSX networking. I'm fairly confident that the correct answer is option D - the default VPC has not been created. The question states that a VPC Connectivity Profile exists in NSX, so the issue must be with the VPC itself. I'll make sure to review my notes on VCF and NSX to solidify my understanding before the exam.
upvoted 0 times
...
Julie
2 months ago
Okay, I think I've got this. The issue is likely that the default VPC hasn't been created, which is preventing the vSphere Supervisor from being able to select a VPC Connectivity Profile. I'd make sure to carefully read through the question and verify the NSX configuration before selecting an answer. Knowing the VMware Cloud Foundation and NSX concepts is going to be really important for this type of question.
upvoted 0 times
...
Tegan
2 months ago
Hmm, this seems like a tricky one. The key information seems to be that the VPC Connectivity Profile dropdown is empty, even though a VPC Connectivity Profile exists in NSX. My guess is that the default VPC hasn't been created, so option D is probably the right answer. I'll make sure to double-check the NSX configuration if I see a question like this on the exam.
upvoted 0 times
...
Lang
2 months ago
I'm a bit confused by this question. I'm not sure what the vSphere Supervisor or VCF Automation are, and the networking terminology is a bit unfamiliar to me. I'll need to review my notes on VMware Cloud Foundation and NSX to try to understand the context better.
upvoted 0 times
...

Save Cancel