HPE2-W07 · Question #49
Which characteristic could make a Virtual Mobility Controller (VMC), as opposed to a hardware controller, a good solution for a customer?
The correct answer is A. need for flexibility in moves and changes. Option A is correct because a VMC runs as a software instance on a hypervisor, making it easy to scale, migrate, clone, or reconfigure without touching physical hardware - ideal for environments that frequently reorganize or expand their network. Why the distractors are wrong…
Question
Which characteristic could make a Virtual Mobility Controller (VMC), as opposed to a hardware controller, a good solution for a customer?
Options
- Aneed for flexibility in moves and changes
- Bdesire to remain on pre-8.0 ArubaOS code
- Cneed for highest throughput
- Dlittle communication between server and networking teams
How the community answered
(36 responses)- A72% (26)
- B6% (2)
- C6% (2)
- D17% (6)
Explanation
Option A is correct because a VMC runs as a software instance on a hypervisor, making it easy to scale, migrate, clone, or reconfigure without touching physical hardware - ideal for environments that frequently reorganize or expand their network.
Why the distractors are wrong:
- B is wrong because VMC requires ArubaOS 8.0 or later; customers wanting to stay on pre-8.0 code must use hardware controllers.
- C is wrong because hardware controllers use dedicated ASICs for packet processing, giving them higher raw throughput than a VMC sharing virtualized compute resources.
- D is wrong because VMCs run on hypervisor infrastructure, which increases the need for coordination between server and networking teams - the opposite of the scenario described.
Memory tip: Think "Virtual = Versatile." The main VMC advantage is agility - spin it up, move it, resize it - not raw power or legacy support.
Topics
Community Discussion
No community discussion yet for this question.