CIS-DF Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Questions and Answers

In the CMDB class hierarchy, Server is a generic parent class, while Linux Server and Windows Server are more specific child classes. When ServiceNow Discovery detects sufficient evidence (such as OS signatures) to move a CI from a generic class to a more specialized one, this action is called a Class Upgrade.

A Class Upgrade occurs when a CI is reclassified down the hierarchy into a more specific subclass, enriching the record with additional attributes, behaviors, and discovery patterns appropriate to that class. This is a standard and expected behavior in mature CMDB implementations and aligns with Data Foundations best practices.

A Class Switch would imply lateral movement between unrelated classes, which is not what happens here. A Class Downgrade would move a CI from a specific class back to a more generic one, typically when discovery confidence is reduced—not the case in this scenario.

By performing class upgrades automatically, Discovery improves CMDB accuracy, reporting precision, and service mapping quality without manual intervention.

Therefore, the correct answer is C – Class Upgrade.

The default staleness threshold is 60 days . A CI is considered stale when it has not been updated within the applicable staleness interval. The update may normally come from Discovery, Agent Client Collector, Service Graph Connectors, IntegrationHub ETL, or another governed source.

Staleness is important because an old CI record may no longer represent the actual environment. Stale data can distort service-impact analysis, misdirect incidents, undermine change-risk calculations, and generate inaccurate operational reports. The guide identifies stale CIs as a core CMDB data-quality condition monitored through CMDB Health.

The 60-day value is the default, not an immutable platform rule. Administrators can configure appropriate thresholds by CI class and organizational requirements. Frequently changing cloud resources may require a shorter period, while stable infrastructure may justify a different governed interval.

Within the Common Service Data Model (CSDM), information objects are used to represent non-CI data entities that 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 in Option A—understanding asset 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 be associated to Business Applications without 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 on CIs, technical services, and operational relationships, not information objects. Option C (proactive case management) is primarily a CSM and service offering use case. Option D (SecOps risk context) relies on application services and business application relationships, not information objects. Option E (business service impact) is addressed through service modeling and service mapping, again without requiring information objects.

Information objects are introduced as organizations mature and need to integrate governance, financial, or compliance data with service and application models—making asset lifecycle compliance the correct match.

Therefore, the correct answer is A.

Agent Client Collector (ACC) → Collects inventory and telemetry from devices using an installed agent, especially where agentless discovery is not practical.

ServiceNow Discovery → Automatically identifies devices and applications on the network and populates the CMDB with accurate, up-to-date information.

Service Graph Connectors → Facilitates integration between ServiceNow and external systems to import and synchronize CMDB data.

Service Mapping → Builds the complete topology of services and shows how they are supported by underlying infrastructure and applications.

Each ingestion product has a specific role in CMDB Data Foundations. ServiceNow Discovery is primarily agentless and discovers infrastructure, applications, and relationships across the network. Agent Client Collector is agent-based and is useful for devices that are intermittently connected, remote, restricted, or difficult to scan through traditional Discovery. Service Graph Connectors are prebuilt, governed integrations used to bring third-party data into the CMDB while aligning with IRE and ServiceNow class models. Service Mapping focuses on service topology by identifying how application services depend on infrastructure and application components. The key distinction is that Discovery and ACC collect technical inventory, Service Graph Connectors integrate external sources, and Service Mapping builds service dependency models.

=========

Health Inclusion Rules are used to control which CI records are included in CMDB Health calculations and dashboard display. This is exactly what the question requires: filtering specific CI classes or CI populations so that only relevant and management-ready data contributes to health reporting. Identification Rules are used by the Identification and Reconciliation Engine to determine whether an incoming CI matches an existing CI or should create a new record. Reconciliation Rules control which data source can update specific attributes. Data Refresh Rules are not the correct CMDB Health scoping mechanism. Health Inclusion Rules allow organizations to exclude irrelevant, transitional, retired, unmanaged, or not-yet-ready CIs from health scoring so the dashboard reflects meaningful and actionable data. Therefore, A is correct.

The correct answer is Basic Info because the class icon is a class-level property, not an attribute, relationship, or CI list configuration. In CI Class Manager, the Basic Info tab is where administrators manage core metadata for a CI class, including class name, label, description, table details, principal class settings, and visual representation such as the class icon. The Suggested Relationships tab is used to define or review recommended relationship patterns between CI classes. The CI List tab is used to view records belonging to the class. The Attributes tab is used to review or manage inherited and class-specific attributes. Since the question specifically asks where the UNIX Server class icon can be changed, the correct location is the Basic Info tab.

=========

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 Data Foundations, “Insight” is about using health metrics to understand whether the CMDB is trustworthy and operationally usable. The CMDB Health Dashboard organizes health into scorecards that group related checks. When leadership asks for Duplicate CIs, Orphan CIs, and Stale CIs, they are asking about the CMDB’s ongoing hygiene and adherence to governance expectations—not simply whether fields are filled in.

These three metrics align best with Compliance because they represent whether CI records comply with rules that keep the CMDB clean and current over time:

Duplicate CIs indicate the identification and governance controls are not consistently preventing multiple records for the same real-world item.

Orphan CIs indicate relationship governance gaps—records exist without expected relationships or context, reducing their operational value and often signaling incomplete ingestion or lifecycle control issues.

Stale CIs indicate lifecycle management gaps—records are not being updated, attested, retired, or archived appropriately, which increases risk and noise in operational processes.

By contrast, Completeness focuses on whether required attributes are populated (owners, support group, environment, etc.). Correctness focuses on whether values and relationships are accurate and logically valid. While duplicates/orphans/stale can affect correctness indirectly, the dashboard’s grouping for these hygiene and lifecycle-oriented measures is best represented by Compliance, which is why B is the correct answer.

