When a device managed by Juniper Apstra has its configuration changed out-of-band (OOB) via the CLI, Apstra detects this as a "Config Deviation" anomaly. Clicking the "Accept Changes" button instructs Apstra to learn these OOB changes and incorporate them into its rendered or "golden" configuration for that specific device. This action effectively updates Apstra's intent to match the new reality on the device, resolving the anomaly.

A: Apstra does not guess intent or add similar configurations; it incorporates the exact changes that were made out-of-band.

C: Clicking "Accept Changes" resolves the deviation immediately; it does not hold changes pending a "Full Config" push.

D: This describes ignoring the anomaly. Accepting the changes prevents them from being overwritten by the next configuration push from Apstra.

1. Juniper Apstra User Guide 4.2.1, "Anomalies > Config Deviation". The guide explains that accepting changes "updates the pristine configuration with the out-of-band configuration."

2. Juniper Apstra Datasheet. Describes Apstra's role as the "single source of truth," which is maintained by either pushing intent-based config or accepting OOB changes to update the intent.