HPE4-A52 - Aruba Certified Campus Access Switching Expert Practical Exam

Correct answer: A

Explanation: Use a loop or port macro in the Central template, then save and commit the template:

%for port in 1/1/1..1/1/24
interface ${port}
description Access-Port-${port}
%endfor

Validation checks: Preview the rendered configuration for a test switch, confirm every intended interface receives a unique description, and verify the committed template reaches the assigned device without syntax errors.

Common mistakes: Applying the loop to unintended ports, omitting the interface context, using an unsupported variable expression, or saving without committing and validating the rendered result.

Correct answer: A

Explanation: Add variables to the template, assign their values per switch or site, and reprovision to apply them:

snmp-server community ${snmp_community}
snmp-server contact ${snmp_contact}
snmp-server location ${snmp_location}

Validation checks: Confirm all variables resolve in the template preview, inspect the device configuration after reprovisioning, and test polling from the authorized monitoring system.

Common mistakes: Leaving a variable undefined, reusing the wrong site's community value, applying the template to the wrong group, or verifying only that the configuration exists without testing monitoring access.

Correct answer: A

Explanation: Navigate to Devices → Switch → Config History. Review the audit records and timestamps to identify what changed and when, then restore a previous configuration if rollback is required.

Validation checks: Match the timestamp and user or workflow to the observed incident, compare the relevant revisions, and confirm service recovery after any restoration.

Common mistakes: Rolling back before identifying the responsible change, selecting the wrong historical version, ignoring group-template changes, or assuming a successful restore automatically proves that every affected protocol recovered.

Correct answer: A

Explanation: Run the following commands:

show running-config source
show aruba-central

The first command identifies whether the running configuration comes from a template, the UI, or manual configuration. The second shows the switch's Central connectivity state.

Validation checks: Confirm both the expected configuration source and an operational Central connection; one does not prove the other.

Common mistakes: Checking only reachability, assuming a connected switch is using the intended provisioning source, or making manual changes that Central later overwrites.

Correct answer: A

Explanation: Download the CSV Import Template from Central, enter MAC, Serial, Group, Site for every switch, and upload it through Devices → Import Devices. Central then auto-assigns the imported switches when they connect.

Validation checks: Check for duplicate or malformed identifiers, confirm that every referenced group and site already exists, review the import result, and verify a sample device lands in the correct scope.

Common mistakes: Editing column headers, swapping MAC and serial values, using inconsistent site names, assigning a device to the wrong template group, or importing all 100 records without first testing a small batch.