A healthy and trusted CMDB that aligns with Data Foundations principles--covering accurate data ingestion, strong governance, and service-aware relationships--directly strengthens the insight available to Change Management. When discovered infrastructure data is integrated with well- maintained non-discoverable attributes (such as assignment groups, support groups, and ownership), the CMDB becomes a reliable source of truth for evaluating change risk and impact.
Option B is correct because Service Mapping establishes relationships between configuration items (CIs) and business services. This enables change practitioners to perform impact analysis, identifying which services, applications, and downstream components may be affected by a proposed change. Rather than relying on assumptions or tribal knowledge, change records can reference real dependency data, improving risk assessment, scheduling decisions, and stakeholder communication. This aligns directly with CSDM and CMDB best practices, where service context is essential for informed decision-making.
Option D is also correct because accurate, governed non-discoverable data--such as support and assignment groups--allows Change Management processes to dynamically route work. When a change is associated with a CI or service, the system can automatically populate the appropriate assignment group based on CMDB relationships. This improves efficiency, reduces manual errors, and ensures accountability across federated support models.