nerdexam
Palo_Alto_Networks

PCNSA · Question #410

A systems administrator momentarily loses track of which is the test environment firewall and which is the production firewall. The administrator makes changes to the candidate configuration of the…

The correct answer is A. Revert to running configuration. Option A is correct because on PAN-OS firewalls, Revert to Running Configuration discards all uncommitted changes in the candidate configuration and resets it to match the last committed state - exactly what's needed here, since the admin edited but never committed. B is wrong…

Submitted by thandi_sa· Apr 18, 2026Device Management and Services

Question

A systems administrator momentarily loses track of which is the test environment firewall and which is the production firewall. The administrator makes changes to the candidate configuration of the production firewall, but does not commit the changes. In addition the configuration was not saved prior to making the changes. Which action will allow the administrator to undo the changes?

Options

  • ARevert to running configuration.
  • BLoad named configuration snapshot, and choose the first item on the list.
  • CRevert to last saved configuration.
  • DLoad configuration version, and choose the first item on the list.

How the community answered

(40 responses)
  • A
    95% (38)
  • C
    3% (1)
  • D
    3% (1)

Explanation

Option A is correct because on PAN-OS firewalls, Revert to Running Configuration discards all uncommitted changes in the candidate configuration and resets it to match the last committed state - exactly what's needed here, since the admin edited but never committed.

B is wrong because named configuration snapshots must be manually created and labeled; there's no guarantee one exists from the right point in time, and selecting "the first item" is unreliable without knowing what it contains.

C is wrong because the question explicitly states the configuration was not saved before the changes were made, so "last saved" may point to a much older state, not the clean pre-change state.

D is wrong because configuration versions in the version history represent committed configurations; since nothing was committed, the version list doesn't capture the pre-change candidate state, and "first item" would likely be a previous committed version of unknown relevance.

Memory tip: Think of it as a two-layer system - running is what's live and committed, candidate is your scratchpad. If you mess up the scratchpad without saving or committing, just "revert to running" to throw away the scratchpad and start fresh from what's actually running.

Topics

#Configuration Management#Candidate Configuration#Revert Changes#Firewall Administration

Community Discussion

No community discussion yet for this question.

Full PCNSA Practice