N10-009 — CompTIA Network+ (N10-009) Exam Blueprint

How to Use This Exam Blueprint

Use this page as a practical readiness map for the CompTIA Network+ (N10-009) exam. It is organized around the major skills a Network+ candidate is expected to demonstrate: networking concepts, implementations, operations, security, and troubleshooting.

For each area, ask:

• Can I explain the concept without notes?
• Can I recognize it in a scenario?
• Can I choose the best tool, protocol, device, or configuration approach?
• Can I eliminate plausible but wrong answers?
• Can I troubleshoot from symptoms instead of memorized definitions?

If an item feels familiar but you cannot apply it to a scenario, mark it for review.

Topic-Area Readiness Map

High-Priority “Can You Do This?” Checklist

Before final review, you should be able to do the following without relying on answer memorization.

Core Networking Tasks

• Explain the purpose of each OSI layer and identify where common devices and protocols operate.
• Compare TCP and UDP using reliability, sequencing, acknowledgments, latency, and common use cases.
• Match common ports to services such as DNS, DHCP, HTTP, HTTPS, SSH, RDP, SMTP, IMAP, POP3, SNMP, NTP, LDAP, and SMB.
• Read IPv4 CIDR notation and determine network, broadcast, usable host range, and host capacity.
• Identify when IPv6 link-local, global unicast, multicast, and loopback addresses are used.
• Explain default gateway behavior and why hosts on different subnets need routing.
• Distinguish routing, switching, bridging, NAT, PAT, and firewall filtering.
• Explain what happens when a client obtains an address through DHCP.
• Explain how DNS resolves names and when caching can cause confusing symptoms.
• Interpret basic route table output and identify the default route.
• Identify causes of latency, jitter, packet loss, duplex mismatch, and congestion.
• Choose between copper, fiber, and wireless media based on distance, interference, speed, cost, and environment.

Implementation and Configuration Tasks

• Choose an appropriate cable or connector for a scenario.
• Identify where to use straight-through, crossover, rollover, console, patch, and fiber cabling concepts.
• Compare multimode and single-mode fiber at a practical level.
• Explain VLAN purpose and identify when a trunk port is required.
• Distinguish access ports, trunk ports, native VLAN concepts, and inter-VLAN routing.
• Explain link aggregation, redundancy, and loop-prevention goals.
• Compare static routing, dynamic routing, and default routing.
• Recognize routing protocol concepts such as administrative distance, metrics, convergence, and neighbor relationships.
• Compare private WAN, broadband, cellular, satellite, and VPN connectivity choices.
• Choose wireless standards, frequencies, channels, antennas, and security settings for a scenario.
• Explain how virtualization, containers, cloud networking, and software-defined networking affect network design.
• Identify where load balancers, proxies, IDS/IPS, firewalls, and VPN concentrators fit.

Operations and Security Tasks

• Identify which network document is needed: topology diagram, rack diagram, IPAM record, asset inventory, baseline, or change record.
• Choose appropriate monitoring methods, logs, metrics, alerts, and thresholds.
• Explain SNMP, syslog, NetFlow-like flow data, packet capture, and event correlation at a practical level.
• Distinguish backup, redundancy, high availability, fault tolerance, and disaster recovery.
• Apply least privilege, segmentation, secure management, and hardening principles.
• Compare authentication factors and common identity/access controls.
• Identify secure versus insecure protocol choices.
• Recognize common attack types and select appropriate mitigations.
• Explain why physical security, environmental controls, and cable management matter.
• Use a structured troubleshooting process instead of jumping to a fix.

Networking Concepts Checklist

Models, Encapsulation, and Traffic Flow

Common Ports and Protocols

You do not need to think like a port-number database, but you should recognize frequently tested services and whether they are secure, insecure, connection-oriented, or name/address related.

TCP, UDP, and Transport Behavior

IPv4 Addressing and Subnetting

You should be able to work subnetting questions quickly and accurately.

Subnetting formulas to know:

Use caution with special-purpose subnets in real environments. For exam readiness, focus on understanding the general method and recognizing scenario intent.

IPv6 Readiness

