HPE7-A11 HPE Network Campus Access Professional Architect Exam Topics and Questions
These HPE Network Campus Access Professional Architect (HPE7-A11) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise HPE7-A11 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the HPE Network Campus Access Professional Architect certification exam.
Let's Practice Free HPE7-A11 Questions Aligned with Official Exam Topics
This is where the entire engagement is won or lost before a single cable is specified. Discovery sets the foundation for every design decision that follows, and the exam treats it seriously: at 23%, roughly one in four questions tests whether you know how to extract, organise, and document what a customer actually needs. Gaps here compound into wrong designs later, and the exam is built to catch that chain of errors. β Stakeholders and their roles Knowing who to...
This is where the entire engagement is won or lost before a single cable is specified. Discovery sets the foundation for every design decision that follows, and the exam treats it seriously: at 23%, roughly one in four questions tests whether you know how to extract, organise, and document what a customer actually needs. Gaps here compound into wrong designs later, and the exam is built to catch that chain of errors.
β Stakeholders and their roles
Knowing who to talk to is half the battle. The exam expects you to distinguish between the people who approve budgets, the people who operate the network day-to-day, and the people who set security or compliance policy. Each group surfaces different requirements, and a design that satisfies one while ignoring another will fail in practice and on the exam. Questions in this area probe whether you can map a given stakeholder to the right lane of influence and adjust your discovery approach accordingly. The 4% weight is modest, but getting this wrong early skews every downstream answer.
β Current environment and technical requirements
Together these two sub-topics carry 15% of the exam, making them the heaviest single cluster in this topic. Collecting and analysing the current environment means more than noting what switches are installed: it means understanding traffic patterns, existing VLANs, uplink capacities, power budgets, and any legacy constraints that a new campus access design must accommodate or replace. Interpreting technical requirements then translates that raw information into design inputs. The exam tests whether you can read between the lines of a customer's stated need and identify the implied technical constraint. A customer who says "we need better Wi-Fi in the conference rooms" is also telling you something about density, roaming, and authentication that must surface in your requirements register.
β Assumptions and documentation
Documenting assumptions is the professional discipline that separates a guesswork design from a defensible one. The exam treats an undocumented assumption as a design flaw, because an assumption that is not recorded cannot be validated or challenged. This sub-topic asks you to recognise when a gap in customer information requires an explicit assumption, and to record it in a form that a reviewer could later accept or reject. On the exam, scenarios will present incomplete information and reward the response that acknowledges the gap rather than silently filling it. The 4% weight mirrors the stakeholder sub-topic, but in the context of a professional architect role, the habit of writing down what you do not yet know is as important as any technical skill.
How Discover customers' requirements is tested
At 23%, this topic will appear frequently enough that a weak performance here is hard to recover from. Items are scenario-driven: you are given a customer situation, sometimes with conflicting signals from different stakeholders, and asked to determine the most appropriate next step or the most complete set of documented inputs. The trap is treating discovery as a formality. Candidates who jump straight to technology selection before the requirements are fully characterised will find that the exam consistently rewards the slower, more methodical path.
A second common loss point is the assumptions sub-topic. When a scenario presents missing information, the instinct is to infer and move on. Items in this area reward the response that flags the gap formally rather than resolving it silently. Similarly, questions on stakeholder mapping reward precision: assigning the wrong role to a stakeholder leads to a requirements set that looks complete but is missing a critical input. Read every scenario detail before committing to an answer.
A question bank with full coverage across all four topics lets you see exactly where your discovery knowledge holds up and where it does not. Working through a timed practice test on this topic alone will surface the specific sub-topics costing you marks, faster than re-reading course notes.
The question below puts you in a live discovery scenario and asks you to make the call a professional architect would make at that moment.
You are developing a technical proposal for a customer that plans to deploy HPE Aruba Networking Cloud Central-managed AOS-10 Access Points in a typical campus office environment. The customer has used ARM-based radio resource management successfully for many years. During their transition to AOS-10, they ask for guidance on suitable initial EIRP (Effective Isotropic Radiated Power) values for new radio profiles in HPE Aruba Networking Central.
Which EIRP configuration option should be recommended as an appropriate starting point for this office deployment?
Once discovery is complete, the work shifts from listening to deciding. Analysis is where requirements become technology choices, diagrams, and a preliminary bill of materials, and at 30% it is the single heaviest topic on the exam. The gap candidates fall into here is treating analysis as a mechanical translation of requirements into products. The exam is testing design judgement, not product recall, and the questions are written to separate the two. β Technology selection Identifying technologies to satisfy requirements...
Once discovery is complete, the work shifts from listening to deciding. Analysis is where requirements become technology choices, diagrams, and a preliminary bill of materials, and at 30% it is the single heaviest topic on the exam. The gap candidates fall into here is treating analysis as a mechanical translation of requirements into products. The exam is testing design judgement, not product recall, and the questions are written to separate the two.
β Technology selection
Identifying technologies to satisfy requirements is not a catalogue exercise. The exam presents requirements with constraints, and the right technology choice depends on reading both. A high-density wireless deployment in an auditorium demands different access-point placement logic and radio management than a sparse office floor, even if both customers ask for "campus Wi-Fi". Wired access decisions similarly depend on power budget, uplink redundancy requirements, and the switching architecture already in place or being replaced. At 9%, this sub-topic rewards candidates who can match a requirement to a technology rationale, not just a product name. If you find yourself memorising SKUs rather than understanding the design triggers that make one approach better than another, redirect that effort.
β Diagrams, topologies, and the preliminary BoM
The functional diagram and the wired/wireless topology sub-topics together carry 21% of the exam, more than any other pair in this topic. A functional diagram or workflow makes the logical relationships in a design visible: which segments are isolated, where policy is enforced, how traffic flows between the access layer and the distribution or core. The exam tests whether a given diagram accurately represents a set of requirements, or whether it introduces a gap or contradiction.
The preliminary bill of materials is where design meets commercial reality. At this stage it is an estimate, not a final commitment, and the exam distinguishes between the two. A preliminary BoM must reflect the topology decisions made above it: if the topology calls for redundant uplinks, the BoM must include the hardware that supports them. Candidates lose marks by treating the BoM as an afterthought rather than a direct output of the topology decisions.
How Analyze requirements is tested
Thirty percent of the exam lives here, and the items are almost entirely scenario-based. You will be given a set of requirements, sometimes with a partial diagram or a partial BoM, and asked to identify what is missing, what is inconsistent, or what the next correct step is. The items do not reward technology trivia. They reward the ability to trace a requirement through to its logical design consequence.
The most common loss point is the preliminary BoM. Candidates treat it as a shopping list and miss the fact that the exam is checking whether the list is consistent with the topology. An item might show a topology diagram and a BoM side by side and ask which element of the BoM is unsupported by the design. That requires reading both artefacts together, not in isolation.
Functional diagrams are tested similarly: a diagram that looks plausible but violates a stated requirement is a standard distractor. Slow down on these items, check each element of the diagram against the requirements, and do not let a familiar-looking topology shortcut your analysis.
Seeing a large volume of analysis-style items before exam day trains your eye to spot the inconsistency in a diagram or BoM that the question is built around. The practice test format lets you work through these under timed conditions, which is where diagram-reading speed matters most.
The question below presents an analysis scenario and asks you to apply the kind of design judgement this topic rewards.
A global cruise line company must refresh its current fleet. It will refresh the ship's ''insides'' to be cost-effective and improve sustainability, replacing all WLAN/LAN hardware. During this refresh, the company will not change its existing security requirements. The CIO also wants to minimize unused switch ports. Any future expansion will require a hardware refresh. They will begin with the smallest ship, with a maximum of 800 guests.
Each ship has a LAN infrastructure comprising two core switches, up to 10 redundant distribution switches, and up to 500 access switches (400 cabins and 100 technical rooms). The core switches are in the ship's MDF, and the distribution switches are in the IDFs. Each cabin and technical room receives one individual access switch.
The ship's cabling infrastructure will not be refreshed. Every IDF is connected to the MDF by SMF, with two pairs available for the interconnect between core and distribution. The SM fiber between the MDF and IDF is less than 300 meters (980 ft) long and is OS1. Each cabin is connected to the IDF by one OM2 pair, with a maximum length of 60 meters (200 ft). Each technical room is connected to the IDF by one OM2 pair, with lengths from 100 to 150 meters (320 to 500 ft).
For every cabin/technical room, the customer wants to replace the existing fan-less 2530/2540 switches without changing the requirements, except that the uplink to the distribution switch must be upgraded to 10GbE to accommodate increased network traffic, and the technical rooms require redundant power.
The WLAN infrastructure will be refreshed 1:1, with no new cabling or AP locations. The WLAN infrastructure uses 200/300 series indoor and outdoor APs running InstantOS (fewer than 300 APs), and the customer has no WLAN requirement changes.
The cruise line company will replace its existing Internet connection before the LAN/WLAN refresh. The new Internet connection will provide 99.8% uptime, required to keep paid guest Wi-Fi operational. With this new Internet connection, the CIO wants to base the design on Aruba's ESP architecture because the Internet connection is guaranteed.
Based on best practices, what optic type should be recommended for the connection between the IDF and the technical rooms?
Analysis produces inputs; architecture produces commitments. This topic is about turning a validated set of requirements and technology choices into documents that a customer, a project manager, and an implementation team can each act on. At 30%, it matches the previous topic in weight, but the demand shifts from design judgement to communication precision. A technically sound design that is poorly documented will fail here just as reliably as a weak design. β Proposal and BoM finalisation The technical proposal...
Analysis produces inputs; architecture produces commitments. This topic is about turning a validated set of requirements and technology choices into documents that a customer, a project manager, and an implementation team can each act on. At 30%, it matches the previous topic in weight, but the demand shifts from design judgement to communication precision. A technically sound design that is poorly documented will fail here just as reliably as a weak design.
β Proposal and BoM finalisation
The technical proposal document is the primary artefact this topic tests. It must be specific enough for an implementation team to execute and clear enough for a technical reviewer to validate. The exam probes whether you know what belongs in a technical proposal and what does not: scope boundaries, design rationale, configuration assumptions, and references to the requirements that drove each decision. Vague or aspirational language in a proposal is a design risk, and the exam treats it as one.
Finalising the BoM is distinct from the preliminary version produced in analysis. At this stage, every line item must be justified by the architecture. The exam will present scenarios where the BoM and the technical proposal are slightly out of alignment and ask you to identify the discrepancy. The skill being tested is cross-document consistency, not arithmetic.
β Executive communication and implementation planning
The solution overview and executive brief serve a different audience than the technical proposal. An executive reader needs to understand what the solution does for the business, the cost envelope, and the risk posture, without working through network diagrams. The exam tests whether you can identify which content belongs in an executive brief and which belongs in the technical document. Putting technical detail into an executive summary is as wrong as putting business justification into a topology diagram.
Implementation and migration guidelines are where the architecture meets operational reality. These documents must address sequencing, rollback options, and dependencies between phases. A campus access migration that does not account for the order in which VLANs are moved, or the impact on active users during cutover, is incomplete. The exam rewards candidates who treat implementation planning as a design discipline, not an afterthought left to the deployment team.
β Technical and business review
Conducting a technical and business review is the checkpoint before the solution moves to proposal. The exam tests what a review is for: validating that the architecture addresses all documented requirements, that the BoM supports the design, and that the assumptions made during discovery are still valid. A review is not a sales meeting, and the exam distinguishes between the two. Questions in this area reward candidates who understand that a review can and should surface design changes before they become contractual commitments. At 5%, this sub-topic is the smallest in the topic, but candidates who treat a review as a rubber stamp rather than a genuine validation step will lose marks on scenario items that hinge on what the review should catch.
How Architect the solution is tested
At 30%, this topic demands sustained performance across five sub-topics that span technical writing, financial accuracy, executive communication, migration planning, and formal review. Items are scenario-based and often present a partially completed artefact, such as a draft technical proposal or an executive brief, and ask you to identify what is missing or misplaced.
The most reliable loss point is audience confusion. The exam consistently presents content that is technically accurate but placed in the wrong document type. Knowing that a detail is correct is not enough; you must also know which artefact it belongs in and why.
Migration and implementation items reward sequencing logic over technical depth. The question is rarely about the technology being migrated; it is about the order of operations and the conditions under which a rollback is valid. Candidates who focus only on the technical architecture and skim the implementation and review sub-topics tend to leave marks on the table in this topic. Spread your preparation across all five sub-topics rather than concentrating on the ones that feel most technical.
Coverage across all five sub-topics in this area is uneven in most study guides. A full question bank lets you check whether you have genuine gaps in the less technical sub-topics, such as executive communication or review conduct, before those gaps cost you on exam day.
The question below draws from this topic and tests the kind of cross-document or audience-awareness judgement the exam rewards here.
Architecture that cannot be communicated and defended does not get built. This final topic moves from documents to dialogue, testing whether you can present a solution to a customer and hold your ground when it is challenged. At 17%, it is the lightest topic on the exam, but the skills it tests are distinct from everything that came before. Candidates who are strong on technical design sometimes underestimate this area and lose marks they could have held. How Propose the...
Architecture that cannot be communicated and defended does not get built. This final topic moves from documents to dialogue, testing whether you can present a solution to a customer and hold your ground when it is challenged. At 17%, it is the lightest topic on the exam, but the skills it tests are distinct from everything that came before. Candidates who are strong on technical design sometimes underestimate this area and lose marks they could have held.
How Propose the solution is tested
With two sub-topics carrying 10% and 7% respectively, this topic splits between contribution to the proposal and defence of it. Items in the contribution sub-topic test whether you know what a professional architect's role is during the proposal phase: what you own, what you hand off, and how the technical content you have produced feeds into the commercial proposal. The trap is conflating the architect's role with the account manager's role. The exam rewards precise role boundaries.
Defending the solution is where scenario items become adversarial. You will be presented with a customer objection or a competing proposal and asked how the architect should respond. Items reward responses that address the technical substance of the objection rather than deflecting or re-selling. A challenge about redundancy, cost, or scalability should be met with design rationale drawn from the architecture itself, not with reassurances.
Candidates lose marks here by selecting responses that are commercially smooth but technically hollow. The exam is assessing an architect, and it rewards architect-level answers.
Before sitting the exam, use the free demo of the practice test to check your feel for how proposal and defence items are framed. If the style is unfamiliar, a full bank gives you enough volume to adjust before it matters.
The question below puts you in the proposal room and asks you to respond the way the exam expects a professional architect to respond.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full HPE7-A11 Exam Questions π