300-370 · Question #34
A user reports being unable to connect to a server with a certain program while connected to wireless. Wh.ch troubleshooting methodology can be used to begin the troubleshooting process?
The correct answer is A. top-down. When troubleshooting an application-specific connectivity problem from a wireless client, the top-down methodology is the most efficient starting point, beginning at the application layer.
Question
A user reports being unable to connect to a server with a certain program while connected to wireless. Wh.ch troubleshooting methodology can be used to begin the troubleshooting process?
Options
- Atop-down
- Bshoot from the hip
- Cfollow the path
- Dbottom-up
- Edivide and conquer
How the community answered
(38 responses)- A95% (36)
- B3% (1)
- E3% (1)
Why each option
When troubleshooting an application-specific connectivity problem from a wireless client, the top-down methodology is the most efficient starting point, beginning at the application layer.
A top-down troubleshooting methodology starts at the application layer (Layer 7) and systematically works down through the OSI model, which is logical when the problem is reported to involve a specific 'program' unable to connect to a 'server'.
'Shoot from the hip' describes a disorganized and inefficient approach to troubleshooting, which is generally not recommended.
'Follow the path' is not a standard, recognized networking troubleshooting methodology.
A bottom-up methodology starts at the physical layer (Layer 1) and works upwards, which is less efficient when the reported issue originates at the application level.
'Divide and conquer' is a general problem-solving strategy but, in networking, it's often applied within a top-down or bottom-up approach to narrow down the problem scope, rather than being the initial starting methodology itself.
Concept tested: Network troubleshooting methodologies (Top-Down)
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/tcp-ip-troubleshooting-methodology
Topics
Community Discussion
No community discussion yet for this question.