FC0-U71 CompTIA Tech+ Study Guide¶

Independent AI-assisted resource — SOURCES + OBJECTIVES CHECKED; HUMAN REVIEW PENDING. Objective coverage, citations, volatility labels, links, and exam-integrity compliance were checked on October 28, 2026. This is not a guarantee that the guide is error-free or current after that date. See the sources-and-objectives record. The official CompTIA Tech+ page is authoritative.

Study guide at a glance

Start here

Report an issue with FC0-U71

Blueprint checked2026-10-28

Review stateSources + objectives checked — human review pending

Guide-only active reading45 min–1 hr 15 min

Prerequisites: No prior experience is required. Build practical technology literacy across computing and notation, devices/components/storage/interfaces, virtualization/cloud/networking, operating systems/applications/browsers/AI, basic programming logic, data/databases/backups, troubleshooting, and security; verify the FC0-U71 versus FC0-U71-CE lifecycle choice during purchase.

Exam essentialsRead the objective map, key distinctions, and readiness checklist.

Deep understandingWork through every domain, including decisions, failure modes, and related items.

Hands-on labsBegin with Original relational-data and restore exercise, then use the remaining labs to produce evidence you can inspect and explain.

Official objective domains

See the objective map in this guide

The active-reading range uses 90–130 words per minute for technical material. Labs, troubleshooting, note-taking, spaced review, and prerequisite gaps add time; it is not a total preparation promise.

Current baseline: Tech+ V6, exam series FC0-U71
Upcoming blueprint change: None announced when checked September 28, 2026
Official delivery snapshot: Maximum 70 questions, 60 minutes, passing score 650 on a 900-point scale; English and Japanese listed
Credential lifecycle detail: The public page lists FC0-U71 as no-expiration and FC0-U71-CE as valid for five years. Confirm which series and renewal terms you are purchasing.

Current guide watch — October 28, 2026¶

The official Tech+ page and V6 objective document still identify FC0-U71 with six weighted domains. This is a stable blueprint check; use the registered CompTIA objective PDF for detailed tasks and the exam page for scheduling details. CompTIA Tech+ page and official FC0-U71 objectives

How to use this guide¶

Tech+ is a broad technology-literacy assessment. It rewards a connected mental model more than isolated acronym recall: data enters a device, components process and store it, an operating system exposes resources to applications, networks connect systems, databases organize persistent data, developers express logic, and security protects the whole flow.

For each concept, practice four moves:

define it in plain language without using the term itself;
identify it in a real device, diagram, operating system, application, or small data set;
compare it with the nearest alternative and state why the distinction matters;
troubleshoot one safe failure using identify → research/theory → test → implement → verify → document.

Do not turn a beginner guide into professional-level engineering trivia. You should recognize choices and reason about basic consequences, not memorize vendor-specific commands or configuration limits beyond the public V6 scope.

Weighted objective map¶

Domain	Weight	Evidence of readiness
1. Tech concepts and terminology	13%	Explain computing, notation, units, and the troubleshooting method
2. Infrastructure	24%	Identify devices/components/storage/interfaces and reason about cloud, virtualization, and basic networks
3. Applications and software	18%	Distinguish operating systems, utilities, applications, browsers, files, and common AI uses
4. Software development concepts	13%	Read simple logic and distinguish language types, data types, control flow, functions, objects, and design representations
5. Data and database fundamentals	13%	Explain data value, relational/non-relational structure, queries/reports, scale, storage, and backups
6. Security	19%	Apply CIA, authentication/authorization, device hygiene, passwords, encryption, safe browsing, and physical protection

The exam page provides 29 summary topic rows. The public FC0-U71 V6 objectives document, version 4.0, linked through CompTIA’s resource portal, provides 31 numbered objectives. Document version 4.0 and exam version V6 are different identifiers. Use the main page for current exam/lifecycle details and the full document for the finer checklist; no new exam transition is inferred from this review.

Objective IDs	Study coverage
1.1–1.4	Computing cycle; number systems; units; troubleshooting
2.1–2.3	Device purposes, internal components and storage
2.4–2.6	Peripherals, interfaces, virtualization/cloud
2.7–2.9	Internet access types, networking and small wireless networks
3.1–3.5	OS components/purpose, software, browser configuration and AI
4.1–4.4	Language categories, types, programming concepts and logic
5.1–5.4	Data value, database purposes/structures and backup
6.1–6.5	Security principles, device protection, passwords, encryption and wireless configuration

1. Tech concepts and terminology — 13%¶

The computing cycle¶

Computing transforms input into output through processing and often storage. A keyboard, camera, sensor, file, or network request provides input. A CPU/GPU and software apply instructions. A display, speaker, file, actuator, or network response provides output. Storage keeps data or instructions beyond the immediate operation.

