You have proposed Aruba 8400 switches as core switches for a customer. The customer is very concerned about the network always being on and has indicated that no maintenance window is permitted even…

Question

Options

• ABackplane stacking
• BNetwork Analytics Engine (NAE)
• CVirtual Switching Extension (VSX)
• DArubaOS-CX Python-based APIs

• A
  3% (1)
• B
  8% (3)
• C
  76% (29)
• D
  13% (5)

Explanation

Virtual Switching Extension (VSX) is correct because it provides an active-active redundancy model pairing two Aruba 8400 switches so that when one undergoes a software upgrade, the other continues forwarding traffic - enabling hitless, zero-downtime upgrades with no maintenance window required. Backplane stacking (A) is a distractor because the 8400 is a chassis-based switch, not a stackable unit, and stacking doesn't inherently solve zero-downtime software upgrades. NAE (B) is a telemetry and analytics framework for monitoring network health via scripts - powerful for visibility, but irrelevant to upgrade continuity. Python-based APIs (D) enable programmable automation and configuration management, but automating an upgrade doesn't eliminate the downtime caused by one.

Memory tip: Think of VSX as "Virtual Switching eXtra-resilience" - two switches act as one logical unit, so you can upgrade one peer while the other holds the fort. If the customer says "always on, no downtime," your answer is VSX.

No community discussion yet for this question.