Examkin

Question

Difficulty: HardRemote Access and Site-to-Site VPN Concepts

A network security administrator is designing a VPN architecture for an enterprise deployment. The primary requirement demands a persistent, gateway-to-gateway encrypted connection between two static data center locations to transparently transport subnets without requiring endpoint software. Additionally, the administrator must support mobile employees who need temporary, browser-based remote access to internal HTTPS web applications from unmanaged personal laptops without installing a dedicated VPN client software. Which combination of VPN deployment types and protocols best fulfills both architectural requirements?

  1. A Site-to-Site IPsec VPN using tunnel mode for data center connectivity, and a Clientless SSL/TLS Remote Access VPN for mobile employee access.Answer
  2. B
    A Remote Access IPsec VPN using transport mode for data center connectivity, and a Client-based IPsec Remote Access VPN using split-tunneling for mobile employee access.
  3. C
    A Site-to-Site SSL/TLS VPN using transport mode for data center connectivity, and a Clientless Remote Access IPsec VPN with GRE encapsulation for mobile employee access.
  4. D
    A Site-to-Site IPsec VPN using transport mode for data center connectivity, and a Client-based SSL/TLS Remote Access VPN enforcing full tunneling for mobile employee access.

Answer

A Site-to-Site IPsec VPN using tunnel mode for data center connectivity, and a Clientless SSL/TLS Remote Access VPN for mobile employee access.
The correct selection correctly pairs Site-to-Site IPsec VPN in tunnel mode for transparent network-to-network data center interconnection with Clientless Remote Access SSL/TLS VPN for mobile workers. Site-to-Site IPsec VPNs use security gateways at each end to encrypt traffic between entire subnets without host configuration. Clientless SSL VPN allows remote users to establish a secure session directly through a web browser using standard TLS, eliminating the need to deploy or manage client software on unmanaged personal devices.

Step-by-Step Solution

1
Analyze the static data center interconnect requirement.
Connecting two static corporate data center networks transparently requires a Site-to-Site topology using IPsec in tunnel mode (encrypting both original header and payload between security gateways).
Site-to-Site VPNs establish permanent peer-to-peer links between edge devices (routers/firewalls) to connect entire subnets.
2
Analyze the mobile employee access requirement.
Providing secure access from unmanaged devices without installing client software necessitates a Clientless Remote Access SSL/TLS VPN.
Clientless SSL VPN utilizes the native web browser's TLS implementation to grant access to internal web portals without requiring administrative installation of VPN client software on personal endpoints.
3
Synthesize and select the matching option.
Combining a Site-to-Site IPsec VPN in tunnel mode with a Clientless SSL/TLS Remote Access VPN fully satisfies both requirements.
This alignment satisfies network-to-network transport for static branches and clientless browser access for remote workers.

Key Concept

Distinction between Site-to-Site IPsec VPNs and Remote Access SSL/TLS (Clientless vs Client-based) VPN architectures.
Rate this question

Topics

Remote Access and Site-to-Site VPN Concepts

More questions from this topic