An architect is helping an organization with the Logical Design of a Layer 2 bridging solution.
This information was gathered during the Assessment Phase:
✑ Workloads are running on ESXi hosts.
✑ Workloads are running on KVM hosts.
✑ Workloads on hypervisors should use bridging services.
✑ VLAN 50 is used for Tier-0 uplink connectivity.
Which selection should the architect include in their design? (Choose the best answer.)
When configuring a bridge instance in an NSX design, it is crucial to avoid using the same VLAN for both bridging and uplink connectivity of other services, including Tier-0 routing. This restriction prevents VLAN conflicts that can disrupt network services. Therefore, creating an NSX Edge Bridge Cluster and configuring the bridging profile with VLAN 60, different from VLAN 50 used for Tier-0 uplink connectivity, ensures there are no conflicts, leading to a more robust and stable design.
Answer A is Correct: When a bridge instance is mixed with L3 routing on T0, the VLAN ID used by the T0 uplinks for the route peer cannot be used by the bridge instances.
A must be correct
NSX-T edge bridge does not support multiple VLAN uplinks (81777); https://kb.vmware.com/s/article/81777?lang=en_US That means that we will be required to use the same VLAN identified for Tier-0 uplink and that's VLAN ID 50. Therefore, B is the correct answer.
My answer is B: If the edge cluster is used for bridging, all traffic associated with that T1 does not go to a centralized location. However, if an edge cluster has existing services, it can be reused under the bridge profile.
Answer A is correct This is a caveat from NSX Bridging document found on VMware communities "VLAN conflicts on the Edge: two services cannot use the same VLAN ID on an edge uplink. That means that, for example, it is not possible to bridge traffic to a VLAN ID that is already used by a Tier 0 interface on an edge. " https://communities.vmware.com/wbsdv95928/attachments/wbsdv95928/4002/70/2/NSX-T%20Bridge%203.1.pdf
B is the correct answer and you can locate it here: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.3/com.vmware.nsxt.admin.doc/GUID-7B21DF3D-C9DB-4C10-A32F-B16642266538.html
A should be the correct answer.
B is correct
The correct answer is A
I am Select "A" While technically possible to configure NSX-T with the same VLAN for Tier-0 uplink connectivity and bridging, it's recommended to use different VLANs to avoid potential conflicts and maintain proper network segmentation. This approach aligns with standard networking practices and helps ensure a clear and robust network configuration. Always refer to the NSX-T documentation and collaborate with your network and NSX administrators for specific organizational guidelines.
A is Correct VLAN conflict on the Edge An edge uplink cannot have two VLAN segments with the same VLAN ID. This limitation is not directly related to the edge bridge, but its consequences will be apparent in some edge bridge related configuration. When a user configures the attachment of segment S1 to VLAN X on a specific edge uplink, the edge automatically creates a local segment VLAN X on the N-VDS owning the uplink. This automatic creation will fail if there was already a VLAN segment configured with the same ID on this N-VDS. To be more precise, the configuration of the VLAN segment will succeed, but the realization of the segment will fail. It is possible to hit this limitation when: Trying to configure attachments of several different segments to the same VLAN ID on the same uplink (only the first attachment will be operational.) Trying to configure the attachment of a segment to a VLAN ID that is already used by other services on this uplink. For example, if there is a Tier 0 router using this VLAN ID to send traffic on the uplink.
It must be the same VLAN in bridging. B is the correct answer.
Answer C is Correct NSX Edge Bridge Cluster: Do not exist, so AB are wrong. ESXi Bridge Cluster: Yes, it exists.