Which three statements are true about Transport Zone? (Choose three.)

Carlos M.Jun 27, 2026

B, D, and E are your three. A transport zone controls which hosts a logical switch can reach and spans one or more vSphere clusters (B), it extends across one or more ESXi clusters and defines the logical switch span (D), and it does not dictate which clusters or VMs are in a specific network, it just sets the boundary of reachability (E). A is wrong because transport zones do not define VTEP members, and C is mixing up the definition with something closer to a cluster or fabric concept.

Nina C.Mar 5, 2026

The answers are B, D, and E because a Transport Zone controls which hosts a logical switch can reach and spans one or more clusters (B and D), and importantly it defines the potential reach of a logical switch but does not force every cluster or VM within those clusters to participate in a specific network (E). A is wrong because VTEPs are a function of the host preparation process, not what a Transport Zone defines, and C reads more like a description of a cluster than a Transport Zone.

Grace U.Mar 4, 2026

B, D, and E are solid picks here. A transport zone really is about defining the reach of a logical switch across clusters, not about dictating which VMs end up on which network, and that distinction between scope and membership is exactly the kind of nuance the exam likes to test.

Ivana K.Jun 27, 2026

B, D, and E are right, though E always trips people up because it sounds like a limitation when it is really just scope clarification. The transport zone does not dictate cluster membership at the VM level, it defines reachability for logical switches, so A is the trap here since VTEPs are a consequence of transport zone membership, not what the transport zone itself defines.

Orla P.Jun 27, 2026

B, D, and E are the ones to lock in here. The transport zone is a boundary object, it defines the reach of a logical switch across one or more clusters, but it does not mandate which specific clusters or VMs inside those clusters end up on a given network, that is left to the logical switch configuration itself. A trips people up because VTEPs live on the hosts, not inside the transport zone definition, and C is describing something more like a cluster or a plain vSphere construct, not a transport zone at all. Sat for the 1V0-642 at a Pearson Vue center last fall and this exact three-pick showed up. I flagged it and moved on, came back at the end, and the thing that cleared it for me was remembering that the transport zone is a container of scope, not a container of assignment. Once I framed it that way, E stopped looking like a trick and started looking obvious, because of course it does not dictate VM membership, that would make it something else entirely.

Johan G.Jun 26, 2026

Sat this one in 2019 and immediately crossed out A because VTEPs are a consequence of the transport zone membership, not the definition itself, and C reads like someone describing a vSphere cluster, not an NSX construct. B, D, and E clicked fast once I reminded myself that the transport zone is purely a scope definition, it tells you which hosts can participate in a given logical switch span, but it says nothing about which VMs inside those clusters are actually connected to anything.

Brenda K.Feb 26, 2026

A has to be in the answer set, the VTEP member definition is textbook Transport Zone language and I circled it on first pass before I even read the other options. Clock says commit to it and move on, do not let this one eat your time.

Kavya H.Mar 4, 2026

I am going with A, B, and D on this one and I feel pretty solid about it. The VTEP angle in A is what keeps tripping people up but if you think about it from a practical standpoint, the transport zone is literally what determines which hosts participate in that overlay fabric, and VTEPs live on those hosts, so A makes complete sense as a true statement. B and D are basically saying the same thing from two different angles, which is common on VMware exams, and both match exactly what you see when you go into NSX Manager and configure a transport zone spanning multiple clusters. C is the one I keep second-guessing myself on because it sounds like it is describing a cluster or a vSphere construct more than a transport zone itself, and E is just worded in a way that contradicts the whole point of a transport zone since the entire job of a transport zone is to dictate scope. Stick with A, B, D and move on.