Classify a component by its role in a particular flow rather than by a permanent label. A touchscreen is both input and output; a network adapter receives and transmits; a storage device can be read as input and written as output.

Notation and measurement¶

Binary uses base 2, decimal base 10, octal base 8, and hexadecimal base 16. Understand positional value and convert small values, especially between binary and decimal and between a four-bit group and one hexadecimal digit. This explains why computing values, addresses, permissions, and colors often use representations other than ordinary decimal.

A bit is one binary value; a byte is eight bits in these examples. Keep capacity, clock frequency, and transfer rate separate:

KB/MB/GB/TB describe storage or memory quantities, subject to decimal/binary convention;
MHz/GHz describe cycles per second, not guaranteed application performance;
bps/Kbps/Mbps/Gbps describe bits transferred per second, not bytes stored;
latency is delay, while bandwidth is potential volume per time.

Do not conclude that a higher number always makes a complete system faster. CPU architecture, core count, memory, storage, network, workload, thermal behavior, and software all contribute.

Worked notation and rate example¶

101101₂ = 32 + 8 + 4 + 1 = 45₁₀ = 2D₁₆ = 55₈. A four-bit hexadecimal group maps to one digit: pad on the left to get 0010 1101, then read 2 D. In octal, group three bits: 101 101, giving 5 5.

The NIST binary-prefix reference distinguishes decimal MB (1,000,000 bytes) from binary MiB (1,048,576 bytes). State the convention before calculating; a display using an ambiguous “MB” label does not redefine the unit. Lowercase b denotes bits; uppercase B denotes bytes. Tbps is terabits per second; TB/s is terabytes per second. The objectives PDF’s “Terabytes per second (Tbps)” example mixes those notations; do not carry that spelling into calculations.

# Python 3: these calculations use explicitly stated units.
value = int("101101", 2)
print(value, format(value, "x"), format(value, "o"))  # 45 2d 55

file_bytes = 100 * 1_000_000  # 100 MB, decimal
link_bits_per_second = 80 * 1_000_000  # 80 Mbps
ideal_seconds = file_bytes * 8 / link_bits_per_second
print(ideal_seconds)  # 10.0, excluding overhead and other delays
print(2**20, 10**6)  # 1 MiB and 1 MB, in bytes

For the 100 MB file, 100 × 1,000,000 × 8 ÷ 80,000,000 = 10 seconds. That is an ideal transfer calculation, not a prediction of a real download. Protocol overhead, shared links, server limits and startup delay can increase elapsed time. A 100 MiB file would take 10.48576 seconds under the same ideal assumptions.

Troubleshooting method¶

Start by identifying the problem: user report, symptoms, changes, scope, reproduction, and constraints. Establish a theory from evidence and research, test it with the least disruptive safe action, plan and implement the solution, verify full function and prevention, then document cause, action, and outcome. Escalate when access, risk, time, or expertise exceeds your boundary.

Changing several variables at once may accidentally restore service while destroying causal evidence. Back up important data and consider safety before opening hardware, removing software, resetting accounts, or changing network/security settings.

Related item: Scientific-method thinking—hypothesis, controlled test, observation, revision—makes troubleshooting transferable even though the exam uses an IT workflow.

2. Infrastructure — 24%¶

Devices and components¶

Recognize general-purpose desktops/laptops, smartphones/tablets, servers, gaming consoles, embedded systems, and Internet of Things devices. The form does not determine trust: a sensor or smart appliance is a networked computer with software, identity, updates, data, and failure modes.

Component	Primary role	Useful distinction
Motherboard	connects components and buses	physical/socket/form-factor compatibility matters
CPU	executes general instructions	frequency alone is not total performance
RAM	fast volatile working memory	contents normally disappear without power
HDD	magnetic persistent storage	mechanical, usually cheaper/capacious but slower
SSD/NVMe	flash persistent storage	NVMe is a protocol/interface path, not a synonym for all SSDs
GPU	highly parallel graphics/compute	may be integrated or discrete; workload support matters
NIC	network interface	wired/wireless and link capability do not guarantee internet reachability

Storage can be volatile or non-volatile, local/direct, network-attached, or cloud-delivered. “Cloud” describes remote service delivery and responsibility allocation; the data still resides on physical infrastructure. Compare capacity, speed/latency, connectivity, sharing, durability, portability, cost, privacy, and backup—not a single “best” label.

Firmware provides low-level startup/device behavior; BIOS/UEFI are familiar examples. It is distinct from an OS driver. ROM/flash can retain firmware without power; that does not make RAM persistent. Recognize optical media, removable flash, NAS and file servers as well as HDD/SSD. A UPS can bridge a brief power interruption; it does not replace a backup. E-readers, wearables, VR headsets and AR displays are computing devices with different inputs, outputs and resource constraints.

Interfaces, peripherals, and drivers¶

