An Administrator has been tasked with creating a new VMware Cloud Foundation (VCF) Automation Region named Region-2. The following information has been provided: - The current environment has two…

Question

Options

• AAdd an additional NSX Edge Cluster In WLD1.
• BDeploy a third workload domain that includes a new, dedicated NSX Local Manager deployment.
• CDeploy an additional vSphere cluster in WLD1.
• DEnsure that that the NSX Manager is deployed in HA mode.

• A
  9% (3)
• B
  73% (24)
• C
  15% (5)
• D
  3% (1)

Explanation

In VMware Cloud Foundation (VCF) Automation, each Automation Region must be associated with a dedicated NSX Local Manager. A single NSX Local Manager instance cannot be reused across multiple Automation Regions. In the provided scenario: The existing environment has WLD1 and WLD2, both sharing one NSX Local Manager. Region-1 in VCF Automation already consumes this shared NSX Local Manager. When creating Region-2, the interface shows "No results" when selecting an NSX Local This behavior matches documented VCF Automation constraints: an NSX Local Manager can only be mapped to a single Automation Region. Once it is consumed by one region, it is not available for any additional region. To create a second region (Region-2), a new NSX Local Manager instance must exist in the environment. The only supported method to obtain a new NSX Local Manager is to deploy a new workload domain, because NSX Local Manager is deployed as part of every VI Workload Thus, the administrator must deploy a new (third) workload domain, which includes its own NSX Local Manager package, allowing Region-2 to be created successfully.

No community discussion yet for this question.