Question 290
A security reviewer sees an unexpected fabric configuration and tries to infer the responsible change solely from the current device configuration. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Require meaningful commit descriptions and retain controller audit evidence in change reviews. Change accountability depends on recorded management operations as well as the final configuration state.
Incorrect Answers
Apstra application event records and device/system syslog messages can describe different layers of activity and require correlated timestamps. Here, apstra management events and revision metadata provide operational evidence of blueprint actions that the current switch state alone cannot reconstruct.
Apstra role-based access control separates monitoring and change authority based on the assigned user permissions and scope. However, the present prevention decision is grounded in: A security reviewer sees an unexpected fabric configuration and tries to infer the responsible change solely from the current device configuration. For this issue, review the relevant Apstra event and revision history alongside approved change tickets before reapplying or reverting the modification.
Treat the blueprint as the approved change source for managed fabric features and audit out-of-band edits. Here, apstra management events and revision metadata provide operational evidence of blueprint actions that the current switch state alone cannot reconstruct. Specifically for the prevention question, the case to validate is: A security reviewer sees an unexpected fabric configuration and tries to infer the responsible change solely from the current device configuration.