TheUnified MapinServiceNowprovides a consolidated view of services and their underlying components, integrating Discovery and Service Mapping data. To make this view actionable, Service Owners can applyfiltersto focus on relevant elements and reduce visual noise.

Filtering byCI type(Option A) is a core capability. It allows the Service Owner to show or hide categories such as servers, databases, load balancers, or applications—making it easier to analyze specific layers of the service.

Filtering byBusiness Criticality(Option D) is also available and highly valuable. This enables Service Owners to prioritize views around high-impact components, ensuring attention is focused on CIs that pose the greatest risk to service delivery.

Option B (Discovery source) is not typically exposed as a Unified Map filter because the map focuses onoperational and service context, not ingestion provenance. Option C (Managed by group) is a governance attribute and is not a standard visual filter within the Unified Map.

Thus, the correct filter options areA – CI typeandD – Business criticality.

TheCMDB Data Foundations DashboardinServiceNowis intended to provideongoing, trend-based visibilityinto how well the CMDB ingestion and maintenance processes are functioning—not just point-in-time issue lists. This is why continual monitoring of its metrics is valuable.

Option Bis correct because trackingactive CIs updated in the last 90 daysprovides a strong indicator ofdata freshness and operational relevance. A healthy CMDB should reflect recent updates from Discovery, integrations, and governed manual processes. Monitoring this metric over time helps organizations detect stagnation, discovery failures, or integration issues early.

Option Cis also correct because metrics forCIs processed by the Identification and Reconciliation Engine (IRE)directly indicate the effectiveness and adoption ofgoverned ingestion practices. Consistent IRE processing confirms that integrations are not bypassing identification rules, reducing duplicates and improving trust in CMDB data. Trending this metric helps validate Data Foundations maturity.

Option A is incorrect because the dashboard is not designed to provide exhaustive audit failure lists; those are handled through certification and remediation workflows. Option D is also incorrect becauseorphan CIsare a specific health condition surfaced via health rules and remediation tools, not a core benefit metric for continual dashboard monitoring.

Therefore, the correct answers areB and C.

TheIdentification and Reconciliation Engine (IRE)is acore platform capabilityinServiceNowand doesnot require CMDB 360 / Multisource CMDBto function. Even without the ITOM Discovery license, organizations can still define and useIRE reconciliation rulesacross multiple data sources.

IRE rules are source-aware and can evaluate attributes based onsource precedence, regardless of whether CMDB 360 is enabled. CMDB 360 enhances visibility, governance, and monitoring of multiple sources, but it isnot a prerequisitefor reconciliation logic itself.

Option A is incorrect because purchasing ITOM Discovery is not mandatory to use multisource reconciliation. Option C is also incorrect because CMDB 360 / Multisource CMDB is alicensed add-on, not a universally available platform feature.

Therefore, the Data Owner can proceed by configuringIRE reconciliation rules directly, makingOption Bthe correct answer.

TheAgent Client Collector (ACC)inServiceNowis designed to collect inventory data fromendpoints that are not consistently reachableby traditional Discovery methods. ACC is especially valuable where credential-based, network-based discovery is impractical or impossible.

Devices in secure environments(Option C), such as isolated networks, restricted zones, or highly regulated environments, often block inbound discovery traffic. ACC runs locally on the device and securely sends inventory data outward, making it ideal for these scenarios.

Devices that intermittently connect to the network(Option D), such as laptops, remote endpoints, or roaming devices, are another core use case. Traditional Discovery requires the device to be reachable during scheduled scans, which is unreliable for mobile or off-network assets. ACC ensures inventory data is collected whenever the device is online.

Option A (data center servers) is better served byagentless Discovery, which provides deeper infrastructure and relationship data. Option B (network devices in the DMZ) are typically discovered usingSNMP and network discovery, not ACC.

ACC complements Discovery as part of a layered ingestion strategy, ensuring accurate inventory coverage across diverse environments.

Therefore, the correct answers areC – Devices in secure environmentsandD – Devices that intermittently connect to the network.

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.

In ServiceNow CMDB governance, theCI Class Managerallows administrators to assignownership and accountabilityat the class level. This ownership is used by governance tools—especiallyCMDB Data Manager—to automatically determinewho receives tasks and actionsrelated to data lifecycle management.

The group reference field that aligns with class ownership and is consumed byCMDB Data Manager policiesis theManaged By Group. This field represents the team responsible for thetechnical stewardship and lifecycle managementof CIs within that class.

When CMDB Data Manager executes policies such as retention, archival, or cleanup, it uses theManaged By Groupto 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 reflectdata 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 isManaged By Group, makingOption Bthe verified answer.

ManagingCI classes and Principal Class designationis aschema-level CMDB activitythat directly impacts how CIs appear in ITSM processes such as Incident, Change, and Problem. InServiceNow, these activities require specific administrative privileges to ensure governance, security, and upgrade safety.

Thesn_cmdb_adminrole is required because it provides administrative access to CMDB structures, including CI class hierarchy management, Principal Class configuration, and overall CMDB governance. Without this role, users cannot add, remove, or govern CI classes effectively.

Thepersonalize_dictionaryrole is also required because adding or removing CI classes involvesdictionary-level changes. CI classes are implemented as tables that extend the CMDB schema, and modifying the Principal Class filter relies on dictionary metadata. This role grants permission to create, modify, or remove class definitions safely.

Thesn_csdm_adminrole focuses on managing CSDM constructs (domains, services, lifecycle alignment) but does not grant dictionary or schema modification rights. Thecmdb_query_builderrole is used only for querying and reporting and does not allow structural changes.

Therefore, the two required roles arepersonalize.dictionaryandsn_cmdb_admin, makingOptions A and Bcorrect.