Match each VPN deployment scenario or operational requirement on the left with the corresponding VPN technology or protocol implementation on the right.
- Connecting two fixed corporate branch office routers across an untrusted WAN using static peer IP addresses and pre-shared keys without dynamic overlay routing.Site-to-Site IPsec VPN (Static LAN-to-LAN)
- Providing web-browser-only remote access to internal intranet web portals for external contractors without installing software on endpoint devices.Clientless SSL VPN (Web Portal Access)
- Authenticating mobile teleworkers using dedicated endpoint software to secure all IP network layer traffic with optional split-tunnel capabilities.Client-Based Remote Access VPN (e.g., Cisco AnyConnect IPsec/SSL)
- Establishing scalable dynamic spoke-to-spoke encrypted tunnels between multiple enterprise sites using Multipoint GRE and Next Hop Resolution Protocol.Dynamic Multipoint VPN (DMVPN)
Cevap
Static branch gateway connections match Static Site-to-Site IPsec VPN. Browser-only contractor access matches Clientless SSL VPN. Mobile endpoint client software matches Client-Based Remote Access VPN. Scalable dynamic spoke-to-spoke using mGRE/NHRP matches DMVPN.
Each requirement maps precisely to its characteristic VPN architecture: standard point-to-point router links map to Static Site-to-Site IPsec, browser-bound contractor access maps to Clientless SSL VPN, full network layer remote connectivity maps to Client-Based Remote Access VPN, and dynamic multi-site scaling with mGRE/NHRP maps to DMVPN.
Adım Adım Çözüm
Anahtar Kavram
Classification and operational mechanics of Remote Access (Clientless SSL and Client-based AnyConnect) versus Site-to-Site VPN architectures (Static IPsec and DMVPN).