試験CIS-DF-JPN トピック2 問題18 スレッド

In Data Foundations, "Configuration" includes modeling CI relationships in a way that reflects real-world technology dependencies and supports operational use cases such as impact analysis, troubleshooting, and service mapping. For "Application Servers host Applications," the scenario describes that multiple Application Servers can host one or more Applications. In most enterprise environments, the reverse is also true: an Application can be hosted across multiple Application Servers (for example, horizontal scaling, clustered deployments, active-active architectures, and separate servers for different tiers or components of the same application).
Because both sides can have multiple related records, the correct logical relationship is many-to-many:
* One Application Server # hosts many Applications
* One Application # can be hosted on many Application Servers
In ServiceNow CMDB terms, many-to-many relationships are represented through the CMDB relationship model (parent/child relationships), enabling the platform to store multiple relationship records linking servers and applications without forcing an unnatural single-reference constraint. This supports better CMDB quality and stronger downstream outcomes-especially for incident triage ("what apps are affected if this server is down?") and change impact analysis ("what servers could be impacted if we change this app component?").
A one-to-many or many-to-one model would incorrectly restrict either the server to one application or the application to one server, which does not align with common hosting patterns and would reduce the CMDB's usefulness and accuracy.