What are key relationships between Change and Problem records?

The key relationship indicated in the answer revolves around the concept that underlying causes of issues, which are documented as Problems, can often be addressed and resolved through Changes. In IT Service Management, Problems are identified when repeated Incidents occur, indicating a deeper, root cause that needs investigation. Once a Problem has been thoroughly analyzed and understood, a Change can be proposed and implemented to address the underlying issue.

For example, if a specific software application is frequently crashing, thus generating multiple Incidents, a Problem record can be created to investigate this issue. Once the root cause is identified—such as a bug in the software—an associated Change can be implemented, such as deploying a software patch. This highlights how a Problem can indeed be resolved through the implementation of a Change.

While the other options indicate different relationships between Change and Problem records, they do not capture this key aspect of how Problems are ultimately solved through Changes. The relationship illustrated in the correct answer emphasizes the proactive nature of Change management in addressing underlying Problems to enhance service reliability and reduce future Incidents.