nerdexam
CompTIA

SK0-003 · Question #74

When making changes to a server, which of the following is the BEST way to troubleshoot a problem?

The correct answer is D. Make a change and if the problem is not resolved, reverse the change. When troubleshooting a server after making changes, the most effective method is to apply one change at a time and reverse it if the problem persists.

Troubleshooting

Question

When making changes to a server, which of the following is the BEST way to troubleshoot a problem?

Options

  • APerform root cause analysis and then test the theory to determine the cause.
  • BMake changes to the system and document everything once the problem is resolved.
  • CMake multiple changes to all affected areas to resolve all potential issues.
  • DMake a change and if the problem is not resolved, reverse the change.

How the community answered

(53 responses)
  • A
    11% (6)
  • B
    2% (1)
  • C
    6% (3)
  • D
    81% (43)

Why each option

When troubleshooting a server after making changes, the most effective method is to apply one change at a time and reverse it if the problem persists.

APerform root cause analysis and then test the theory to determine the cause.

Performing root cause analysis is a step within troubleshooting, but it does not describe the specific best practice for making changes during the process.

BMake changes to the system and document everything once the problem is resolved.

Documenting after resolution is important, but making changes without real-time tracking or making multiple changes before documenting is not ideal troubleshooting practice.

CMake multiple changes to all affected areas to resolve all potential issues.

Making multiple changes simultaneously makes it impossible to determine which specific change introduced or resolved the problem, hindering effective troubleshooting.

DMake a change and if the problem is not resolved, reverse the change.Correct

Making one change at a time allows the administrator to isolate the impact of each modification, making it clear which change caused or resolved an issue. Reversing a non-resolving change ensures the system returns to a known good state, preventing further complications and simplifying troubleshooting.

Concept tested: Troubleshooting methodology-one change at a time

Source: https://learn.microsoft.com/en-us/system-center/scom/manage-troubleshooting-methodologies?view=sc-opsmgr-2022

Topics

#troubleshooting methodology#change management#problem resolution

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SK0-003 Practice