The form factor of an NSX Manager virtual appliance (e.g., Small, Medium, Large, XL) is determined at the time of its deployment. This selection configures the appliance's vCPU, memory, and disk resources. According to official VMware documentation for both NSX and VMware Cloud Foundation (VCF), this configuration cannot be modified in-place after the appliance is running. To change the form factor, the existing appliance must be replaced by deploying a new one with the correct size specifications. Any direct modification through vCenter or an API would result in an unsupported configuration within the VCF-managed environment.

B. Each NSX manager must be resized using the API.

This is incorrect. There is no supported API endpoint in either VCF or NSX to perform an in-place resize of a deployed NSX Manager's form factor.

C. Each NSX manager must be resized through vCenter.

This is incorrect. Directly modifying the hardware of a VCF-managed component like an NSX Manager via vCenter is an unsupported action that causes configuration drift from the SDDC Manager's inventory.

D. Each NSX manager must be rightsized using VCF Operations.

This is incorrect. VMware Cloud Foundation lifecycle management, handled by the SDDC Manager, does not include a "rightsizing" workflow for changing the form factor of NSX Managers after deployment.

1. VMware NSX-T Data Center Installation Guide (3.2): In the "NSX Manager VM and Host Transport Node System Requirements" section, the documentation explicitly states, "You cannot change the appliance size after deployment. To change the size, you must redeploy the appliance." (Page 21). This principle applies to NSX appliances managed by VCF.

2. VMware Cloud Foundation 4.5 Administration Guide: This guide details the lifecycle management capabilities of the SDDC Manager. It describes procedures for deploying workload domains, adding resources, and performing upgrades, but it does not contain any procedure for resizing core management components like NSX Managers post-deployment, confirming this is not a standard VCF operation. The entire operational model of VCF is based on maintaining a consistent, declared state, which prohibits direct, out-of-band modifications. (See Chapter 4: "Managing Workload Domains").