8 Network+ Practice and Exam Readiness

Exam structure and domain weights

The N10-009 exam is described as having up to 90 multiple-choice and performance-based questions in 90 minutes. Its published domain weights are Networking Concepts, 23 percent; Network Implementation, 20 percent; Network Operations, 19 percent; Network Security, 14 percent; and Network Troubleshooting, 24 percent. Check CompTIA's current objectives before scheduling because exam materials can be updated.

Networking concepts

Review the OSI model, network devices and services, cloud networking, common ports and protocols, transmission media, topologies, IPv4 subnetting, IPv6, and modern network designs. In a scenario, first identify what is being communicated and at which layer; then select a suitable device or protocol.

A switch generally forwards frames within a LAN, while a router forwards packets between IP networks. A firewall enforces traffic policy; an IDS detects suspicious activity, while an IPS can block it. Other review topics include VPN, QoS, TTL, VPCs, and IPv6 coexistence approaches such as dual stack and NAT64.

Addressing example

A workstation with address 169.254.18.7 that cannot reach other networks has an address in the APIPA range. Suspect that it did not obtain an IPv4 lease from DHCP. Check the link and VLAN, then verify DHCP service or relay configuration.

For 192.168.40.64/27, the subnet mask is 255.255.255.224, the block size is 32, and the address range is .64–.95. The network address is .64, the broadcast address is .95, and the usable host range is .65–.94.

Network implementation

Review static and dynamic routing, route selection, NAT/PAT, VLANs, 802.1Q, link aggregation, spanning tree, wireless configuration, and physical installation. The most specific matching prefix is normally preferred in route selection; metrics and administrative distance help compare routes according to the routing process.

For switching scenarios, distinguish an access port from a trunk. Consider whether VLAN assignment, tagging, speed or duplex, or an STP block explains the symptom. Wireless scenarios may depend on band, channel, interference, encryption, authentication, or access-point placement.

When two switches must carry several VLANs over one inter-switch link, configure a trunk using 802.1Q and ensure the required VLANs are allowed at both ends. A host-facing port normally belongs to the host's access VLAN.

Network operations

Review network documentation, asset and configuration management, monitoring, disaster recovery, network services, and management access. Distinguish a logical diagram from a physical or rack diagram. Understand what SNMP, flow data, packet capture, logs, and baselines can reveal.

For recovery planning, Recovery point objective (RPO) concerns acceptable data loss, while Recovery time objective (RTO) concerns acceptable restoration time. Also distinguish MTTR from MTBF, and compare cold, warm, and hot recovery sites.

For DHCP, review scopes, reservations, leases, exclusions, options, and relays. Know common DNS record types and what they resolve. If the DHCP server is on a different subnet from its clients, configure a DHCP relay, often called an IP helper, on the client VLAN's routing interface so broadcast requests can reach the server.

Network security

Review security principles, attack patterns, and defensive controls. Recognize rogue DHCP servers, evil twins, ARP or DNS spoofing, MAC flooding, VLAN hopping, denial-of-service, and social engineering.

Match controls to the risk: harden devices, remove unused services, change default credentials, segment networks, use ACLs and filtering, and apply access controls such as 802.1X or port security where appropriate. A screened subnet can isolate public-facing services from trusted internal networks.

If users connect to a wireless network using the company name but traffic passes through an unauthorized access point, treat it as a possible evil twin or rogue AP. Locate and contain the device, then verify that users connect to the authorized SSID and authentication method.

Troubleshooting process and evidence

Network Troubleshooting is the largest published domain, at 24 percent. Use a consistent process: identify the problem, establish a probable cause, test the theory, plan and implement a solution, verify full functionality, and document findings. Gather information, check for recent changes, and consider divide-and-conquer or moving top-to-bottom or bottom-to-top through the OSI model.

Use symptoms to narrow the likely layer and tool:

• No link light: Inspect power, cable, transceiver, and interface status.

• Link is up but the host has no valid address: Inspect DHCP, VLAN, and relay settings.

• IP connectivity works but names do not resolve: Test DNS with nslookup or dig.

• High latency or packet loss: Compare interface counters, utilization, wireless interference, and a baseline.

• Only remote destinations fail: Check the default gateway, route table, ACLs, and the path with traceroute or tracert.

Rising CRC errors can point to a cabling, connector, transceiver, or other link-quality issue. Compare counters over time and inspect the physical path.

Practice scenarios and diagnosis

