Harborview is told that a future NSX Federation (Global Manager) might join the civic fabric, so all GUI work must stay Federation-ready. How should operators use the NSX GUI today?
Select an answer to reveal the explanation.
Short Explanation
If two city halls might share one playbook later, write that playbook in Policy. Global Manager does not speak Manager-mode objects. Host Client and Carbon Black are not Federation.
Full Explanation
Harborview is told a future NSX Federation (Global Manager) might join the civic fabric, so operators should stay in Policy mode for GUI configuration today because Global Manager supports only Policy mode—Federation-ready practice. Creating remaining objects in Manager mode so Global Manager can import Advanced objects is backwards; Manager-mode objects are the ones Federation will not manage. Using the ESXi Host Client as the Global Manager GUI is incorrect; Host Client is per-host administration. Building Federation objects in Carbon Black Cloud and syncing them to NSX confuses endpoint cloud with NSX Federation. Exam caveat: this item identifies GUI practice for Federation readiness; it does not design sites, stretched networks, or GM deployment topology. Operational check: inventory recent Harborview objects, confirm new GUI work is created in Policy mode, avoid new Manager-only objects where Policy equivalents exist, and note Federation readiness in the civic architecture decision record. In municipal operations, record the chosen control and the rejected alternatives in the change ticket so future on-call staff understand which failure modes would affect city services. Re-validate after the next maintenance window that the same GUI path and realized state still hold under the current NSX build used by the civic platform team.