USB connects many peripherals and can carry different combinations of data, display, and power depending on version/device/cable. HDMI commonly carries digital audio/video. Ethernet is a wired network technology. Bluetooth supports short-range wireless peripherals; NFC supports very short-range interactions. The connector's shape does not guarantee every optional feature or speed.

Recognize older VGA/DVI and newer DisplayPort/HDMI/USB-C display paths, Thunderbolt and Lightning peripherals, and copper Ethernet versus fiber/SFP interfaces. An adapter must support the signals at both ends. Mirroring repeats a display; casting sends content to a receiver using a supported protocol. Cable testers check connectivity/wiring; a crimper attaches compatible cable connectors. Neither tool proves internet service is working.

A driver lets an operating system communicate with hardware. Before replacing a “failed” peripheral, verify power, physical connection, correct port/input, operating-system detection, driver/status, configuration/default selection, permissions, and a known-good cable/device. Use safe electrostatic and electrical practices; do not work inside powered equipment unless trained and authorized.

Virtualization and cloud¶

A hypervisor enables multiple virtual machines to share a host while maintaining logical separation. A container shares more of the host operating-system kernel and is not equivalent to a VM. Virtualization improves utilization and isolation but does not eliminate capacity, patching, backup, or security responsibilities.

In IaaS, the provider supplies lower-level infrastructure while the customer manages more of the OS and application stack. PaaS manages more runtime/platform layers. SaaS presents a finished application. On-premises infrastructure is operated in an organization's facilities; public cloud uses shared provider infrastructure; hybrid connects environments. Responsibility shifts rather than disappears.

Internet service choices¶

Objective 2.7 explicitly compares access services. These describe the connection to an internet provider, not the Wi-Fi connection between a laptop and its nearby access point.

Access type	Basic distinction	Evidence to compare
Fiber	Light over optical fiber	Available service, upstream/downstream rates and termination equipment
Cable	Provider access over coaxial cable	Local availability, shared capacity and modem compatibility
DSL	Data over telephone copper	Line quality/distance and service rates
Fixed wireless	Radio path to a provider site	Coverage, antenna placement, obstructions and contention
Cellular	Mobile network radio	Coverage, congestion, plan limits and device compatibility
Satellite	Radio path through a satellite system	Sky view, weather, service limits and the system’s latency

Do not assume every satellite service has the same delay or that every fiber plan has identical upload/download rates. Read the actual service specification. A modem/optical terminal connects the provider access medium; a router forwards between IP networks. Consumer equipment may combine roles.

Networking fundamentals¶

A LAN connects a limited local area; a WAN connects locations over distance. A switch primarily connects devices within a local network. A router forwards traffic between IP networks. A firewall applies traffic policy. A wireless access point connects Wi-Fi clients to a network; a home “router” often combines all four roles.

A client requests a service from a server; peer-to-peer systems let peers provide and consume resources. A port number helps identify a transport endpoint for an application service, not a physical socket on a laptop. Recognize web, email and file-transfer services without treating them as interchangeable.

A MAC address identifies a network interface at the local-link layer; an IP address enables logical routing. DNS translates names to records such as IP addresses. DHCP commonly supplies IP configuration. Test a path in layers: link/power, local configuration, local gateway, DNS, destination/service, then security policy. “The internet is down” can actually be one application, one name lookup, one device, one wireless channel, or one external service.

Name resolution is a separate request/response exchange; ordinary web payloads do not travel “through the DNS server.” A failed ping can mean blocked ICMP rather than a failed website, and reaching one IP address does not prove DNS, TLS or every destination works. Record exactly what each test establishes.

The detailed objectives name 802.11n/ac/ax and 2.4/5/6 GHz options. A band, radio standard and security protocol are separate properties. Do not infer 6 GHz capability from any generic Wi-Fi 6/802.11ax label; check the actual access point, client, driver and permitted regional bands.

Wi-Fi performance depends on standard, band/channel, distance, obstructions, interference, client/access-point capability, contention, and upstream service. A theoretical maximum is not an application guarantee.

Related item: The OSI and TCP/IP models are useful troubleshooting maps. Tech+ does not require professional packet analysis, but separating physical/link, addressing/routing, transport, and application failures prevents random fixes.

3. Applications and software — 18%¶

Operating systems and files¶

An operating system manages hardware, processes, memory, storage/files, devices, users, security, and interfaces for applications. Desktop, mobile, server, and embedded operating systems emphasize different interaction and workload needs. A graphical interface and command line are alternate management surfaces, not different operating systems.

A file system organizes data and metadata on storage. NTFS and FAT32 illustrate different capability and compatibility tradeoffs; avoid assuming every file system supports the same permissions, size, journaling, encryption, or operating systems. Files have paths, names, extensions/types, ownership/permissions, timestamps, and content. An extension helps association but does not prove that a file is safe or that its content matches its name.

