N10-009 · Entry

CompTIA Network+ (N10-009)

Plan, implement, operate and troubleshoot vendor-neutral networks with practical addressing, connectivity and security decisions.

Start Free

Your free account includes a full N10-009 practice exam.

ExamNova practice

Your first session

Questions: 90
Time limit: 90 min
Coverage: 5 domains

Practise, review your answers and see where to focus next.

Is N10-009 your next step?

Explore the coverage below to see how this certification fits your study goals.

What you’ll study

Your N10-009 practice covers every domain on the exam.

Networking Concepts
Network Implementation
Network Operations
Network Security
Network Troubleshooting

Consult the official guide for the vendor’s current exam outline.

Put it into practice.

Explore hands-on tasks connected to N10-009. These are real Labs from the catalogue.

Lab

Restore DHCP across two routed VLANs

Edit dhcp-service-plan.json. The central DHCP server is 10.60.0.10 on 10.60.0.0/24; 10.60.0.1 is the only verified return router on that server LAN. Staff uses 10.60.16.0/24 with gateway 10.60.16.1, fixed devices 10.60.16.20 and 10.60.16.21, and 40 simultaneous DHCP clients. Voice uses 10.60.17.0/24 with gateway 10.60.17.1, fixed devices 10.60.17.10 and 10.60.17.11, and 24 simultaneous DHCP clients. The approved reachable DNS servers are 10.60.0.53 and 10.60.0.54. These facts are read-only. Set serviceEnabled to a boolean. Configure exactly one relay for each vlanId, staff and voice, with target set to the central server and giaddr set to that VLAN's client-facing gateway. Use exactly one scope for each VLAN's /24 network; scope ids may be any distinct nonempty strings. Each scope needs network, poolStart, poolEnd, exclusions, router and dnsServers. Give each scope an ordered contiguous pool of usable host addresses. Subtract excluded addresses inside the pool when counting client capacity. Protect every gateway and fixed device by excluding its address or keeping it outside the pool; exclusions elsewhere in the same subnet are harmless. Advertise the client's local gateway as router and one or both approved DNS servers. Add serverRoutes with destination and nextHop. For each relay gateway, the most specific matching route must use 10.60.0.1; an aggregate, individual VLAN routes or a suitable default may work. Other next hops are unavailable in this model, and duplicate route destinations are not supported. Keep the four top-level fields serviceEnabled, relays, scopes and serverRoutes. Enable the service, run the checks after each repair, inspect route selection and remaining lease capacity, and recover without Reset. This exercise models initial address acquisition, not renewal, failover or a live DHCP exchange.

medium · About 30 min

Lab

Restore split-view DNS without breaking public names

Edit dns-resolution-plan.json. Keep public example.test and private example.test, corp.example.test and 4.80.10.in-addr.arpa zones. Place records in their most specific zone; use A/CNAME for forward zones and PTR for reverse. Verified private resolvers: 10.80.0.53 and 10.80.0.54; public: 192.0.2.53 and 192.0.2.54. Either or both within a class work. Office portal.example.test must return 10.80.4.20; internet must return 203.0.113.40. Private api.corp.example.test must own A value 10.80.4.30. inventory.corp.example.test must reach that canonical owner through one or more CNAMEs, within 16 hops. Each alias owner must have one target and no other data. PTR owner 30.4.80.10.in-addr.arpa must name api.corp.example.test, whose office A lookup must still return 10.80.4.30. Both clients must retain status.example.test at 203.0.113.60 and the read-only external public record updates.vendor.test at 198.51.100.80. Internet API and inventory lookups must return NXDOMAIN. No public record may expose corp.example.test names, targets into that namespace or RFC 1918 addresses, even if unused. Office forwarding uses the longest matching label suffix, otherwise defaultForwarders. Defaults must use verified public resolvers. Conditional rules must use verified private resolvers, cover the whole corp.example.test and reverse-zone suffixes, and stay inside example.test or 4.80.10.in-addr.arpa. Each source selects its most specific zone without public fallback after a private negative answer. A broad private view therefore needs the public status record too. Alias targets follow the same client's forwarding rules again. Names are absolute; case and a final root dot are equivalent. Replay checks after edits and repair failures without Reset. Addresses and .test names are practice data.

hard · About 35 min

Make N10-009 your next step.

Create your free account. Start practising.

Start Free