IT Troubleshooting Methodology & Documentation

1. Which troubleshooting technique involves testing one variable at a time?

Isolation

Documentation

Escalation

Verification

2. What is the main advantage of following a standardized troubleshooting methodology?

It ensures consistency, reduces resolution time, and improves documentation

It eliminates the need for user communication

It prevents all technical problems

It reduces the need for IT staff training

3. Which documentation format is best for tracking multiple IT issues over time?

A ticketing system database

Sticky notes on a monitor

Email chains only

Handwritten notebooks

4. What is 'troubleshooting by substitution'?

Replacing a component to test if it's faulty

Hiring a new IT technician

Changing user passwords

Updating all software versions

5. When documenting a resolved issue, which detail is least important?

The technician's personal opinion about the user

The steps taken to resolve the problem

The solution that worked

The time spent on resolution

6. What is the purpose of a 'runbook' in IT documentation?

A step-by-step guide for performing routine tasks or troubleshooting

A financial budget report

A list of user complaints

A hardware inventory log

7. In troubleshooting methodology, which step involves confirming the problem no longer exists?

Implementation

Verification

Documentation

Theory establishment

8. What does 'SLA' stand for in IT service documentation?

Service Level Agreement

System Log Archive

Support Licensing Agreement

Software Load Analysis

9. When a user reports a software crash, what should be your first documentation step?

Create a ticket with the user's description and contact info

Assume it's a hardware failure

Tell the user to reinstall everything

Skip documentation if it seems minor

10. What is 'change management' in IT documentation?

The process of tracking and controlling modifications to systems

Replacing all IT staff annually

Changing passwords weekly

Moving office locations

11. Which step in the CompTIA A+ troubleshooting model comes immediately after identifying the problem?

Establish a theory of probable cause

Document findings and lessons learned

Implement the solution

Verify full system functionality

12. What is the benefit of creating a baseline in IT troubleshooting?

It establishes normal system performance for comparison

It eliminates the need for updates

It prevents all future problems

It reduces user training requirements

13. In the troubleshooting process, what does 'escalation' mean?

Increasing the volume when speaking to users

Passing an issue to a higher level of support

Asking the user to restart their device

Deleting the support ticket

14. Which is a critical element of proper IT incident documentation?

Timestamp of when the issue was reported

Only the final solution, no steps

Vague descriptions to protect privacy

Excluding user contact information

15. What does MTTR stand for in IT support metrics?

Mean Time To Recover

Maximum Total Technical Resources

Monthly Ticket Tracking Report

Multi-Team Technical Response

16. When troubleshooting a network connectivity issue, which approach is most methodical?

Test random solutions until one works

Restart the entire system immediately

Test from the user's device up to the network infrastructure

Assume the problem is always the router

17. What is a ticket in IT support documentation?

A permission slip for users

A formal record of a user request or issue

A financial receipt for hardware

A security badge for the IT department

18. Which documentation practice helps prevent repeated troubleshooting of the same issue?

Creating a knowledge base or FAQ

Verbal communication only

Keeping notes on personal devices

Deleting old ticket records

19. In IT troubleshooting, what does 'root cause' refer to?

The user's initial complaint

The underlying reason why a problem occurs

The first symptom detected

The cost of fixing the issue

20. What is the primary purpose of documenting IT incidents and resolutions?

To create a knowledge base for future reference and training

To blame users for technical failures

To reduce the need for technical staff

To avoid communicating with management

Tech+ IT Troubleshooting Methodology and Documentation Quiz