The correct answer is Service Consumption. Service Portfolio Management focuses on defining, organizing, and presenting services and offerings to business consumers. In CSDM, this aligns with the Service Consumption, or Sell/Consume, domain. This domain explains how business-facing services and offerings are made available to users, departments, locations, or customer groups. Design and Planning is concerned with strategic planning objects such as Business Applications, Business Capabilities, and Information Objects. Build and Integration focuses on development and delivery pipelines. Service Delivery focuses on the technical operation and management of services. Since the scenario is about presenting offerings to business consumers through Service Portfolio Management, it clearly belongs to Service Consumption.

=========

The Common Service Data Model (CSDM) organizes CMDB data into domains that reflect how services are planned, delivered, and consumed. Correct placement of objects is essential for reporting, ownership, and downstream ITSM, ITOM, and IRM use cases.

Design and Planning domain → Business Process

Business Processes describe how the business operates and what capabilities are required. These are planning constructs used to design services and applications before they are built or delivered.

Foundation domain → Business Application

Business Applications are foundational reference objects that represent what applications exist and who owns them . They anchor ownership, lifecycle, and governance but are not directly operational.

Service Delivery domain → Application Service

Application Services represent running, operational technical services (often created via Service Mapping). They are central to Incident, Change, and Event Management, making them part of Service Delivery.

Sell / Consume domain → Business Service

Business Services represent what is offered to customers or consumers . They define value delivery, SLAs, and consumption context, which is why they belong in the Sell/Consume domain.

This mapping aligns with CSDM v5 guidance and ensures clear separation between planning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMDB.

In Data Foundations, “Govern” is about putting repeatable, controlled mechanisms in place to keep CMDB data healthy over time. Duplicate CI cleanup is a governance activity because duplicates degrade trust, break reporting, create incorrect service impacts, and cause operational confusion (for example, incidents linked to the wrong CI). The preferred approach is to use the guided and purpose-built de-duplication experience designed for CMDB administrators rather than relying on generic task lists or ad-hoc work.

The de-duplication dashboard in CMDB Workspace is the preferred place because it centralizes duplicate identification, prioritization, and remediation in a single operational experience. It typically provides visibility into suspected duplicates, helps users review records side-by-side, and supports controlled actions (such as merge/retire workflows, depending on configuration) while maintaining auditability. This aligns with Data Foundations’ emphasis on standard processes and consistent remediation patterns rather than one-off manual fixes.

“My Tasks” is a generic work queue and does not provide the purpose-built context or tooling required to confidently resolve duplicates in a safe, repeatable way. A standalone “de-duplication task module” may exist as a navigation entry, but the recommended operational method is to use the workspace dashboard where duplicate remediation is organized and guided as part of CMDB health and governance. Therefore, the correct answer is the de-duplication dashboard on CMDB Workspace.

Dynamic reconciliation rules are tied to CMDB 360 / Multisource CMDB because they depend on visibility into multiple contributing data sources for the same CI. Standard reconciliation rules control which data source is allowed to update specific CI attributes based on source precedence, but dynamic reconciliation adds more advanced logic, such as choosing a value based on source reporting behavior or data comparison rules. CMDB Workspace and CMDB Data Manager do not enable dynamic reconciliation; they are management and governance interfaces. Reconciliation Rules alone are not the enabling feature because basic IRE reconciliation can exist without the CMDB 360 dynamic reconciliation capability. Therefore, to use dynamic reconciliation rules, CMDB 360 / Multisource CMDB must be enabled.

=========

Managing CI classes and Principal Class designation is a schema-level CMDB activity that directly impacts how CIs appear in ITSM processes such as Incident, Change, and Problem. In ServiceNow, these activities require specific administrative privileges to ensure governance, security, and upgrade safety.

The sn_cmdb_admin role 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.

The personalize_dictionary role is also required because adding or removing CI classes involves dictionary-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.

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

Therefore, the two required roles are personalize.dictionary and sn_cmdb_admin, making Options A and B correct.

The CMDB Data Foundations Dashboard identifies foundational CMDB data-quality deficiencies, including hardware CIs that lack important identification attributes such as serial numbers. A missing serial number is particularly serious because serial number is commonly included in Hardware identification rules. Without it, Discovery and external integrations may fail to match an incoming device to its existing record, resulting in duplicate CIs.

The dashboard exposes the affected population and provides remediation playbooks that help administrators analyse the responsible data sources, correct existing records, and establish controls to ensure that serial numbers continue to be populated.

CI Class Manager is used to configure class structures and identification rules, but it is not the dashboard used to locate the full population of affected CIs. CMDB Data Manager governs lifecycle policies, while the CSDM dashboard focuses on service-model alignment.

=========

The fastest and most supportable time-to-value option is the SCCM Service Graph Connector . Service Graph Connectors are purpose-built integrations for bringing third-party source data into the CMDB using ServiceNow-supported mappings, Identification and Reconciliation Engine processing, source tracking, and standardized class alignment. For SCCM specifically, the SCCM Service Graph Connector avoids the technical debt of building custom JDBC imports, transform maps, and scripts. Import sets and transform maps can work, but they require more implementation effort and create higher risk if IRE is not correctly invoked. IntegrationHub ETL with RTE is a stronger pattern than raw imports, but for SCCM the dedicated Service Graph Connector is still the fastest and most governed solution. SCCM Usage Metering Spoke is not the CMDB ingestion tool for Windows computer CI data. Therefore, D is correct.

The Assignment Group attribute on the CI provides the operational routing information needed to direct work to the responsible technical team. When the affected CI is associated with the change, governed group information from the CMDB can be used to populate or determine the appropriate assignment group, reducing manual routing and preventing the change from being assigned incorrectly.

The Approval Group serves a different purpose: it identifies a group responsible for approval decisions rather than the team that performs the work. A Service Offering can provide service, environment, entitlement, or consumption context, but it does not by itself identify the resolver group for this question. Service Subscriptions identify service consumers and are not task-assignment mechanisms.

