Courseiva

JNCIA-SEC Practice Question: The purpose of the 'commit confirmed' command in Junos OS on an SRX Series device?

What is the purpose of the 'commit confirmed' command in Junos OS on an SRX Series device?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

It tests the configuration and applies it temporarily, automatically reverting if not confirmed within a timeout period.

'commit confirmed' automatically rolls back the configuration if a confirmation command is not issued within a specified time limit, preventing lockout.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    It tests the configuration and applies it temporarily, automatically reverting if not confirmed within a timeout period.

    Why this is correct

    'commit confirmed' activates the new configuration immediately but starts a timer, 10 minutes by default or a value you set. If you do not issue another 'commit' before it expires, Junos automatically rolls back to the previous configuration. It is ideal for risky remote changes on an SRX, such as policies affecting management access, because a mistake that locks you out is undone automatically.

  • ✗

    It permanently saves the configuration without any rollback capability.

    Why it's wrong here

    A plain 'commit' makes a configuration active and permanent, but Junos still keeps up to 50 previous versions for rollback, so no commit ever removes rollback capability. 'commit confirmed' goes further in the other direction: the change is provisional and reverts automatically unless confirmed. This option therefore describes the opposite of what the command does.

  • ✗

    It confirms that the hardware is operating correctly.

    Why it's wrong here

    Hardware health is checked with operational commands such as 'show chassis alarms', 'show chassis hardware' and 'show chassis environment', not with commit. Commit commands work on the configuration: 'commit check' validates it without applying, and 'commit confirmed' applies it provisionally with automatic rollback. Confusing the word 'confirmed' with hardware verification makes this option tempting.

  • ✗

    It sends an email confirmation of the commit to the admin.

    Why it's wrong here

    The commit confirmed command activates a rollback timer: if no confirming commit follows within ten minutes, Junos automatically reverts to the previous configuration. It sends no email. It is tempting because commit scripts and event policies can trigger email notifications, but those are separate configuration mechanisms, not this command's rollback safety function.

About these practice questions

Courseiva writes every JNCIA-SEC question from scratch — 393 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar JNCIA-SEC questions

Written and reviewed by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

Last reviewed August 2026 · checked against the official Juniper Networks exam blueprint

This JNCIA-SEC practice question is part of Courseiva's free Juniper Networks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the JNCIA-SEC exam.