Principal Classesare a key CMDB configuration concept used to controlwhich CI classes are selectable in reference fieldsacross ITSM processes. This helps reduce noise, prevent incorrect CI selection, and improve data quality.
InServiceNow, Principal Classes are designated within theCI Class Manager. This tool allows CMDB administrators to manage the CI class hierarchy, define ownership, and explicitly mark classes asprincipal.
Once a class is marked as principal, its CIs become available in CI reference fields such as those on Incident, Change, and Problem forms.
Option A (CMDB Workspace) provides operational and analytical views but does not control schema-level class behavior. Option C (System Properties) does not manage class designation. Option D (CMDB Data Manager) governs lifecycle and data quality policies, not reference field behavior.
By configuring Principal Classes in theCI Class Manager, organizations ensure that only relevant, high-value CI classes are exposed to end users, aligning with Data Foundations best practices.
Therefore, the correct answer isB - CI Class Manager.

InServiceNow, theDuplicate CI Remediatoris a governed tool designed to safely resolve duplicate Configuration Items while preserving themost valuable and authoritative record. The first step in the remediation wizard is identifying theMain CI, which will be retained after remediation.
ServiceNow uses two primary attributes to help determine the best candidate for theMain CI:
Oldest Created (Option A)
The oldest CI is often preferred because it typically has alonger operational history, may be referenced by historical incidents, changes, problems, or audits, and is more likely to be embedded in downstream processes and reports. Retaining the oldest CI helps avoid breaking historical references.
Most Related Items (Option B)
A CI with themost relationships(for example, links to applications, services, incidents, or other CIs) is generally the most valuable from abusiness and operational contextperspective. Preserving these relationships is critical for impact analysis, Change Management, and CSDM-aligned service modeling.
Options C (Newest Created) and D (Least Related Items) are not used as selection criteria because newer or weakly-related CIs typically contain less historical and relational value and are better candidates for removal or merging.
By prioritizingOldest CreatedandMost Related Items, the Duplicate CI Remediator aligns withCMDB Data Foundations best practices, ensuring minimal data loss, preserved business context, and safer de-duplication outcomes.
Therefore, the correct answers areA and B.

In a mature Configuration Management implementation withinServiceNow, CI operational attributes are leveraged to automateChange Management workflowsand reduce manual effort.
When a CI is selected on aChange record, ServiceNow evaluates the CI'sChange Groupattribute. If this field is populated on the CI, the platform automatically copies its value into theChange Group field on the Change form. This ensures that change ownership and governance are immediately aligned with the responsible technical team.
TheChange Groupis distinct from theAssignment Group, which is used primarily in Incident and Task routing.
Managed by Grouprepresents lifecycle ownership and is used by CMDB governance tools, whileApproval Groupcontrols approval workflows but is not auto-populated from CI selection.
This behavior demonstrates the value of accurate CI attributes: once populated consistently, they enableautomatic field population, reduced manual errors, and faster processingacross ITSM workflows.
Therefore, the correct answer isA - Change Group.

Within theCommon Service Data Model (CSDM),information objectsare used to representnon-CI data entitiesthat provide important business or governance context but are not configuration items themselves.
These objects are especially important when extending service visibility beyond pure infrastructure and application relationships.
The use case described inOption A-understandingasset lifecycle compliance in a Business Application context-explicitly requires information objects. Asset lifecycle data (such as financial state, depreciation, warranty, and compliance milestones) is typically managed in IT Asset Management (ITAM) and must beassociated to Business Applicationswithout converting every asset-related data point into a CI. Information objects enable this linkage while maintaining clean CMDB boundaries.
Option B focuses on event-to-incident automation, which relies onCIs, technical services, and operational relationships, not information objects. Option C (proactive case management) is primarily aCSM and service offeringuse case. Option D (SecOps risk context) relies onapplication services and business application relationships, not information objects. Option E (business service impact) is addressed throughservice modeling and service mapping, again without requiring information objects.
Information objects are introduced as organizations mature and need to integrategovernance, financial, or compliance datawith service and application models-making asset lifecycle compliance the correct match.
Therefore, the correct answer isA.

When organizations transition from legacy CMDB status fields (such as custom install status or operational status values) toCSDM-aligned lifecycle status fields, the goal is tomap old values to standardized lifecycle stageswithout disrupting existing processes. InServiceNow, this is achieved through theLife Cycle Mappingtable.
TheLife Cycle Mappingtable is specifically designed to translatelegacy or custom status valuesintoCSDM lifecycle stages and statuses. This allows organizations to preserve historical data and integrations while progressively adopting CSDM standards. By modifying this table, administrators can define how existing status values correspond to CSDM lifecycle stages such asPlan, Build, Deploy, Operate, and Retire.
TheLife Cycle Stagestable (Option A) defines the standard stages themselves and should not be modified, as these are core to CSDM governance.Life Cycle Stage Status(Option C) defines valid statuses within a stage and is also part of the standardized model.Life Cycle Controls(Option D) enforce governance rules but do not perform value translation.
Therefore, to safely transition from legacy status fields to CSDM lifecycle statuses, the correct and supported approach is to modify theLife Cycle Mappingtable, makingOption Bthe correct answer.