HPE3-U01 HPE Network Technician Exam Topics and Questions

Network Fundamentals sets the floor for every other topic on this exam. The danger here is underestimating it: candidates who have worked in networking for years often drop marks because they rely on intuition rather than precise definitions. Expect the exam to test exact boundaries between LANs and WANs, what specific media types imply about transmission, and whether you can convert between numbering systems fast enough under time pressure.

– Networks, media, and traffic types

The exam treats LAN and WAN as technical boundaries, not geography. You need to know what components belong to each and why. Media type questions are not about memorising cable colours: they turn on what each medium implies about bandwidth, distance, and interference. Coaxial, twisted pair, fibre, and wireless each carry specific trade-offs that appear as scenario differentiators.

Unicast, multicast, and broadcast matter because they determine how a frame or packet is handled at the device level. The exam will place you in a scenario where the traffic type explains a behaviour, a performance issue, or a design choice. Knowing the definition is not enough; you need to know what each type means for the devices in the path.

– Numbering systems and conversion

Binary-to-decimal and decimal-to-binary conversion is a working skill on this exam, not a background fact. Subnetting, addressing, and VLAN questions all assume you can convert quickly and accurately. Hexadecimal matters too, particularly when reading MAC addresses.

Practice converting under time pressure. Candidates who work these conversions slowly burn time they need for the longer scenario items later in the exam. A mistake in conversion here can cascade into a wrong answer on an addressing question even when the networking logic is sound. Build the conversion reflex before exam day, not during it.

How Network Fundamentals is tested

At 9% of the exam, this topic contributes a focused set of items that reward precision over general familiarity. Items tend to be short and definitional, but the traps are in the edges: a question about media will often hinge on a single characteristic that distinguishes two options that are otherwise similar. Traffic-type items reward knowing the forwarding behaviour that results from each type, not just the label.

Numbering conversion items are unforgiving. There is no partial credit for getting close. Candidates lose marks here by rushing or by not having drilled the conversion process to the point where it is automatic.

The LAN and WAN component questions look straightforward but often include a component that could plausibly belong to either environment. Items reward placing each component in the right context based on its functional role. Familiarity with the terminology as HP Aruba uses it, rather than generic textbook definitions, is what separates the answers.

Where Network Fundamentals dealt with components and conversions, this topic shifts to behaviour: how data actually moves through a network and what the rules are at each layer. At 20%, it carries the second-highest weight on the exam, which means the number of items here is large enough that a weak area in any one protocol or process will show up in your score. Expect scenario items, not just recall.

– OSI layers, encapsulation, and headers

The OSI model is examinable at the layer-function level, meaning you need to know what each layer does and, more importantly, what it does not do. Items frequently describe a behaviour and ask which layer is responsible: the trap is a layer that seems correct because it is adjacent to the right one.

Encapsulation is tested as a process. You need to trace what is added at each layer as data moves down the stack, and what is stripped as it moves up. Headers carry addressing and control information specific to their layer, and exam items will reference a header field to anchor a question about protocol behaviour. Knowing which fields live at which layer, and what they control, is the working knowledge this section demands.

– TCP, L2–L7 protocols, and networking services

The TCP three-way handshake is tested as a sequence. Items reward knowing what each step establishes and what happens if one step fails or is out of order. This is not background knowledge; it is a direct source of exam items.

Common protocol questions span a wide range: DHCP lease process, DNS resolution order, HTTP vs HTTPS implications, SSH as a secure replacement for Telnet, FTP data and control connections, LLDP neighbour discovery, and ICMP's role in diagnostics. Each protocol has a specific operational characteristic that the exam uses as a differentiator.

For services like DHCP and DNS, the exam cares about the exchange sequence and what each message does. Knowing that DHCP uses DORA, for example, matters only if you can apply it to a scenario where a client is failing to get an address. That applied level is where marks are won or lost.

How Network Communications Model is tested

At 20%, this is a topic where the volume of items means you will encounter multiple difficulty levels. Some items are direct protocol recall; others embed the protocol in a scenario that requires you to reason about what should happen next or why something failed.

The OSI layer items are a known trap. Two options will often be adjacent layers, and the item rewards the candidate who knows the precise boundary, not the one who knows the layers in order. Encapsulation items reward tracing the correct direction and identifying the correct header for the layer in question.

Protocol and services items reward operational knowledge. The exam does not ask you to define ICMP; it places ICMP output in front of you and asks what it means for connectivity. Candidates lose marks by knowing what a protocol is without knowing how it behaves step by step. Drilling the exchange sequences for DHCP, DNS, and TCP before the exam is the single most effective preparation move for this topic.

