You have a configuration deviation in the Juniper Apstra dashboard. What does this anomaly indicate in this scenario?

A "configuration deviation" anomaly in the Juniper Apstra dashboard indicates a mismatch between the intended configuration and the actual running configuration on a device. The intended configuration, or "golden configuration," is rendered by Apstra based on the blueprint. This anomaly is raised when Apstra detects that the device's configuration has been altered through an external method, such as a user logging into the device's command-line interface (CLI) and making manual changes. Apstra continuously validates the running configuration against the intended state to detect such out-of-band changes.

A. A configuration update by the Apstra server is an expected operation and would not be flagged as a deviation anomaly.

B. A device ready to be configured is a normal state (e.g., 'Ready' mode) and not an anomaly indicating a configuration mismatch.

D. A device that cannot support a command would likely result in a deployment or probe error, not a configuration deviation anomaly.

1. Juniper Apstra 4.2 User Guide. In the section "Dashboard > Anomalies", the "Config Deviation" anomaly is defined. The documentation explains this anomaly occurs when "the running configuration on the device does not match the golden configuration generated by Apstra," which is typically caused by out-of-band configuration changes.