An administrator is tasked with enabling a Supervisor in a VMware vSphere Foundation (VVF) environment using vSphere networking and the Foundation Load Balancer. The vSAN-backed cluster has been…

Question

Options

• ASelect a vSphere namespace template to define initial namespace limits.
• BProvide a static IP address range for the Supervisor control plane VMs.
• CConfigure a Tier-0 Gateway with BGP or static routing.
• DEnable the VM Service before deploying the Supervisor.
• EAssign a vSphere Distributed Switch and a corresponding port group.

• A
  6% (1)
• B
  72% (13)
• C
  6% (1)
• D
  17% (3)

Explanation

When enabling a Supervisor with vSphere networking, the wizard requires two foundational inputs: the network assignment and the IP addressing. Option E is required because you must select a vSphere Distributed Switch and a port group to provide the network fabric for Supervisor communication - since the cluster already has a VDS, you designate it here. Option B is required because the Supervisor control plane runs as three dedicated VMs, and static IP addresses must be explicitly provided for them during enablement; there is no DHCP fallback for this role.

Why the distractors are wrong:

• A - Namespace templates are applied after the Supervisor is enabled, when provisioning namespaces, not during Supervisor setup.
• C - A Tier-0 Gateway with BGP/static routing is an NSX networking requirement. The question explicitly specifies vSphere networking with the Foundation Load Balancer, making this irrelevant.
• D - VM Service is configured post-enablement; it does not need to be enabled as a prerequisite for deploying the Supervisor.

Memory tip: Key on the phrase "vSphere networking" - if you see it, think "Switch + Static IPs" (E + B). Anything involving Tier-0 Gateways or BGP immediately signals NSX networking, which is a different deployment path entirely.

No community discussion yet for this question.