143-085 · Question #101
You want to implement Traffic Isolation (TI) zones in your Gen 5 fabric. Which statement is true?
The correct answer is D. The TI zones can force low-priority traffic on to a given ISL. See the full explanation below for the reasoning.
Question
You want to implement Traffic Isolation (TI) zones in your Gen 5 fabric. Which statement is true?
Options
- AThe TI zones modify the route table.
- BThe TI zones modify the link cost for traffic on the path.
- CThe TI zones set the QoS traffic for the path.
- DThe TI zones can force low-priority traffic on to a given ISL.
How the community answered
(35 responses)- A6% (2)
- B3% (1)
- C9% (3)
- D83% (29)
Community Discussion
7
Samuel O.Jun 24, 2026D is your answer. TI zones let you steer specific traffic classes onto designated ISLs, so you can literally push low-priority flows off your high-priority paths and onto a separate link, which is the whole point of traffic isolation in a Gen 5 fabric.
Mei-Ling H.Jun 25, 2026D is right but watch the exam wording on "enforce" mode, because without that flag enabled a TI zone will still allow traffic to fall back to a non-designated ISL if the preferred link goes down, which means isolation is not guaranteed unless you specifically set enforce to active.
Mei-Ling H.Jun 27, 2026D is the right pick here, and the key word in that option is "force," which tells you TI zones are about constraining where traffic can travel, not about modifying costs or QoS markings or touching the route table at all. Can someone explain what specifically stops low-priority traffic from bleeding onto a high-priority ISL when TI zones are configured, is it enforced at the switch level per frame, or is there a zone membership check earlier in the path decision?
Lena V.Jun 27, 2026Leaned B, but TI zones steer traffic onto ISLs, not costs. D.
Orla P.Jun 16, 2026D is right, TI zones steer low-priority traffic onto designated ISLs without touching routing tables.
Goran A.Jun 17, 2026TI zones are about path isolation, not priority, so calling it "low-priority traffic steering" muddles the concept with QoS zoning, which is a separate feature entirely on Brocade fabrics.
Goran A.Jun 27, 2026I almost marked B on this one because I kept thinking about how FSPF link cost shapes paths and assumed TI zones must be doing something similar under the hood, but that is a different mechanism entirely. TI zones do not touch FSPF metrics or the route table at all, they operate on top of the existing topology by binding specific port members to dedicated ISL paths. The key insight that flipped me to D is that TI zones are explicitly designed to segregate traffic flows, so you can push your low-priority, high-bandwidth replication traffic onto a designated ISL and keep it from competing on the same trunk as your latency-sensitive host I/O. C tempted me for about two seconds because QoS also deals with traffic priority, but QoS zones handle bandwidth percentages and ingress rate limiting, not path assignment. Run a "zone --show" on your switch and look at the TI zone entries, you will see the ISL ports locked in there, and that physical path binding is the whole point.