300-730 · Question #13
Which feature of GETVPN is a limitation of DMVPN and FlexVPN?
The correct answer is D. no requirement for an overlay routing protocol. GETVPN operates tunnel-less over trusted private WANs, so it does not require an overlay routing protocol, which is a dependency in both DMVPN and FlexVPN.
Question
Options
- Asequence numbers that enable scalable replay checking
- Benabled use of ESP or AH
- Cdesign for use over public or private WAN
- Dno requirement for an overlay routing protocol
How the community answered
(23 responses)- A13% (3)
- B9% (2)
- C4% (1)
- D74% (17)
Why each option
GETVPN operates tunnel-less over trusted private WANs, so it does not require an overlay routing protocol, which is a dependency in both DMVPN and FlexVPN.
Sequence-number-based replay checking is a standard IPsec feature available in DMVPN and FlexVPN as well, so it is not a differentiating capability unique to GETVPN.
ESP and AH are IPsec encapsulation options supported equally by DMVPN, FlexVPN, and GETVPN, making this a shared trait rather than a GETVPN-exclusive feature.
GETVPN is specifically designed for trusted private WANs such as MPLS and cannot function over the public Internet, whereas DMVPN and FlexVPN support both public and private transports - so this describes a limitation of GETVPN, not of the other two.
GETVPN encrypts packets in-place while preserving the original IP header, meaning the existing underlay routing infrastructure delivers packets without any virtual tunnel interface or overlay protocol. DMVPN and FlexVPN both build mGRE or IPsec tunnel interfaces that require an overlay routing protocol such as EIGRP or BGP to advertise networks across the VPN fabric. Because GETVPN has no tunnel overlay, no overlay routing protocol is needed, which is a capability DMVPN and FlexVPN lack.
Concept tested: GETVPN tunnel-less design vs overlay routing requirement
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_getvpn/configuration/xe-16/sec-conn-getvpn-xe-16-book/sec-conn-get-vpn.html
Topics
Community Discussion
No community discussion yet for this question.