From protocols and models, the exam moves to physical and logical devices: what they are, how they differ, and how you configure and interrogate them. At 18%, this topic is largely about Aruba-specific knowledge, particularly the AOS-CX operating system. Generic networking experience will get you partway, but candidates who have not worked with AOS-CX CLI contexts or Aruba's device hierarchy will find several items unfamiliar.

– Device types and their roles

Switches, routers, multilayer switches, and wireless routers each occupy a defined position in a network design, and the exam tests whether you can place them correctly in a scenario. Multilayer switches are a frequent source of confusion because they blur the line between Layer 2 and Layer 3 functions. The exam rewards knowing which forwarding decision happens at which layer for each device type.

Out-of-band management (OOBM) is tested as a design and operational concept. You need to know why it exists, what it provides when the production network is unreachable, and how it differs from in-band management. Switch interfaces are covered at the functional level: port types, interface states, and what each state means for traffic.

– AOS-CX CLI, show commands, and basic configuration

AOS-CX CLI contexts are a specific Aruba construct. The exam expects you to know how the context hierarchy works: which commands are available in which context, and what moving between contexts requires. This is not transferable from IOS or EOS experience; it is Aruba-specific and will appear in scenario items where the right answer depends on being in the right context.

Show commands are tested at the output-interpretation level. You will be expected to read show command output and identify what it tells you about device state, interface status, or a configuration problem. Memorising command syntax matters less than knowing what the output means.

Basic configuration items cover initial device setup: hostname, interface addressing, and management access. These items reward knowing the correct sequence and the correct context for each configuration step in AOS-CX.

How Networking Devices is tested

At 18%, this topic generates a substantial number of items, and the Aruba-specific content is where generic networking knowledge fails. Items on AOS-CX CLI contexts reward candidates who know the exact context required for a command, not those who know the command in isolation.

Device-type items are scenario-driven: a network design is described and you are asked which device fits a role, or a symptom is described and you are asked which device type is the source. Items reward matching device capability to the scenario requirement.

Show command items reward reading output rather than recalling syntax. The exam presents output and asks what it indicates. Candidates lose marks by misreading interface state flags or by confusing fields that look similar across different show commands.

OOBM items are a specific trap: candidates who treat it as equivalent to in-band management will pick the wrong option. The exam rewards knowing what OOBM provides that in-band management cannot.

Device knowledge carries you to the door; L2 Switching takes you inside the forwarding logic. At 12%, this topic tests whether you understand what a switch actually does with a frame, not just that it switches. The items here are more analytical than definitional: collision domains, broadcast domains, MAC tables, VLANs, and loop prevention all appear in scenarios that require you to trace traffic or predict behaviour.

– Domains, devices, and forwarding tables

Collision and broadcast domains are tested together because the exam wants to see whether you can identify the boundary each device type creates. A hub, a switch, and a router each handle these domains differently, and an item will often turn on which boundary is relevant to the scenario.

MAC address tables and ARP tables are distinct, and the exam treats them as such. MAC tables drive Layer 2 forwarding decisions; ARP tables map IP addresses to MAC addresses at Layer 3. Items reward knowing which table a device consults for which forwarding decision, and what happens when an entry is missing from either table. The flooding behaviour that results from a MAC table miss is a specific behaviour that appears in scenario items.

– VLANs and loop prevention

VLANs are tested at the design and operational level. You need to know what a VLAN does to broadcast traffic, how trunk and access ports differ, and what misconfiguration looks like in a symptom. Items will describe a connectivity failure and expect you to identify whether a VLAN mismatch or a missing trunk configuration is the cause.

Layer 2 loops are the most dangerous failure mode in a switched network, and the exam expects you to know both why they occur and how Spanning Tree Protocol prevents them. Items reward knowing the STP port states and what each state means for traffic. The trap is candidates who know that STP exists but cannot explain what happens during convergence or which port ends up in a blocking state. Avoiding loops in a design scenario requires knowing the rules STP applies, not just knowing STP's name.

How L2 Switching is tested

At 12%, this topic contributes items that are consistently scenario-based. The exam does not ask you to define a MAC table; it describes a forwarding situation and asks what the switch does next. Items reward tracing the forwarding logic step by step.

VLAN items are a reliable source of marks lost. Candidates who know VLANs conceptually but have not worked through trunk and access port configuration scenarios will misread the symptom and pick the wrong cause. The exam rewards identifying the exact misconfiguration from the described behaviour.

