HPE6-A85 HPE Network Campus Access Associate Exam Topics and Questions

Planning is where the exam tests whether you can think before you touch a device. At 13%, this topic rewards candidates who understand the full arc from reading an existing environment to producing a design document an engineer can actually build from. Miss this foundation and you will make costly assumptions later in the exam, particularly when Configure and Troubleshoot items reference a design decision you were supposed to have made here.

– Reading the environment and the architect's intent

Before any design work begins, you need to understand what is already in place. Analysing the current environment means identifying existing switching and wireless infrastructure, capacity constraints, coverage gaps, and any business or compliance requirements that will shape what you propose. On the exam, this shows up as scenarios where you must decide what information is relevant before moving forward.

Interpreting a high-level design is a different skill. The architect gives you intent, not detail: topology diagrams, VLAN strategy at a broad level, wireless coverage zones. Your job is to extract what the design is actually asking for, not to second-guess it. Items here test whether you can read a diagram or design brief and correctly infer the requirements that will drive your low-level work.

– Translating design into a buildable plan

Creating a low-level design is where planning becomes actionable. This means specifying IP addressing, VLAN assignments, SSID parameters, AP placement, uplink configurations, and the sequence of steps a technician will follow. The exam expects you to know what belongs in a low-level design document and, crucially, what level of detail is appropriate at this stage versus what gets decided during deployment.

Preparing for implementation covers the practical groundwork: staging equipment, confirming firmware versions, gathering credentials, and verifying that the physical site is ready. Items in this area often present a scenario where something is missing from the pre-implementation checklist and ask you to identify the gap. Candidates who treat preparation as an afterthought lose marks here because the exam treats it as a distinct, examinable step, not a footnote to the design phase.

How Plan the Solution is tested

At 13%, this topic contributes a meaningful slice of items, and they tend to be scenario-based rather than recall-based. You will be given a description of a site, an existing topology, or a fragment of a high-level design, and asked to decide what the next correct step is or what the low-level design should specify.

The most common trap is conflating design phases. Candidates who blur the line between high-level intent and low-level specification, or who skip straight to configuration thinking, choose options that are premature or too vague. Items reward selecting the action that matches the correct phase of planning.

A second trap is ignoring the current environment. When a scenario includes details about what is already deployed, those details are there for a reason. Answers that treat the site as a greenfield when it is not will consistently lead you to the wrong option. Read every environmental detail as a constraint, not background noise.

After planning comes execution, and at 32% this is the heaviest topic on the exam by a significant margin. Configure the Solution is where most candidates either build a comfortable lead or bleed marks they cannot recover. The weight reflects how central hands-on configuration knowledge is to the associate-level role: if you cannot onboard, provision, deploy, and validate an Aruba campus solution, nothing else in the syllabus matters much.

– Getting devices onto the network

Device onboarding covers the initial steps of bringing Aruba access points and switches under management, whether through Aruba Central, AirWave, or a controller-based setup. You need to know the provisioning models, how devices are claimed or discovered, and what can go wrong during that first contact. The exam presents scenarios where onboarding has stalled and asks you to identify the cause or the correct next step.

Device provisioning follows onboarding and deals with pushing the right configuration to the right device. This includes group-based provisioning in Central, template logic, and the relationship between device profiles and site settings. A common exam trap is assuming that onboarding and provisioning are the same step. They are sequential and distinct, and items will test whether you know which action belongs to which phase.

– Deploying and confirming the build

Deploying the solution means taking a provisioned device and making it operational in the network: configuring SSIDs, VLANs, uplinks, security settings, and any integrations such as role-based access. At this weight, expect the exam to go deep on Aruba-specific configuration choices, including the difference between tunnel and bridge forwarding modes, VLAN tagging behaviour on wired uplinks, and how wireless security profiles map to SSIDs.

Validating the solution is the confirmation step that closes the configuration loop. Validation means verifying that clients can associate and authenticate, that traffic is forwarded correctly, and that the configuration matches the design intent. Items here reward candidates who know which show commands, dashboard views, or test procedures confirm a specific aspect of the build. Skipping straight to troubleshooting when validation would have caught the issue is a pattern the exam penalises.

How Configure the Solution is tested

With nearly a third of the exam sitting here, you will see more items from this topic than from any other. They range from straightforward recall of configuration steps to multi-step scenario questions where you must identify what is misconfigured or what is missing from a partial setup.