Utilities perform system-oriented tasks such as file management, backup, compression, security scanning, disk management, and monitoring. Drivers bridge the OS and hardware. Applications help the user perform work: word processing, spreadsheets, presentations, communication/collaboration, browsers, media, remote support, and specialized tools.

Install from trusted sources, confirm platform/version and resource compatibility, review permission needs, patch responsibly, and know how to remove or roll back. Licensing answers whether/how software may be used; it is separate from technical compatibility.

Browsers and remote applications¶

Browsers render web applications and manage tabs, history, cookies/site data, cache, extensions, downloads, permissions, saved passwords, and private-browsing sessions. Private browsing mainly limits local session history; it does not make activity anonymous to networks, sites, accounts, employers, or providers. Clearing cache may resolve stale local content but can remove useful offline data and does not fix every server-side issue.

The Firefox private-browsing reference also distinguishes session history from saved downloads/bookmarks. Closing a private session does not delete downloaded files. In a disposable browser profile, practice bookmarks, default search, accessibility/appearance, pop-up controls and selective extension disable/enable. Inspect profile synchronization before enabling it; syncing can move settings/data to another device. Clearing cookies can sign you out, whereas clearing cached content serves a different purpose.

Treat extensions as software with permissions. Review publisher/source, requested access, updates, necessity, and removal. A password manager can create and store unique passwords, but it still needs a strong protected account and recovery plan.

Artificial intelligence uses and limits¶

Chatbots and assistants accept requests and produce responses; generative AI creates text, images, audio, code, or other content; predictive systems estimate classifications or future outcomes. AI output can be plausible but wrong, biased, unsafe, copyrighted, or based on sensitive input. Verify important results, protect confidential data, cite sources where required, and keep accountable human judgment for consequential decisions.

Related item: Automation follows encoded rules or learned behavior; intelligence and correctness should not be inferred merely because a system produces fluent output.

4. Software development concepts — 13%¶

Compiled languages are translated before execution; interpreted languages are executed through an interpreter/runtime; scripting languages often automate or glue tasks; markup describes document structure; assembly maps closely to processor instructions. Query languages such as SQL express data requests; assembly expresses low-level processor operations. These are separate purposes even where a printed outline’s indentation is ambiguous. Real ecosystems blur these categories, so learn the purpose of the comparison rather than absolute labels.

Data types constrain representation and operations: characters and strings hold text, integers whole numbers, floating-point types approximate fractional values, and Boolean values represent true/false. A variable names changeable state; a constant represents an intended unchanging value. An array/list groups values. A function packages reusable behavior with inputs/parameters and output/side effects. An object combines state and behavior according to a type/class model.

Branching chooses a path based on a condition; loops repeat while/for a condition or collection; errors/exceptions represent abnormal behavior. Read pseudocode by tracing one statement at a time and recording variable values. Check initial state, boundary/termination, input types, path condition, output, and error case.

Pseudocode communicates logic without strict language syntax. Flowcharts visualize sequence, decisions, input/output, and loops. Object-oriented design organizes responsibilities around objects/classes. These are design/communication tools; they do not automatically produce correct, secure, or maintainable code.

Trace a branch inside a loop¶

This original example uses the Python control-flow tutorial as an implementation reference. Python syntax is a practice tool, not a claim that Tech+ requires this language.

def count_ready(percentages):
    count = 0
    for percentage in percentages:
        if type(percentage) is not int or not 0 <= percentage <= 100:
            raise ValueError("Each percentage must be an integer from 0 to 100")
        if percentage >= 80:
            count += 1
    return count

print(count_ready([79, 80, 100]))  # 2
print(count_ready([]))  # 0

Iteration	Value	Meets `>= 80`?	Count afterward
Start	—	—	0
1	79	No	0
2	80	Yes	1
3	100	Yes	2

The loop visits each value once; the branch decides whether to increment. >= includes the boundary 80, while > would exclude it. An empty list returns zero. Negative numbers, values above 100, strings, floats and Booleans are rejected here because the exercise contract requires whole-number percentages. Other applications may choose different input contracts. A flowchart would show the loop and two decisions; comments explain intent but do not execute.

Related item: Testing turns an expected behavior into evidence. For beginner logic, use a normal case, boundary case, invalid input, and repeated/empty case rather than only the happy path.

5. Data and database fundamentals — 13%¶

Data becomes useful when it is accurate enough, timely, relevant, understood, protected, and connected to a decision. Reports summarize; analytics identifies patterns; operational systems support transactions; organizations may create products or revenue from data only when rights, consent, ethics, quality, and security permit it.

In a relational database, tables contain rows/records and columns/fields. A primary key uniquely identifies a row; a foreign key relates it to another table. Normalized design can reduce duplication and inconsistency, while deliberate denormalization may help some reads. A query requests or changes data; a report presents selected information. Schema, constraints, indexes, permissions, transactions, and backups all affect behavior even if Tech+ treats them conceptually.

