N10-010 — CompTIA Network+ V10 Exam Blueprint
Practical exam blueprint for CompTIA Network+ V10 (N10-010) candidates reviewing networking concepts, implementation, security, operations, and troubleshooting.
How to Use This Exam Blueprint
Use this independent Exam Blueprint as a practical readiness map for CompTIA Network+ V10 (N10-010). It is designed to help you confirm that you can recognize networking concepts, make implementation decisions, interpret symptoms, and select appropriate troubleshooting steps.
For each area, ask three questions:
- Can I explain it clearly?
- Can I apply it in a scenario?
- Can I troubleshoot it when the symptom is indirect?
Mark an area as ready only when you can handle diagrams, short scenarios, command output, and “best next step” decisions without relying on memorized definitions alone.
Topic-Area Readiness Table
| Readiness area | What to review | You are ready when you can… |
|---|---|---|
| Network models and encapsulation | OSI layers, TCP/IP model, frames, packets, segments, ports, sockets, encapsulation and decapsulation | Map a symptom, protocol, device, or tool to the correct layer and explain what changes as data moves across a network |
| IPv4 and IPv6 addressing | CIDR, subnet masks, default gateways, private/public addressing, APIPA/link-local, IPv6 notation, SLAAC/DHCPv6 concepts | Determine whether two hosts are on the same subnet and identify addressing errors from sample host configurations |
| Subnetting | Network ID, broadcast address, usable host range, borrowed bits, route summarization concepts | Calculate subnets quickly and avoid off-by-one errors under time pressure |
| Switching | MAC tables, VLANs, trunks, access ports, STP concepts, link aggregation, port security, PoE | Diagnose VLAN mismatches, loops, incorrect port modes, and local switching issues from symptoms |
| Routing | Static routes, default routes, dynamic routing concepts, next hop, route selection, longest-prefix match | Explain why traffic takes a path, why it cannot reach another network, and what route is missing or preferred |
| Wireless networking | Bands, channels, SSIDs, BSSIDs, roaming, interference, authentication, antenna concepts, site surveys | Choose placement, channel, security, and troubleshooting steps for common wireless performance and connectivity problems |
| Network services | DNS, DHCP, NTP, NAT/PAT, SNMP, syslog, IPAM, directory and authentication services | Distinguish name resolution, address assignment, time synchronization, monitoring, and translation failures |
| Physical infrastructure | Copper, fiber, transceivers, patch panels, racks, cable management, grounding, environmental concerns | Select media and tools for a scenario and identify likely physical-layer causes |
| Cloud and virtualization networking | Virtual switches, virtual NICs, overlays, SDN concepts, cloud subnets, route tables, security groups, load balancers, VPNs | Translate traditional networking concepts into virtual and cloud-based designs without confusing control-plane and data-plane roles |
| Security controls | Firewalls, ACLs, IDS/IPS, VPNs, NAC, 802.1X, segmentation, least privilege, secure protocols | Choose the control that best reduces a stated risk and identify where it should be placed |
| Network operations | Monitoring, baselines, logging, documentation, configuration management, change control, backups | Identify what to monitor, what to document, and how to reduce operational risk |
| Troubleshooting | Methodical troubleshooting, command-line tools, packet captures, cable tools, logs, escalation | Move from symptom to likely cause without skipping validation or documentation |
| Resilience and performance | Redundancy, failover, load balancing, QoS, latency, jitter, packet loss, throughput, MTU | Match performance symptoms to bottlenecks and select appropriate availability or optimization techniques |
Core Networking Concepts Checklist
Models, Layers, and Traffic Flow
- Explain the difference between a frame, packet, segment, and datagram.
- Identify which OSI layer is involved when a question mentions MAC addresses, IP addresses, ports, encryption, routing, or applications.
- Describe encapsulation as traffic moves from an application to the wire.
- Explain why switches primarily forward based on MAC addresses and routers forward based on IP addresses.
- Distinguish unicast, broadcast, multicast, and anycast concepts.
- Explain collision domains and broadcast domains in modern switched networks.
- Recognize how ARP supports IPv4 local network communication.
- Recognize how Neighbor Discovery supports IPv6 local network communication.
- Explain the purpose of MTU and why fragmentation or dropped packets can occur.
- Identify when a symptom is likely physical, data link, network, transport, or application related.
OSI Layer Readiness Map
| Layer | Primary concern | Common examples | Scenario cues |
|---|---|---|---|
| 7 Application | User-facing network services | HTTP/S, DNS, SMTP, DHCP, SNMP | “Website fails by name,” “mail cannot send,” “DHCP not assigning” |
| 6 Presentation | Format, encryption, encoding | TLS, certificates, compression | “Certificate warning,” “encryption mismatch” |
| 5 Session | Session establishment and persistence | Authentication sessions, RPC concepts | “Session drops,” “re-authentication required” |
| 4 Transport | Ports, reliability, flow | TCP, UDP, port numbers | “Port blocked,” “connection refused,” “UDP stream choppy” |
| 3 Network | Logical addressing and routing | IPv4, IPv6, ICMP, routers | “Can reach local subnet but not remote network” |
| 2 Data Link | Local delivery and switching | Ethernet, VLANs, MAC, STP, Wi-Fi framing | “Wrong VLAN,” “loop,” “MAC flapping” |
| 1 Physical | Signals and media | Cables, optics, RF, pinouts | “No link light,” “bad cable,” “weak signal” |
Addressing and Subnetting Readiness
IPv4 Skills
- Convert between dotted-decimal subnet masks and CIDR notation.
- Identify network, broadcast, first usable, and last usable IPv4 addresses.
- Determine whether two IPv4 addresses are in the same subnet.
- Recognize private IPv4 ranges and why they commonly require NAT/PAT for internet access.
- Recognize APIPA/link-local symptoms when DHCP fails.
- Explain the difference between a default gateway and a DNS server.
- Understand why overlapping IP ranges can break routing, VPNs, and cloud connectivity.
- Interpret host configuration output and spot wrong IP, mask, gateway, or DNS values.
IPv6 Skills
- Recognize compressed IPv6 notation.
- Identify the role of link-local addresses.
- Distinguish IPv6 concepts from IPv4 habits, especially the lack of broadcast in IPv6.
- Explain when SLAAC, DHCPv6, or static addressing may be used.
- Recognize dual-stack as a transition or coexistence approach.
- Avoid assuming NAT is required in IPv6 designs.
Subnetting Formulas to Know
For traditional IPv4 subnetting, the common usable-host calculation is:
\[ \text{Usable hosts} = 2^{h} - 2 \]Where \(h\) is the number of host bits. Be aware that special-purpose subnets, point-to-point addressing, and host routes may be treated differently depending on context.
To estimate transfer time:
\[ \text{Transfer time} \approx \frac{\text{data size in bits}}{\text{effective throughput in bits per second}} \]Use this as an approximation. Real throughput is affected by protocol overhead, congestion, retransmissions, and device limitations.
Fast Subnetting Self-Check
| Prompt | You should be able to answer |
|---|---|
| A host has an IP address, mask, gateway, and DNS server. What is wrong? | Identify whether the issue is local addressing, gateway reachability, or name resolution |
| A subnet needs more hosts. What changes? | Choose a larger host space and understand the routing impact |
| A design needs more subnets. What changes? | Borrow more bits and understand smaller host ranges |
| Two sites use overlapping private ranges. What breaks? | VPN routing, NAT design, route selection, and address uniqueness |
| A host can ping its gateway but not the internet. What next? | Check routing, NAT, firewall policy, upstream connectivity, and DNS depending on symptom |
Protocols, Ports, and Services Checklist
You do not need to memorize ports in isolation. Know what the service does, whether it commonly uses TCP, UDP, or both, and what a failure looks like.
| Service/protocol | Common port(s) | Readiness cue |
|---|---|---|
| FTP | TCP 20/21 | Legacy file transfer; understand control/data channel concept |
| SSH / SFTP | TCP 22 | Secure remote administration and secure file transfer |
| Telnet | TCP 23 | Insecure remote terminal; recognize why it should be avoided |
| SMTP | TCP 25 | Mail transfer between servers |
| DNS | TCP/UDP 53 | Name resolution; TCP may appear for larger transfers or zone-related operations |
| DHCP | UDP 67/68 | Automatic IPv4 addressing; know the basic discovery process |
| TFTP | UDP 69 | Simple unauthenticated file transfer often used in infrastructure scenarios |
| HTTP | TCP 80 | Unencrypted web traffic |
| POP3 | TCP 110/995 | Mail retrieval; secure variant commonly uses TLS |
| NTP | UDP 123 | Time synchronization; important for logs and authentication |
| IMAP | TCP 143/993 | Mail access/synchronization; secure variant commonly uses TLS |
| SNMP | UDP 161/162 | Monitoring and traps/informs |
| LDAP / LDAPS | TCP/UDP 389, TCP 636 | Directory access and secure directory access |
| HTTPS | TCP 443 | Encrypted web traffic and many APIs |
| SMB | TCP 445 | File sharing and Windows network services |
| Syslog | UDP/TCP 514 | Log forwarding; transport depends on implementation |
| RDP | TCP/UDP 3389 | Remote desktop access |
Switching, VLANs, and Local Network Implementation
Switching Checklist
- Explain how a switch learns MAC addresses.
- Describe what happens when a switch receives an unknown unicast frame.
- Distinguish access ports from trunk ports.
- Explain VLAN tagging and why mismatched trunk settings cause outages.
- Recognize symptoms of native VLAN or allowed VLAN mismatches.
- Explain why inter-VLAN routing requires a Layer 3 function.
- Describe Spanning Tree Protocol concepts at a high level and why loops are dangerous.
- Recognize broadcast storm symptoms.
- Explain link aggregation and why both ends must be compatible.
- Understand port security concepts and common violation symptoms.
- Recognize PoE use cases and basic troubleshooting concerns.
VLAN Decision Checks
| Scenario cue | Likely focus | Best decision path |
|---|---|---|
| Host gets an address from the wrong subnet | VLAN assignment or DHCP scope issue | Check switchport VLAN, trunk tagging, DHCP relay, and scope mapping |
| Two hosts on same VLAN cannot communicate | Layer 2 or host firewall issue | Check link, switchport status, MAC table, host firewall, duplicate IPs |
| Host reaches same VLAN but not another VLAN | Routing or ACL issue | Check default gateway, inter-VLAN routing, route table, and policy |
| New AP works but only one SSID maps correctly | VLAN trunking issue | Verify allowed VLANs, SSID-to-VLAN mapping, and switchport mode |
| Network becomes unstable after cabling change | Loop or STP issue | Check redundant links, STP state, and unmanaged switch placement |
Routing and WAN Readiness
Routing Concepts
- Explain the purpose of a default route.
- Recognize longest-prefix match as a route-selection concept.
- Distinguish static routing from dynamic routing.
- Compare internal routing and external routing at a high level.
- Understand next hop, route metric, route redistribution concept, and route summarization concept.
- Explain why missing return routes can cause one-way or failed communication.
- Recognize asymmetric routing as a troubleshooting concern.
- Understand basic high-availability routing concepts such as redundant gateways or failover paths.
- Identify when NAT/PAT is part of the path and when it is not.
- Explain the difference between a routing issue and a firewall policy issue.
WAN and Site Connectivity Checklist
- Compare private WAN, broadband, cellular, satellite, and VPN-based connectivity at a conceptual level.
- Recognize site-to-site VPN versus remote-access VPN use cases.
- Understand split tunnel versus full tunnel as design choices.
- Identify where encryption, authentication, and routing decisions apply in a VPN.
- Recognize latency-sensitive traffic and why link quality matters.
- Understand redundancy options such as multiple providers, multiple paths, and failover links.
- Explain why overlapping address spaces complicate site-to-site connectivity.
Wireless Networking Checklist
Wireless Fundamentals
- Compare 2.4 GHz, 5 GHz, and 6 GHz bands at a practical level.
- Understand channel overlap and interference.
- Distinguish signal strength from signal quality.
- Recognize common sources of RF interference.
- Explain SSID, BSSID, roaming, and controller-based management concepts.
- Identify when a site survey or spectrum analysis is appropriate.
- Understand antenna directionality at a high level.
- Recognize the effect of building materials, distance, and client density.
- Compare personal and enterprise wireless authentication models.
- Understand why shared passwords may not be appropriate for enterprise access.
Wireless Scenario Checks
| Scenario | Likely cause area | What to verify |
|---|---|---|
| Users connect near the AP but drop in conference rooms | Coverage, attenuation, capacity | AP placement, power levels, client density, building materials |
| Good signal but poor throughput | Interference or congestion | Channel utilization, co-channel interference, band selection |
| Only some devices cannot connect | Client capability or authentication | Supported bands, security mode, certificates, credentials |
| Guest Wi-Fi reaches internal resources | Segmentation failure | VLANs, firewall rules, captive portal, ACLs |
| Roaming users experience call drops | Roaming design and QoS | AP overlap, controller settings, QoS markings, client behavior |
Network Services and Name Resolution
DNS Readiness
- Explain recursive versus authoritative DNS roles.
- Recognize A, AAAA, CNAME, MX, TXT, PTR, and SRV record use cases.
- Understand forward and reverse lookup concepts.
- Explain TTL at a practical level.
- Diagnose “can ping IP but not hostname” as a likely name-resolution issue.
- Recognize split DNS or internal/external DNS design concepts.
- Understand why stale DNS, wrong search suffixes, or wrong DNS servers create confusing symptoms.
DHCP Readiness
- Explain the basic DHCP discovery and lease process.
- Identify DHCP scope, exclusion, reservation, and lease concepts.
- Recognize why DHCP relay/helper configuration is needed across subnets.
- Diagnose APIPA/link-local assignment as a likely DHCP reachability problem.
- Distinguish a DHCP problem from a DNS or gateway problem.
- Understand risks from rogue DHCP servers.
NAT, Time, and Monitoring Services
- Explain static NAT, dynamic NAT, and PAT concepts.
- Identify when NAT hides internal addressing and when it does not provide complete security by itself.
- Explain why accurate time matters for logs, certificates, authentication, and incident investigation.
- Recognize SNMP polling versus trap/inform style notifications.
- Understand syslog collection and why centralized logs help troubleshooting.
Network Security Exam Blueprint
Security Controls
| Control or concept | What to know | Scenario cue |
|---|---|---|
| Firewall | Permit/deny traffic based on rules and context | “Block this port,” “allow only this subnet,” “inspect traffic” |
| ACL | Filter traffic, often near routers, switches, or firewalls | “Only finance VLAN should reach server subnet” |
| IDS/IPS | Detect or prevent suspicious activity | “Alert on attack patterns” or “block malicious traffic inline” |
| VPN | Encrypted tunnel for remote or site connectivity | “Secure traffic over untrusted network” |
| NAC / 802.1X | Control network access based on identity/posture | “Only managed devices should connect” |
| Segmentation | Limit lateral movement and scope | “Separate guest, user, server, and management traffic” |
| AAA | Authentication, authorization, accounting | “Centralize admin login and track activity” |
| MFA | Add authentication factor | “Reduce risk from stolen passwords” |
| Certificates / PKI | Trust, encryption, identity | “Certificate warning,” “mutual authentication,” “TLS issue” |
| Secure protocols | Replace insecure management and transfer methods | “Use SSH instead of Telnet,” “HTTPS instead of HTTP” |
Security Readiness Prompts
- Choose where to place a firewall, ACL, IDS/IPS, or VPN gateway in a diagram.
- Explain why segmentation reduces blast radius.
- Identify management-plane protections for switches, routers, firewalls, and wireless controllers.
- Recognize insecure protocols and select safer alternatives.
- Understand basic hardening: disable unused ports, change defaults, restrict admin access, update firmware/software, and log administrative actions.
- Distinguish authentication from authorization.
- Recognize social engineering, rogue devices, evil twin APs, credential theft, and misconfiguration risks.
- Explain why physical security still matters for network closets, ports, cabling, and devices.
- Understand least privilege and need-to-know access in network policy design.
Cloud, Virtualization, and Modern Network Architecture
Virtual and Cloud Networking Checklist
- Explain virtual switches, virtual NICs, and port groups or logical network segments.
- Understand overlay networking at a conceptual level.
- Distinguish software-defined networking control plane from data plane.
- Recognize cloud equivalents of subnets, route tables, security filtering, NAT, VPNs, and load balancers.
- Understand east-west versus north-south traffic.
- Explain why cloud security filtering may occur at multiple layers.
- Recognize hybrid connectivity issues: overlapping CIDR ranges, missing routes, DNS forwarding, and firewall policy.
- Understand container networking at a high level if presented in a scenario.
- Identify when load balancing, autoscaling, or redundancy changes traffic flow.
- Recognize that cloud networking still requires sound IP, routing, DNS, and security fundamentals.
Architecture Decision Checks
| Requirement | Likely design focus |
|---|---|
| Isolate development, production, and guest users | Segmentation, VLANs, subnets, firewall policy |
| Support remote workers securely | Remote-access VPN, MFA, endpoint posture, split/full tunnel decision |
| Connect two sites securely | Site-to-site VPN or private WAN concept, routing, encryption, address planning |
| Improve web application availability | Load balancing, health checks, redundant paths, DNS considerations |
| Reduce lateral movement | Microsegmentation, ACLs, firewalls, NAC, least privilege |
| Improve visibility | Flow logs, packet capture, syslog, SNMP, SIEM integration |
| Prepare for device failure | Redundant links, redundant devices, failover, backup configurations |
Operations, Monitoring, and Documentation
Operational Readiness Checklist
- Interpret basic network diagrams and identify missing information.
- Create or review an IP address plan.
- Maintain device inventory, interface labels, cable labels, and rack diagrams.
- Understand configuration backup and restore importance.
- Recognize the purpose of baselines for bandwidth, latency, errors, CPU, memory, and wireless utilization.
- Explain alert fatigue and why thresholds should be meaningful.
- Identify useful log sources for troubleshooting and security review.
- Understand change management: request, approval, implementation, backout, validation, and documentation.
- Explain why maintenance windows reduce business risk.
- Distinguish incident, problem, and change concepts at a practical level.
- Recognize when escalation is appropriate and what information should be included.
Monitoring and Observability Tools
| Tool or artifact | What it helps answer |
|---|---|
| Interface counters | Are there errors, drops, saturation, or duplex/speed issues? |
| Logs | What changed, failed, authenticated, or was blocked? |
| SNMP monitoring | Are devices reachable and healthy over time? |
| Flow data | Who is talking to whom, using which protocols, and how much? |
| Packet capture | What is actually on the wire? |
| Baseline reports | Is this behavior normal or abnormal? |
| Wireless analyzer | Are channels, signal, noise, and utilization acceptable? |
| Configuration archive | What changed between working and broken states? |
Troubleshooting Checklist
Methodical Troubleshooting
Be ready to follow a disciplined process instead of jumping to the most familiar fix.
- Identify the problem and gather symptoms.
- Determine scope: one user, one VLAN, one site, one application, or all users.
- Check recent changes.
- Establish a likely theory.
- Test the theory with the least disruptive method.
- Create a plan of action and consider impact.
- Implement the fix or escalate with evidence.
- Verify full system functionality.
- Apply preventive measures when appropriate.
- Document findings, actions, and outcomes.
Command Recognition Checks
Know what each command or tool is used for and what kind of evidence it provides.
ipconfig /all Show Windows IP configuration details
ping Test basic reachability and latency
tracert / traceroute Show path toward a destination
nslookup / dig Test DNS queries and responses
arp View or troubleshoot local IP-to-MAC resolution
route / ip route View routing table information
netstat / ss View connections, listening ports, and socket details
tcpdump / Wireshark Capture and inspect packets
Hardware and Physical Tools
| Tool | Readiness expectation |
|---|---|
| Cable tester | Identify wiring faults and continuity issues |
| Certifier | Validate cabling against performance requirements |
| Tone generator and probe | Trace cable runs |
| Loopback plug | Test interface transmit/receive functionality |
| Crimper | Terminate copper connectors |
| Punchdown tool | Terminate cabling on blocks or patch panels |
| OTDR | Troubleshoot fiber distance/reflection issues |
| Light meter | Check fiber signal levels |
| Wi-Fi analyzer | Inspect wireless signal, channels, and interference |
| Spectrum analyzer | Identify RF interference beyond Wi-Fi-only views |
Scenario and Decision-Point Checks
| Symptom | First likely area | Do not confuse it with… |
|---|---|---|
| Host has a link-local IPv4 address | DHCP failure or unreachable DHCP service | DNS failure |
| Host can ping IP but not hostname | DNS resolution problem | Default gateway failure |
| Host can reach local subnet but not remote networks | Default gateway, routing, or firewall issue | Bad switchport only |
| All users on one VLAN fail | VLAN, trunk, SVI/router interface, DHCP relay, or ACL | Individual host misconfiguration |
| One application fails but others work | Port, firewall, DNS alias, certificate, or application service | Total network outage |
| Intermittent outages after adding a switch | Loop, STP issue, bad cable, or duplicate IP | ISP outage by default |
| Slow voice/video but web browsing works | Latency, jitter, packet loss, QoS, congestion | DNS only |
| Wireless works in one area but not another | Coverage, interference, roaming, AP placement | WAN routing |
| VPN connects but resources are unreachable | Routes, split tunnel, DNS, firewall, overlapping subnets | Authentication only |
| Logs have wrong times | NTP/time sync issue | SIEM failure only |
| Duplicate IP warnings | Static/DHCP overlap or rogue device | Incorrect subnet mask only |
| Certificate warning | Trust chain, hostname mismatch, expiration, TLS inspection, or wrong certificate | DHCP issue |
Performance and Resiliency Readiness
Performance Concepts
- Distinguish bandwidth from throughput.
- Explain latency, jitter, packet loss, retransmissions, and congestion.
- Recognize why duplex or speed mismatches can degrade performance.
- Identify bottlenecks across client, access switch, uplink, firewall, WAN, server, and application layers.
- Understand QoS as traffic classification, marking, queuing, and prioritization concepts.
- Recognize that encryption, inspection, and tunneling can add overhead.
- Understand MTU-related symptoms, especially when tunnels are involved.
- Explain why wireless throughput differs from theoretical maximums.
Resiliency Concepts
- Identify single points of failure in a diagram.
- Explain redundant links, redundant devices, redundant power, and failover.
- Understand link aggregation as both capacity and resiliency depending on design.
- Recognize load balancer use cases and health-check concepts.
- Distinguish backup connectivity from active-active designs at a high level.
- Understand configuration backups and disaster recovery documentation.
- Explain why redundancy must be tested, not assumed.
Common Weak Areas and Exam Traps
| Weak area | Why candidates miss it | Readiness fix |
|---|---|---|
| DNS versus gateway confusion | Both can make “the internet is down” reports sound similar | Test by IP, then by name; separate routing from resolution |
| Subnet off-by-one errors | Network and broadcast addresses are counted as usable by mistake | Practice network ID, broadcast, and host range calculations |
| VLAN trunk/access mismatch | Symptoms may look like DHCP or routing failure | Trace VLAN path end to end |
| ACL direction and placement | Correct rule in wrong place may not work | Identify source, destination, protocol, port, and direction |
| NAT versus firewall | NAT changes addresses; firewall policy allows or blocks | Ask whether the issue is translation, permission, or both |
| Wireless signal assumptions | Strong signal does not always mean clean channel | Consider noise, interference, utilization, and client density |
| Routing return path | Forward path exists but response path is missing | Check routes on both sides |
| Layer jumping | Candidates troubleshoot applications before checking connectivity | Work from scope and evidence, not guesses |
| Memorized port numbers only | Scenario asks what the service does or why it fails | Link port to protocol behavior and symptom |
| Ignoring recent changes | Many outages follow a change | Ask what changed before assuming hardware failure |
| Overlooking time sync | Authentication and logs can fail when time is wrong | Check NTP and clock consistency |
| Assuming cloud is different networking | Cloud abstractions still use IP, routes, DNS, and policy | Translate concepts into cloud terms |
“Can You Do This?” Readiness Checklist
Mark each item only when you can do it without notes.
Addressing and Routing
- Given an IP address and CIDR mask, identify the subnet and usable range.
- Decide whether a host’s gateway is valid for its subnet.
- Explain why a host can reach local resources but not remote resources.
- Identify a missing route from a simple routing table.
- Explain how NAT/PAT changes traffic flow.
- Detect overlapping subnet problems in a site-to-site scenario.
Switching and Wireless
- Determine whether a switchport should be access or trunk.
- Identify likely causes of a VLAN-specific outage.
- Explain why a loop can disrupt an entire segment.
- Choose wireless troubleshooting steps for interference, low coverage, and authentication failures.
- Map SSIDs to VLANs in a segmented wireless design.
Services and Security
- Diagnose DHCP versus DNS versus gateway symptoms.
- Choose secure replacements for insecure protocols.
- Place a firewall, ACL, VPN, or IDS/IPS in a scenario.
- Explain segmentation for users, servers, guests, and management networks.
- Identify where logs should be collected for an investigation.
Operations and Troubleshooting
- Select the best tool for cable, wireless, routing, DNS, or packet-level evidence.
- Interpret simple command output and identify the next test.
- Build a troubleshooting sequence that validates each assumption.
- Identify what should be documented after a change or incident.
- Explain how monitoring baselines help identify abnormal behavior.
Final-Week Review Checklist
Seven to Five Days Before the Exam
- Revisit subnetting until it is fast and consistent.
- Review common protocols and ports by scenario, not just number.
- Redraw OSI and TCP/IP models from memory and attach tools, protocols, and devices to each layer.
- Practice distinguishing DNS, DHCP, default gateway, NAT, firewall, and routing failures.
- Review switching and VLAN scenarios, especially trunks and inter-VLAN routing.
- Review wireless authentication, interference, and coverage troubleshooting.
- Review security controls and when to choose each one.
Four to Two Days Before the Exam
- Work mixed scenarios that force you to identify the best next step.
- Review command-line tools and what evidence each provides.
- Review physical tools and media types.
- Practice reading small network diagrams.
- Review cloud, virtualization, and SDN concepts at a practical level.
- Make a one-page sheet of weak topics, then retire it after active recall.
Day Before the Exam
- Do a light pass through ports, subnetting, wireless, VLANs, routing, and troubleshooting.
- Avoid cramming brand-new topics late.
- Review common traps: DNS versus gateway, ACL placement, VLAN tagging, and return routes.
- Sleep and prepare logistics.
Exam-Day Mental Checklist
- Read the full scenario before choosing an answer.
- Identify the scope: one device, one subnet, one site, or all users.
- Look for recent changes.
- Separate symptoms from causes.
- Eliminate answers that fix a different layer or different problem.
- Prefer the least disruptive valid troubleshooting step when the prompt asks for the next action.
- Watch for words such as “most likely,” “best,” “first,” and “next.”
Practical Next Step
Use this checklist to identify your weakest three readiness areas for CompTIA Network+ V10 (N10-010). Review those topics, then practice mixed networking scenarios that require subnetting, tool selection, security control placement, and troubleshooting decisions in the same session.