Which three advantages does trunking provide when in Access Gateway mode? (Choose three.)

Samuel O.Jun 23, 2026

The answer is C, D, and E. When you trunk in Access Gateway mode, you are bonding multiple physical links into one logical pipe, and the three things that buys you are transparent failover, maximized utilization across all those links, and in-order delivery even when one link drops. I have seen shops lose sleep over out-of-order frames causing application errors during a link failure, and trunking specifically handles that sequencing problem so the fabric keeps frames orderly through the transition. A is a distractor because quick port ID reassignment is an NPIV behavior, not a trunking benefit, and B is just wrong territory entirely since HBA teaming is a host-side driver concept that has nothing to do with what the AG trunk is doing on the switch side. On the real hardware, trunking in AG mode is one of those features that looks optional until you hit a link flap at 2 AM and realize the fabric absorbed it without a single host seeing a logout.

Imani T.Jan 13, 2026

C, D, E are your correct picks. Trunking in Access Gateway mode keeps frames in order when a link drops (E), balances traffic across all links so you are not wasting bandwidth (D), and handles failover and fallback without the host ever knowing a link changed (C). A and B are throwaways, port ID reassignment and HBA teaming have nothing to do with what trunking actually delivers in AG mode.

Mateus R.Jan 8, 2026

C, D, E is right. Trunking keeps traffic balanced, keeps frames in order, and self-heals quietly.

Haruki E.Jun 26, 2026

C, D, and E are correct. The in-order delivery guarantee in E is the detail that trips people up, but it is critical because when a trunk link drops, the AG redistributes the N_Port traffic across remaining links without scrambling frame sequence, which keeps the fabric from throwing RSCN storms at the attached hosts.

Carlos M.Jun 26, 2026

I wasted time on A at first because AG mode is all about N_Port virtualization so reassigning port IDs when N_Ports drop sounded right, but that is not really a trunking feature, that is just normal AG behavior. Once I focused on what trunking itself actually does, C, D, and E clicked. Trunking in AG mode bundles multiple ISL links so load spreads across them for better utilization (D), and when one link drops the switch handles failover transparently without the host seeing an interruption (C) while also making sure frames do not arrive out of sequence after the failover (E). A and B are distractors, teaming is an HBA NIC concept and has nothing to do with FC trunking.

Orla P.Jun 26, 2026

The three they're looking for all center on what happens to traffic when links in the trunk are under stress or fail, so if you're second-guessing yourself, ask whether each option describes behavior that protects or balances live traffic versus something that's really just an HBA or port management feature unrelated to trunking itself. Can you explain why maintaining in-order delivery during a link failure matters more in an AG environment than it might in a standard fabric connection?

Viktor S.Jan 28, 2026

C, D, and E are the right three. The reason B tempts people is the word "Brocade HBAs" makes it sound like it fits the context, but teaming is a host-side bonding concept that has nothing to do with what the AG trunk is doing at the fabric edge. A is the sneaky one because N_Port reassignment sounds like something trunking would help with, but port IDs are not what trunking manages, it manages the physical links between the AG and the edge switch. The actual value of trunking in AG mode is that you get one logical pipe spread across multiple physical links, so when a link drops the other links absorb the traffic without the connected servers seeing a fabric disruption (C), the bandwidth of all links is used instead of leaving capacity idle (D), and because the trunk keeps frame ordering intact during the failover you avoid the upper-layer protocols going sideways over out-of-sequence delivery (E). If you understand that trunking is fundamentally about combining links while hiding individual link events from the rest of the fabric, C D and E fall out naturally and you never have to memorize a list.

Goran A.Feb 9, 2026

A is NPIV behavior, not trunking. Answer is C, D, E.