Loop prevention items reward knowing STP mechanics at the port-state level. Describing STP as a loop prevention protocol is not enough; items require you to apply the port-state rules to a topology. Broadcast domain items reward counting boundaries correctly across a mixed-device topology. Candidates who conflate the domain boundaries introduced by switches and routers will lose marks on items that look straightforward.

L2 Switching keeps traffic within a network; Internetwork Communication is about what happens when traffic needs to leave it. At 9%, this topic is tightly scoped but the items are applied: IP addressing, routing decisions, inter-VLAN communication, and IPv6 all appear in scenarios that require you to calculate, trace, or compare. Candidates who are comfortable with binary addressing but have not practised inter-VLAN routing or IPv6 notation will find gaps here.

– IP addressing, default gateways, and routing

IP addressing items on this exam go beyond assigning an address. You need to determine whether two hosts are on the same subnet, identify the correct subnet mask for a given requirement, and recognise when a default gateway is relevant to the forwarding decision. These are applied skills, not recall.

Default gateway items reward understanding what a host does when the destination is outside its subnet: it sends the frame to the gateway's MAC address while keeping the destination IP intact. Items that describe a connectivity failure often hinge on whether the default gateway is correctly configured or reachable.

IP routing items reward knowing how a router selects a path from its routing table: longest prefix match is the key rule. Candidates who apply a simpler rule, such as first match or most specific network number, will pick the wrong forwarding decision.

– Inter-VLAN routing and IPv6

Inter-VLAN routing connects the L2 Switching topic to this one. Traffic between VLANs must pass through a Layer 3 device, and the exam tests whether you know the two main approaches: a router with subinterfaces (router-on-a-stick) and a multilayer switch with SVIs. Items reward matching the approach to the scenario and knowing what configuration each requires.

IPv6 addressing is tested at the descriptive level: address format, prefix length notation, and the types of IPv6 addresses (link-local, global unicast, and multicast). You are not expected to subnet IPv6 to the same depth as IPv4, but you must be able to read an IPv6 address, identify its type, and know what each type is used for. Confusing link-local and global unicast addresses is a common source of lost marks.

How Internetwork Communication is tested

At 9%, this topic's items are applied and often involve a network diagram or address table. Addressing items reward calculating the correct subnet or identifying whether a host is reachable without routing. Candidates who cannot apply subnet masks quickly under time pressure lose marks that their routing knowledge would otherwise earn.

Routing items reward applying longest prefix match correctly. The trap is a routing table with multiple plausible matches: items are constructed so that a candidate who applies a less precise rule picks a different, wrong interface.

Inter-VLAN routing items reward identifying the correct Layer 3 mechanism for the described topology. Picking the right mechanism when the topology already has a multilayer switch versus a separate router is the distinction the exam tests.

IPv6 items reward address-type recognition. The exam describes a scenario or shows an address and expects you to identify its scope and purpose. Candidates who have only studied IPv4 in depth will find IPv6 items disproportionately costly for a topic this size.

WLAN Fundamentals is the largest topic on this exam at 23%, and it is where candidates without a wireless background feel the weight of the syllabus most acutely. RF behaviour does not follow the same intuitions as wired networking, and the exam exploits that. Standards, signal propagation, channel planning, interference, antenna characteristics, and frame types all appear here, and the items are applied rather than definitional.

– Standards, RF propagation, and channels

802.11 standards and amendments are tested at the capability level: which amendment introduced which frequency band or modulation scheme, and what that means for range, throughput, and compatibility. Items reward knowing the operational implication of each amendment, not just its letter designation.

RF signal propagation is about how signals behave in physical space. Reflection, refraction, absorption, and diffraction each affect coverage and throughput in different ways. Items will describe an environment or a symptom and expect you to identify the propagation effect responsible.

Channel planning is where RF knowledge becomes a design skill. The exam tests channel reuse, the difference between overlapping and non-overlapping channels, and what happens when adjacent or co-channel interference occurs. Knowing which channels are non-overlapping in the 2.4 GHz and 5 GHz bands is the working knowledge that underpins several items.

– Interference, RF design, and transmit power

Adjacent channel interference (ACI) and co-channel interference (CCI) are distinct problems with distinct solutions, and the exam tests both. ACI results from overlapping channel use; CCI results from the same channel being reused too close together. Items reward identifying which interference type is present in a described scenario and what the appropriate design response is.

