Exam 220-1101 topic 1 question 89 discussion

Troubleshooting methodology says if the plan to fix the problem does not work go back to this step - examine the system or ask more questions.

We would already have gathered information from the user, developed a hypothesis, and then attempted it resulting in failure. The next step would be to perform further research and make a new hypothesis.

Asking the user more questions will probably lead to nothing. The one option that make more sense is B.

The statement say’s “The monitor with a VGA connector was previously working fine for another user” that means the technician already asked the user about the issue then the technician must Research the issue further and formulate a new hypothesis to test.🙌

Establish a new theory of possible cause

answer C

Answer should be C A - Already Tried B - Already researched and provided a solution. D - Final Step

It's B because the fact that his solution didn't work means he needs to establish a new theory/hypothesis.

Option A is incorrect because using another brand of VGA to DisplayPort adapter is only one possible hypothesis to test, not the next step. Option C is incorrect because asking the user additional clarifying questions regarding the issue may not provide any useful information, since the technician has already identified the source of the problem. Option D is incorrect because documenting the action taken and the outcome is not a troubleshooting step, but a final step after resolving the issue.

I think B

Why not D? Document what you tried so that you know what didn't work. Now any other techs who might look at the problem know what has already been done so they don't waste time repeating the same action. To be fair, I think I got this question wrong by selecting D, but isn't there some argument that you would want to keep track of what you have tried and its outcome before moving on to establishing a new theory or gathering more info? Per CompTIA, documentation begins at the first step (identifying the problem), so I don't see why in the real world that documentation wouldn't be a persistent part of your troubleshooting. I don't think CompTIA would say DO NOT document anything until you have verified full system functionality. In the real world, a problem could span multiple shifts or days, and I think it would be important to keep your ticket updated between shifts, especially if others could end up working on the same issue.

I doubt there is much info the user could give you that would be beneficial in solving the issue. Best bet is to research

C. Ask the user additional clarifying questions regarding the issue. Before attempting any additional troubleshooting steps, the technician should seek more information from the user about the issue. The technician can ask the user about the specific circumstances when the fuzzy video occurs, such as if it occurs only during certain activities or if it occurs randomly. Based on the user's response, the technician can make a more informed decision about what to do next.

Continuing research makes the most sense.

Identify the problem: Gather information from the user, identify user changes, and, if applicable, perform backups before making changes. Begin documentation. Inquire regarding environmental or infrastructure changes. Establish a theory of probable cause (question the obvious): If necessary, conduct external or internal research based on symptoms. Test the theory to determine the cause: Once the theory is confirmed, determine the next steps to resolve the problem. If the theory is not confirmed, re-establish a new theory or escalate. Establish a plan of action to resolve the problem and implement the solution: Refer to the vendor’s instructions for guidance. Verify full-system functionality and, if applicable, implement preventive measures. Document the findings, actions, and outcomes.

its B guys

B. A new hypothesis has to be formulated. Doing that entails further research that does not leave out further questioning of the user.