To ensure device redundancy in an HPE Campus Access network, which configurations should be applied?

Question

Options

• ALink Aggregation
• BActive-Active Failover
• CDHCP Snooping
• DVRRP

• A
  88% (29)
• B
  3% (1)
• C
  9% (3)

Explanation

Link Aggregation (A) and VRRP (D) together provide device redundancy at the link and gateway levels respectively. Link Aggregation (LAG/LACP) bonds multiple physical links into one logical connection, so if one link fails, traffic continues over the remaining links without interruption. VRRP (Virtual Router Redundancy Protocol) allows multiple routers/switches to share a virtual IP address, with one acting as master and another as backup - if the master fails, the backup automatically takes over, ensuring default gateway availability.

Why the distractors are wrong:

• B (Active-Active Failover) is a valid redundancy concept in general networking, but it is not a specific configuration protocol applied in HPE Campus Access designs for device redundancy - VRRP handles gateway failover in this context.
• C (DHCP Snooping) is a security feature that prevents rogue DHCP servers; it has nothing to do with device or link redundancy.

Memory tip: Think "LAG + VRRP = Link + Virtual Router" - one protects your physical connections, the other protects your gateway. Together they cover both layers of redundancy. If you see "device redundancy" in an HPE Campus question, think ports bundled (LAG) and routers backed up (VRRP).

No community discussion yet for this question.