A CSV file can represent structured rows; a JSON document can have a flexible, semi-structured shape; free-form audio/text needs additional interpretation. “Non-relational” does not mean “no structure.” A spreadsheet or flat file can be adequate for a small single-user task, while concurrent edits, constraints and repeated relationships may justify a database. Big data describes scale/variety/processing challenges; collecting more records does not fix biased or incorrect data. Correlation alone does not establish why a result occurred.

Non-relational databases may organize documents, key-value pairs, graphs, or wide columns. They are not simply “unstructured” or always faster. Choose based on data shape, access patterns, consistency, scale, operations, and tooling. Local versus cloud database placement changes responsibility, connectivity, scale, cost, control, and resilience considerations.

A file copy can protect selected content; an image/system backup captures broader state. Local backup restores quickly but can share the site's failure; cloud/remote backup improves separation but depends on connectivity, account security, cost, and restore process. A sync is not automatically a backup because deletion or corruption can propagate. Test restoration and define how much data loss and downtime are acceptable.

Related item: The 3-2-1 principle—multiple copies, different media, one offsite—is a useful foundation, but backup quality is proven by protected, monitored restores.

Original relational-data and restore exercise¶

Read the Python sqlite3 reference and SQLite foreign-key documentation for the implementation details. This uses only invented names and a temporary directory. SQLite runs locally; no server, account or paid service is needed. Use Python 3.12 or later for the explicit autocommit argument.

# Python 3.12+; all files are created inside a new temporary directory.
from contextlib import closing
from pathlib import Path
from tempfile import TemporaryDirectory
import shutil
import sqlite3

QUERY = """
SELECT m.name, COUNT(a.event_id)
FROM members AS m LEFT JOIN attendance AS a ON a.member_id = m.id
GROUP BY m.id, m.name ORDER BY m.id
"""

def run_database_demo(folder):
    source, backup, restored = [folder / name for name in
                               ("club.sqlite", "backup.sqlite", "restored.sqlite")]
    with closing(sqlite3.connect(source, autocommit=True)) as db:
        db.execute("PRAGMA foreign_keys = ON")
        assert db.execute("PRAGMA foreign_keys").fetchone() == (1,)
        db.executescript("""
        CREATE TABLE members (id INTEGER PRIMARY KEY, name TEXT NOT NULL);
        CREATE TABLE attendance (
            member_id INTEGER NOT NULL REFERENCES members(id),
            event_id TEXT NOT NULL,
            PRIMARY KEY (member_id, event_id)
        );
        """)
        db.executemany("INSERT INTO members VALUES (?, ?)",
                       [(1, "Ari"), (2, "Bo"), (3, "Cy")])
        db.executemany("INSERT INTO attendance VALUES (?, ?)",
                       [(1, "meetup-a"), (1, "meetup-b"), (2, "meetup-a")])
        before = db.execute(QUERY).fetchall()
        with closing(sqlite3.connect(backup, autocommit=True)) as copy:
            db.backup(copy)
        db.execute("DELETE FROM attendance")  # synthetic loss, after backup
        after_loss = db.execute(QUERY).fetchall()

    # The backup connection is closed. Restore to a different file.
    shutil.copyfile(backup, restored)
    with closing(sqlite3.connect(restored, autocommit=True)) as db:
        after_restore = db.execute(QUERY).fetchall()
        assert db.execute("PRAGMA integrity_check").fetchone() == ("ok",)
    assert after_restore == before
    return before, after_loss, after_restore

if __name__ == "__main__":
    with TemporaryDirectory(prefix="tech-plus-demo-") as folder:
        for result in run_database_demo(Path(folder)):
            print(result)

Expected reports are:

[('Ari', 2), ('Bo', 1), ('Cy', 0)]
[('Ari', 0), ('Bo', 0), ('Cy', 0)]
[('Ari', 2), ('Bo', 1), ('Cy', 0)]

members.id identifies a person. The attendance pair (member_id, event_id) prevents the same attendance from being entered twice, and its foreign key rejects a nonexistent person. SQLite foreign-key enforcement must be enabled and checked for each connection, before starting a transaction; declaring the relationship alone is insufficient. NOT NULL prevents missing required values. Placeholders pass values separately from SQL text.

The left join retains Cy, who has no attendance. COUNT(a.event_id) counts matching non-null event values; COUNT(*) would count Cy’s joined placeholder row as one. The backup API captures the database before synthetic deletion. Restoring into a separate file and reopening it proves these toy rows survived; an integrity check alone would not prove the expected records were present. All files disappear when the temporary-directory context ends. Production recovery additionally needs protected independent storage, retention, authorization and a measured recovery target.

Actual local review: all three Python examples ran with Python 3.13.14 and SQLite 3.50.4; 30 checks passed, including input boundaries, orphan/duplicate/required-field rejection, parameter binding, persisted backup contents and the restored report. This was a local synthetic restore on one machine. It did not test offsite recovery or any of the complete device/platform labs below.

