Aruba ACMP study plan

Configure a mobility controller from factory default: management IP, NTP, syslog, licensing, and VLAN interfaces

Provision at least three access points and verify they appear as Up with correct regulatory domain and AP group

Configure AP discovery through both DHCP option 43 and DNS so you can explain the fallback order

Build AP groups and virtual AP profiles so a single SSID is broadcast only by a designated AP subset

Document every command path and GUI screen you used into a repeatable build order

Differentiate predictive, pre-deployment, and validation site surveys and state when each is required

Produce a 2.4 GHz and 5 GHz channel and transmit-power plan that avoids co-channel overlap for a multi-floor building

Calculate AP count from both coverage radius and client density, and justify which constraint wins

Set data rates, band steering, and minimum RSSI so clients prefer 5 GHz without creating sticky-client drops

Validate your plan by mapping expected SNR and channel reuse across a floor diagram

Configure a RADIUS server group and an LDAP server group, then test both authentication paths with a real client

Compare 802.1X, PSK, and captive portal and select the correct method for four distinct client populations

Write role derivation rules that assign roles from user attributes, VLAN, and device type

Create role-based firewall policies that restrict inter-role traffic while permitting required services

Map each role to a VLAN and an access control decision so the policy is auditable end to end

Harden management access using certificates, restricted management VLAN, and role-limited admin accounts

Configure rogue AP detection and classify detected devices as interfering, rogue, or known neighbor

Tune WIDS/WIPS signatures and explain which actions are detect-only versus containment

Build three production-style SSIDs: corporate 802.1X, guest captive portal, and IoT PSK with client isolation

Rebuild the full SSID and role configuration from a blank controller without consulting notes

Explain and configure Layer 2 versus Layer 3 roaming, including which traffic is tunneled and where it terminates

Configure controller redundancy using VRRP and a backup LMS so APs re-home after a controller failure

Test AP and controller failover and record the measured outage duration

Configure cluster or standby behavior and verify license and AP database synchronization

Identify which roaming designs break voice and which preserve the session across subnets

Read controller dashboards and alarms and correlate them to underlying radio or infrastructure faults

Capture and interpret a client packet trace and an over-the-air capture to isolate an association failure

Use client debug and event logs to trace a full association, authentication, and DHCP sequence

Rank the most probable causes for low throughput, intermittent drops, and failed authentication

Build a triage sequence that starts from scope of impact and narrows to a single layer

Re-run a validation survey and compare measured SNR and channel reuse against your week 2 plan

Diagnose injected faults in the lab within 15 minutes each without following a script

Revisit roaming scale limits and confirm your redundancy design still holds under peak client counts

Compile a ranked list of your weakest objectives from all domains and close the top five

Explain each answer you missed on a mixed practice set by naming the correct behavior, not just the correct option

Complete two timed 60-question practice exams under exam conditions

Review every missed item and re-study the underlying configuration or design principle

Recite the design-to-deployment workflow from RF plan through role policy without prompts

Confirm weak-area remediation from week 7 held by re-testing the same objectives

Finalize a one-page reference sheet of configuration paths and design rules