Question

Difficulty: HardRemote Access Technologies and Tools

A systems administrator is establishing a remote management infrastructure to allow internal engineers to manage both Windows 11 Pro workstations and Linux servers located at a remote branch office across an untrusted public network. Which TWO of the following requirements and settings must be implemented to ensure secure remote access and protocol functionality?

  1. Establish a secure Virtual Private Network (VPN) connection prior to initiating unencrypted or direct remote management sessions over the internet.Answer
  2. Configure the perimeter firewall to allow inbound traffic on TCP port 22 for secure command-line administration of Linux systems via SSH.Answer
  3. C
    Configure perimeter firewall rules to allow inbound TCP port 23 to enable encrypted command-line session management.
  4. D
    Enable the inbound Remote Desktop feature natively on remote client endpoints that run Windows 11 Home edition.

Answer

Establishing a VPN connection prior to managing systems over public networks and allowing inbound traffic on TCP port 22 for SSH Linux administration are the required settings.
Establishing a VPN connection secures administrative traffic sent across untrusted public networks by creating an encrypted tunnel. Additionally, SSH uses default TCP port 22 to provide encrypted command-line management for Linux systems.

Step-by-Step Solution

1
Evaluate transport security requirements over untrusted networks.
Connecting across an untrusted public network requires a secure tunnel such as a VPN to protect internal administrative traffic.
VPN encapsulation encrypts traffic end-to-end or site-to-site, preventing eavesdropping on internal management protocols.
2
Identify the standard secure protocol and port for Linux remote command-line administration.
SSH utilizing TCP port 22 is selected for secure CLI management.
SSH provides strong encryption for authentication and terminal data, unlike legacy unencrypted protocols like Telnet (TCP port 23).
3
Analyze endpoint OS limitations and unencrypted protocol risks.
Reject Telnet (TCP 23) due to cleartext transmission risks and reject inbound RDP on Windows Home endpoints because incoming RDP host features are omitted in Windows Home editions.
Windows 11 Home cannot host RDP sessions without upgrading to Windows Pro or higher, and Telnet lacks encryption.

Key Concept

Remote access protocol security, default ports (SSH TCP 22 vs Telnet TCP 23), VPN tunneling requirements, and Windows edition RDP hosting capabilities.
Rate this question