Common Use Cases for Encryption for CompTIA Tech+ (FC0-U71): Data at Rest, Data in Transit, and Real-World Examples

Why Objective 6.4 Matters on the Tech+ Exam

CompTIA Tech+ (FC0-U71) devotes Domain 6.0 (Security) to 19% of the exam, tying it for the largest domain weight on the test. Inside that domain, Objective 6.4, "Identify common use cases for encryption," is one of the shortest objectives on the blueprint, but it is also one of the most frequently misunderstood. Candidates often assume encryption is a single thing they either "turn on" or "turn off," when the exam actually wants you to recognize where encryption applies and why that location changes which tool gets used. This guide breaks the objective into its three tested pieces: the vocabulary of plaintext and ciphertext, protecting data at rest, and protecting data in transit, with a quick detour into the everyday apps where you already rely on all three without thinking about it.

This article builds on an earlier Tech+ guide worth reviewing first: our Security Fundamentals for Tech+ guide, which covers the CIA triad that encryption directly supports (confidentiality). Encryption is the mechanism that makes that concept work in practice.

Plaintext vs. Ciphertext: The Vocabulary the Exam Expects

Before anything else, FC0-U71 wants you to be fluent in two terms. Plaintext is data in its original, readable form — a Word document before you save it, an email before you hit send, a credit card number as you type it into a form. Ciphertext is what that same data looks like after an encryption algorithm has scrambled it using a key. Anyone who intercepts ciphertext without the correct key sees only noise.

The exam will sometimes phrase a question as "which of the following best describes data that has been transformed so it cannot be read without a key" — that is simply asking you to identify ciphertext. It is a vocabulary check wrapped in a scenario, and missing it usually comes down to not recognizing the plain-language description rather than not knowing the term. If you want the deeper mechanics of how a key actually transforms plaintext into ciphertext, our Security+ level breakdown of asymmetric encryption goes further than Tech+ requires, but it is useful context for where this topic eventually leads if you continue toward Security+.

Data at Rest: Encrypting Information in Storage

"Data at rest" means information that is sitting still — saved to a hard drive, stored in a database, or resting on a phone's internal storage rather than being actively sent somewhere. Objective 6.4 calls out three flavors of this:

• File-level encryption: a single file or folder is encrypted, while the rest of the drive remains in plaintext. This is common when only certain sensitive documents need protection and performance matters for everything else.
• Disk-level (full-disk) encryption: the entire storage volume is encrypted, including the operating system files, temporary files, and swap space. BitLocker on Windows and FileVault on macOS are the classic real-world examples, and both depend on protections we cover in more depth in our self-encrypting drive breakdown.
• Mobile device encryption: modern smartphones encrypt local storage by default once a passcode or biometric lock is set, protecting contacts, photos, and app data if the device is lost or stolen.

The exam-relevant distinction is scope. File-level encryption protects specific content; disk-level encryption protects everything on that volume, including files you forgot you had. A Tech+ question that describes someone losing a laptop and asking "what would have prevented the data from being readable" is testing whether you connect that scenario to full-disk encryption rather than a narrower control. For a deeper technical comparison of how these layers differ once you're past Tech+, see our Security+ guide to data at rest.

Data in Transit: Encrypting Information on the Move

"Data in transit" is the opposite scenario: information actively traveling across a network, where it is exposed to anyone positioned to intercept the traffic. FC0-U71 lists four contexts where this matters:

• Email: messages can be encrypted in transit between mail servers, though whether the body itself is protected depends on whether the sender also used message-level encryption.
• HTTPS: the padlock icon in a browser address bar indicates that traffic between the browser and the website is encrypted using TLS, preventing anyone on the same network from reading the page content, form submissions, or login credentials as they travel.
• VPN (Virtual Private Network): creates an encrypted tunnel between a device and a remote network, which is especially relevant when using the untrusted public Wi-Fi networks described in our Internet Service Types guide.
• Mobile applications: banking apps, messaging apps, and most modern mobile software encrypt data before it leaves the device, independent of whether the underlying network connection is itself secure.

A useful way to keep data at rest and data in transit straight for exam day: if the question describes something being stored, think disk or file encryption; if it describes something being sent, think TLS, VPN, or application-level encryption. Our Security+ level guide to data in transit expands on the protocol details if you want to go beyond what Tech+ tests.

Encryption You're Already Using Without Noticing

Objective 6.4 is deliberately practical, so it helps to map the vocabulary onto tools you already touch daily:

• Checking a bank balance on a phone app uses data-in-transit encryption (the app's own TLS connection) layered on top of data-at-rest encryption (the phone's storage encryption protecting cached data).
• A locked, encrypted laptop that an employee takes home is relying on full-disk encryption to keep data unreadable if the device is stolen from a car or a bag.
• Logging into a web-based email client over a hotel's public Wi-Fi is protected by HTTPS for the connection to the mail provider, and optionally by a VPN for the connection to the hotel network itself.
• A messaging app showing "end-to-end encrypted" under a conversation is describing data-in-transit protection that persists even if it passes through the provider's own servers.

Recognizing these everyday patterns is exactly what separates candidates who memorize four bullet points from candidates who can correctly answer a scenario-based question that never uses the words "data at rest" or "data in transit" explicitly.

Common Exam Traps on Objective 6.4

A few wording patterns trip up candidates on this objective specifically:

• Confusing "encrypted" with "safe." Encryption protects confidentiality, not availability or integrity. A ransomware attacker encrypting a victim's files is misusing the same concept for the opposite purpose — this is why Tech+ pairs 6.4 with the CIA triad concepts from Objective 6.1.
• Mixing up data at rest and data in use. Data in use (actively being processed in memory) is a Security+ and SecurityX level concept and is not part of the FC0-U71 blueprint, so if an exam option mentions "data in use," it is almost certainly a distractor on a Tech+ exam.
• Assuming HTTPS and a VPN do the same job. HTTPS encrypts one connection to one website; a VPN encrypts all traffic leaving the device to the VPN endpoint. A question describing "protecting all traffic on a public Wi-Fi network" points to a VPN, not just checking for a padlock icon.

Key Takeaways

• Plaintext is readable data; ciphertext is that same data after encryption makes it unreadable without the correct key.
• Data at rest covers file-level, disk-level, and mobile device encryption — all protecting stored information.
• Data in transit covers email, HTTPS, VPN, and mobile application encryption — all protecting information actively moving across a network.
• The exam tests recognition of real-world scenarios, not just definitions, so practice mapping everyday tools (banking apps, encrypted laptops, VPNs) back to the correct category.
• Encryption protects confidentiality specifically, not integrity or availability — don't let an exam option conflate the three.