Routing and Switching Concepts

Network Implementation Checklist

Cables, Connectors, and Physical Media

Network Devices and Placement

VLAN and Segmentation Checklist

• Can you explain why VLANs reduce broadcast domains?
• Can you identify when two hosts in different VLANs need routing?
• Can you distinguish an access port from a trunk port?
• Can you interpret a scenario where the wrong VLAN causes loss of connectivity?
• Can you identify why voice VLANs are commonly used?
• Can you explain how segmentation improves security and performance?
• Can you recognize when firewall rules are needed between segments?
• Can you identify management, guest, server, user, and IoT network separation scenarios?

Wireless Networking Checklist

WAN, Remote Access, and Internet Connectivity

Cloud, Virtualization, and Modern Network Concepts

Network Operations Checklist

Documentation and Operational Artifacts

Monitoring, Metrics, and Logs

Availability, Redundancy, and Recovery

RPO and RTO concept check:

• RPO asks: “How much data can we afford to lose?”
• RTO asks: “How long can the service be unavailable?”

Change, Configuration, and Governance

• Can you identify why unauthorized changes cause outages?
• Can you explain change request, approval, testing, implementation, validation, and rollback?
• Can you choose a maintenance window for risky work?
• Can you explain configuration backup and version control at a practical level?
• Can you identify why baselines matter before and after a change?
• Can you recognize when escalation is needed?
• Can you distinguish a standard change from an emergency change conceptually?
• Can you explain why documentation must be updated after implementation?

Network Security Checklist

Security Principles

Network Access and Identity Controls

Secure and Insecure Protocol Choices

Threats and Attack Recognition

Firewall, ACL, and Segmentation Decision Checks

Troubleshooting Checklist

Structured Troubleshooting Method

Know the sequence conceptually and use it in scenarios:

1. Identify the problem.
2. Establish a theory of probable cause.
3. Test the theory.
4. Establish a plan of action.
5. Implement the solution or escalate.
6. Verify full system functionality.
7. Document findings, actions, and outcomes.

Readiness cue: if an answer jumps to replacing hardware before gathering evidence, it is often not the best troubleshooting choice.

Tool and Command Selection

Example command-review block:

ping <destination>
tracert <destination>        # Windows path test
traceroute <destination>     # Linux/macOS path test
ipconfig /all                # Windows IP, gateway, DNS, DHCP details
ip addr                      # Linux interface addressing
ip route                     # Linux route table
nslookup <hostname>
dig <hostname>
arp -a
netstat -ano                 # Windows connections/listeners
ss -tulpen                   # Linux listeners/connections

Symptom-to-Cause Readiness Table

Layered Troubleshooting Prompts

Calculation and Interpretation Checks

IPv4 Subnetting Quick Table

Practice prompts:

• Given 192.168.10.0/26, can you list the subnet ranges inside 192.168.10.0/24?
• Given 10.1.5.77/28, can you find the network and broadcast address?
• Given two IP/mask pairs, can you tell whether they are on the same subnet?
• Given a required host count, can you choose an efficient prefix length?
• Given a route table, can you identify the most specific matching route?

Wireless Channel and Frequency Checks

Throughput, Latency, and Capacity Checks

Scenario and Decision-Point Checks

Service Selection Scenarios

Troubleshooting Decision Path

    flowchart TD
	    A[User reports network problem] --> B{One user or many?}
	    B -->|One user| C[Check local link, IP config, VLAN, DNS]
	    B -->|Many users| D{Same area or different areas?}
	    D -->|Same area| E[Check switch, AP, VLAN, DHCP scope, local uplink]
	    D -->|Different areas| F[Check core routing, firewall, WAN, DNS, shared services]
	    C --> G{Can reach IP address?}
	    G -->|Yes, but not name| H[Focus on DNS]
	    G -->|No| I[Focus on IP, gateway, route, firewall, physical path]
	    E --> J[Verify recent changes and device health]
	    F --> J
	    H --> K[Verify fix and document]
	    I --> K
	    J --> K

“Best Answer” Judgment Prompts

Common Weak Areas and Traps

