VMware 2V0-15.25 Exam - Topic 3 Question 2 Discussion

In VMware Cloud Foundation, deletion of a workload domain requires that VCF Operations can correctly discover and process the NSX components attached to that domain. The workload domain delete workflow explicitly includes removal of the NSX Manager and NSX Edge components associated with the domain, unless those NSX components are shared.

In earlier and current VCF guidance, VMware state that NSX Edge clusters for a workload domain must be removed using the documented/VCF-aware method (for example, using the NSX Edge removal process referenced in KB 78635, not by deleting objects directly in NSX Manager). If an administrator deletes the NSX Edge cluster directly in NSX Manager, the VCF inventory and orchestration logic still ''believes'' the Edge cluster exists. When the workload domain delete workflow reaches the stage ''Gather input for deletion of NSX component'', it queries NSX / internal state for Edge cluster data. Because the underlying object has been manually removed, the returned structure is null, which results in an internal ''Cannot read the array length because '<locall9>' is null'' style error.

Using the NSX Edge Cluster Deployment Removal Tool as per documentation keeps VCF and NSX in sync and is the supported path, so option A is not the likely cause. Network pools and shared NSX Manager configurations do not match the specific NSX-component array/null condition described.