6. Security — 19%¶

Principles and identity¶

Confidentiality limits disclosure, integrity protects correctness/completeness, and availability keeps systems/data usable. Authentication proves an identity; authorization determines allowed actions; accounting/auditing records activity. A login can authenticate successfully yet be correctly denied a protected file because authorization is separate.

Single sign-on lets one authentication session support multiple applications; it is not itself an additional factor. Two passwords are still the same factor type. Non-repudiation concerns evidence connecting an action to an actor; merely enabling logs does not guarantee it. Protect log access, integrity and clock context. Treat personal identifiers and browser/location history as sensitive, and understand consent/purpose limits before collecting or sharing them.

Use least privilege, separation of duties where practical, and layered controls. Physical access can bypass many software controls, so secure devices, screens, ports, removable media, and disposal. Lock unattended systems and report loss promptly.

Device and user hygiene¶

Keep supported software patched, use anti-malware and host/network firewalls appropriately, install from trusted sources, remove unnecessary software, back up, and avoid running routinely as an administrator. Treat unexpected links, attachments, QR codes, support calls, MFA prompts, removable media, and urgent requests as potential social engineering. Verify through an independent trusted channel.

Passwords should be long, unique, private, and stored in a reputable password manager; do not reuse or share them. Multi-factor authentication combines different factor types and reduces—but does not eliminate—account risk. Never approve an unexpected prompt.

Objective 6.3 names history, expiration, complexity and reset processes so you can explain them; their presence is not a universal instruction to force frequent rotation. For centrally verified passwords, NIST SP 800-63B-4 section 3.1.1 rejects routine periodic changes and mandatory character-mixture rules, while requiring a change when compromise is evident. Its minimum is 15 characters for password-only authentication; a password used within MFA may have a minimum of eight. Those are verifier requirements within that standard, not a guarantee that every service follows them or that the minimum is ideal for every account. Use unique generated passwords, secure reset/recovery and the applicable service policy; change default credentials.

Encryption protects readable data with keys. Data at rest includes files/devices/backups; data in transit includes network communications. HTTPS protects the connection to an authenticated web endpoint when correctly used; a VPN protects traffic across a tunnel but does not make every destination trustworthy. Device encryption is weakened if an unlocked session or recovery key is exposed. Protect keys and recovery paths.

Configure a small wireless network¶

Objective 6.5 requires configuration reasoning, beyond recognizing Wi-Fi names. On an authorized spare router, record a recovery method, use its current manufacturer instructions, change the administrative default password and choose a recognizable SSID without personal information. The router administrator password and the Wi-Fi joining passphrase protect different things. Renaming the SSID does not encrypt traffic.

Inspect the supported security modes and client compatibility. WPA/WPA2/WPA3 name security generations; a pre-shared key/passphrase is shared access material, and an open network lacks that password-based access control. Prefer current supported protection such as WPA3 when the router and clients support it. Microsoft’s wireless-security guidance identifies WEP/TKIP warnings as a reason to improve the security settings or equipment. Do not remove encryption just to connect an incompatible device.

Apply one change, reconnect a test client, inspect the negotiated security mode, and verify its intended network/service access. A wrong-passphrase test should fail without locking you out of administration. Record firmware, mode, test results and rollback location; never put actual passwords in a lab report. This configuration lab remains proposed; the review did not alter a router or wireless settings.

Related item: Risk combines likelihood and impact. Security controls should reduce a real risk without making recovery or legitimate use impossible.

Integrated scenarios¶

Scenario 1: New-student workstation¶

A student receives a laptop, monitor, printer, cloud-storage account, and collaboration application. Identify ports/components, select trusted drivers/software, create a unique password and MFA, configure updates and backup, connect Wi-Fi, print a test page, and document the setup. Then diagnose a deliberately disconnected cable, wrong display input, and stale browser cache one at a time.

Scenario 2: Small club data project¶

Model members and events as relational tables with keys, write plain-language queries/reports, trace pseudocode that counts attendance, back up/export the data, and explain which personal fields should not be broadly shared. Compare a local spreadsheet, relational database, and cloud application without declaring one universally best.

Scenario 3: “Internet down” and suspicious message¶

One user cannot open a named site but other apps work. Test device/link, IP/gateway, DNS, browser, destination, and policy in order. During diagnosis, a message asks for an urgent password reset. Preserve the message, do not use its link, verify through an official channel, report it, and document both the technical and security outcomes.

Hands-on labs¶