A trusted CMDB therefore improves Change Management by supplying accurate ownership and group information, enabling dynamic routing and clearer accountability.

=========

Managing CMDB data volume is a key Data Foundations governance objective. Over time, CMDBs naturally accumulate retired, obsolete, or decommissioned CIs. If these records are not properly managed, they degrade CMDB performance, reduce reporting accuracy, and negatively impact discovery reconciliation and health scores.

Archive Policies are the mechanism designed to address this challenge. They define when CI records should be archived or deleted based on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that only relevant, active CIs remain in the operational CMDB, keeping data volume manageable and performant.

Business Rules (Option A) are used to enforce logic during record creation or updates, not for long-term data volume control. Scheduled Jobs (Option B) may execute tasks, but without archive policies they have no governance logic to determine what should be removed or retained.

Archive policies work in conjunction with CMDB Data Manager to enforce lifecycle-based retention and cleanup, making them the correct and verified answer.

Therefore, Option C – Archive Policies is correct.

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.

=========

Application Service Mapping is a critical capability in ServiceNow for enabling business-aware Change Management. Its primary value is not in identifying physical shutdown sequences or CI locations, but in translating technical changes into business impact.

When an organization plans a data center move, multiple infrastructure components—servers, databases, network devices—may be affected. On their own, these technical CIs provide little insight into business risk. Application Service Mapping connects these CIs to Application Services and Business Services as defined by the Common Service Data Model (CSDM). This relationship allows Change Managers to see which business services, customers, and processes are impacted by the planned change.

By leveraging service maps, Change Management can answer critical questions such as:

Which customer-facing services may experience downtime?

What revenue-generating or mission-critical services are at risk?

Which stakeholders must be notified or involved in approvals?

Option A is incorrect because service mapping does not determine shutdown order; that is handled by infrastructure planning. Option C focuses on physical location data, which is typically managed through Location CIs and Discovery, not service mapping.

Therefore, the correct answer is B – To understand the business impact of CIs, which aligns directly with ITIL 4, CSDM, and Change Management best practices.

In Data Foundations, “Govern” includes maintaining consistency between closely related data domains so that operational and asset lifecycle processes remain trustworthy. For hardware endpoints (and other asset-backed items), Asset and CI records often represent the same real-world item from two perspectives: financial/lifecycle management (Asset) and operational/service context (CI). Automatic synchronization prevents drift such as different owners, locations, or statuses appearing in Asset vs CI, which can cause reporting errors, incorrect fulfillment decisions, and audit issues.

The platform supports synchronization through out-of-box synchronization logic (commonly implemented as business rules and related configuration) that updates the CI when an Asset changes, and updates the Asset when a CI changes—so the records stay aligned regardless of which team updates which record. Therefore, ensuring the Asset-to-CI update logic is active (A) and the CI-to-Asset update logic is active (B) is the right way to keep data synchronized automatically.

Option C is not required for synchronization; the intent is near real-time consistency driven by record changes, not batch jobs that run later. Scheduled jobs might exist for other maintenance activities, but they are not the primary mechanism for keeping Asset/CI synchronized. Option D is important as a data quality principle—ideally one Asset maps to one CI for physical items—but “ensuring one-to-one mapping” is not the automation mechanism itself. Automation is achieved through the active synchronization logic, which is why A and B are the correct answers.

Enhancing Incident Management in ServiceNow often involves integrating complementary products that enrich context, prioritization, and decision-making.

Discovery strengthens incident resolution by automatically populating accurate CI data and relationships, allowing responders to quickly understand affected infrastructure and applications.

Hardware Asset Management (HAM) adds visibility into asset lifecycle, ownership, and maintenance actions, which is especially valuable when incidents involve physical devices or failures.

Risk Management (part of IRM) provides insight into business and financial risk exposure, helping teams prioritize incidents based on potential regulatory, safety, or financial impact.

Service Portfolio Management (SPM) connects incidents to the service lifecycle, enabling better understanding of whether an incident affects a live, retiring, or planned service—and improving communication with stakeholders.

Together, these integrations transform Incident Management from a reactive process into a context-rich, business-aligned capability.

Service Graph Connectors are a key Data Foundations ingestion capability in ServiceNow. They provide out-of-the-box, upgrade-safe integrations that ingest data into the CMDB using the Identification and Reconciliation Engine (IRE), ensuring data quality and source governance.

Two primary categories of Service Graph Connectors are:

Cloud (Option A): These connectors integrate with major cloud providers and platforms (such as AWS, Azure, and GCP) to ingest infrastructure, platform, and service data into the CMDB. They are essential for managing hybrid and multi-cloud environments and maintaining accurate cloud CI relationships.

Observability (Option B): These connectors integrate with monitoring and observability tools (such as APM, infrastructure monitoring, and telemetry platforms). They provide near-real-time operational data that enriches CI records and supports incident correlation, impact analysis, and service health insights.

Option C (DevOps) is incorrect because DevOps integrations are typically handled through CI/CD tools and workflow integrations rather than Service Graph Connectors. Option D (Workflow Automation) is unrelated; Service Graph Connectors focus on data ingestion, not process orchestration.

Therefore, the correct connector categories are Cloud and Observability, making Options A and B the correct answers.

In ServiceNow, validating whether Configuration Items (CIs) still exist is a core CMDB governance activity. Over time, environments change rapidly—servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or “ghost” CIs.

Attestation policies are specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them to confirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.

Certification policies (Option A) are used when specific attributes must be validated, such as lifecycle status, support group, or environment. While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.

Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability—ensuring accountability for CI ownership. This makes it the correct and Data Foundations–aligned policy type for validating CI existence.

Therefore, Option D – Attestation is the correct answer.

In Data Foundations, “Insight” focuses on turning configuration data into actionable visibility. CMDB 360 (often associated with Multisource CMDB capabilities) provides a guided experience in CMDB Workspace for exploring CI data and running queries across sources. Within this experience, Saved Queries are managed directly under the CMDB 360 area of CMDB Workspace because they are part of the CMDB 360 query-and-analysis workflow.

