ExamFinch.com My Study

Study guide

Physical Installation Implications

Practice this exam

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

Physical Installation Implications

Key Takeaways Explain This Topic AI

PoE standards scale by wattage: 802.3af 15.4W, 802.3at (PoE+) 30W, 802.3bt Type 3 60W and Type 4 up to ~90-100W per port.

A switch's total PoE power budget can be exhausted before all ports are used, leaving later devices underpowered.

A UPS bridges short outages and enables graceful shutdown; it is not a generator and must be sized to load and runtime.

Patch panels, labeling both cable ends, and rack elevation diagrams cut troubleshooting time during outages.

Environmental controls (HVAC, humidity, EMI distance, leak detection) and physical access controls protect availability.

Last updated: June 2026

The Physical Layer Still Decides Uptime

A flawless VLAN or routing design fails if power, cooling, cabling, or rack organization is wrong. N10-009 tests whether you can spot the physical-layer cause behind an expansion problem - often a PoE power budget that ran out.

Power over Ethernet

PoE (Power over Ethernet) delivers DC power and data over the same twisted-pair cable. Know the IEEE standards and their wattage at the power sourcing equipment (PSE) port:

  • Standard Common name PSE power/port Powers
  • 802.3af PoE 15.4 W VoIP phones, basic APs, simple cameras
  • 802.3at PoE+ 30 W Dual-band APs, PTZ cameras
  • 802.3bt Type 3 PoE++ / 4PPoE 60 W Wi-Fi 6 APs, video phones
  • 802.3bt Type 4 PoE++ up to ~90-100 W Multi-radio APs, displays

Key term: a switch has a finite power budget (e.g., a 24-port switch rated 370 W total). You can deplete that budget before every port is used - so 24 PoE ports does not mean 24 high-power APs. A PoE injector adds power to one run when the switch is not PoE-capable.

Implementation checks:

Confirm each powered device's wattage requirement.

Confirm the switch supports the needed standard and has budget headroom.

Stay within cable distance limits (100 m for Ethernet).

Document which ports power critical devices; consider redundant power supplies.

Diagnostic clue: if an AP boots but disables radios or runs at reduced power , the switch port is likely supplying 802.3af when the AP needs 802.3at/bt, or the budget is exhausted. PoE negotiation is class-based: the powered device signals its class to the PSE, and if the switch cannot satisfy that class it either supplies less power or denies power entirely. This is why a Wi-Fi 6 AP that ran fine on a bench injector may cripple itself on an older 802.3af switch port. Always cross-check three numbers - the device's required wattage, the port's supported standard, and the switch's remaining budget - before assuming a hardware fault.

Remember also that PoE rides the same 100 m channel limit as data; a powered device at the end of a 130 m run will have both data and power problems. Mid-span injectors and PoE extenders exist for longer reaches but introduce their own power and management considerations.

UPS and Power Protection

A UPS (uninterruptible power supply) provides battery power during a utility failure and conditions power during brief sags or surges.

  • Need Consideration
  • Keep gear running briefly Size runtime for switches, routers, firewalls, modem
  • Graceful shutdown UPS signaling (USB/SNMP) to servers/management
  • Critical availability Redundant PSUs on separate circuits
  • Surge protection Clamp voltage spikes

Size a UPS by load (VA/watts) and required runtime . A UPS is not a generator - it covers short outages or bridges to a generator or to a controlled shutdown, typically minutes, not hours. Know the topologies the exam may reference: a standby UPS switches to battery only on failure (cheapest, brief transfer gap), a line-interactive unit also regulates voltage sags and swells, and a double-conversion (online) UPS continuously runs the load from the inverter for zero transfer time, which suits sensitive routers and firewalls.

Overloading a UPS beyond its VA rating collapses runtime to almost nothing, so always total the connected device wattage before sizing.

Racks, Patch Panels, and Cable Management

  • Component Purpose
  • Rack (measured in U) Mounts switches, routers, panels, PDUs
  • Patch panel Terminates horizontal cabling for organized patching
  • Cable manager Routes and strain-relieves patch cords
  • Labeling Maps ports, cables, panels, racks, rooms
  • Rack elevation diagram Documents device placement by rack unit

Best practices: label both ends of every cable; keep patch cords sized to avoid strain yet manageable; maintain copper/fiber bend radius ; never bundle cables across switch exhaust vents; document spare ports and growth space. Poor cable management lengthens every outage because techs cannot trace links quickly.

Environmental and Safety Factors

  • Factor Risk Mitigation
  • Heat Failure, thermal throttling HVAC, blanking panels, hot/cold aisle
  • Humidity Corrosion or static Monitoring and control (40-60% RH)
  • Dust Clogged vents, overheating Filtration, cleaning schedule
  • Water Shorts, outages Avoid plumbing paths, leak detection
  • EMI Signal degradation Shielded cable, distance from motors/ballasts
  • Physical access Tampering, theft Locked rooms/cabinets, cameras, access logs

Outdoor or industrial installs may need weatherproof enclosures, grounding/bonding , surge protection, and temperature-rated equipment in conduit.

PBQ-Style Closet Buildout

Task: install switching for new APs, cameras, and office drops.

Terminate horizontal runs on patch panels.

Label panel ports, wall jacks, and switch ports.

Install PoE switches with budget for the AP and camera load (verify 802.3at/bt support).

Connect critical switches and the firewall to a correctly sized UPS.

Route patch cords through cable managers without blocking airflow.

Verify temperature, ventilation, rack security, and grounding.

The exam often asks "which issue is most likely" after an expansion. A switch with enough Ethernet ports but too little PoE budget cannot run high-power APs or PTZ cameras - that is the trap answer made correct.