Objective 3.4

N10-009

Given a scenario, implement IPv4 and IPv6 network services.

Objective 3.4 sits in Network Operations, which carries 19% of the Network+ exam. The questions below are original, written from the official objective title above, and each explanation cites the CompTIA page it rests on.

Objective title verbatim from the official objectives. CompTIA exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

3-4Network Operations

A technician enables IPv6 on a server and it forms a global address from a router advertisement. What must the node complete before that address can be used?

A DHCPv6 Solicit exchange confirming the addressA Solicit begins stateful DHCPv6. That is the right first step when a router advertisement sets the managed configuration flag instead.
Duplicate address detection on the tentative addressCorrect · your answerCorrect: every unicast address is checked for uniqueness before assignment, whatever produced it.
Duplicate address detection limited to the link local addressTesting only the link local address is a deprecated shortcut. It would pass if every address on the interface shared one interface identifier.
A dynamic DNS registration of the AAAA recordRegistering an AAAA record publishes a name to address mapping. It matters for reachability by name, after the address is already usable.

Correct.

Checked against datatracker.ietf.org, August 2026

Concept

An IPv6 node has to prove a unicast address is unique on the link before it starts using it. The obligation follows the address itself, not the mechanism that produced it.

Why B

The address stays tentative until the node sends a neighbor solicitation naming that address and no neighbor answers. Only then may the interface treat it as assigned.

Source

To ensure that all configured addresses are likely to be unique on a given link, nodes run a "duplicate address detection" algorithm on addresses before assigning them to an interface. The Duplicate Address Detection algorithm is performed on all addresses, independently of whether they are obtained via stateless autoconfiguration or DHCPv6.

IETF RFC 4862: IPv6 Stateless Address Autoconfiguration, checked August 2026
#ipv6#slaac#duplicate-address-detection

Now you: objective 3.4 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

3-4Network Operations

A DNS administrator adds a host record whose leftmost label is 70 characters long, and the server rejects the name. Which size limit does that label break?

Sample question 2 of 3

3-4Network Operations

A client workstation halfway through its DHCP lease sends the packet below. Which client state does this exchange show?

16:02:11.418393 IP 10.20.4.55.bootpc > 10.20.1.10.bootps: BOOTP/DHCP, Request from 00:1a:2b:3c:4d:5e, length 300    Client-Ethernet-Address 00:1a:2b:3c:4d:5e    Client-IP 10.20.4.55    Vendor-rfc1048 Extensions      Magic Cookie 0x63825363      DHCP-Message Option 53, length 1: Request

Sample question 3 of 3

3-4Network Operations

A client receives a DHCPACK for 192.168.30.44, then an ARP probe for that address draws a reply from another host. What must the client send next?

Full Network+ question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Network Operations