Transit applies a transport-node profile to the ESXi clusters that will host fare-system VMs, but no IP pools exist for tunnel endpoints. Overlay transport nodes fail to come up. What should the administrator add in the NSX-T preparation workflow?
Select an answer to reveal the explanation.
Short Explanation
A transport-node profile is like handing out tunnel radios with no phone numbers. TEP IP pools are those numbers. Create the pool first, then apply the profile, or the overlay never comes up for the fare VMs.
Full Explanation
Host overlay preparation in NSX-T requires tunnel-endpoint addressing so transport nodes can form GENEVE tunnels. The documented workflow creates TEP IP pools (or static TEPs) before applying a transport-node profile. Carbon Black device control and Workspace ONE compliance do not assign TEP addresses. Distributed Firewall cannot realize on hosts that never become transport nodes; TEP prep here is fabric enablement for security, not a routing-design exam item.