Study guide
Attack-to-Mitigation PBQ Tables
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
Attack-to-Mitigation PBQ Tables
Key Takeaways Explain This Topic AI
PBQs map symptom to attack to control; identify the attack path first, then pick the least-disruptive fix.
Layer 2 attacks: port security, DHCP snooping, dynamic ARP inspection, access-mode ports, 802.1X.
Wireless attacks: WPA3 or WPA2-Enterprise with 802.1X, certificate validation, wireless IDS, user training.
Volumetric DDoS needs upstream/cloud scrubbing because local firewalls sit behind the saturated link.
Choose the control that breaks the specific path, and always preserve logging and validation.
Last updated: June 2026
Attack-to-Mitigation Tables
Performance-based questions (PBQs) on the N10-009 ask you to drag controls onto a topology, toggle device settings, or complete a policy table. With a 90-minute clock and up to 90 items, do not over-think them. The reliable method: identify the attack path first , then pick the control that breaks that path with the least side effect.
Layer 2 and Access Edge
Symptom or evidence Likely attack Best mitigation direction
A user port negotiates as a trunk and reaches other VLANs VLAN hopping / trunk misconfig Force access mode, disable DTP, restrict allowed VLANs, harden native VLAN
CAM table fills with many source MACs MAC flooding Port security with MAC limits, storm control, 802.1X
Clients get a wrong gateway and DNS Rogue DHCP DHCP snooping, trust only the uplink port, hunt the rogue server
ARP cache maps the gateway IP to an attacker MAC ARP poisoning Dynamic ARP inspection bound to DHCP snooping; static entries for critical hosts
Unknown device plugged into an office jack Unauthorized access 802.1X / NAC, disable unused ports, port security
DNS, Wireless, and User-Focused Attacks
Symptom or evidence Likely attack Best mitigation direction
Known hostname resolves to an unexpected IP DNS / rogue DNS poisoning Harden DNS infra, restrict resolver assignment, monitor changes, DNSSEC where supported
Familiar SSID with a weak signal near the lobby Evil twin WPA3 or WPA2-Enterprise, certificate validation, wireless IDS, user training
Clients repeatedly drop, then join a fake portal Deauth abuse + evil twin Wireless monitoring, strong enterprise auth, no auto-join to open networks
Help desk resets a VPN password after a suspicious call Social engineering Identity-verification procedure, MFA reset controls, training, ticket evidence
User enters credentials into a fake VPN page Phishing MFA / phishing-resistant auth, domain monitoring, reporting workflow
Availability and Perimeter
Symptom or evidence Likely attack Best mitigation direction
Internet circuit saturated from many sources Volumetric DDoS ISP coordination, scrubbing provider, CDN/anycast, upstream rate limiting
Firewall session table exhausted State-exhaustion DoS Tune limits, rate limit, upstream filtering, capacity planning
Web app overwhelmed by expensive requests Application-layer DoS WAF, rate limiting, caching, application tuning
Public DNS receives amplified response floods Reflection / amplification Provider mitigation, source validation, rate limiting, close open resolvers
Management Plane and Credential Abuse
- Symptom or evidence Likely problem Best mitigation direction
- Admin logins from unusual countries Compromised credential MFA, geofencing, conditional access, account review
Router changed via a shared admin account Weak accountability Named accounts, TACACS+, command authorization, accounting logs
SNMP community string seen in a packet capture Insecure management protocol Use SNMPv3 with authentication and privacy
Management interface reachable from the guest VLAN Excessive exposure ACLs, dedicated management VLAN, jump host, firewall rules
The PBQ Method
Identify the affected layer : physical, wireless, Layer 2, IP, DNS, application, identity, or provider edge.
Identify the asset and trust boundary : guest, user, server, management, cloud, or OT.
Match the evidence to a specific attack, not a vague fear.
Select the control that blocks that exact path .
Preserve visibility : logs, alerts, and a validation test from the source network.
Worked Example: Completing a Switch-Hardening PBQ
A PBQ presents an access switch with these requirements: prevent VLAN hopping, stop rogue DHCP, and block ARP spoofing, while leaving the uplink to the distribution switch fully functional. The defensible drag-and-drop answer is layered. On every user-facing port : set switchport mode access , assign the user VLAN, disable DTP, and enable port security with a low MAC limit. On the single uplink port : leave it as the trunk, restrict allowed VLANs, and mark it as the DHCP-snooping trusted port so legitimate offers from the real server pass while rogue offers on user ports are dropped.
Globally enable DHCP snooping and dynamic ARP inspection for the user VLANs. Notice the uplink is trusted and the user ports are untrusted; reversing that breaks legitimate DHCP, which is the trap option the exam plants.
Why Order of Operations Matters
Many candidates lose PBQ points by choosing a control that is correct in isolation but applied at the wrong place. DAI depends on the DHCP-snooping binding table, so snooping must be enabled first or DAI has no valid bindings to check and may drop everything. Likewise, IP source guard relies on the same binding table. For availability, a WAF in front of a web application stops application-layer floods but does nothing for a volumetric flood that saturates the circuit upstream of the WAF. The exam consistently rewards placing the control at the point in the path where it can actually see and act on the malicious traffic.
Common Traps
A firewall rule will not solve a rogue DHCP problem on the same access VLAN, because DHCP discovery is local broadcast traffic the firewall never sees.
Encryption does not stop a user from joining a fake SSID if certificate validation is ignored.
DDoS filtering must happen before the bottleneck link when bandwidth is already saturated.
Enable DHCP snooping before dynamic ARP inspection; DAI needs the snooping binding table to validate ARP.
A good mitigation answer includes validation, such as testing from the guest VLAN or reading switch security counters.
More controls are not better if they do not address the observed path; match the fix to the evidence.