Question 494 of 512
IT Concepts and TerminologyhardMultiple SelectObjective-mapped

Quick Answer

The answer is "Establish a theory of probable cause," as it is one of the core steps in the CompTIA troubleshooting methodology. This step comes after identifying the problem and involves using logical reasoning to determine the most likely source of the issue, such as checking for recent software changes or hardware failures. On the CompTIA ITF+ FC0-U61 exam, common troubleshooting steps are tested to ensure you understand the structured process, not just random fixes. A frequent trap is confusing "establish a theory" with "implement a solution" — the theory comes before testing, not after. Remember the mnemonic "I-T-E-S-T": Identify the problem, Theory of probable cause, Establish a plan, Test the theory, and then implement or escalate. This sequence helps you avoid skipping critical diagnostic logic and is a reliable memory anchor for the exam.

FC0-U61 IT Concepts and Terminology Practice Question

This FC0-U61 practice question tests your understanding of it concepts and terminology. 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.

Which THREE of the following are common troubleshooting steps? (Select THREE).

Question 1hardmulti select
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

Identify the problem

Option B is correct because identifying the problem is the first step in the CompTIA A+ troubleshooting methodology. Without clearly defining symptoms and scope, subsequent steps lack direction. This step involves gathering information from users, duplicating the issue, and identifying any recent changes to the system.

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.

  • Install new software

    Why it's wrong here

    Installing software is not a standard troubleshooting step.

  • Identify the problem

    Why this is correct

    First step: identify symptoms and scope.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Test the theory to determine cause

    Why this is correct

    Third step: verify hypothesis through testing.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Escalate to vendor immediately

    Why it's wrong here

    Escalation is a later step after initial troubleshooting fails.

  • Establish a theory of probable cause

    Why this is correct

    Second step: hypothesize likely cause.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

CompTIA often tests the order of the troubleshooting steps, and the trap here is that candidates confuse 'test the theory to determine cause' (step 3) with 'establish a theory of probable cause' (step 2), or they mistakenly include actions like installing software as a step rather than a solution.

Detailed technical explanation

How to think about this question

The CompTIA troubleshooting methodology is a six-step process: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the solution, verify full system functionality, and document findings. This structured approach ensures systematic isolation of root causes, reducing downtime and preventing recurrence. For example, a network connectivity issue would first require pinging the gateway to confirm the problem scope before hypothesizing a faulty cable or DHCP failure.

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 FC0-U61 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 FC0-U61 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 FC0-U61 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 FC0-U61 question test?

IT Concepts and Terminology — This question tests IT Concepts and Terminology — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Identify the problem — Option B is correct because identifying the problem is the first step in the CompTIA A+ troubleshooting methodology. Without clearly defining symptoms and scope, subsequent steps lack direction. This step involves gathering information from users, duplicating the issue, and identifying any recent changes to the system.

What should I do if I get this FC0-U61 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 30, 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 FC0-U61 practice question is part of Courseiva's free CompTIA 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 FC0-U61 exam.