The following list represents the basic steps in a troubleshooting methodology:
Identify the problem
Determine the scope of the problem
Establish a theory of probable cause/question the obvious
Test the theory to determine the cause
Establish a plan of action
Implement the solution or escalate the issue
Verify full system functionality
Implement preventive measures
Perform a root cause analysis
Document findings, actions, and outcomes throughout the process.
Root cause analysis is part of "implementing preventive measure" cause it helps you in:
Knowing WHAT happened
WHY it happened
and HOW to prevent it from happening again.
I want to do RCA during the implementation of solutions not afterward otherwise how do you know you implemented the right fix if you weren't certain of the cause. Due to this C and F seem right to me, document and then tell people they can use it again.
I also thought the answers were A and C, but from CompTIA:
https://www.comptia.org/blog/troubleshooting-methodology
1. Identify the problem
2. Establish a theory of probable cause
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
Root cause should be identified in step #3, and you can't do step #5 where you implement preventive measures without knowing root cause.
However, in the real world, cause isn't necessarily root cause. Cause, in most cases, is be a byproduct of root cause. What you implement to fix the problem isn't always the same root issue that caused the problem. I've been in IT for over 30 years and I've seen many-a-cases where root cause is different than the byproduct issue that the user was dealing with. But we have to think like CompTIA and stick to their theory to the T.
1 Identify the problem and determine the scope
2 Establish a theory of probable cause (question the obvious)
3 Test the theory to determine the cause
4 Establish a plan of action to resolve the problem (Notify impacted users is here)
5 Implement the solution or escalate
6 Verify full system functionality and, if applicable, implement preventive measures
7 Perform a root cause analysis
8 Document findings, actions, and outcomes throughout the process
You are correct, but final step according to CompTIA is outcome, finds, and conclusion. You need to know your final answer through all the troubleshooting and documentation that you do.
Answer looks suspect. If you follow the troubleshooting methodology A&C are after Implementing the solution no escalation was needed since the technician found the solution then A - perform a root cause analysis with C documenting findings.
upvoted 2 times
...
This section is not available anymore. Please use the main Exam Page.SK0-005 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Dion79
Highly Voted 2 years, 8 months agoi_bird
2 years, 2 months agoTimock
2 years, 1 month agoDion79
Highly Voted 2 years, 6 months agoccoli
Most Recent 5 months, 1 week agoITken
1 year, 1 month agoPongsathorn
1 year, 11 months agoPEsty93
2 years, 6 months agoDion79
2 years, 4 months agoDion79
2 years, 7 months ago