Study guide

Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction

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

Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction

Key Takeaways Explain This Topic AI

PBQs bundle addressing, name resolution, segmentation, and firewall policy into one scenario - read them in dependency order.

Firewall rules are stateful and directional: for a client-initiated session the source is the client and the destination is the server.

DHCP scopes and relay must align with each VLAN's subnet and SVI gateway; a wrong gateway option strands clients in their subnet.

A default-deny posture with explicit allows enforces least privilege and is easier to audit than any-to-any rules.

Troubleshoot in order: addressing, DNS, routing, firewall, listening port, then the application itself.

Last updated: June 2026

Reading a Combined PBQ in Order

The N10-009 exam includes performance-based questions (PBQs) - drag-and-drop or simulation tasks where you configure or repair a small network. They reward candidates who read in dependency order: addressing, then name resolution, then routing, then firewall policy, then service behavior. Guessing wastes the limited 90-minute clock.

Consider this design:

  • VLAN 10 - Employees, 10.10.10.0/24, gateway 10.10.10.1
  • VLAN 20 - Servers, 10.10.20.0/24, gateway 10.10.20.1
  • VLAN 30 - Guests, 10.10.30.0/24, gateway 10.10.30.1
  • VLAN 40 - Management, 10.10.40.0/24, gateway 10.10.40.1
  • DNS and DHCP server: 10.10.20.10
  • Web application: app.example.local at 10.10.20.50

Required behavior: employees reach the web app by name; guests reach only the internet; management administers servers; every VLAN gets correct DHCP options. Each requirement maps to one specific service or rule.

Mapping Requirements to Configuration

  • Requirement Configuration that satisfies it
  • Employee name lookup DNS A record app.example.local -> 10.10.20.50
  • Employee addressing DHCP scope 10.10.10.0/24, gateway 10.10.10.1, DNS 10.10.20.10
  • Guest addressing DHCP scope 10.10.30.0/24, gateway 10.10.30.1, approved DNS
  • Central DHCP reachability DHCP relay/ip-helper on every VLAN SVI outside VLAN 20
  • Server management Firewall allow Management VLAN -> servers on admin ports

A frequent trap is setting a VLAN's gateway option to the server's IP. The gateway must be the routed SVI for that VLAN (10.10.10.1 for employees), never 10.10.20.10. Another trap: pointing every VLAN's DNS at an external resolver, which can break internal name resolution for app.example.local.

Notice how the design separates concerns. DHCP delivers the plumbing (address, mask, gateway, DNS server) so a client can communicate at all. DNS then turns the application name into the server's address. Routing carries the packet between VLANs through the Layer 3 switch. The firewall decides whether that flow is allowed . Finally the server must actually be listening. Each PBQ usually breaks exactly one of these links, and the artistry is recognizing which symptom maps to which link rather than reconfiguring everything.

For example, a client with a 169.254 address has a DHCP problem and you never even reach DNS; a client that resolves a name but cannot connect has already passed DHCP and DNS, so you move down to routing and firewall.

Firewall Direction Is Stateful

Firewall rules are scoped to source, destination, service, and action - and modern firewalls are stateful , so they track each connection by the side that initiates it and automatically permit the return traffic.

  • Source Destination Service Action Reason
  • Employee VLAN DNS server DNS (UDP/TCP 53) Allow Name resolution
  • Employee VLAN Web app HTTPS (TCP 443) Allow Business application
  • Guest VLAN Internal subnets Any Deny Guest isolation
  • Guest VLAN Internet DNS / HTTP / HTTPS Allow Guest browsing
  • Management VLAN Servers SSH 22 / RDP 3389 / HTTPS Allow Administration
  • Any Any Any Deny + log Default deny

Direction is the load-bearing detail. A rule that allows Server VLAN -> Employee VLAN on HTTPS does not let an employee open a browser session to the server, because for a client-initiated connection the source is the employee and the destination is the server. Because the firewall is stateful, you only write the rule in the initiating direction; the response is allowed automatically.

Troubleshooting Order, Traps, and a Walkthrough

When a user says "the app is down," follow dependencies instead of guessing:

Verify the client's IP, mask, gateway, and DNS server are correct.

Verify the name resolves to the intended address.

Verify the client can route to the destination subnet.

Verify a firewall rule allows the client-to-service flow.

Verify the service is listening on the expected port.

Verify the application itself is healthy.

  • Common PBQ trap Why it is wrong
  • Broad allow from guest to internal Violates the segmentation requirement
  • DHCP scope with the wrong gateway Clients cannot route off their subnet
  • DNS A record still points at the old server Name resolves but reaches the wrong host
  • Firewall source and destination reversed The intended clients still cannot initiate
  • Missing DHCP relay on a new VLAN Clients fail though the server is healthy
  • Temporary any-to-any allow May restore connectivity but breaks least privilege
  • PBQ walkthrough

Facts: employees in VLAN 10 hold 10.10.10.x addresses; their DNS is 10.10.20.10; app.example.local resolves to 10.10.20.50; both ping and HTTPS to 10.10.20.50 fail; the only HTTPS rule is Server VLAN -> Employee VLAN . Best answer: leave DHCP and DNS alone (they return correct values), add an allow rule Employee VLAN -> 10.10.20.50 on TCP 443 , keep guest-to-internal denied, and log the default-deny rule. The reversed firewall rule is the key clue - a new client-initiated HTTPS session needs the employee as source and the server as destination.