Which of the following statements about configuration checkpoints in Nokia SR Linux is FALSE?

In Nokia SR Linux, checkpoint 0 is a reserved identifier that refers to the current running configuration datastore. It is not a historical, saved checkpoint file. Historical checkpoints, which are created automatically after each successful commit, are numbered sequentially starting from 1. Checkpoint 1 represents the oldest available checkpoint, not checkpoint 0. Therefore, the statement that checkpoint 0 is always the oldest checkpoint is false.

B. The tools system configuration save command allows an operator to save the running configuration to a file, and the format can be specified as JSON.
C. The tools system configuration revert command is used to replace the current running configuration with the contents of any existing checkpoint file.
D. SR Linux automatically creates a new configuration checkpoint file after every successful commit operation, capturing the state of the configuration at that time.

1. Nokia SR Linux System Management Guide (Release 23.10), Section: "Configuration management > Configuration checkpoints".

This section states: "SR Linux automatically creates a configuration checkpoint file after every successful commit operation... The checkpoint files are numbered sequentially, starting with 1." This directly refutes option A and confirms option D.

2. Nokia SR Linux CLI User Guide (Release 23.10), Section: "tools > system > configuration > save".

This section details the save command and its parameters, including output-format {json | xml}. This confirms that the configuration can be saved in JSON format, making option B correct.

3. Nokia SR Linux CLI User Guide (Release 23.10), Section: "tools > system > configuration > revert".

This section describes the revert command, stating its function is to "replace the running configuration with the contents of a specified checkpoint file." This confirms option C is correct.

4. Nokia SR Linux CLI User Guide (Release 23.10), Section: "Configuration mode commands > compare".

The documentation for the compare command shows usage like compare to checkpoint , where checkpoint-id 0 is implicitly understood by the system to mean the running configuration, reinforcing that it is not a historical file like checkpoints 1, 2, etc.