Question 245 of 514
Junos Configuration BasicsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to temporarily disable a configuration statement without removing it from the configuration. This is the correct use of the deactivate command in Junos because it allows you to test changes or isolate a problem by having the device ignore a specific configuration element during the commit operation, while the statement itself remains intact in the configuration hierarchy. On the JNCIA-Junos exam, this concept tests your understanding of operational configuration management versus editing; a common trap is confusing deactivate with delete, where delete permanently removes the statement. The exam often presents a scenario where you need to quickly rule out a configuration line without losing it for later reactivation. A helpful memory tip is to think of deactivate as putting a configuration line on "pause" rather than "stop"—the line is still there, but Junos simply skips over it until you use the activate command to resume it.

JNCIA-JUNOS Junos Configuration Basics Practice Question

This JNCIA-JUNOS practice question tests your understanding of junos configuration basics. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Under what circumstance would the 'deactivate' command be useful in Junos configuration?

Question 1mediummultiple choice
Full question →

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

To temporarily disable a configuration statement without removing it from the configuration

The 'deactivate' command in Junos temporarily disables a configuration statement without removing it from the configuration. This is useful for testing changes or troubleshooting because the deactivated statement remains in the configuration but is ignored by the commit operation, allowing easy reactivation with the 'activate' command.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • To delete a configuration statement after commit

    Why it's wrong here

    Deactivate does not delete; use 'delete'.

  • To permanently remove a configuration statement

    Why it's wrong here

    Deactivation only makes it inactive; it remains in the candidate config.

  • To temporarily disable a configuration statement without removing it from the configuration

    Why this is correct

    Deactivation disables the statement until it is activated again.

    Related concept

    Read the scenario before looking for a memorised answer.

  • To mark a statement as inactive while keeping it in the active configuration

    Why it's wrong here

    It is deactivated in the candidate; after commit it is inactive in the active config.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is confusing 'deactivate' with 'delete' or assuming that deactivated statements remain active; candidates often think 'deactivate' removes the statement or that it still applies after commit, but in Junos, deactivated statements are completely ignored by the commit operation.

Detailed technical explanation

How to think about this question

Under the hood, the 'deactivate' command adds an 'inactive:' tag to the configuration statement in the candidate configuration. When you commit, Junos ignores all statements marked with 'inactive:', effectively removing them from the active configuration without deleting them. This is particularly useful in scenarios like testing a new BGP policy where you want to quickly disable and re-enable the policy without losing the configuration text.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the JNCIA-JUNOS exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related JNCIA-JUNOS practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free JNCIA-JUNOS practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this JNCIA-JUNOS question test?

Junos Configuration Basics — This question tests Junos Configuration Basics — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: To temporarily disable a configuration statement without removing it from the configuration — The 'deactivate' command in Junos temporarily disables a configuration statement without removing it from the configuration. This is useful for testing changes or troubleshooting because the deactivated statement remains in the configuration but is ignored by the commit operation, allowing easy reactivation with the 'activate' command.

What should I do if I get this JNCIA-JUNOS question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This JNCIA-JUNOS 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-JUNOS exam.