Question 65 of 527
Essential ToolsmediumMultiple ChoiceObjective-mapped

EX200 Essential Tools Practice Question

This EX200 practice question tests your understanding of essential tools. 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.

Exhibit

$ systemctl status sshd
● sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Mon 2024-10-10 10:00:00 EDT; 2min ago
  Process: 1234 ExecStart=/usr/sbin/sshd -D $OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 1234 (code=exited, status=0/SUCCESS)

Feb 10 10:00:00 host systemd[1]: sshd.service: start request repeated too quickly.
Feb 10 10:00:00 host systemd[1]: sshd.service: Failed with result 'start-limit'.

Refer to the exhibit. Why did the sshd service fail?

Question 1mediummultiple choice
Full question →

Exhibit

$ systemctl status sshd
● sshd.service - OpenSSH server daemon
   Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Mon 2024-10-10 10:00:00 EDT; 2min ago
  Process: 1234 ExecStart=/usr/sbin/sshd -D $OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 1234 (code=exited, status=0/SUCCESS)

Feb 10 10:00:00 host systemd[1]: sshd.service: start request repeated too quickly.
Feb 10 10:00:00 host systemd[1]: sshd.service: Failed with result 'start-limit'.

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

The service start was requested too many times in quick succession.

B is correct because systemd's `StartLimitIntervalSec` and `StartLimitBurst` settings (default: 10 seconds and 5 starts) prevent rapid service restarts. When `sshd` fails repeatedly within the interval, systemd marks it as failed with the status 'start-limit-hit' to avoid resource exhaustion from restart loops.

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.

  • The service binary is missing.

    Why it's wrong here

    The log shows the binary executed successfully, so it is present.

  • The service start was requested too many times in quick succession.

    Why this is correct

    The log explicitly says 'start request repeated too quickly', resulting in start-limit.

    Related concept

    Read the scenario before looking for a memorised answer.

  • The configuration file /etc/ssh/sshd_config has a syntax error.

    Why it's wrong here

    The log does not mention configuration errors; it shows a start limit.

  • The system ran out of memory.

    Why it's wrong here

    No memory issues are indicated in the log.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume the failure is due to a configuration error or missing binary, but the 'start-limit-hit' status is a systemd mechanism that explicitly indicates too many restart attempts, not a problem with the service itself.

Trap categories for this question

  • Command / output trap

    The log shows the binary executed successfully, so it is present.

Detailed technical explanation

How to think about this question

Under the hood, systemd tracks start attempts via `StartLimitIntervalSec` (default 10s) and `StartLimitBurst` (default 5). Once the burst is exceeded, systemd applies the configured `StartLimitAction` (default: 'none', which just fails the unit). In real-world scenarios, a misconfigured `ExecStartPre` script that exits non-zero can trigger this loop, masking the actual root cause in the service's own logs.

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 EX200 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 EX200 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 EX200 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 EX200 question test?

Essential Tools — This question tests Essential Tools — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The service start was requested too many times in quick succession. — B is correct because systemd's `StartLimitIntervalSec` and `StartLimitBurst` settings (default: 10 seconds and 5 starts) prevent rapid service restarts. When `sshd` fails repeatedly within the interval, systemd marks it as failed with the status 'start-limit-hit' to avoid resource exhaustion from restart loops.

What should I do if I get this EX200 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 EX200 practice question is part of Courseiva's free Red Hat 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 EX200 exam.