Study guide
Mixed-Set Decision Strategy for Qualifiers and Close Answers
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
Mixed-Set Decision Strategy for Qualifiers and Close Answers
Key Takeaways Explain This Topic AI
Network+ mixed sets reward disciplined reading: identify the failure domain, qualifier, and required action before scanning answer choices.
Close answers usually differ by OSI layer, timing, administrative scope, or whether they treat a symptom instead of root cause.
Words such as FIRST, BEST, MOST LIKELY, LEAST DISRUPTIVE, and MOST SECURE change which option is correct even when all four are technically valid.
Validate port, subnet, route, wireless, security, and process choices against the exact evidence stated in the scenario.
When two answers seem plausible, prefer the one that fits the stated constraint and makes the smallest correct change.
Last updated: June 2026
Mixed-Set Decision Strategy
CompTIA Network+ N10-009 launched on June 20, 2024. The exam delivers a maximum of 90 questions in 90 minutes , mixes multiple-choice with performance-based questions (PBQs) , and requires a passing score of 720 on a 100-900 scale . The five domains carry official weights of 23% (Networking Concepts), 20% (Network Implementation), 19% (Network Operations), 14% (Network Security), and 24% (Network Troubleshooting) .
Those numbers matter for your final review because Troubleshooting and Concepts together are nearly half the exam, so your decision drill should over-rehearse "what is the most likely cause" and "what should be done next" wording.
Mixed sets are harder than chapter quizzes because any topic can sit beside any other. A routing item may bury a Dynamic Host Configuration Protocol (DHCP) clue. A wireless item may actually test channel overlap, attenuation, 802.1X authentication, or client roaming. A security item may be answered by segmentation, an access control list (ACL) , network access control (NAC) , WPA3-Enterprise , a VPN, or better logging, depending entirely on the wording.
The Four-Part Read
Use the same read pattern on every scenario before you look at the options:
Step Question to ask Example clue
1. What is broken or requested? Connectivity, performance, security, design, or process? "Users cannot reach the SaaS application"
2. Where is the boundary? Client, access switch, wireless, default gateway, WAN, DNS, or server? "Only one VLAN is affected"
3. What qualifier controls it? First, best, most likely, least disruptive, most secure, or next? "What should the technician do first ?"
4. What evidence rules out distractors? IP, mask, gateway, port, route, signal, log, duplex, or policy? "Other VLANs reach the Internet"
Never start from the answer choices. They are written to contain familiar words, and familiar words pull you toward a memorized keyword rather than the actual failure.
Qualifier Words That Change the Answer
- Qualifier What it usually demands
- First The next logical troubleshooting step or least-invasive initial check
- Best The option that solves the problem while respecting every constraint
- Most likely The cause most supported by the evidence, not every possible cause
- Least disruptive A change or test that avoids unnecessary downtime
- Most secure Stronger protection that still meets the stated business need
- Root cause The underlying reason, not the visible symptom
- Next The step that immediately follows the current stage
Example: a user reports no access after moving desks and the switch port has no link light. "What should be checked first ?" is not asking for a routing redesign; it asks for a physical or local check. Change the wording to "most likely root cause after the patch cable and switch port both test good" and the decision moves deeper into the stack.
Close-Answer Patterns
Close answers on Network+ usually differ in exactly one of these ways:
- Pattern Wrong-answer behavior Better-answer behavior
- Layer mismatch Replaces a cable when evidence points to DNS Matches the OSI layer of the evidence
- Scope mismatch Changes a core route when one host is misconfigured Fixes the smallest affected scope
Security mismatch Opens broad access to make a service work Allows only the required source, destination, port, and direction
Process mismatch Implements a fix before identifying the problem Follows the stated methodology step
Protocol mismatch Chooses Telnet, FTP, HTTP, or SNMPv2c for management Chooses SSH, SFTP, HTTPS, or SNMPv3 when security is required
Symptom mismatch Reboots a device with no explanation Addresses the cause shown by logs or tests
When two choices both sound valid, ask which is better constrained by the prompt. A Network+ scenario almost always makes one option narrower, earlier, safer, or more evidence-based.
A Practical Elimination Method
When the answer is not obvious, work the choices in this order:
Remove choices that contradict a hard fact in the question.
Remove choices that act on a different layer or different location.
Remove choices that are too broad for the affected scope.
Remove choices that ignore the qualifier ("first," "least disruptive").
Compare the survivors against the exact requested outcome.
Worked example: a new printer receives an Automatic Private IP Addressing (APIPA) address of 169.254.x.x while the rest of the office works. A firewall answer is a trap. APIPA means the client could not reach DHCP. Because only the printer is affected, a site-wide DHCP outage is unlikely; the better causes are a wrong VLAN assignment, a disconnected cable, an exhausted scope or reservation, or a missing DHCP relay (IP helper) on that segment.
Network+ Decision Anchors
Keep one anchor question per topic ready so you can classify any item in seconds:
Topic Anchor question
Subnetting Are the host IP, mask, gateway, and broadcast range internally consistent?
Ports Is the service allowed, blocked, encrypted, or exposed in the correct direction?
Layers Does the evidence point to physical, data link, network, transport, or application?
Routes Does longest-prefix match, a default route, next hop, metric, or a missing return path apply?
Wireless Is the issue coverage, interference, channel plan, authentication, roaming, or capacity?
Security Is the needed control preventive, detective, corrective, or access-limiting?
Process Which methodology step has happened, and which step logically follows?
Mixed practice should feel uncomfortable at first; that discomfort is the point. The objective is a habit of reading the scenario as evidence rather than hunting for a memorized keyword. Build that habit now and the live exam becomes a series of small, controlled decisions instead of a stressful tour of every term you have studied.