Aruba Campus Access Architect (HPE7-A11) study plan

Diagram a three-tier campus topology (core, aggregation/access) labeling uplink types, oversubscription ratios, and PoE budget assumptions

Compare centralized, distributed, and mixed-control wireless architectures and justify a placement decision for a given building layout

Calculate required AP density from a stated user density and throughput target, showing the arithmetic

List the design inputs you must collect before sizing a campus (user counts, device types, roaming needs, PoE classes, uplink media)

Map each design requirement from week 1 to a specific wired infrastructure component (switch class, stacking, uplink speed, PoE tier)

Describe how VLANs, spanning tree, and link aggregation interact in an access-to-aggregation design

Explain wireless RF planning inputs (channel width, band steering, transmit power) and their effect on capacity

Identify which design decisions create downstream security and HA constraints and note them

Configure and verify VLAN assignment, trunking, and link aggregation on access and aggregation switches in a lab

Configure PoE class-based power budgeting and verify delivered power against AP requirements

Describe AP onboarding flow (discovery, controller/central association, firmware) and list failure points at each step

Compare tunneling versus local/bridge forwarding modes and state when each is appropriate

Validate wireless coverage and roaming behavior using a site survey or simulated survey output

Design a role-based access control model mapping user/device groups to roles, VLANs, and policy enforcement points

Explain how RADIUS, 802.1X, and MAC authentication combine for wired and wireless onboarding

Place enforcement (gateway, switch ACL, tunneled node) for guest, IoT, and corporate traffic and justify each placement

Identify segmentation gaps in a given flat-network scenario and propose remediation steps

Configure centralized monitoring and alerting for switch and AP health in a lab or simulator

Describe how configuration templates and group-based policy push reduce drift across many devices

Outline an automation workflow (inventory, template apply, verify) and identify idempotency risks

Select the metrics and logs you would retain for capacity planning and incident review

Design an HA topology covering controller/cluster redundancy, switch stacking, and redundant uplinks with failover expectations

Trace a failover scenario step by step and predict client-visible impact and convergence time

Build a troubleshooting decision tree for the top five campus symptoms (no DHCP, no auth, roaming failure, PoE fault, uplink down)

Map each symptom to the specific show/debug outputs or logs you would collect first

Plan a migration from a legacy flat campus network to the segmented design from week 4, sequencing cutover by building and by device class

Define coexistence rules so old and new authentication and VLAN schemes work during transition

List integration touchpoints with external systems (identity provider, NAC, monitoring, IPAM) and the data each needs

Draft a rollback and communications plan for a failed cutover

Re-derive the week 1 design brief from memory and reconcile differences against the original

Re-run the week 3 lab tasks and the week 6 troubleshooting tree without notes, logging any gap

Write a one-paragraph explanation for each domain's core trade-off (design, infrastructure, security, ops, HA, migration)

Build a personal weak-topic list ranked by confidence and schedule two review sessions per weak area