RDP vs SSH vs VNC: A+ Core 2 Remote Access Guide
Remote access protocols allow administrators to manage systems from a distance. RDP (port 3389) provides a Windows GUI, SSH (port 22) offers secure CLI access primarily for Linux, and VNC (port 5900) provides a platform-independent GUI. Choosing the right one depends on the OS, security needs, and required interface.
What are the essential port numbers you need to memorize?
If there is one thing the CompTIA A+ exam loves, it is testing your ability to match a protocol to its default port. For remote access, you have three heavy hitters you must know by heart: RDP uses TCP 3389, SSH uses TCP 22, and VNC typically starts at TCP 5900.
I always tell my students to treat these numbers as non-negotiable facts. You won't just see these in multiple-choice questions; you'll need them when you're configuring firewall rules in a performance-based question (PBQ). If you see a scenario where a technician cannot connect to a Windows server, your first thought should be: 'Is port 3389 open?'
When should you use a GUI versus a CLI for remote access?
The choice between a Graphical User Interface (GUI) and a Command Line Interface (CLI) comes down to the task at hand. RDP and VNC are GUI-based, meaning you see the desktop exactly as if you were sitting in front of the monitor. This is essential for tasks like installing software with a wizard or troubleshooting a visual glitch in an application.
SSH, however, is all about the CLI. It is lean, fast, and incredibly powerful. When you're managing a Linux web server or updating a fleet of network switches, you don't want the overhead of a desktop environment. You want a terminal where you can execute scripts and manage configurations in seconds. In the real world, the CLI is where the real power lies, but for the A+ exam, know that GUI = RDP/VNC and CLI = SSH.
Which protocol is the most secure for production environments?
Security is a massive part of the 220-1102 objectives. SSH (Secure Shell) is the gold standard here because it was designed from the ground up to be encrypted. It protects your credentials and your data from packet sniffing, making it safe for use over the open internet.
RDP is encrypted, but it is a frequent target for brute-force attacks. You should never expose RDP directly to the internet; instead, use a VPN or a gateway. VNC is the riskiest of the three; many legacy VNC versions send passwords in clear text or use very weak encryption. If you must use VNC over a public network, the professional move is to 'tunnel' the VNC traffic through an SSH connection to ensure the data is encrypted.
How do you choose the right tool for Windows vs. Linux?
While these tools can be cross-platform, they each have a 'home' OS. RDP is native to Windows. If you are managing a Windows Pro or Enterprise machine, RDP is your best bet because it is optimized for the Windows graphics engine and integrates perfectly with Active Directory.
Linux is the kingdom of SSH. While you can install a GUI on Linux and use VNC, most Linux admins live in the terminal. VNC is the 'Switzerland' of remote access—it works across Windows, macOS, and Linux. Because it simply shares the screen pixels, it doesn't care which OS is running. However, this makes it slower than RDP, which sends drawing instructions rather than raw images.
How do these protocols appear on the A+ Core 2 exam?
You won't just be asked to define these protocols; you'll be asked to apply them to a scenario. For example, you might be tasked with choosing a protocol to manage a remote Linux server with minimal bandwidth—the answer is SSH. Or, you might need to provide remote support to a user who needs to see their own screen—that's a VNC or RDP scenario.
To truly master this, you need to see these scenarios repeatedly. That's why we built Cert Sensei with 1,000 expert-curated practice questions for the A+ Core 2 (220-1102). We don't just tell you that you got an answer wrong; we provide detailed expert reasoning and domain-level analytics so you can see exactly where your knowledge of remote access protocols is lagging.
Why does the choice of protocol impact network performance?
Bandwidth is a critical consideration in IT. SSH is incredibly lightweight because it only transmits text characters. You can run an SSH session on a shaky 3G connection and it will still feel snappy. RDP is more efficient than VNC because it uses a high-level protocol to describe the UI elements, meaning it sends less data over the wire.
VNC is the 'heavyweight' because it captures and sends actual pixel data. If you're on a slow connection, VNC will feel laggy and 'choppy.' When you're studying for the A+ exam, remember that the more 'visual' the protocol, the more bandwidth it consumes. This is a key distinction when choosing the right tool for a remote office with limited connectivity.
❓ Frequently Asked Questions
Can I use SSH on a Windows machine for the A+ exam?
Yes. While SSH is primarily associated with Linux, modern versions of Windows 10 and 11 have OpenSSH built-in. However, for the exam, remember that RDP is the primary GUI tool for Windows, and SSH is the primary CLI tool for Linux/Unix.
Is VNC better than RDP for remote support?
It depends. VNC is often better for 'screen sharing' where the technician and the user both see the same session. RDP typically creates a new session, which can lock the local user out of the console on some Windows versions.
What happens if I try to connect via RDP but port 3389 is blocked?
The connection will time out. As a technician, you would check the Windows Firewall settings or the network router's Access Control List (ACL) to ensure TCP 3389 is allowed through.