An administrator has been tasked with expanding an existing VMware Cloud Foundation (VCF) workload domain by adding a new cluster. The VCF fleet has the following configuration: - Three workload…

Question

Options

• AUse the SDDC Manager UI to create the cluster in WLD-02.
• BUse the SDDC Manager API to create the cluster in WLD-03.
• CUse the vSphere Client UI to create the cluster in WLD-03.
• DUse the VCF Operations Fleet Manager UI to create the cluster in WLD-02.

• A
  3% (1)
• B
  13% (4)
• C
  3% (1)
• D
  81% (26)

Explanation

VMware Cloud Foundation 9.0 introduces a major architectural redesign that replaces the traditional SDDC Manager璫entric domain management model with a unified Fleet Management architecture implemented through VCF Operations Fleet Manager. In this model, each Workload Domain operates with its own vCenter, but Enhanced Linked Mode (ELM) is removed to improve isolation, reduce blast radius, and support multi-site scalability. As a result, administrators logged into the vSphere Client of the Management Domain can no longer manage or expand clusters in other Workload Domains, which explains why the vSphere UI blocks the attempted expansion of Fleet Manager becomes the new authoritative control plane for lifecycle, topology, host commissioning, and workload domain expansion. Only Fleet Manager maintains the full global view necessary to orchestrate cluster addition operations across distributed vCenters and domains. Because WLD-02 is running VCF 9.0 and is fully fleet-aware, its expansion must occur through VCF Operations Fleet Manager, not through the vSphere Client or legacy SDDC Manager workflows.

No community discussion yet for this question.