1Y0-350 · Question #101
Scenario: A NetScaler appliance currently has a manually configured channel containing four interfaces; however, the engineer has been told that the NetScaler must now only use a single interface…
The correct answer is B. Disable the unused interfaces. See the full explanation below for the reasoning.
Question
Scenario: A NetScaler appliance currently has a manually configured channel containing four interfaces; however, the engineer has been told that the NetScaler must now only use a single interface for this network. The engineer removes the channel and immediately notices a decrease in network performance. How could the engineer resolve this issue?
Options
- AReset the unused interfaces
- BDisable the unused interfaces
- CEnable flow control on all interfaces
- DDisable HA monitoring on the three interfaces that are no longer required
How the community answered
(65 responses)- A9% (6)
- B85% (55)
- C5% (3)
- D2% (1)
Community Discussion
6
Isolde G.May 20, 2026The answer is B, disable the unused interfaces. When the channel is removed, those three formerly bundled interfaces do not disappear from the NetScaler's perspective, they remain enabled and the appliance still has to process traffic and state across them, which introduces overhead and can cause MAC flapping or duplicate-frame issues at the switch layer. Disabling the interfaces you no longer need tells both the NetScaler and the connected switch fabric that those ports are out of play, so all forwarding decisions cleanly collapse onto the single active interface. Resetting the interfaces (A) still leaves them up, flow control (C) addresses congestion signaling rather than the root cause, and disabling HA monitoring (D) only affects failover heartbeat detection, none of which touch the forwarding overhead created by three live but orphaned interfaces.
Prof. SaraApr 16, 2026B is correct. When a channel is removed, the three formerly bundled interfaces remain enabled and active, creating unnecessary overhead as the NetScaler continues processing traffic and signals on those idle links, so disabling them eliminates that drag and restores normal throughput on the single production interface.
Orla P.Apr 28, 2026The wording "immediately notices a decrease" is doing a lot of heavy lifting here, because what's actually happening is the three now-unused interfaces are still active and pulling traffic, so the fix is B, disable the unused interfaces. D is the trap if you conflate HA monitoring with traffic flow, but monitoring state has nothing to do with bandwidth saturation on idle links.
Giovanna H.May 10, 2026Saw this verbatim on my CCA-V sit, picked B instantly, idle interfaces left up will bleed your throughput.
Anjali D.Mar 31, 2026Okay so our group went back and forth on this one but I keep landing on A, resetting the unused interfaces, because when you tear down a channel the individual interfaces can retain stale configuration state from the bonding setup, and that leftover state is what drags performance down until you reset and let them reinitialize cleanly. Has anyone seen a lab scenario where that did not hold up, because I want to make sure we are not missing something before the exam?
Isolde G.Apr 2, 2026Anjali, good reasoning on the state concern but B is the right call here, because when the port channel interface is deleted the member interfaces are automatically released and their individual configurations are restored by the protocol, so there is no leftover bond state to manually clear out.