A CMDB 360 Saved Query is not the same as a generic CMDB Query Builder query created from classic navigation modules. The CMDB 360 experience typically uses a tile/window approach where users can view existing saved queries, create new queries, modify them, and run them to retrieve CMDB 360 data aligned to multisource reporting and analysis. Keeping saved queries on the CMDB 360 tab makes them easy to discover and reuse for repeatable insights (for example, coverage and source comparisons, CI data quality checks by source, and targeted investigation of records).

The Insights tab in CMDB Workspace is generally used to understand adoption and health-related insights about CMDB features, not as the primary location for creating CMDB 360 multisource saved queries. “Coverage” is a specific lens/view and does not represent the saved-query creation workspace. “CMDB Query Builder” is a related capability, but the question explicitly asks where CMDB 360/Multisource Saved Queries are viewed and created in CMDB Workspace , which is the Saved queries window on the CMDB 360 tab.

The organization should use a CMDB Query to identify application services and their related infrastructure because those records are CMDB classes and relationships. CMDB Query Builder is designed to traverse CMDB relationships, such as application services to databases, servers, and supporting infrastructure. Since the requirement also includes incidents, the query must include a non-CMDB table because Incident is a task/process table, not a CMDB CI class. That is why adding a non-CMDB table to the query is required. A Service Mapping Query is not the correct approach for adding Incident data; Service Mapping is used to discover and visualize service topology, not to build mixed CMDB and task-table analytical queries. Therefore, the correct steps are using a CMDB Query for application services and infrastructure, then adding the non-CMDB Incident table.

=========

Data Foundations strongly encourages using out-of-box synchronization mechanisms rather than custom scripting whenever possible, to reduce technical debt and improve upgrade safety. In this scenario, endpoint data is being ingested into the CI record, and the Asset team needs the corresponding Asset record kept in sync automatically for their asset management processes.

The recommended approach is to use Asset CI Field Mapping, which is designed specifically to map and synchronize fields between an Asset and its related CI. Creating or updating a mapping rule for “Assigned to” allows the platform to replicate the value in a controlled, supportable way without writing scripts. This approach aligns with best practices: standard configuration, clear governance, and minimal custom code.

Option B (a scripted business rule) can work technically, but it introduces maintenance risk, testing overhead, and potential upgrade fragility—exactly the kind of technical debt Data Foundations warns against when an OOTB capability exists. Option A (dot-walking) changes the user experience and does not truly populate the Asset field; it only displays a derived value and may not meet Asset team needs for reporting, exports, integrations, or lifecycle workflows that expect the Asset field to be set. Therefore, the best automated and best-practice solution is Asset CI Field Mapping.

Foundation → Use the base system tables when implementing CSDM to get the highest value from ServiceNow products and the Now Platform.

Design and Planning → Understand CIs related to Business Applications and related capabilities; identify redundancies, monitor costs, and make better investment decisions around the roadmap.

Service Consumption → Understand Business Services, ownership, cost, scope of work offered to business consumers, and request access to business services.

Service Delivery → Understand Technical Services, Technical Service Offerings, service support, and all relationships to underlying technology CIs.

CSDM separates data into domains so organizations can model business planning, consumption, and technical delivery without mixing concerns. The Foundation domain provides base reference data such as users, groups, companies, locations, and foundational tables used across the platform. Design and Planning supports architecture and portfolio planning through Business Applications, Business Capabilities, and Information Objects. Service Consumption focuses on how services are exposed to and consumed by business users through Business Services and Business Service Offerings. Service Delivery focuses on how services are technically operated using Technical Services, Technical Service Offerings, Application Services, and supporting infrastructure CIs. This separation is what makes CSDM valuable: each domain answers a different management question while still connecting to a unified service model.

=========

The CMDB Process Owner is accountable for the overall Configuration Management process and its governance framework. This includes establishing data standards, defining ownership and stewardship expectations, coordinating remediation processes, monitoring CMDB health, and ensuring that identification and reconciliation practices support trustworthy data.

A CI Analyst performs operational work on assigned CI classes, including updating records and resolving specific CMDB-related tasks. However, the analyst does not own organization-wide governance standards. A CMDB Architect designs the CMDB data model and technical architecture, while a Service Owner is accountable for a particular service. The IT Asset Manager focuses primarily on financial, contractual, and asset-lifecycle information.

Because the requirement covers organizational standards, cross-source data quality, and ongoing governance accountability—not merely individual record maintenance—the CMDB Process Owner is the correct role.

=========

The Related items panel displays records associated with the selected CI, including active incidents, problems, changes, and other task-related information. This allows the Service Desk Manager to move from the CI’s topology to the operational records currently affecting or involving that CI.

The Overview panel presents summarized CI information. The Attributes panel displays field values belonging to the CI. The Application services panel identifies service associations and dependencies, but it is not the primary panel for listing related Incident and Problem records.

Unified Map is intended to combine CI details, relationships, service context, and operational information in a single graphical experience. Its filtering capabilities also allow users to focus on relevant CI types and business-critical elements when analysing a service or CI topology.

Therefore, Related items is the panel that provides the required active task information.

=========

Custom CMDB class tables should begin with u_cmdb_ci . The u_ portion identifies a customer-created table, while cmdb_ci preserves the standard CMDB naming convention and clearly indicates that the table extends the Configuration Item hierarchy.

For example, appropriate custom class names may resemble u_cmdb_ci_custom_router or u_cmdb_ci_special_switch. The uploaded guide uses these exact naming patterns when discussing custom-class consolidation and the technical debt created by unnecessary custom classes.

Using only cmdb_ci would incorrectly suggest an out-of-box ServiceNow table. Prefixes such as u_ci_cmdb and ci_cmdb do not follow the standard hierarchy convention. Before creating any custom class, the administrator should still verify that a suitable supported class is not already available through the CMDB CI Class Models application.

