How does NSX simplify physical network design?
A.
VLANs are moved into the virtual network for virtual machine traffic, eliminating the need to use
PVLANs on the physical network.
B.
Network administrators only need to configure routing on the physical network for virtual
machine traffic since all other network functions are moved to the virtual network.
C.
Transport zones are created in the virtual network for virtual machine traffic, removing the need
to make changes to the physical network.
D.
Virtual network integration can make changes to the physical network programmatically using
REST API calls which automates network changes and increases agility.
In the simplest sense, a Transport Zone defines a collection of ESXi hosts that can communicate with each other across a physical network infrastructure. As previously mentioned, this communication happens leveraging one (or more) specific interface defined on each ESXi host and named VXLAN Tunnel EndPoints (VTEPs).
A Transport Zone extends across one or more ESXi clusters and in a loose sense defines the span of logical switches.
comment above is an explanation ?
C has no relation with the physical network design.
It should be B.
There is nothing move from physical to virtual, except routing exchange and MTU setting on physical (Jumbo frame support, at least 1550 bytes, 1600+ bytes is recommended by VMware). So B is not true. Like i said, C is correct if we are enable Jumbo Frame support on physical network.
I dont think so B is correct. if it say routed configure routing for vtep then could be but as for me answer is C
How does a NSX transport zone simplify a physical network design? Weird question with wrong answers.
B is the best among the answers, while C has nothing to do with simplification. it’s a design consideration and is a about LS cluster expansion