A. This plan will also cause a total network outage, as it still requires LAC
B. This will cause MAC address flapping on the physical switch ports.
C. This provides no automatic failover; if Uplink 2 fails, the VM assigned to it will lose connectivity.
D. This manually balances the load but does not provide *automatic* load balancing if traffic patterns change.
Explanation:
- D. Correct. This plan manually balances the load by forcing specific VMs onto specific uplinks. This will likely resolve the *current* saturation issue. However, it is a static configuration. If the VMs' traffic patterns change (e.g., the VM on Uplink 1 becomes busy and the VM on Uplink 2 goes idle), the saturation problem can return. It does not provide dynamic load balancing.
- A. Incorrect. This plan works perfectly with independent switch ports. Overriding the policy at the port group level to set Active/Standby uplinks is a standard, supported configuration that does not require LACP.
- B. Incorrect. Because each VM is pinned to a single port, there will be no MAC flapping.
- C. Incorrect. The plan *does* provide failover. By setting Uplink 1 as "Standby" for the VM on Uplink 2, ESXi will automatically move the VM to Uplink 1 if Uplink 2 fails.
Knowledge Point: Troubleshoot HPE Server Solutions
Associated Topics (Primary): Given a defined issue and action plan, explain the effects and results of the proposed actions
Question_Type: SingleChoice
Keywords: action plan | vSwitch | load balancing | failover | manual balancing
Persona: Network Administrator
Persona_Modifier: troubleshooting a critical performance issue
Target_Component: HPE FlexibleLOM
Data_Format_Used: Scenario-TextDescription
Assessment_Focus: ScenarioAnalysis-SolutionDesign