=========

This question tests understanding of how the Identification and Reconciliation Engine (IRE) evaluates incoming CI data against Identification Rules and their priority order in ServiceNow.

From the identification rule shown:

Serial number (+ type) → Priority 100

Serial number → Priority 200

Name (Hardware) → Priority 300

MAC address + name (Network Adapter) → Priority 400

For a CI to be identified and matched, the incoming record must satisfy one complete identifier entry exactly as defined for that class.

CI1 (Name match only)

Although the name matches an existing Hardware CI, name alone is a low-priority identifier (300) and is not sufficient to uniquely identify a Hardware CI unless no higher-priority identifiers exist and the identifier entry criteria are fully satisfied. In practice, Hardware identification relies on serial number–based identifiers, not name-only matching, to avoid false positives. Therefore, CI1 cannot be confidently matched and is inserted as a new record.

CI2 (IP address match)

IP address is not part of any Hardware identification rule shown. IP address is typically used for discovery correlation or network relationships, not as a primary Hardware identifier. Since no identifier entry includes IP address, CI2 does not match any valid identification rule and is also inserted as a new record.

Because neither CI satisfies a valid identifier entry, both records are inserted as new CIs.

The contextual side panel is the correct work area because it displays detailed information about the selected node in Unified Map. When a Service Owner selects the home node or a related CI/service node, the contextual side panel provides supporting operational context such as active Incidents, planned Changes, related records, and other actionable details. This is exactly the requirement in the question: the Service Owner does not merely need to see topology; they need related work items connected to the selected node. The Map itself displays relationships and topology, but it does not provide the detailed related-record panel by itself. The toolbox provides map interaction tools, and content controls influence what layers or types of content are displayed. Neither of those is the correct place to review related Incidents and Changes for a selected node. Therefore, the correct answer is Contextual side panel.

The correct answer is CSDM Data Foundation Dashboard because the requirement is specifically about end-to-end service modeling and guided improvement through status and playbooks. CSDM guidance focuses on modeling services, application services, business applications, offerings, technical services, and their relationships. The CSDM Data Foundation Dashboard provides visibility into CSDM maturity and uses playbooks to guide remediation of weak or missing service-model data. Service Mapping is only one technical capability used to discover and map service relationships; it is not the overall governance dashboard for CSDM adoption. CMDB Workspace is the broader operational workspace for CMDB management, but the question asks for status and playbook-based guidance for CSDM service modeling quality. Therefore, the best reference point is the CSDM Data Foundation Dashboard.

=========

The Desired State audit type is included in the CMDB Health Compliance calculation. A desired-state audit compares the actual values stored on a CI against the values or conditions that the organization expects the CI to meet.

In this scenario, the organization’s desired state is that every server must have the current approved patch level. A Certification Template can define the server population and attributes to be evaluated. The resulting audit identifies servers that do not satisfy the expected patch condition, and those results contribute to the Compliance KPI.

“Compliance” is the name of the overall CMDB Health scorecard, not the audit type selected for this check. “Architecture Compliance” is not the applicable audit type for validating server patch-level attributes.

The Compliance scorecard uses audit results to determine whether CIs conform to defined organizational standards. Therefore, the correct audit type is Desired State .

=========

In ServiceNow, controlling source precedence when multiple authorized data sources update the same CI attributes is a core responsibility of Identification and Reconciliation Engine (IRE) governance.

The correct and supported method is to assign priority to each data source in reconciliation rules. Reconciliation rules determine which source wins when multiple sources attempt to update the same attribute on a CI. By defining source precedence, the Configuration Manager ensures that the most authoritative system of record (for example, Discovery over manual imports, or HR systems over spreadsheets) consistently controls specific attributes or classes.

Option B is incorrect because manually sequencing data source runs is unreliable, does not scale, and violates Data Foundations best practices. Option C only controls how often data is refreshed, not which source is authoritative. Option D is incorrect because identification rules are used to uniquely identify CIs—not to control attribute-level precedence.

Using reconciliation rules provides deterministic, auditable, and automated control, which is essential for maintaining CMDB trust and avoiding data conflicts.

Therefore, the correct answer is A – Assign a priority to each data source in reconciliation rules.

IntegrationHub ETL provides a guided, low-code Extract, Transform, and Load experience. Administrators can define a source, map source fields and relationships to ServiceNow target structures, transform the data through the Robust Transform Engine, and execute recurring imports.

It also integrates with the Identification and Reconciliation Engine for CMDB targets. Incoming CI data is processed against identification rules to determine whether a record should be inserted or updated. Reconciliation rules and source precedence then control whether the source is permitted to update specific attributes.

IntegrationHub ETL does not inherently require SQL or extensive scripting for normal transformations. It also does not replace Discovery or Service Mapping. Discovery actively identifies infrastructure and technical relationships, while Service Mapping builds application-service topology. IntegrationHub ETL primarily imports and transforms data supplied by an external source.

=========

The Correctness scorecard evaluates whether CI data accurately represents the real environment. It includes the Duplicate , Orphan , and Staleness metrics.

Duplicate identifies cases where the same real-world configuration item is represented by multiple CMDB records. Orphan identifies CIs that lack expected relationships or supporting context. Staleness identifies records that have not been updated within the configured period and may no longer represent active infrastructure.

The other choices belong to different CMDB Health KPIs. Audit belongs to Compliance because it evaluates whether CI values satisfy defined standards or desired-state conditions. Required and Recommended belong to Completeness because they measure whether mandatory and useful attributes are populated.

Therefore, Duplicate, Orphan, and Staleness are the metrics shown under Correctness.

=========