RF design basics cover cell sizing, coverage overlap, and the trade-offs involved in AP placement. Items in this area reward understanding why a design choice produces a particular coverage or capacity outcome, not just what the design looks like.

Transmit power directly affects cell size and interference. Increasing power extends range but increases the potential for CCI. Items reward knowing this relationship and applying it to a design or troubleshooting scenario. Candidates who treat transmit power as simply more-is-better will be caught by items where the problem is too much power, not too little.

– Antennas, mobility, and frames

Antenna fundamentals cover gain, directionality, and polarisation. Omnidirectional and directional antennas have different use cases, and items reward matching antenna type to deployment scenario. Gain is expressed in dBi, and understanding what a dB change means in practical terms (doubling or halving power) is a working skill for this section.

WLAN mobility and roaming cover what happens when a client moves between APs. The exam tests the roaming process at a functional level: when does a client decide to roam, and what does the network need to support seamless transitions.

Management and control frames are the signalling layer of 802.11. Beacon, probe, authentication, and association frames each play a specific role in the client join process. Items reward knowing the sequence and what each frame type establishes. The 802.11 frame header fields (frame control, duration, address fields) are tested at the field-purpose level.

How WLAN Fundamentals is tested

At 23%, this topic generates more items than any other on the exam. The range of sub-topics means you cannot afford a weak area: RF propagation, channel planning, interference, antenna selection, frame sequences, and roaming all contribute items independently.

RF items reward applying physical principles to described environments. The trap is applying a wired-network intuition to a wireless scenario: more power, for example, does not always improve performance, and items are designed to catch that assumption.

Channel and interference items reward precise identification. ACI and CCI look similar to a candidate who has not drilled the distinction; items are constructed so that a vague understanding produces a plausible but wrong answer.

Frame sequence items reward knowing the order and purpose of each management frame in the client association process. Candidates who know frame types by name but not by function will misidentify what a frame accomplishes at a specific step.

Antenna items reward matching gain and directionality to the deployment requirement. Picking the wrong antenna type for a described environment is the most common loss point in this section.

WLAN Fundamentals gave you the RF and protocol knowledge; this topic shifts to the management plane: how Aruba Central ties the deployment together. At 9%, the items are platform-specific. Candidates who know generic cloud management concepts will recognise the architecture, but the exam tests Aruba Central's own terminology, wizard stages, and communication model. Generic Wi-Fi deployment experience does not substitute for knowing how Central works.

– Network planes and management models

Network device planes (management, control, and data) are the architectural foundation for this topic. The exam tests whether you can identify which plane handles which function and why separating them matters in a cloud-managed deployment. Items reward placing a specific function in the correct plane, not just naming the three planes.

The distinction between local management and server-based management is tested as a trade-off: what each model provides, where each model falls short, and which scenarios favour one over the other. Aruba Central represents the server-based model, and items will contrast its capabilities against local management to test whether you understand the operational difference.

– Aruba Central architecture and WLAN deployment

Aruba Central as a cloud-based management platform is tested at the architectural and operational level. The exam expects you to know what Central manages, how it communicates with APs, and what prerequisites an AP must meet before it can be managed by Central. Items reward knowing the onboarding requirements and what happens when they are not met.

Central's communication path to APs involves specific connectivity and licensing prerequisites. Items will describe a scenario where an AP is not appearing in Central and expect you to identify the missing prerequisite from the described conditions.

The Central wizard deployment stages are tested in sequence. The exam rewards knowing what each stage of the wizard configures and in what order. Candidates who know the end state of a WLAN deployment but not the step-by-step wizard process will find these items harder than expected. Each stage has a distinct purpose, and confusing adjacent stages is a common source of lost marks.

How Deploying WLANs with Central is tested

At 9%, this topic's items are platform-specific and scenario-driven. The exam does not test generic cloud management theory; it tests Aruba Central's specific architecture, prerequisites, and wizard workflow. Generic knowledge of cloud platforms will not carry you through items that ask about Central's communication requirements or onboarding steps.

Plane-identification items reward placing a function in the correct plane without hesitation. The trap is the control plane versus the management plane: candidates who conflate the two will pick the wrong plane for functions that sit at the boundary.

Management model items reward understanding the operational trade-off, not just knowing that two models exist. Items describe a scenario and expect you to identify which model fits and why.

Wizard-stage items reward sequential knowledge. The exam will describe a partially completed deployment or a configuration gap and expect you to identify which wizard stage addresses it. Candidates who have not worked through the Central wizard stages in order will find these items the most difficult in the topic.