Q: 3
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?
Options
Discussion
Annoying how VMware makes this dependent on the Tier-0 mode. A tbh.
Would it still be A if the workload network didn't require NAT at all?
Its A. The active/active Tier-0 is the usual trap here, VPC needs active/standby. Seen a similar gotcha in a practice exam.
Nah, it isn't D here. Trap is thinking "default VPC" but it's really about the Tier-0 mode, so A.
A , had something like this in a mock. VPC profiles won't show if your Tier-0 is active/active-you need active/standby for stateful services like NAT. Pretty sure that's the catch here, but open to other takes.
A tbh. The active/active T0 setup is a classic trap for this, VPC profiles don't show unless it's active/standby.
Be respectful. No spam.