Items reward precision. Aruba terminology matters: knowing the difference between a network profile and a security profile, or between an AP group and a site, is the kind of detail that separates strong options from plausible-looking distractors. Candidates who think in generic networking terms and do not anchor their answers to Aruba-specific constructs lose marks consistently.

The validation sub-topic is where overconfident candidates drop points. Items do not reward stopping at deployment; they reward closing the loop by confirming the outcome against the design. Read every scenario for whether the configuration step or the verification step is being asked about, because the exam treats them as separate skills.

Once the solution is live, the work shifts from building to running. Operate the Solution, at 22%, tests the day-to-day skills that keep a campus network healthy over time. Candidates who have only studied deployment often underestimate this topic, assuming operations is just monitoring dashboards. The exam disagrees: it treats monitoring, firmware management, ongoing configuration changes, and documentation as distinct disciplines, each with its own correct procedures.

– Visibility and keeping the platform current

Monitoring and reporting tasks cover how you use Aruba Central or AirWave to observe client health, AP status, switch performance, and network-wide trends. The exam is not interested in whether you can find a dashboard; it tests whether you know what a specific alert or metric means and what action it implies. Items present a monitoring output and ask you to interpret it correctly.

Firmware updates are a procedural area with real consequences for getting the order wrong. You need to know how to stage firmware, how to manage update groups in Central, and what the risks of updating controllers or APs out of sequence are. The exam rewards the candidate who treats firmware management as a change-control exercise, not a click-and-forget task. Scenarios will often include a constraint, such as a maintenance window or a mixed-version environment, that changes which update path is correct.

– Making changes and keeping records

Performing basic ongoing configuration changes tests whether you can modify a live environment without breaking it. This includes updating SSIDs, adjusting VLAN assignments, changing security profiles, and modifying switch port configurations in response to a business request. The key exam skill is knowing the scope of a change: which devices are affected, whether a service interruption is expected, and how to confirm the change took effect.

Maintaining documentation is often dismissed by candidates as soft overhead, but the exam includes it for a reason. Accurate records of IP addressing, VLAN tables, AP placement, and configuration baselines are what make every other operational task faster and safer. Items in this area test whether you know what documentation should be updated after a change and why an undocumented change creates risk. The exam rewards treating documentation as part of the change process, not something you do later if you remember.

How Operate the Solution is tested

At 22%, Operate the Solution is the second-largest topic, and it catches candidates who over-prepared for configuration and under-prepared for everything that follows go-live.

Monitoring items typically present a dashboard view, a log excerpt, or an alert description and ask you to identify the right operational response. Items reward matching the observation to the correct action, not just recognising that something is wrong. Candidates who jump to configuration changes when the scenario calls for a monitoring verification step lose marks.

Firmware items reward sequential thinking. The exam will test whether you know what to check before initiating an update and what to confirm afterwards. Skipping pre-checks is the most common losing pattern.

Documentation items are short but unforgiving. They test whether you treat record-keeping as integral to operations. Candidates who treat documentation as optional lose these marks entirely, and they are easy marks for anyone who takes the sub-topic seriously.

Troubleshooting is the topic where associate-level candidates most often overestimate themselves. At 25%, it is the second-heaviest topic on the exam, and it demands structured thinking, not instinct. The exam is not looking for candidates who can eventually find a fix; it rewards candidates who follow a defined methodology, scope the problem correctly, and work systematically from the physical layer upward before drawing conclusions.

– Method and scope before any action

Defining a basic troubleshooting methodology means knowing the steps in order: gather information, establish a theory, test the theory, implement a fix, verify the fix, and document the outcome. The exam tests this sequence directly. Items will present a scenario where a technician has jumped ahead, and the strongest option will be the one that returns to the correct step rather than continuing down the wrong path.

Determining the issue scope is the skill of deciding how wide the problem is before touching anything. Is this one client, one AP, one VLAN, one building, or the whole campus? The exam rewards narrowing scope through evidence, not assumption. Candidates who treat every problem as potentially network-wide and over-escalate, or who treat a widespread outage as a single-client issue, choose weaker options. Scope determines your next action, and the exam knows it.

– Physical layer and what you can see

Physical layer troubleshooting covers the things you can observe or measure directly: cable connectivity, port LEDs, PoE status, AP mounting and orientation, and RF interference sources. The exam expects you to know what physical symptoms point to which root causes. An AP that powers on but does not associate is a different problem from one that never powers on, and the troubleshooting path diverges at that observation.

