Aruba Architect Expert (Written)

Experienced network architects and senior consultants who design Aruba solutions and already hold professional-level Aruba certifications. It suits people who own design decisions - segmentation models, redundancy, wireless RF planning, automation strategy - rather than only implementing someone else's design.

Multiple-choice and multiple-response questions, many framed as design scenarios. Multiple-response items typically require exact selection, so read whether the stem asks for all that apply or the best answer before committing.

Question count, time limit, and scoring are set by the certifying body and change over time. The official Aruba certification site publishes the current exam description and logistics; use that as the authoritative source rather than figures quoted in forums or training blogs.

Passing score and exam fee are published by the certification body and are not fixed indefinitely. Check the official Aruba certification page for the current values before you schedule, and budget for a possible retake if your first attempt falls short.

It is an expert-level written exam, so difficulty comes from breadth and from scenario ambiguity rather than obscure trivia. Candidates with several years of real design experience usually find the technology familiar but the trade-off questions demanding. Weak spots are usually automation and assurance depth.

Retakes are generally permitted, but the waiting period, fees, and any attempt limits are governed by the certification body's policy. Confirm the current retake rules on the official site, and use the score report to target the domains where you lost the most ground.

Start with design methodology, because it frames every later scenario, then campus and branch design, which carries the heaviest weight. Layer in security segmentation, then data center and WAN edge, then automation and assurance. Finish with migration and lifecycle topics, which reward everything you learned earlier.

Answering from product habit instead of the stated requirements, ignoring constraints like budget, staffing, or existing investment, and under-preparing automation and monitoring because they feel less like 'design'. Another frequent error is choosing the technically elegant option when the scenario asks for the operationally realistic one.

Write reference designs against realistic constraints: a campus refresh with wireless density targets, a segmented branch, a data center fabric, an API-driven provisioning workflow. For each, state requirements, options considered, and why you rejected alternatives. That habit maps directly onto how the scenario questions are written.

The written exam is one component of the certification path defined by the certifying body, which may require additional steps. Review the official certification requirements to understand exactly what the written exam contributes and what else is needed.