1V0-604 · Question #70
Which statement correctly defines third-party gateway support in NSX for vSphere and NSX for Multiple Hypervisors (NSX-MH) for application workloads that span virtual and physical spaces?
The correct answer is C. Both versions of NSX provide support for hardware based gateways. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
Which statement correctly defines third-party gateway support in NSX for vSphere and NSX for Multiple Hypervisors (NSX-MH) for application workloads that span virtual and physical spaces?
Options
- AOnly NSX-MH provides support for hardware based gateways.
- BOnly NSX for vSphere provides support for hardware based gateways.
- CBoth versions of NSX provide support for hardware based gateways.
- DNeither version of NSX provides support for hardware based gateways at this time.
How the community answered
(37 responses)- A3% (1)
- B8% (3)
- C76% (28)
- D14% (5)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
4
Fatima Z.Jun 27, 2026Both NSX for vSphere AND NSX-MH support hardware-based gateways, so the answer is C. Picture it as a TWO-HAND HIGH-FIVE: both flavors of NSX reach out to shake hands with physical third-party gateways, because workloads do not stop at the virtual fence.
Ivana K.Jun 27, 2026The wording "third-party gateway" trips people up here because it sounds like a vendor-specific limitation, so you start second-guessing whether NSX-MH really had that capability, but the answer is C. Both NSX for vSphere and NSX-MH support hardware-based gateways for workloads that bridge virtual and physical environments, which is exactly what the L2 gateway service was designed to handle in both deployment models.
Kavya H.Jun 26, 2026Both NSX for vSphere and NSX-MH support hardware-based gateways, so C is the right pick. This matters in practice because physical workloads like bare-metal servers or legacy network appliances need that L2 gateway bridging to participate in the same logical overlay as your VMs, and both platforms handle that without forcing you to keep everything virtual.
Ivana K.Jun 29, 2026Worth adding that from a blueprint perspective in Aria Automation, the practical payoff is that your catalog item can reference a single logical segment whether the consuming endpoint is a VM or a bare-metal node sitting behind that hardware VTEP, so you avoid proliferating network profiles just to accommodate physical workloads in the same overlay.