2V0-16.25 · Question #48
Which two configurations must be considered when scaling an NSX Edge Cluster in VMware Cloud Foundation?
The correct answer is B. Verify the BGP configuration for route propagation C. Add or remove edge transport nodes. Scaling an NSX Edge Cluster requires adding or removing edge transport nodes (C) to adjust capacity, and verifying BGP configuration (B) because edge nodes participate in dynamic routing - adding or removing nodes changes the routing topology, which can disrupt route…
Question
Which two configurations must be considered when scaling an NSX Edge Cluster in VMware Cloud Foundation?
Options
- AEnsure that the vCenter Server is set to HA mode
- BVerify the BGP configuration for route propagation
- CAdd or remove edge transport nodes
- DEnsure that storage policies are properly assigned
How the community answered
(64 responses)- A8% (5)
- B77% (49)
- D16% (10)
Explanation
Scaling an NSX Edge Cluster requires adding or removing edge transport nodes (C) to adjust capacity, and verifying BGP configuration (B) because edge nodes participate in dynamic routing - adding or removing nodes changes the routing topology, which can disrupt route propagation if BGP peers and route reflectors aren't reconfigured accordingly. These two are tightly coupled: you can't just scale the cluster without accounting for how traffic is advertised externally.
A is wrong because vCenter HA mode governs vCenter's own availability, not NSX Edge Cluster scaling - it has no bearing on edge node capacity or routing. D is wrong because storage policies apply to VM workloads, not to NSX Edge transport nodes, which are network-function components, not storage consumers.
Memory tip: Think "scale = nodes + routes" - whenever you resize the cluster (nodes), you must re-examine how routes flow (BGP). The other two options belong to different domains: compute HA (vCenter) and storage (policies).
Topics
Community Discussion
No community discussion yet for this question.