In ServiceNow, the Duplicate CI Remediator is designed to resolve duplicate records while preserving the most authoritative data from each source. Data Foundations guidance clearly states that automated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often contain valuable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-date technical data, making it the correct CI to retain as the primary record. However, the manually imported CI has a critical relationship to a business application, which is essential for impact analysis, incident prioritization, and CSDM alignment. Deleting this CI without preserving the relationship would result in loss of business context and reduced CMDB value.

The Duplicate CI Remediator supports selective merging, allowing administrators to retain one CI while merging specific attributes or relationships from the duplicate. Option C reflects this best practice by retaining the discovered CI and merging the relationship from the manually imported CI, ensuring both technical accuracy and business relevance are preserved.

Options A and D would result in the loss of important relationship data, while Option B would discard the discovered CI, violating the principle that discovery should be the authoritative source for technical attributes.

Therefore, Option C is the correct and Data Foundations–aligned answer.

Identification Inclusion Rules restrict the population of existing CIs that the Identification and Reconciliation Engine considers when attempting to identify an incoming CI. They add qualifying conditions to the identification process so that IRE searches only the relevant subset of records instead of evaluating every CI in the class.

For example, an inclusion rule could constrain matching to CIs belonging to a particular company, environment, domain, or other defined population. After narrowing the candidate records, IRE applies the class’s identifier entries and identification criteria to decide whether an existing CI matches the incoming data. Identification rules determine whether an incoming record matches an existing CI or requires creation of a new record.

Option A describes reconciliation rules, which control source authority over attributes. Option B is incorrect because inclusion rules do not stop the source from submitting data.

The video displays “Health Inclusion Rules,” but that is a terminology error. Health Inclusion Rules control CMDB Health scope; Identification Inclusion Rules are used by IRE.

=========

The CMDB plays a critical role in security operations by providing trusted, structured insight into the organization’s IT landscape. When built according to Data Foundations principles—accurate discovery, governed relationships, and alignment to CSDM—the CMDB becomes an essential enabler for security incident response and vulnerability management.

Option D is correct because the CMDB allows security teams to identify exactly which IT infrastructure components are affected by a vulnerability. By correlating vulnerability scan results with configuration items (CIs), security teams can determine whether an issue exists on a server, application, cloud resource, or network device—and understand where that CI sits within the broader service context. This eliminates blind spots and reduces time spent investigating unknown or unmanaged assets.

Option A is also correct because the CMDB supports assessment and remediation activities during security incidents. Once affected CIs are identified, the CMDB provides ownership, support group, environment, and service relationships. This enables security teams to quickly route remediation tasks to the correct resolver groups, assess business impact, and prioritize response based on service criticality. While the CMDB does not perform remediation itself, it enables informed and coordinated action.

Option B is incorrect because vulnerabilities are not auto-resolved by the CMDB; remediation requires human decision-making and execution through security, patching, or change processes. Option C, while related to governance and compliance use cases, is more aligned with GRC and audit functions rather than day-to-day security operations, making it less appropriate for this question.

In summary, the CMDB’s primary value in security operations is visibility and actionable insight, enabling faster identification, assessment, and response to security threats.

The correct option is Allow fallback to parent’s rules . In CI identification, ServiceNow evaluates the configured identification rule for the target class first. If the Tomcat rule cannot find a match using its class-specific criterion attributes, fallback behavior allows the Identification and Reconciliation Engine to attempt matching against the parent class identification rule. Since Tomcat is a more specific application class, falling back to the parent Application identification rule helps prevent unnecessary duplicate records when a match cannot be made at the subclass level. “Applies to” defines the class or scope for the identifier entry. “Independent” controls whether a rule is evaluated independently rather than through parent inheritance. “Criterion attributes” are the fields used for matching, not the fallback setting. Therefore, the correct configuration is Allow fallback to parent’s rules .

=========

The Walk stage introduces the service-model relationships required to connect business-facing services and offerings to the Application Services that technically enable them. At this stage, the organization has progressed beyond foundational CMDB population and begins establishing service context for operational processes.

Relating Business Service Offerings to Application Services allows service owners to determine which technical services support each consumable business offering. This enables impact assessment, outage communication, change-risk evaluation, and identification of affected consumers. The guide explains that the Walk stage establishes Business Services and their relationships with Application Services and infrastructure so the CMDB can support Incident, Problem, and Change impact analysis.

Crawl primarily establishes foundational CI data and ingestion controls. Run and Fly represent more advanced operationalization and optimization. Foundation is a CSDM domain rather than the appropriate maturity stage for this relationship.

=========

This question tests understanding of reconciliation source priority in the Identification and Reconciliation Engine (IRE) in ServiceNow.

In reconciliation rules, lower numeric values represent higher priority. Therefore, the priority order is:

ServiceNow (100) – highest authority

Altiris (200)

SCCM (300) – lowest authority

Why A is correct

Because Altiris (200) has higher priority than SCCM (300), data from Altiris can update records originally inserted by SCCM. This is exactly how reconciliation precedence works—higher-priority sources can overwrite lower-priority ones.

Why C is correct

SCCM, even though it has the lowest priority, is still an authorized discovery source. It can insert new records into the Windows Server table when no existing CI is identified. Priority only affects updates, not the ability to create records.

Why B is incorrect

ServiceNow (priority 100) can update records from Altiris and SCCM because it has the highest priority. The statement incorrectly claims it cannot.

Why D is incorrect

SCCM does not have the highest authority. A higher numeric value means lower priority, so SCCM cannot update records created by higher-priority sources.

Life cycle mappings are used to review how legacy CMDB status values correspond to the newer CSDM life cycle stage and life cycle stage status model. This is a key governance activity during transition from older status fields to CSDM-aligned lifecycle management. The mapping layer allows administrators to understand and control how legacy operational values translate into standardized lifecycle stages and stage statuses. This prevents inconsistent reporting, incorrect CI retirement behavior, and confusion between old and new status models. A choice list only stores selectable values and does not provide the mapping relationship between legacy status and CSDM lifecycle fields. Life cycle properties may control behavior but do not serve as the review location for legacy-to-CSDM value alignment. Therefore, when reviewing equivalent legacy status and CSDM lifecycle values, the correct location is Life cycle mappings.

