Match each remote access operational scenario or requirement with the correct protocol, default port assignment, or Windows OS restriction.
- A network engineer requires an encrypted, authenticated command-line session to securely manage a remote Linux router across an untrusted network.SSH (Secure Shell) utilizing default TCP port 22
- A help desk technician attempts to configure native incoming Remote Desktop host capabilities on an employee's company-issued laptop running Windows 11 Home edition.Feature unavailable on host OS; incoming RDP server hosting requires Windows Pro, Enterprise, or Education edition
- A systems administrator establishes a native Windows graphical user interface (GUI) session to perform maintenance on a remote Windows Server 2022 instance.RDP (Remote Desktop Protocol) utilizing default TCP port 3389
- A security analyst flags an unencrypted, legacy text-based remote administration session during a network packet capture audit.Telnet transmitting plain-text credentials and data over default TCP port 23
Answer
1 matches SSH on TCP port 22; 2 matches Windows Home RDP hosting limitation; 3 matches RDP on TCP port 3389; 4 matches Telnet on cleartext TCP port 23.
Each scenario maps to its underlying protocol specification or OS constraint. Secure command-line access relies on SSH (TCP 22), plain-text legacy access uses Telnet (TCP 23), native Windows GUI management relies on RDP (TCP 3389), and incoming RDP hosting is limited to Windows Pro and higher editions.
Step-by-Step Solution
Key Concept
Remote Access Protocols, Port Numbers, and OS Feature Restrictions
Estimated Time:2m 0s