Which statement is true about the relationships mentioned in change and CI records?

The statement that it is mandatory for every Change to reference Configuration Items (CIs) reflects a fundamental principle in IT Service Management (ITSM). In ITSM frameworks like ITIL, a Change is typically associated with the specific CIs that are impacted or modified as part of that Change process. This linkage is crucial for several reasons:

1. Impact Assessment: When a Change is proposed, identifying which CIs are affected helps in understanding the potential impact and the risks associated with the Change. This assessment is essential for informed decision-making during the change approval process.

2. Change Tracking: Linking Changes to CIs provides a clear audit trail and visibility into how specific CIs are evolving over time. This is vital for maintaining effective asset management and configuration management.

3. Change Coordination: Many Changes can affect the services and functionalities that rely on multiple CIs. By mandating that Changes reference CIs, organizations ensure that all relevant components are considered and coordinated, leading to more successful implementation and reduced disruption.

While some other statements might appear plausible, they do not reflect the necessity of Change-CI associations in the context of structured ITSM practices.