A financial enterprise requires a secure connection for dynamic, roaming field auditors back to corporate headquarter applications while allowing them to maintain simultaneous access to local subnet resources such as home printers. Concurrently, the organization must maintain a permanent, always-on encrypted connection between a fixed regional branch router and the headquarter security appliance to route entire subnet traffic transparently.
Which architectural combination correctly satisfies the operational requirements for both deployment models?
- Deploy a client-based Remote Access VPN using split-tunneling for the roaming auditors, and establish an IPsec Site-to-Site VPN using tunnel mode between the regional branch router and headquarter security appliance.Answer
- BDeploy a full-tunneling Remote Access VPN for the roaming auditors to preserve local subnet printing, and configure a clientless SSL VPN on the regional branch gateway for the site-to-site connection.
- CDeploy TACACS+ payload encryption across a Site-to-Site VPN for roaming auditors, and configure a clientless RADIUS tunnel for the branch router connection.
- DDeploy an IPsec Site-to-Site VPN operating in transport mode directly on the roaming auditor laptops, while configuring a split-tunneling profile on the regional branch router to connect the two sites.
Answer
Deploy a client-based Remote Access VPN using split-tunneling for the roaming auditors, and establish an IPsec Site-to-Site VPN using tunnel mode between the regional branch router and headquarter security appliance.
Remote Access VPNs with split-tunneling allow individual endpoints to send corporate-bound traffic through an encrypted tunnel while accessing local network resources directly. Site-to-Site IPsec VPNs operate between fixed security gateways (routers or firewalls) using tunnel mode to securely bridge entire IP subnets over public networks.
Step-by-Step Solution
Key Concept
Remote Access vs. Site-to-Site VPN Topology & Split-Tunneling Mechanics