Question 640
The HPE AOS-CX switching case is: A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change. Select TWO: a corrective switching action and separate evidence that the correction worked. (Select TWO.)
Explanation
Correct Answers
The targeted correction for A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change is: Compare switch running state with an approved intended configuration on a controlled schedule and investigate meaningful policy drift. It reduces the risk that undetected local overrides and drift can accumulate across branches and weaken segmentation or network reliability.
A separate operational validation for A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change is: A comparison report identifies all unauthorized changes and confirms approved exceptions remain documented without false matches. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns switch configuration archive and baseline governance; its associated risk is: A configuration backup with no device/version identity can restore an incorrect VLAN or security baseline during a major outage. The observed case A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change requires the more specific scheduled configuration audit and desired-state compliance control. The targeted action is: Compare switch running state with an approved intended configuration on a controlled schedule and investigate meaningful policy drift.
This alternative concerns central firmware and group compliance rollouts; its associated risk is: A queued or blocked Central operation can leave some switches on old software while dashboards imply the deployment finished. The observed case A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change requires the more specific scheduled configuration audit and desired-state compliance control. The targeted action is: Compare switch running state with an approved intended configuration on a controlled schedule and investigate meaningful policy drift.
This alternative concerns safe firmware release and feature compatibility planning; its associated risk is: Upgrading incompatible software across peer switches can create avoidable outages and leave routing or stacking features unavailable. The observed case A Central group reports compliant while two devices retain documented overrides that were never reviewed after the last change requires the more specific scheduled configuration audit and desired-state compliance control. The targeted action is: Compare switch running state with an approved intended configuration on a controlled schedule and investigate meaningful policy drift.