In Data Foundations, a low “Unique Locations” result indicates the CMDB contains duplicate Location records (or inconsistent location usage) that reduce data reliability for operational reporting and service analytics. This sits under “Insight” because the dashboard is highlighting a measurable quality issue, and the playbook provides a structured remediation path to restore confidence.

The recommended playbook-aligned process is to review the duplicate locations, determine which one is correct per the organization’s naming and data standards, then re-point dependent records (CIs) to the correct Location before removing the duplicate. That sequence is essential: if you delete a duplicate location without first updating related CIs, you risk leaving CIs with missing/invalid location references, creating new completeness and correctness issues.

Option C matches best practice: validate which location record should remain, update all affected CIs (and any other dependent records) to use the correct location, and then delete (or retire/merge, depending on process controls) the duplicate record. Option B is risky because it skips validation and dependency updates. Option D defeats the purpose of “Unique Locations” by allowing ongoing inconsistency. Option A is not the best fit because “Duplicate CI Remediator” is oriented toward CI duplicates; Location is typically a reference/organization data domain and is handled through the specific remediation steps for that data set. Therefore, C is the recommended process.

CMDB Data Foundations Dashboard playbooks explain why a deficient metric matters and provide recommended actions for improving it. This includes insight into downstream consequences such as duplicate creation, inaccurate assignment, unreliable impact analysis, weak service context, incorrect reporting, or ineffective Incident, Change, and Security Operations processes.

The playbooks also provide remediation options. These guide administrators through analysing affected records, identifying responsible data sources, correcting existing data, and introducing governance controls to prevent the condition from returning. The guide describes remediation playbooks as structured guidance for analysing issues and implementing targeted corrective actions.

They are not automatically executed scripts. Human analysis, source correction, ownership decisions, and governance changes are generally required. They are also more than generic remediation templates because their value includes contextual impact information and metric-specific recommendations.

Therefore, the two stated benefits are downstream-impact insight and remediation options, making B and D correct.

=========

The Unified Map is designed to provide enhanced visual insight and analysis across the CMDB by consolidating configuration item (CI) relationships from multiple sources—such as Discovery, Service Mapping, and manual relationships—into a single, interactive view. While traditional Service Mapping maps are optimized for modeling and understanding application-to-infrastructure dependencies, the Unified Map extends this capability with more flexible visualization and exploration features.

Option B is correct because the Unified Map allows users to zoom in and out, enabling both high-level overviews and detailed inspections of complex CI relationships. This capability is particularly valuable in large enterprise environments where services may span hundreds or thousands of infrastructure components. Zoom functionality supports impact analysis, troubleshooting, and architectural reviews without overwhelming the user with unnecessary detail.

Option C is also correct because the Unified Map supports filtering of map nodes based on user preferences. Administrators and analysts can filter by CI class, relationship type, lifecycle state, or other attributes, allowing them to focus on what is most relevant to their task—such as identifying only production CIs, security-relevant components, or a specific technology stack. This aligns strongly with Data Foundations principles by improving usability and decision-making without altering underlying data.

Option A is incorrect because modifying the number of levels displayed is a characteristic more closely associated with Service Mapping configuration rather than an added Unified Map capability. Option D is incorrect because visibility into an application and its host is a core Service Mapping function, not an enhancement unique to the Unified Map.

In summary, the Unified Map adds value by improving interactivity, flexibility, and user-driven insight across the CMDB.

The Common Service Data Model (CSDM) prescribes an incremental, maturity-based rollout approach to reduce risk and ensure sustainable adoption. The recommended order is Crawl, Walk, Run, Fly, which aligns implementation effort with increasing organizational capability and value realization.

Crawl focuses on foundational data hygiene: core CI classes, identification rules, reconciliation, basic Discovery ingestion, and CMDB Health basics.

Walk introduces service context, including Business Services, Application Services, and relationships that enable impact analysis for Incident and Change.

Run expands into operational excellence with Service Mapping, service offerings, advanced governance, and process automation.

Fly represents optimization and scale, leveraging analytics, AI/ML, proactive operations, and cross-domain integration (e.g., SecOps, APM, CSM).

This progression ensures teams do not over-model early or introduce complexity before data quality and governance are established. The other options describe generic project lifecycles or organizational categorizations, not the CSDM-recommended adoption path.

Therefore, the correct answer is D – Crawl, Walk, Run, Fly.

The CMDB Data Foundations Dashboard helps administrators assess whether important CMDB data is valid, properly configured, and aligned with expected data quality practices. It is designed to surface actionable gaps and risks, then guide remediation through playbooks. Therefore, B and C are correct. The dashboard does not automatically remediate all risks by itself; it guides administrators and data owners toward corrective actions through structured playbooks. It also is not primarily a custom metric development framework. Its purpose is to provide curated, ServiceNow-aligned metrics and remediation guidance for CMDB and CSDM maturity. This makes it useful for improving data health, identifying configuration issues, and supporting governance without requiring custom reporting or manual analysis from scratch.

=========

The correct answer is Establishing clear governance and continuously monitoring CMDB health . A functional CMDB is not achieved simply by loading large quantities of data or deploying discovery tools. Operationalizing the CMDB requires ownership, standards, data policies, lifecycle controls, class governance, relationship governance, health monitoring, and remediation processes. Discovery is valuable, but without governance it can still create stale, incomplete, duplicated, or poorly related CI data. Allowing teams to freely modify CMDB records creates inconsistency and weakens trust. Populating the CMDB with as much data as possible is also a common failure pattern because excessive, unmanaged data reduces usability and increases maintenance effort. Data Foundations emphasizes trusted, governed, and actionable data. Therefore, the most critical success factor is clear governance combined with continuous CMDB Health monitoring.