The scenarios below apply the concepts to common diagnostic decisions.

Addressing and services

A newly installed host shows 169.254.8.21/16, while other hosts on its floor work normally. First check the host's physical connection and VLAN, then whether it can reach DHCP. An APIPA address commonly indicates that a DHCP lease was not obtained.

VLAN connectivity

A user can reach devices in the same VLAN but not a server in another subnet; the user's IP address, mask, and local switch link are correct. Focus next on the default gateway or Layer 3 routing path. Verify the gateway, routing interface or SVI, and any route or ACL affecting the destination.

Route selection

For destination 10.20.30.45, both 10.20.0.0/16 and 10.20.30.0/24 match. The 10.20.30.0/24 route is normally selected because it is the more specific prefix.

Wireless security

A nearby network has the organization's SSID but presents an unexpected login page. The likely concern is a rogue or evil-twin access point. Report and investigate it; do not enter credentials into an unverified portal.

Monitoring and diagnosis

For intermittent slow file transfers, rising CRC errors on an interface are useful evidence of possible physical-layer errors. Compare counters over time and inspect the physical path.

Security control

If users must authenticate before a switch port grants network access, the matching control is 802.1X, which provides port-based network access control using authentication.

Recovery planning

If a service owner says the organization can tolerate losing no more than 15 minutes of data after an outage, the requirement is expressed as an RPO. RPO specifies maximum acceptable data loss; RTO specifies the target time to restore service.

Recent change and limited scope

After a switch replacement, a department loses access to its printer and server while other departments work normally. Check what changed and verify the affected ports' VLAN configuration. The timing and limited scope point toward the change and the department's VLAN path; test the likely cause before making a broad change.

Performance-based tasks

Translate a configuration or drag-and-drop prompt into requirements before acting. If two VLANs must communicate through a switch, identify the VLAN IDs, create or verify the VLANs, assign the correct access ports, and provide a Layer 3 gateway for each VLAN.

For a wireless deployment, record the required SSID, security method, authentication type, band or channel constraints, and guest isolation. Validate the outcome—for example, by checking addressing, reachability, or interface state—instead of assuming the configuration succeeded.

Test-taking strategy

Use the wording and constraints in each question to guide the decision:

1. Read the final requirement first. Determine whether the prompt asks for the best first step, the most likely cause, or the best fix; these are different decisions.

2. Use the scenario's constraints. Scope, timing, recent changes, and whether the fault affects one user, one VLAN, or the whole network may matter more than extra technical detail.

3. Eliminate answers that do not address the symptom. A DNS change cannot repair a broken physical link, and replacing hardware is premature when a VLAN mismatch is evident.

4. Use a structured troubleshooting model. Gather facts, form a testable theory, make a controlled change, verify the result, and document it.

5. Manage time deliberately. The published allowance is 90 minutes for up to 90 questions, including performance-based items. If a question is taking too long, mark it if the testing interface permits, move on, and return later.

6. Match performance tasks to requirements. Complete the requested configuration, then check that the result satisfies every stated requirement. Avoid unrelated changes.

7. Watch for absolute wording. “First,” “most likely,” and “best” can signal that several answers may be technically possible, but one fits the evidence and priority best.

Final review checklist

Before the exam, confirm that you can explain or perform each of these tasks without relying only on memorized definitions:

• Map common network functions to OSI layers, devices, and protocols.

• Distinguish TCP from UDP, common traffic types, and frequently used service ports.

• Calculate IPv4 network, broadcast, and usable host ranges from a prefix; recognize private, loopback, and APIPA addresses.

• Explain IPv6 coexistence methods, including dual stack, tunneling, and NAT64.

• Choose between routing, switching, VLAN, NAT/PAT, wireless, and physical-layer solutions in a scenario.

• Interpret DHCP and DNS symptoms; distinguish a DHCP relay from a local broadcast domain and know common DNS record purposes.

• Read network documentation and explain what monitoring data, interface counters, logs, flow data, or packet captures can reveal.

• Distinguish RPO, RTO, MTTR, and MTBF, and compare cold, warm, and hot recovery sites.

• Recognize common network attacks and select a proportionate control, such as segmentation, ACLs, 802.1X, port security, or device hardening.

• Apply the troubleshooting process, select a suitable command or tool, verify the fix, and record the result.

A strong final review focuses on explaining why an answer fits the evidence, not merely recognizing a familiar term. Use CompTIA's official objectives as the authoritative checklist for exam coverage.

• longest-prefix match