Aruba Architect Expert (Written) key terms

A layered approach that separates access, distribution, and core functions so each tier has a clear role, which simplifies scaling, troubleshooting, and policy enforcement across campus networks.

A campus topology with distinct access, distribution, and core layers, typically used in large buildings where distribution switches aggregate access closets and the core provides high-speed transport between them.

A two-tier design where the core and distribution roles are combined into a single layer of switches, reducing cost and hops in smaller campuses while preserving redundancy through paired devices.

A design where Layer 3 routing extends to the access layer, eliminating spanning tree dependence and enabling per-link load sharing, which is common in modern fabric-style campus deployments.

A Layer 2 loop-prevention protocol that elects a root bridge and blocks redundant paths, ensuring a loop-free topology; design choices such as root placement and edge features affect convergence and stability.

Bundling multiple physical links into one logical channel to increase bandwidth and provide redundancy, requiring consistent configuration on both ends and supported by protocols such as LACP.

An aggregation technique that spans two or more switches so a downstream device can form a single logical bundle to both, providing device-level redundancy without relying on spanning tree.

A data center and campus architecture that uses VXLAN to stretch Layer 2 segments over a Layer 3 underlay and EVPN as the control plane for MAC and IP reachability and multitenancy.

A tunneling protocol that encapsulates Layer 2 frames in UDP packets, allowing segments to span routed networks; a 24-bit identifier supports many logical networks over shared infrastructure.

A data center design where every leaf switch connects to every spine switch, giving predictable latency and equal-cost paths; servers attach to leaves, and spines only forward traffic.

The underlay is the physical routed network carrying traffic, while the overlay is the logical tunneled network built on top; separating them lets each be designed and scaled independently.

A WAN architecture that centrally manages policy and steers traffic across multiple transports such as broadband and MPLS, using application awareness and dynamic path selection to improve cost and resilience.

The ability to choose a WAN path per application or flow based on measured latency, loss, and jitter, rerouting traffic automatically when a link degrades.

A policy that defines acceptable performance thresholds for an application and directs traffic only over paths that meet those thresholds, falling back to alternates when they are not met.

The device or function at a branch or data center that connects the local network to WAN transports, applying routing, policy, encryption, and path selection before traffic leaves the site.

A security approach that enforces policy between individual workloads or users rather than only at network boundaries, limiting lateral movement after a compromise.

Assigning permissions to roles rather than to individual users or devices, so policy follows function and can be applied consistently across wired, wireless, and remote access.

Automatically placing users and devices into the correct network segment based on identity, device type, or posture at connect time, instead of relying on static port or SSID assignments.

A security model that assumes no implicit trust based on location and verifies identity and device health for every access request, enforcing least privilege continuously.

A port-based authentication standard that uses an authenticator, supplicant, and authentication server to admit devices to the network only after credentials are validated.

A framework that authenticates endpoints, assesses their compliance posture, and then permits, restricts, or remediates access before or during connection to the network.

A planning or validation exercise that measures signal coverage, interference, and capacity at a location so access point placement and channel plans meet design requirements.

A coordinated assignment of radio channels and widths across access points to minimize co-channel interference and maximize reuse within a coverage area.

Degradation that occurs when multiple access points or clients transmit on the same channel in overlapping areas, reducing throughput and increasing retransmissions.

A design tradeoff between ensuring signal reaches all areas and ensuring enough access points and airtime exist to serve the number of clients and their bandwidth demands.

Wireless planning for venues with many concurrent users, emphasizing smaller cells, band steering, airtime fairness, and adequate backhaul rather than maximum transmit power.

A mechanism that prevents slow clients from consuming a disproportionate share of wireless medium time, improving experience for all clients sharing an access point.

Planning connectivity, security, and survivability for small sites, often using a single integrated device or SD-WAN appliance with local breakout and centralized management.

Operating network infrastructure through programmatic interfaces rather than only graphical or command-line tools, enabling repeatable configuration, integration, and automation.

Coordinating multiple automated tasks and systems into an ordered workflow so that end-to-end services can be provisioned and changed consistently across domains.

Defining network and system configuration in version-controlled files that tools apply automatically, making changes reviewable, repeatable, and recoverable.

The gradual divergence between intended and actual device configuration caused by manual or ad hoc changes; automation and compliance checks are used to detect and correct it.

A model where administrators declare desired outcomes such as policy or service levels, and the system translates them into device configuration and continuously verifies they are met.

Continuous measurement of network health and user experience against intended outcomes, combining telemetry, analytics, and testing to detect problems before users report them.

Streaming operational data such as interface statistics, flow records, and client metrics from devices to a collector for near-real-time visibility and analysis.

Applying analytics and machine learning to network telemetry and events to correlate anomalies, predict issues, and reduce manual troubleshooting effort.

A recorded snapshot of normal performance and configuration used as a reference for detecting anomalies, validating changes, and planning capacity growth.

Planning and governing each phase of equipment and software from design through deployment, maintenance, and retirement, including end-of-sale and end-of-support tracking.

Sequencing the move from an existing design to a new one, including validation, rollback, and cutover steps, to reduce service risk during change.

A limited-scope rollout used to validate design, configuration, and operations before broad deployment, producing evidence and refinements for the full migration.

The full cost of a solution over its life, including acquisition, licensing, operations, staffing, power, and retirement, used to compare design alternatives.