Pass the ServiceNow CIS-Data Foundations (CMDB and CSDM) CIS-DF Questions and answers with ExamsMirror

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.

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.

The CMDB Health Dashboard is a central component of CMDB Data Foundations insight and governance. It measures and tracks data quality using well-defined health indicators that focus on the accuracy, relevance, and usability of CI data.

Two key data quality areas included in the dashboard are Stale CIs and Duplicate CIs.

Stale CIs (Option D) refer to configuration items that have not been updated within a defined time window. These records are risky because they may no longer reflect the current state of the environment, leading to inaccurate impact analysis, poor change decisions, and misrouted incidents. Monitoring staleness helps organizations identify where discovery, integrations, or ownership processes are failing.

Duplicate CIs (Option E) occur when the same real-world asset or service is represented by multiple records. Duplicates undermine trust in the CMDB, distort reporting, and break service mappings. The CMDB Health Dashboard highlights duplicate trends and integrates with de-duplication and remediation workflows to address them.

Options A (Downgraded CIs), B (Upgraded CIs), and C (Missing CIs) are not standard CMDB Health Dashboard quality dimensions. While “missing” data may be inferred through completeness checks, Missing CIs as a category is not directly tracked.

Therefore, the correct answers are D – Stale CIs and E – Duplicate CIs, which are core CMDB Health indicators used to maintain high-quality configuration data.

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 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.

In CSDM 5, production line monitoring systems (such as SCADA, MES, IoT telemetry platforms, and operational monitoring tools) are technical systems responsible for operating, monitoring, and supporting services, not for designing them or consuming them. These systems directly align with the Service Delivery (Manage Technical) domain.

The Service Delivery domain is used to model how services are technically delivered and operated, including the infrastructure, platforms, and operational technologies that ensure availability, performance, and reliability. In a manufacturing context, production line monitoring systems continuously observe equipment health, throughput, alerts, and operational metrics—making them part of the technical service delivery layer.

Option A (Build and Integration) applies to CI/CD pipelines and system construction activities. Option B (Foundation) focuses on base CIs such as locations, people, and organizations. Option C (Service Consumption) models how customers or consumers use services, which is not applicable here. Option D (Design and Planning) is used for service architecture and planning artifacts, not live operational systems.

Therefore, production line monitoring systems correctly belong in Service Delivery (Manage Technical), making Option E the correct answer.

CMDB 360 / Multisource CMDB extends the standard IRE by enabling Dynamic Reconciliation Rules, which determine attribute values dynamically based on incoming data patterns rather than fixed source priority.

Within the Create Reconciliation Rule wizard, two supported dynamic rule types are:

Most Reported (Option B): selects the attribute value that is reported most frequently across all sources. This is useful when multiple sources contribute data and consensus is a strong indicator of correctness.

Last Updated (Option C): selects the most recently updated value, which is useful for rapidly changing attributes such as IP address or operational state.

Option A (Smallest Value) and Option D (Last Created) are not supported dynamic reconciliation rule types in ServiceNow.

Dynamic reconciliation rules are particularly valuable in complex, multisource environments where rigid source precedence is insufficient and data confidence must be inferred.

Therefore, the correct answers are B – Most Reported and C – Last Updated.

A CMDB delivers business value when it enables better outcomes across IT and enterprise service delivery—especially when aligned with CSDM so services, offerings, and supporting technology are connected in a consumable model. Two major business values are improved operational execution and improved business continuity.

Option C is a direct business value: a trusted CMDB improves incident and change management by providing accurate CI details, relationships, and service context. This supports faster triage and assignment, better prioritization, and higher-quality impact analysis for changes. When incidents and changes are informed by dependable configuration data, organizations reduce downtime, avoid unnecessary escalations, and make safer change decisions—benefits that the business experiences as higher service quality and fewer disruptions.

Option D is also a core business value: CMDB strengthens operational resiliency by enabling clearer dependency understanding and faster response to failures. Resiliency improves when teams can quickly identify what’s impacted, understand upstream/downstream relationships, and plan mitigation steps using known service-to-technology mappings. In regulated or mission-critical environments, this translates into better continuity, reduced risk exposure, and improved compliance reporting.

Option A can be beneficial, but it is more of a technical/operational mechanism than a primary “business value” statement in Data Foundations framing. Option B is primarily the domain of IT Asset Management and financial systems; while CMDB can relate to assets, it is not the system of record for financial management. Hence, the best two business values are streamlining incident and change management and strengthening operational resiliency.

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.

Within the Common Service Data Model (CSDM), service types are clearly defined to separate business-facing value, application logic, and technical enablement. Correct classification is foundational to impact analysis, ownership, reporting, and service visibility.

An Application Service is a logical representation of a deployed application or system stack. It models how an application runs, including servers, databases, middleware, and integrations. Application Services are typically created and maintained through Service Mapping and are primarily consumed by IT operations, DevOps, and support teams.

A Technology Management Service (also called a Technical Service) represents shared technical capabilities such as databases, authentication platforms, messaging systems, or cloud infrastructure. These services are published to Service Owners, not business users, and underpin one or more Application Services or Business Services. They are critical for understanding technical dependencies and risk but are not business-facing.

A Business Service is published to Business Users and directly supports business capabilities and outcomes. It represents what the business consumes , such as “Online Banking,” “Order Fulfillment,” or “Employee Onboarding.” Business Services sit at the top of the CSDM hierarchy and are the anchor point for SLAs, experience, and value measurement.

Correctly distinguishing these service types ensures alignment with CSDM best practices, enables accurate impact analysis, and prevents common CMDB anti-patterns such as exposing technical services to business users or misrepresenting application stacks as business value.