=========

Creating new CI classes is a high-impact configuration activity and must follow strict Data Foundations and CSDM-aligned best practices to avoid long-term technical debt and upgrade risk.

Option B is a recommended first step. Before creating any new CI class, administrators should install or update the CMDB CI Class Models Store application and verify whether an appropriate class already exists. ServiceNow frequently delivers new CI classes through updates and class model packages, and duplicating an existing or planned class can lead to fragmentation and governance issues.

Option C is also correct. When a new class is truly required, it should be added under an appropriate parent class to inherit attributes, behaviors, and discovery patterns. For an IoT Sensor, this might be under a hardware or device-related parent class, ensuring consistency and minimizing customization.

Option A is incorrect and dangerous—deleting unused classes can break dependencies and historical data. Option D is also discouraged; modifying existing classes to repurpose them violates upgrade-safe design principles and can negatively impact discovery, integrations, and reporting.

By verifying existing models first and extending the class hierarchy correctly, organizations maintain a clean, scalable, and upgrade-safe CMDB.

Therefore, the correct answers are B and C.

In the Common Service Data Model (CSDM), the Incident form is designed to capture operational impact and enable effective incident routing, prioritization, and communication. To achieve this, CSDM prescribes using classes that represent how services are delivered and consumed, not how they are planned or governed.

Application Service (Option A) is an appropriate class on the Incident form because it represents the technical service that is running in production and is directly impacted during an incident. Application Services are service-mapped, relate to underlying infrastructure, and support impact analysis, root cause investigation, and automated assignment. This makes them ideal for associating incidents with technical outages or degradations.

Service Offering (Option C) is also appropriate because it represents how a service is consumed by users or business units. Service Offerings allow Incident Management to understand who is affected, enable targeted communications, and support SLA/OLA alignment. For example, an email service offering for a specific department clearly identifies the impacted consumer group.

Business Application (Option B) is not recommended on the Incident form. Business Applications are logical representations used for portfolio, ownership, and governance purposes, not day-to-day operational incident handling. Using them directly on incidents can reduce precision and automation.

Service Portfolio (Option D) is a strategic construct used for service lifecycle management and is never associated with operational incidents.

Therefore, according to CSDM best practices, the correct classes used on the Incident form are Application Service and Service Offering, making Options A and C the correct answers.

The CMDB Data Foundations Dashboard is paired with Get Well Playbooks that guide administrators through structured remediation. The “Services Have Owners Identified” playbook focuses on closing ownership gaps for services, which is a governance and data correction activity.

Fix Data (Option A) is used to correct missing or incorrect values, such as populating owner fields, assigning responsible groups, or updating relationships. In this playbook, Fix Data actions are required to actually remediate the issue by assigning owners to services.

Govern Data (Option D) is also required because ownership is not a one-time correction—it must be enforced and sustained. Govern Data establishes policies, ownership accountability, and controls (such as certifications or attestations) to ensure services continue to have owners over time and do not regress.

Analyze Data (Option B) is used to understand patterns and root causes, but it does not remediate the issue. Report Data (Option C) provides visibility and communication, not corrective action.

Therefore, the remediation plays that apply to the Services Have Owners Identified playbook are Fix Data and Govern Data, making Options A and D correct.

Delete and archive policies are designed for end-of-life CMDB lifecycle governance. They should apply to records that are no longer active operational CIs and have reached an appropriate retired state. End of Life - Retired is the correct lifecycle state because it indicates that the CI has completed its useful operational lifecycle and can be governed through archival or deletion according to retention rules. Applying delete or archive policies to Inventory - Available records would be dangerous because those CIs may still be valid and usable. “In any lifecycle state” is wrong because unrestricted archival or deletion can remove active, dependent, or operationally important records. “Missing - Stolen” is more aligned with asset disposition and exception handling, not the standard CMDB Data Manager delete/archive target state. Therefore, these policies should affect servers in End of Life - Retired.

=========

When duplicate CIs are evaluated, one record is treated as the main or original CI and the remaining records are marked as duplicates of that record. In this scenario, the oldest record—created on January 20—is retained as the primary CI. The records created on January 21 and January 22 therefore have their Duplicate Of field populated with a reference to the January 20 CI.

This approach preserves the record with the longest history and reduces the risk of breaking references from incidents, changes, relationships, and other dependent records. The Duplicate CI Remediator similarly presents Oldest Created and Most Related Items as significant criteria when determining the Main CI.

The January 20 record itself is not marked as a duplicate of one of the newer records. Consequently, the two later records receive the Duplicate Of reference, making Option A correct.

=========

The correct answer is Pinned Classes . In CI Class Manager, pinning a class is used to keep frequently managed CI classes easily accessible. A CI Class Owner who regularly manages the Windows Server class does not need to search for it repeatedly through the full class hierarchy. By pinning the class, the owner can return to it quickly, improving administrative efficiency and reducing navigation overhead. “CI Favorites” is not the correct CI Class Manager feature in this context, and “Search CI Classes” can locate a class but does not streamline ongoing repeated management in the same way. Search is useful for one-time discovery, while pinned classes are specifically useful for recurring ownership and class administration tasks. Therefore, the feature that best supports this requirement is Pinned Classes.

=========

Duplicate identifies data quality issues where the same asset is modeled more than once, violating CMDB trust principles.

Required ensures minimum viable CI creation and update—critical for ingestion and lifecycle integrity.

Orphan highlights broken relationships, which directly impact impact analysis, Service Mapping, and Change Management.

Stale flags CIs that are no longer being refreshed by Discovery or other sources but still exist in the CMDB.

Recommended improves completeness and usability, supporting operational and reporting use cases without being mandatory.

Audit validates data correctness by comparing CI field values against predefined templates or policies.

This exact mapping is what ServiceNow expects in CMDB Health Dashboard–related exam questions and real-world implementations.