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.

In a mature Configuration Management implementation within ServiceNow, CI operational attributes are leveraged to automate Change Management workflows and reduce manual effort.
When a CI is selected on a Change record, ServiceNow evaluates the CI's Change Group attribute. If this field is populated on the CI, the platform automatically copies its value into the Change Group field on the Change form. This ensures that change ownership and governance are immediately aligned with the responsible technical team.
The Change Group is distinct from the Assignment Group, which is used primarily in Incident and Task routing. Managed by Group represents lifecycle ownership and is used by CMDB governance tools, while Approval Group controls approval workflows but is not auto-populated from CI selection.
This behavior demonstrates the value of accurate CI attributes: once populated consistently, they enable automatic field population, reduced manual errors, and faster processing across ITSM workflows.
Therefore, the correct answer is A - Change Group.

In ServiceNow CMDB governance, the CI Class Manager allows administrators to assign ownership and accountability at the class level. This ownership is used by governance tools-especially CMDB Data Manager-to automatically determine who receives tasks and actions related to data lifecycle management.
The group reference field that aligns with class ownership and is consumed by CMDB Data Manager policies is the Managed By Group. This field represents the team responsible for the technical stewardship and lifecycle management of CIs within that class.
When CMDB Data Manager executes policies such as retention, archival, or cleanup, it uses the Managed By Group to assign tasks to the appropriate data owners. This ensures governance actions are routed to the correct accountable team without manual intervention.
Approval Group, Support Group, and Change Group serve different purposes. Approval Group is used for workflow approvals, Support Group is used for operational ticket routing, and Change Group supports Change Management governance. None of these reflect data ownership at the class level.
Therefore, to leverage CI class ownership defined in the CI Class Manager within CMDB Data Manager policies, the correct field is Managed By Group, making Option B the verified answer.

Creating a custom CI class in the CMDB is a dictionary-level configuration activity and must be performed with the correct minimum privileges to ensure governance and upgrade safety in ServiceNow.
The sn_cmdb_admin role is required because it grants administrative access to CMDB structures, including CI class hierarchy management. This role ensures that changes align with CMDB governance controls and Data Foundations practices.
The personalize_dictionary role is also required because adding a new CI class involves creating or extending dictionary entries (tables, attributes, inheritance). Without dictionary-level access, a user cannot define new classes or attributes in the CMDB schema.
Option A is incorrect because sn_cmdb_admin alone is insufficient without dictionary privileges. Option B and D focus on form personalization, which affects UI layout only and does not allow creation of new CI classes. Additionally, itil_admin is not the correct role for schema-level CMDB changes.
Therefore, the minimal and correct role combination is sn_cmdb_admin and personalize_dictionary, making Option C the verified answer.

The correct answer is Configuration File Path . When the same application can be installed more than once on the same server, the identification rule must use an attribute that can distinguish one installed instance from another. Configuration File Path is stronger than file name because the same file name can exist in multiple installation directories. It is also stronger than version because multiple instances may run the same version.
Port can help in some cases, but ports may be reused, changed, or not consistently available for every application pattern. Class is too broad because it only identifies the type of CI, not the specific application instance. A path-based criterion is more precise because it identifies where that application instance is installed on the server. Therefore, Configuration File Path is the best criterion attribute for preventing incorrect matches between multiple instances.
=========