Study guide
Cloud and Virtual Networking Concepts
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
Cloud and Virtual Networking Concepts
Key Takeaways Explain This Topic AI
A VPC (AWS) or VNet (Azure) is a logically isolated cloud network with subnets, route tables, gateways, and security controls.
Security groups are stateful and filter at the instance/interface level; network ACLs are stateless and filter at the subnet level.
Internet gateways allow public routing, NAT gateways allow outbound-only from private subnets, and VPN/Direct-Connect gateways link to on-prem.
NFV turns firewalls, routers, and load balancers into software; SDN separates the control plane from the data plane.
SD-WAN does policy-based path selection across links; SASE adds cloud-delivered security (SWG, CASB, ZTNA, FWaaS) at the edge.
Last updated: June 2026
Cloud Reuses Familiar Network Concepts
Cloud networking applies the same ideas you already know - subnets, routes, gateways, firewalls, NAT, VPNs, load balancers, DNS - but the controls are software-defined and managed through a cloud control plane. Network+ is vendor-neutral, so translate each brand term into its network function.
- Concept Vendor-neutral meaning Common clue
- VPC (AWS) / VNet (Azure) Logically isolated cloud network Cloud subnets and route tables
- Subnet IP range inside the cloud network Public, private, app, or DB tier
- Cloud gateway Connects the virtual network outward Internet, NAT, or VPN gateway
- Security group Stateful instance/interface filter "Allow 443 from the load balancer"
- Network ACL Stateless subnet-level filter Numbered allow/deny rule list
- Load balancer Distributes traffic across targets Public front end or internal service
The single most-tested distinction: security groups are stateful (return traffic is auto-allowed) while network ACLs are stateless (you must permit both directions explicitly), and they apply at different scopes - instance versus subnet.
VPC / VNet Design and Subnet Tiers
A cloud network spans multiple subnets across availability zones for fault tolerance. Public subnets have a route to an internet gateway for inbound/outbound internet; private subnets reach the internet only outbound via a NAT gateway or use private endpoints, and never accept unsolicited inbound internet traffic. Each subnet sits inside a non-overlapping CIDR block (for example a /16 VPC carved into /24 subnets).
- Tier Subnet placement Security focus
- Web / load balancer Public subnet Only ports 80/443 from the internet
- Application Private subnet Allow only from web/LB tier
- Database Private subnet Allow only DB port from app tier
- Management Private + controlled path MFA, VPN, bastion, ZTNA, logging
Overlapping CIDR ranges are a classic blocker: two VPCs/VNets with the same address space cannot peer or route to each other, so plan non-overlapping subnets from the start.
Gateways and Cloud Connectivity
Each gateway type maps to one connectivity job. Knowing the job is enough for the exam.
- Gateway / connection Purpose
- Internet gateway Public internet routing for resources with public paths
- NAT gateway Outbound-only internet for private subnet resources
- VPN gateway Encrypted IPsec tunnel between cloud and on-prem
- Private circuit (Direct Connect / ExpressRoute) Dedicated provider path, bypasses public internet
- Transit gateway / hub Central routing point between many VPCs/VNets
- Peering Direct private connectivity between two virtual networks
The difference between an internet gateway (bidirectional public routing) and a NAT gateway (outbound only, blocks unsolicited inbound) is heavily tested. A private database server that needs OS patches uses NAT for outbound updates while staying unreachable from the internet.
NFV, SDN, SD-WAN, and SASE
Network function virtualization (NFV) moves firewalls, routers, load balancers, WAN optimizers, and IPS from dedicated appliances into virtual machines or cloud services. Software-defined networking (SDN) separates the control plane (decisions) from the data plane (forwarding) so a central controller programs behavior via APIs. SD-WAN uses software control to choose WAN paths per application across broadband, LTE/5G, and MPLS based on link health and policy.
SASE (Secure Access Service Edge) fuses WAN access with cloud-delivered security - secure web gateway (SWG), cloud access security broker (CASB), zero trust network access (ZTNA), and firewall-as-a-service (FWaaS).
- Technology Exam meaning Best clue
- NFV Network appliance as software Virtual firewall or virtual router
- SDN Centralized programmable control Controller programs forwarding via API
- SD-WAN Policy-based WAN path selection Picks broadband/LTE/MPLS per app
- SASE Cloud-delivered network + security edge Remote users reach apps through a security edge
Worked Scenarios and Cloud Routing Traps
Scenario 1: A three-tier cloud app has public load balancers, private app servers, and private databases. A correct security-group design: allow HTTPS (443) from the internet to the load balancer, allow the app port from the load balancer to app instances, and allow the database port only from app instances. Never open the database port to the internet.
Scenario 2: A company wants branch traffic to use whichever WAN circuit is healthy and to send SaaS traffic straight through cloud security instead of hairpinning through HQ. That is SD-WAN plus SASE : policy-based path selection with cloud-delivered enforcement.
- Symptom Likely area to check
- Private server cannot reach updates NAT gateway or outbound route missing
- Public web server unreachable Public IP, internet-gateway route, security group
- Database reachable from internet Subnet route + security-group rules too open
- Two VNets cannot communicate Peering missing or overlapping CIDR
- VPN tunnel up but no traffic Routes, encryption domains, firewall rules
Translate every brand-specific word into a network function - isolated network, subnet, route, gateway, filter, inspection, or policy controller - and the vendor-neutral exam answer becomes clear.