Locate a Failure Using Component Evidence

Supplied materials

• Paper and pencil; answers may also be spoken or typed.
• All cases, labels, numbers and rules are supplied on this page. No real account, private information or purchase is needed.

Learn the idea

A fault report should narrow a cause using observed evidence. One working function can rule out a completely failed component while leaving other possibilities open. Our supplied diagnostic record names a confirmed failed part, so the exercise does not require guessing a real device’s cause.

Use the stated diagnostic evidence to identify the confirmed component, keeping other causes unresolved when not tested. A blank screen alone does not prove the processor is broken.

Use this supplied case: Diagnosis says display does not show a known-working local test. Which component is confirmed failed in the supplied diagnosis? Use the details in this example. Say which detail helped you choose. This pretend example does not tell us how every real system works.

1. Follow the worked example one step at a time. Say or draw what happens.
2. Use the stated diagnostic evidence to identify the confirmed component, keeping other causes unresolved when not tested.
3. Say which detail makes the example answer fit. Pick another answer and say why it does not fit.
4. Try the question and practice questions. Read the rule again if your answer does not match the explanation.

Check your reasoning

Your answer is temporary and is not saved to an account. Download your current answer before leaving or reloading. Written work on paper or in another app stays in your own file.

Take it further

Evidence only says a page is slow. Expected: cause remains unconfirmed; propose a safe measured check rather than declaring a failed component.

Nothing here is saved to an account or sent to a teacher. The answer download includes your current choice and any checked feedback. It does not include choices from the separate More practice section. Download that section separately.