Read a sample: 1. Read the Question Before You Fix the Problem
A user says, “The network is down.” You glance at the answer choices and see replace the network adapter. The computer cannot reach a website, so the adapter might be involved. But the same symptom could result from a disconnected cable, an addressing problem, a name-resolution failure, or an unavailable website.
More importantly, you may not yet know what the question asked you to do.
Troubleshooting questions test more than your ability to recognize technology terms. They ask you to make a decision using a limited set of facts. Sometimes that decision is a likely cause. Sometimes it is the next test, the first action, or the best response under a stated constraint. A technically possible answer can be wrong because it answers a different question.
This chapter introduces a repeatable reading method you can use throughout the book. It will not turn every scenario into an obvious answer. It will help you see what the evidence supports, what remains uncertain, and what kind of decision you are being asked to make.
The practice scenarios in this guide are original. They are designed to build troubleshooting judgment, not to reproduce questions from an actual exam.
Before you investigate the fictional problem, find the sentence that asks for an answer. Pay particular attention to its decision word or phrase:
- Most likely cause: Choose the explanation best supported by the available evidence.
- Next test: Choose a check that helps distinguish plausible explanations.
- First action: Identify the appropriate immediate step, taking the circumstances and any required precautions into account.
- Best solution: Select an action that resolves the established problem, rather than merely gathering information.
- Most appropriate response: Consider the technical facts along with policies, user impact, safety, or other stated constraints.
These phrases overlap in ordinary conversation, but they can lead to different answers in a multiple-choice scenario. A cause is not a test. A test is not necessarily a repair. A repair is not necessarily the first thing a technician should do.
Imagine that a laptop displays an image on an external monitor but not on its built-in screen. A question asking for the most likely affected area may call for an answer involving the laptop’s internal display path. A question asking for the next test may call for checking display settings or examining the built-in screen under the conditions specified in the choices. Replacing a display assembly is an action; it is not itself an explanation of the symptom.
You do not need to read every question backward or follow a rigid ritual. The point is to identify the requested decision before a familiar technical term pulls your attention toward a favorite fix.
A scenario often begins with a user’s interpretation:
> “The printer is broken.”
That statement tells you what the user believes, not which component has failed. The useful symptom might be that a document remains in a print queue, that pages emerge blank, or that the printer does not respond to a power button. Each leads toward a different investigation.
As you read, sort information into three practical categories:
1. Reported symptom: What someone says is happening.
2. Verified observation: What the scenario says was observed or tested.
3. Inference: A possible explanation drawn from those observations.
For example:
- Reported symptom: “The internet is down.”
- Verified observation: The computer can reach a web service by IP address but cannot reach it by hostname.
- Inference: Name resolution may be failing.
The inference is stronger because it accounts for the stated contrast. It is still not the same thing as a direct observation of a failed DNS server. The problem might be local to the device, involve its configured resolver, or lie elsewhere in the name-resolution path. The answer choices and the wording of the question determine how specific you can reasonably be.
Do not dismiss a user report merely because it is unverified. It is often the starting point for the entire investigation. Treat it as a clue with a source, not as proof of the user’s proposed cause.
Also notice who performed a test and what the test actually showed. “The user says another cable did not help” is useful information, but it may be less precise than “the technician connected a known-good cable and verified the link.” Neither statement tells you more than it says. A cable described as different is not automatically known to be functional.
A good answer fits the scenario’s limits. Before comparing choices, look for constraints such as:
- The technician must preserve user data.
- Only one device or one account is affected.
- The problem began after a stated change.
- A service must remain available during investigation.
- The technician has not yet received authorization for a disruptive action.
- The question asks for a test rather than a repair.
Constraints are not decorative details. If the question asks for a non-disruptive test, an action that restarts a shared server may be a poor choice even if it could produce useful information. If user data must be preserved, reinstalling an operating system without first establishing the problem and protecting the data is difficult to justify.
Scope is a particularly important boundary. One affected user suggests a different starting point from an entire department reporting the same failure. Neither scope proves a cause, but each changes which hypotheses deserve attention first.
Time matters…