Depending on a switch's role in the topology, the demands on various tables differ. Several HPE Aruba CX switch models support different profiles, each of which optimizes the correct table for a…

Question

Options

• AL3 Aggregates profile allocates more space to the support more overlay host entries table
• BL3 Aggregates profile allocates more space to the routing table compared to L3 core profile
• CL3 Aggregates profile allocates more space to the ARP/ND table compared to L3 core profile
• DL3 Aggregates profile allocates more space to the routing table compared to Spine switch

• A
  4% (1)
• B
  4% (1)
• C
  85% (23)
• D
  7% (2)

Explanation

Option C is correct because L3 Aggregation switches sit between the access and core layers and connect directly to many end hosts and subnets - this means they must resolve a large volume of Layer 3-to-Layer 2 mappings, making a larger ARP/ND (Address Resolution Protocol / Neighbor Discovery) table the critical resource to optimize.

Option A is wrong because overlay host entries (used in EVPN/VXLAN environments) are a concern for spine or border-leaf roles handling tunnel endpoints, not L3 Aggregation switches focused on host reachability.

Option B is wrong because it's actually the L3 Core profile that requires a larger routing table - core switches peer with many upstream networks via BGP and carry a heavier routing information base than aggregation switches.

Option D is wrong because Spine switches in modern data center fabrics require very large routing tables to handle underlay/overlay prefixes across all leaf nodes, dwarfing the routing needs of an aggregation switch.

Memory tip: Think of the role each switch "faces" - Aggregation faces hosts (→ big ARP/ND table), Core faces routes (→ big routing table), Spine faces tunnels and prefixes (→ big routing + overlay tables). Match the table to what the switch "sees most of."

No community discussion yet for this question.