A cooperative's compliance policy requires that every committed router configuration be automatically copied off the device to a central archive, without relying on a technician to remember to do it manually. Which Junos feature is designed for this?
Select an answer to reveal the explanation.
Short Explanation
The router can push a copy of its own config off-box every time someone commits — you just have to tell it where to send it and how. That's exactly what configuration archival is for.
Full Explanation
Junos supports a system archival configuration hierarchy where an administrator specifies a transfer method, such as SCP or FTP, along with a destination server, and Junos then automatically pushes a copy of the configuration off the device whenever a commit occurs, which satisfies an automatic, hands-off compliance requirement exactly as described. Manual USB copying during site visits is precisely the error-prone, human-dependent process the policy is trying to eliminate, since it depends entirely on a technician remembering to do it on every visit. Rescue configuration is a different feature: it snapshots one known-good configuration on the router itself as a local safety net for recovery, not an automatic, recurring, off-box copy mechanism for every commit. Relying solely on local commit history keeps every copy on the same device, which fails the requirement entirely if that device is lost, damaged, or compromised. To verify archival is actually working, check show system archival for the configured destination and confirm a new file lands on the archive server shortly after the next commit.