Device inventory: identify CPU, RAM, storage, NIC, OS, interfaces, peripherals, and capacity units on an authorized device; explain each role.
Notation and rates: convert small binary/decimal/hex values and calculate simple file-transfer estimates while distinguishing bits/bytes and bandwidth/latency.
Peripheral troubleshooting: install or inspect a printer/display/USB device, introduce one safe failure, use the method, verify, and document.
Virtual/cloud comparison: inspect a VM and one SaaS application; map provider/user responsibility, storage, identity, updates, and backup.
Network path and access: compare two internet-service options, diagram device → AP/switch → router/firewall → service, and show DNS lookup as a separate exchange. Test reachable layers with built-in tools; record what each result proves and what remains uncertain.
Software and browser hygiene: inspect trusted source, permissions, version/update, extension access, cache/cookies, password manager, and safe removal.
Logic and data: trace pseudocode with branches/loops, create two related tables, insert test rows, run simple queries, and explain keys and backup.
Security/recovery capstone: on an authorized spare router, distinguish admin password, SSID and Wi-Fi passphrase; configure a supported security mode and verify/roll back with a test client. Harden a disposable account/device, simulate a phishing report and lost file, restore it, and record evidence without secrets.

Use only your own or explicitly authorized devices, accounts, networks, and test data. Do not scan, reset, open, or alter systems belonging to others.

Original knowledge checks¶

In a video call, identify one input, process, output, and storage element.
Why can a touchscreen be both input and output?
Convert binary 1010 to decimal and hexadecimal.
Why is 100 Mbps not the same as 100 MB/s?
Which troubleshooting step should precede changing several settings?
When should a beginner escalate instead of continuing?
Why does more GHz not guarantee a faster computer?
Compare RAM with SSD storage after power loss.
What distinguishes an NVMe SSD from the general SSD category?
What should you check before replacing a failed peripheral?
Why can the same USB-shaped connector provide different capabilities?
Compare a VM and a container at a high level.
Which responsibilities remain with a SaaS user?
Distinguish switch, router, firewall, and access point.
What is the difference between MAC and IP addressing?
Why can DNS failure look like an internet outage?
Which factors make real Wi-Fi speed differ from its advertised maximum?
What does an operating system manage for applications?
Why does a filename extension not prove content or safety?
Distinguish driver, utility, and end-user application.
What does private browsing not hide?
Why should browser-extension permissions be reviewed?
Name two risks of using generative AI output without verification.
Distinguish compiled, interpreted, scripting, and markup languages.
What are variable, constant, array, function, and object used for?
How do branching and looping differ?
Which cases should test a simple input-validation function?
Distinguish pseudocode from a flowchart.
How do primary and foreign keys work together?
Why is non-relational not a synonym for unstructured or faster?
Why can synchronization fail as a backup strategy?
What proves that a backup is useful?
Apply confidentiality, integrity, and availability to a student record.
Distinguish authentication from authorization.
Why are unique long passwords and MFA complementary?
What should you do with an unexpected MFA prompt?
Compare encryption at rest and in transit.
Why does a VPN not make every website or download trustworthy?
What is the safest response to an urgent credential-reset message?
What is unusual about the lifecycle choice shown for FC0-U71 versus FC0-U71-CE?
How is a cellular or fiber internet service different from a local Wi-Fi connection?
Why does changing a wireless SSID not secure the network by itself?

Answers and reasoning¶

