Q: 7
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 workload domains named WLD1 and WLD2.
• The workload domains share one NSX Local Manager deployment.
• A VCF Automation Region named region-1 exists that uses the shared NSX Local Manager
deployment.
When creating the second Region in VCF Automation, the administrator sees "No results" when
attempting to select a NSX Local Manager for the Region. What should the Administrator do to
resolve this issue?
Options
Discussion
B or possibly D, but I'm leaning B because VCF Automation Regions need their own dedicated NSX Local Manager. If region-1 already took the only instance, region-2 can't select it. HA mode (D) is just about availability, doesn't fix the assignment issue. Anyone see any recent VCF changes that allow sharing here?
I think D makes more sense here. NSX Manager in HA mode means more availability and maybe that's what's blocking the selection for the new region. The question threw me off mentioning "dedicated" but if region creation checks for HA it's easy to get tripped up. Let me know if that's off base.
B makes the most sense. Each Automation Region in VCF needs a dedicated NSX Local Manager instance, so you'd have to deploy a new workload domain with its own NSX for Region-2. That's what the official docs and practice tests point to, pretty sure but if someone saw differently in recent updates let me know.
Option B is the right move. Each Automation Region needs its own dedicated NSX Local Manager, so deploying a new workload domain with a separate NSX instance is required. D trips people up but HA mode doesn't affect the region assignment, just availability. Pretty sure that's correct but open to other thoughts.
D
D tbh. I saw a similar question on a practice test and it mentioned HA mode as a requirement for region selection limitations, so I was thinking ensuring NSX Manager is in HA could let you select it for another region. Maybe missing something but that's how I read it, agree?
B
Why does D keep coming up? Isn't HA mode just for resilience, not about assigning NSX Local Manager per region?
Maybe B, since separate NSX Local Manager needed per automation region. Not totally sure though. Anyone disagree?
D imo, since HA mode should help the NSX Manager scale. B is tempting but HA might be the catch here.
Be respectful. No spam.