This sub-topic also covers the use of site survey tools and spectrum analysis at a basic level. You do not need deep RF engineering knowledge for an associate exam, but you do need to know when a physical layer check is the right starting point versus when the evidence already points higher up the stack.

– Layer 2 through Layer 7 and closing the loop

L2 through L7 troubleshooting covers the bulk of the technical depth in this topic. At Layer 2, expect questions around VLAN misconfiguration, STP behaviour, and trunk port issues on wired uplinks. Layer 3 items will test IP addressing, routing between VLANs, and gateway reachability. Further up the stack, the exam covers DHCP failures, DNS resolution problems, authentication failures (802.1X, MAC-auth, captive portal), and application-layer connectivity.

For wireless, this range includes association failures, authentication rejections, and roaming problems. You need to know which log or show output reveals the failure at each layer, because the exam presents a symptom and asks you to identify the layer and the tool.

Implementing and validating a resolution closes the troubleshooting cycle. Items here reward confirming that the fix resolved the original symptom and did not introduce a new one, then documenting the change. Candidates who stop at the fix and do not verify lose marks that are straightforward to keep.

How Troubleshoot the Solution is tested

At 25%, this topic produces a large number of scenario-based items, and they are among the most demanding on the exam. A typical item gives you a symptom, some diagnostic output, and a set of plausible actions. Items reward the candidate who applies the methodology correctly, not the one who recognises the symptom from experience and skips steps.

The most reliable losing pattern is acting before scoping. Candidates who read a symptom and immediately select a configuration fix, without first determining whether the problem is isolated or widespread, choose options that are premature. The exam consistently rewards the scoping step.

Physical layer items are often treated as easy and skipped mentally, which is how candidates miss them. The exam includes physical checks because real engineers skip them too.

Validation after resolution is tested as a separate skill. Stopping at implementation is penalised. Know what confirmation looks like for each type of fix, and treat verification as mandatory.

After troubleshooting comes refinement. At 8%, Optimize the Solution is the lightest topic on the exam, but candidates who ignore it leave marks on the table unnecessarily. Optimisation sits at the intersection of operations and design: you need to know what good looks like, measure what you actually have, apply best practices to close the gap, and confirm the improvement. The exam tests this as a disciplined cycle, not a collection of tips.

– Establishing and using a baseline

Performing an environment baseline means capturing the current state of the network before making any optimisation changes. This includes RF metrics such as signal strength, channel utilisation, and client SNR values, as well as wired performance indicators like port utilisation and error rates. The exam tests whether you know what to measure and why the measurement must happen before any change, not after.

Comparing results to the baseline is the closing step of the optimisation cycle. Once best practices have been applied, you return to the same metrics and determine whether performance improved, stayed the same, or degraded. Items here reward candidates who treat the comparison as a formal verification step. The trap is assuming that applying a best practice automatically constitutes an improvement; the exam expects evidence.

– Wireless and wired best practices

Applying WLAN best practices covers channel planning, transmit power settings, band steering, minimum data rates, and client density management. For an associate-level exam, you are expected to know the standard recommendations and the reasoning behind them well enough to identify when a configuration deviates from best practice and what effect that deviation is likely to have.

Applying LAN best practices addresses the wired side: spanning tree configuration, port security, VLAN segmentation, uplink redundancy, and QoS marking. The exam does not expect deep design expertise here, but it does expect you to recognise a configuration that violates a standard recommendation and to select the option that corrects it. Both best-practice sub-topics are tested against realistic scenarios, not as abstract rule recall.

How Optimize the Solution is tested

At 8%, this topic contributes a small number of items, but they are not throwaway marks. Optimisation items tend to be scenario-based, presenting a network with a performance problem and asking you to identify the best-practice change that would address it.

The baseline sub-topics are tested as process questions: items reward candidates who know that measurement must precede change and that verification must follow it. Candidates who select options that apply a fix without establishing a baseline, or who skip the post-change comparison, choose weaker options.

WLAN best-practice items reward knowing the effect of a setting, not just its name. Knowing that reducing minimum data rates can help or hurt client density depending on the environment is the kind of nuance the exam probes.

LAN best-practice items are often framed around a symptom that a correct configuration would prevent. Items reward identifying the configuration gap, not just naming the protocol involved. Because this topic is small, thorough preparation here is efficient: the effort-to-mark ratio is favourable.