Camera/microphone; codec/app/CPU; screen/speaker/network response; recording/cache/file.
It displays information and detects touch/gesture input.
Decimal 10 and hexadecimal A.
There are eight bits per byte: 100 Mbps is 12.5 MB/s before overhead, using decimal units. Keep MB and MiB distinct and account for shared capacity and startup delay.
Identify/reproduce and form an evidence-based theory; preserve a baseline.
When authorization, safety, data risk, access, time, or expertise exceeds the task boundary.
Architecture, cores, memory, storage, thermals, workload, and software also constrain performance.
RAM is volatile working memory; an SSD retains stored data without power.
NVMe describes a high-performance storage protocol/interface path; SSD describes flash storage generally.
Power, cables/ports/input, OS detection, driver/status, configuration, permissions, and a known-good comparison.
Connector form and protocol/version/power/display capabilities are separate.
A VM virtualizes a full OS environment; a container shares the host kernel more directly.
Account/access, data handling, endpoints, configuration, acceptable use, and often backup/export choices.
Local forwarding, inter-network routing, policy enforcement, and wireless attachment.
MAC is local-link interface identity; IP is logical routed addressing.
Connections by address may work while human-readable names fail to resolve.
Standard/band/channel, interference, distance/obstacles, contention, client/AP capability, and upstream service.
Hardware, processes, memory, files/storage, devices, users/security, networking, and interfaces.
It can be renamed or misleading; inspect trusted source, type, signatures/scans, and behavior.
A driver connects OS to hardware; utility maintains/manages; application performs user work.
It does not hide traffic or identity from sites, accounts, networks, employers, or providers.
Extensions can read/change browsing data and expand attack or privacy exposure.
Hallucinated facts, bias, unsafe advice/code, sensitive-data leakage, and rights/copyright issues.
Pretranslated code, runtime-executed code, automation/glue code, and structural description.
Named changing state, intended fixed state, grouped values, reusable behavior, and bundled state/behavior.
A branch selects paths; a loop repeats based on a condition or collection.
Normal, boundary, invalid/type, empty, and repeated cases.
Pseudocode is language-neutral written logic; a flowchart is a graphical control/data-flow representation.
A primary key uniquely identifies a row; a foreign key restricts a relationship to an existing referenced key when enforced. The SQLite example enables enforcement per connection and uses a composite attendance key to prevent duplicates.
Non-relational systems have defined models and tradeoffs; performance depends on workload and design.
Deletion, corruption, or encryption can synchronize to every copy.
A protected, monitored backup that successfully restores within required loss/time limits.
Restrict disclosure, prevent/detect unauthorized change, and keep records accessible to authorized users.
Authentication proves who; authorization decides what that identity may do.
Uniqueness limits damage from reuse, length helps resist guessing, and a different authentication factor adds another barrier. Two passwords are not MFA; routine expiration and character-mixture rules are not universal current best practice.
Deny it, inspect account activity, change credentials through a trusted path if needed, and report it.
At-rest encryption protects stored media/data; in-transit encryption protects communications.
It secures a tunnel segment, not the destination's honesty, content, account, or endpoint.
Do not click; verify through an independently located official channel and report/preserve it.
The official page lists FC0-U71 as no-expiration and FC0-U71-CE as five-year validity; verify purchase/renewal terms.
Internet service connects your network to a provider; local Wi-Fi connects a client to a nearby access point. Strong Wi-Fi signal does not establish working provider service.
An SSID is a network name. Configure supported encryption/authentication and protect both router administration and the Wi-Fi joining credential; then test the actual client connection.

Source and freshness notes¶

CompTIA controls the V6 domain weights, delivery details, languages, passing score, series/lifecycle wording, and official learning options.
Hardware, wireless standards, operating-system behavior, browser/AI features, and security recommendations change; use supported current product documentation for implementation.
This review reads the public exam page and officially linked version 4.0 objectives PDF, with original teaching/examples and a numbered coverage map. It does not reproduce the PDF in full, paid course content or exam questions.

About related items: A Related item: callout adds prerequisite, operational, architectural, or adjacent context that makes the current topic easier to understand. It is useful supporting knowledge, not a claim that the item appears verbatim in the published exam objectives.

Places to learn¶

This is not a complete list and is not meant to be consumed in full. Choose one coherent primary course or book, add hands-on practice and one explanation-led assessment, and use the official objectives as the final scope checklist.

Resource	Access	Estimated time
CompTIA CertMaster Learn	Paid official learning platform	Provider estimate: 25–40 hours; add your own notes/review
CompTIA CertMaster Labs	Paid official labs; availability/bundle varies	Provider estimate: 15–25 hours
CompTIA CertMaster Practice	Paid official adaptive practice	Provider estimate: 10–20 hours
Pluralsight Tech+ FC0-U71 path	Subscription; 9 courses, 3 labs, practice exam	13 listed hours plus 8–15 practice hours
LinkedIn Learning Tech+ Cert Prep	Subscription; Total Seminars; March 13, 2025 release listed	4 hours 50 minutes plus 8–15 practice hours
O'Reilly TOTAL Tech+ FC0-U71	Subscription video	About 5–8 hours estimated; verify current listed runtime
Udemy Tech+ by Mike Chapple	Paid marketplace course	Current runtime unverified (page blocked); budget separate lab/review time
MeasureUp Tech+ practice test	Paid; 171-question bank listed	About 4–8 hours across attempts and explanation review
Technical Institute of America full course	Free YouTube course	Verify current video runtime; allow 8–15 hours with notes and labs

The CertMaster estimates above are shown on the current Tech+ page; they are provider estimates, not personal completion promises. The Pluralsight path and LinkedIn/MeasureUp public metadata were rechecked. O'Reilly and Udemy blocked automated access; the YouTube fetch exposed only a short shell, so video content/runtime were not verified. No paid lesson interiors were reviewed.

Troubleshooting method: Damon M. Garn’s December 18, 2024 CompTIA article supports evidence gathering, a rollback plan and full functional verification. Its opening list splits planning and implementation, while its body combines them; use objective 1.4 for Tech+ scope and practice the actions rather than a blog’s step count.
Focused practice: pair the Python/SQLite references above with the original examples, and the browser/wireless references with authorized device labs. Product-specific syntax is implementation practice, not an extra exam requirement.

No exact current Whizlabs Tech+ product was independently verified. Practice questions should diagnose concepts and explain alternatives, not promise recalled exam content. Provider prices, bundles, question counts, runtimes, access, and revision dates are volatile—verify before purchase.