Conceptual Traps

• Confusing DNS failure with total connectivity failure.
• Treating TCP and UDP as “secure” versus “insecure” instead of reliable versus connectionless behavior.
• Forgetting that switches forward frames using MAC addresses, while routers forward packets using IP addresses.
• Assuming VLANs can communicate without a Layer 3 device or service.
• Confusing NAT with firewall filtering.
• Thinking hidden SSID is strong wireless security.
• Treating more AP power as the universal fix for wireless coverage.
• Ignoring client device transmit power in wireless design.
• Confusing bandwidth with throughput.
• Confusing latency with jitter.
• Assuming encryption automatically provides authorization.
• Forgetting that time synchronization affects log correlation.
• Choosing replacement before testing a theory.

Subnetting Traps

• Misreading the prefix length.
• Forgetting that block size changes by octet.
• Including network and broadcast addresses as normal hosts in typical IPv4 subnet questions.
• Choosing a subnet that does not provide enough usable host addresses.
• Failing to identify whether two hosts are on the same subnet.
• Overlooking the default gateway’s subnet.
• Forgetting longest-prefix match when reading routes.

Security Traps

• Opening broad firewall rules when a narrow rule would satisfy the requirement.
• Allowing management access from user or guest networks.
• Using insecure management protocols when secure alternatives are expected.
• Treating guest Wi-Fi as safe without segmentation.
• Forgetting physical security for network closets, ports, and devices.
• Ignoring default credentials and unused services.
• Confusing authentication with authorization.
• Missing the role of logging and monitoring after prevention controls.

Troubleshooting Traps

• Skipping recent changes.
• Testing only by hostname and missing DNS as the issue.
• Testing only from one client and assuming a sitewide outage.
• Ignoring cable and physical-layer indicators.
• Forgetting DHCP relay when clients in a remote VLAN cannot get addresses.
• Misdiagnosing a firewall block as a routing issue.
• Misdiagnosing a routing issue as a DNS issue.
• Not verifying full functionality after a fix.
• Not documenting the final cause and action.

Final-Week Review Checklist

Seven to Five Days Out

• Revisit every weak topic area in this checklist.
• Redo subnetting until you can solve common CIDR questions quickly.
• Review common ports and protocols in scenario form, not just flashcards.
• Practice reading routing, DNS, DHCP, and wireless symptoms.
• Review cable types, connector types, transceivers, and tools.
• Review VLAN, trunking, inter-VLAN routing, and segmentation scenarios.
• Review wireless interference, channel planning, roaming, and authentication.
• Review monitoring outputs, logs, metrics, and documentation artifacts.

Four to Two Days Out

• Take a mixed practice set under timed conditions.
• For each missed question, identify the reason: knowledge gap, misread wording, or poor elimination.
• Create a one-page last-review sheet with ports, subnetting reminders, commands, and troubleshooting flow.
• Practice tool-selection questions: cable tester versus toner, ping versus traceroute, DNS tool versus packet capture.
• Review secure protocol replacements and remote access security.
• Review change management and documentation scenarios.
• Review high-availability and disaster recovery terms.

Day Before

• Do light review only; avoid trying to learn large new topics.
• Recheck subnetting shortcuts and common protocol roles.
• Review the troubleshooting methodology.
• Review your most common mistakes.
• Prepare identification, appointment details, and exam logistics.
• Sleep instead of cramming late.

Exam-Day Mindset

• Read the scenario before looking for keywords.
• Identify whether the question asks for the first step, best solution, likely cause, or most secure option.
• Eliminate answers that are technically true but do not solve the stated problem.
• Watch for scope: one user, one VLAN, one site, all users, wired only, wireless only, names only, IP only.
• For troubleshooting questions, prefer evidence-based next steps.
• Mark difficult questions and return if allowed by your exam interface.
• Do not let one hard subnetting or command question consume too much time.

Practical Next Step

Use this checklist to label each area as ready, needs review, or needs practice. Then focus practice on scenario questions that force you to choose tools, interpret symptoms, apply subnetting, secure a design, or troubleshoot step by step for CompTIA Network+ (N10-009).