Exam N10-008 topic 1 question 71 discussion

eh this a bad question

Those questions aim to trick you - and to make you fail. It all about the money. _________ This stage may require significant research on your part. Vendor documentation, your organization’s own documentation and a good old-fashioned Google search may all be required to provide the basis for your theory. Specific steps here may include: Questioning the obvious Considering multiple approaches, including top-to-bottom or bottom-to-top for layered technologies (such as networks) One of the main issues that I’ve observed with newer troubleshooters is failing to question the obvious. In my classes, I rephrase this as “start simple and work toward the complex.” Yes, I am aware that operating systems, networks and cloud deployments are all very complex. However, that does not mean that your issue is complex. I have found over the years that careful note-taking is important at this point. Your notes can include data copied from websites, web URLs, suggestions from your team members, etc. ________ https://www.comptia.org/blog/troubleshooting-methodology

Checking the link light is an example of using a bottom-to-top approach to troubleshoot network connectivity issues. Why Not the Other Options?: B. Establishing a plan of action: A plan of action is created after identifying the probable cause of the issue, not during the initial troubleshooting steps. C. Documenting a finding: Documenting findings occurs after identifying or resolving an issue to keep a record of the troubleshooting process. D. Questioning the obvious: Questioning the obvious involves asking the user basic questions, such as "Is the device powered on?" or "Is the cable plugged in?" Checking the link light is a physical verification step, not a questioning step.

In troubleshooting, a bottom-to-top approach (also known as the OSI model bottom-up approach) involves starting with the physical layer and working up through the layers to diagnose network issues. Checking for a link light is part of verifying the physical connection, which is at the bottom of the OSI model (Layer 1). This approach ensures that basic physical connectivity is in place before moving on to higher-level network configurations or settings.

D. questioning the obvious.

I vote for D. Questioning the obvious. What the technician did is an example of questioning the obvious. Bottom-to-top is more generalized and not specific enough.

Bad question but let me break down my understanding. This isn't bottom to top because they don't reference how they are starting from the bottom of the osi model, or anything to do with the physical layer. They just casually mention that they take a quick peek at an obvious thing (the link light) and so apparently we are supposed to just know that it's question the obvious and not bottom-to-top. >.> my brain jumped at light = hardware = physical layer, physical layer = base of osi model. Base of osi model must mean bottom to top! lol but logically the first step is to question the obvious and then to do bottom to top, so it actually makes sense that D. is a better answer.

The action described, where the technician first checks for a link light when troubleshooting a network connectivity issue, aligns with: D. questioning the obvious. In troubleshooting methodology, questioning the obvious involves starting with the most basic and straightforward steps to rule out simple causes of the issue before proceeding to more complex troubleshooting steps. Checking for a link light is one of the fundamental steps in diagnosing network connectivity problems, as it helps determine whether there is a physical connection between the device and the network.

someone at Examtopics is having a laugh me thinks

bottom-to-top approach is troubleshooting methodology.

A. using a bottom-to-top approach. Checking for a link light as a first step in troubleshooting a network connectivity issue is an example of using a bottom-to-top approach. This method starts with the physical layer (Layer 1 of the OSI model), ensuring that the basic physical connections are intact before moving on to higher-level potential issues. It's a systematic way to diagnose and resolve network problems by first verifying the simplest, most fundamental connections and configurations.

Nothing is more bottom-to-top than starting with "questioning the obvious". Questioning the obvious is not a "troubleshooting methodology", but rather just plain old common sense. The correct answer should be A. This is a greedy trick question, intended to help you fail the exam by one point, and forcing you to pay to take it over again.

I think the bottom-to-top approach would be more systematic and tedious. If you were to start at the physical layer I’d think you’d start testing cables, NIC loopbacks, CLI commands etc. Just looking at a link light I’d say is more along the lines of a simple “Is the light even on” approach, more indicative of questioning the obvious to me. So I’d say D.

D. questioning the obvious Checking for a link light at the start of connectivity troubleshooting is an example of questioning the obvious. Even basic or seemingly obvious issues should be confirmed during structured troubleshooting. A bottom-to-top approach refers to working through the OSI model layers systematically. Establishing a plan of action and documenting findings occur after initial troubleshooting steps. Checking the link light status validity questions whether the physical connectivity is working. This counts as questioning obvious components that could be assumed to be working or overlooked. Doing so methodically is important best practice when troubleshooting.

Will go with D GPT: In the context of troubleshooting methodology, when a technician first checks for a link light while assisting a user who cannot connect to a network resource, this is an example of: D. questioning the obvious. Questioning the obvious refers to verifying the most basic elements of a problem before moving on to more complex diagnostics. In this case, checking for a link light (which indicates whether a physical connection is present and active) is a fundamental step that addresses the most straightforward potential cause of the connectivity issue. It's about ensuring that the simplest explanations are either confirmed or ruled out before proceeding to more in-depth troubleshooting steps.

A=D and D=A You question the obvious by using the top to bottom approach by questioning the obvious using the top to bottom approach by questioning the obvious using the top to bottom approach by questioning th.....etc. The CompTIA troubleshooting methodology: https://www.comptia.org/blog/troubleshooting-methodology 1. Identify the problem. 2. Establish a theory of probable cause. Specific steps here may include: - Questioning the obvious. - Considering multiple approaches, including top-to-bottom or bottom-to-top for layered technologies (such as networks). 3. Test the theory to determine the cause. 4. Establish a plan of action to resolve the problem and implement the solution. 5. Verify full system functionality, and, if applicable, implement preventive measures. 6. Document findings, actions and outcomes.

Once again it’s what CompTIA wants you to say, rather than actual logic.