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

Application Service Mapping is a critical capability inServiceNowfor enablingbusiness-aware Change Management. Its primary value is not in identifying physical shutdown sequences or CI locations, but in translating technical changes intobusiness 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 toApplication Services and Business Servicesas defined by the Common Service Data Model (CSDM). This relationship allows Change Managers to seewhich business services, customers, and processes are impactedby 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 isB – To understand the business impact of CIs, which aligns directly with ITIL 4, CSDM, and Change Management best practices.

Service Graph Connectorsare a keyData Foundations ingestion capabilityinServiceNow. They provideout-of-the-box, upgrade-safe integrationsthat ingest data into the CMDB using theIdentification 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 ondata ingestion, not process orchestration.

Therefore, the correct connector categories areCloudandObservability, makingOptions A and Bthe correct answers.

In CSDM,Technology Services(and their Service Offerings) representhow technical capabilities are delivered and consumedby internal teams. When a server team requests a catalog item for infrastructure services (e.g., VM provisioning, storage, OS builds), the role responsible forinitiating the request and defining requirementsis theTechnology Service Owner.

Technology Service Owners understand the operational capabilities, constraints, SLAs, and fulfillment workflows required to deliver infrastructure services. They define catalog requirements such as options, approvals, fulfillment tasks, and guardrails—ensuring the request aligns with standardization, security, and operational readiness.

Application Service Ownersfocus on how applications are delivered and supported, not on defining infrastructure catalog items.Enterprise Architectsprovide standards and guidance but do not initiate or define catalog request requirements.

Thus, the correct role isB – Technology Service Owners.

InServiceNow, theDuplicate CI Remediatoris designed to resolve duplicate records while preserving themost authoritative datafrom each source. Data Foundations guidance clearly states thatautomated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often containvaluable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-datetechnical data, making it the correct CI to retain as the primary record. However, the manually imported CI has acritical 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 supportsselective 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 Cis the correct and Data Foundations–aligned answer.

TheCommon Service Data Model (CSDM)organizes CMDB data into domains that reflect how services areplanned, 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 describehow the business operatesand 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 representwhat applications existandwho owns them. They anchor ownership, lifecycle, and governance but are not directly operational.

Service Delivery domain → Application Service

Application Services representrunning, 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 representwhat 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 withCSDM v5 guidanceand ensures clear separation betweenplanning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMDB.

InServiceNow, Service Graph Connectors deliver data ingestion patterns usingprotected, upgrade-safe artifacts, including script transforms. When a customercustomizesa script transform provided by a Service Graph Connector, ServiceNow follows standardupdate set and upgrade behaviorto protect customer customizations.

During a subsequent upgrade, if theout-of-box (default) script transform definition changes, ServiceNowdoes not overwrite the customized version. Instead, the platform records askipped change, indicating that an update was available but intentionally not applied due to a local customization. This ensures customer-specific logic is preserved while still maintaining transparency about what changed in the newer release.

Option A is incorrect because upgrades do not halt due to customized transforms. Option C is also incorrect because Service Graph Connector upgrades proceed normally; they do not refuse to start because of customizations.

This behavior aligns with Data Foundations best practices:avoid modifying OOTB content when possible, but when customization is necessary, ensure it is protected during upgrades. Administrators should review skipped changes after upgrades to decide whether to manually adopt new OOTB logic.

Therefore, the correct answer isB – A skipped change is created and no change is made to the script transform definition.

InServiceNow, protecting CMDB data quality during ingestion is a coreData Foundationsprinciple. TheIdentification and Reconciliation Engine (IRE)is designed to ensure that CI records areuniquely identified,merged correctly, andprotected from unauthorized overwrites. Any ingestion method that bypasses IRE introduces a high risk of duplicates and data corruption.

IntegrationHub ETLis the recommended method because it isnatively designed to work with the Identification and Reconciliation API. When properly configured, IntegrationHub ETL ensures that incoming data is processed through IRE, applying identification rules, reconciliation rules, and source precedence. This allows multiple data sources to coexist safely while maintaining CMDB integrity.

Option B (Table API) is explicitly discouraged for CMDB ingestion because it writes directly to CMDB tables andbypasses IRE entirely, making it one of the most common causes of duplicate and conflicting CI records. While REST and SOAP APIs are powerful, they are not safe for CMDB ingestion unless they explicitly invoke the IRE API, which most generic table integrations do not.

Option C (Import Sets and Transform Maps) can be configured to call IRE, but this requiresadditional scripting and strict governance. Because of this complexity and higher risk of misconfiguration, it is not the recommended approach when safer, purpose-built options exist.

Therefore,IntegrationHub ETLis the verified and best-practice answer, makingOption Acorrect.

TheRuntab in theCSDM Data Foundations Dashboardfocuses on enablingoperationalized, risk-aware use cases, includingIntegrated Risk Management (IRM)andEntity Scoping. These use cases require organizations to understandwhat data is processed,where it resides, andwhich technical components are involved, rather than only service impact for ITSM.

Information Objectsplay a central role at this stage.

Option Ais correct becauseBusiness Applications related to Information Objectsallow organizations to identifywhat types of data (PII, PCI, PHI, regulated data)are processed by each business application. This relationship is essential forrisk classification, regulatory compliance, and audit scopingin IRM. Without it, risk assessments lack data sensitivity context.

Option Dis also correct becauseLogical CIs (such as databases, schemas, or data stores) related to Information Objectsestablishwhere sensitive data is stored or processedat a technical level. This enables IRM to trace risk from business context down to technical exposure, supporting control testing, issue management, and remediation prioritization.

Option B (Location hierarchy) supports foundational data quality but does not directly enable risk or entity scoping. Option C (Business Applications to Application Services) is critical forservice impact and Change/Incident Management, but it is more aligned toservice operationsrather thanrisk and data-centric scoping, which is the focus of the Run playbooks for IRM.

Therefore, the correct answers areA and D, as they directly supportIRM entity scoping, regulatory analysis, and risk visibilitythrough CSDM-aligned data modeling.

InServiceNow,CMDB 360 / Multisource CMDBextends the Identification and Reconciliation Engine (IRE) to supportmulti-source visibility, reconciliation, and confidence scoring. Configuration is controlled throughsystem properties, each enabling a specific capability.

glide.identification_engine.multisource_enabledis the master switch that activates CMDB 360 functionality.

glide.identification_engine.multisource_cmdb_ci_enabledallows CMDB 360 to collect and evaluate data specifically fromCMDB CI classes.

glide.cmdb.logger.source.cmdb_multisourceenables detailed logging for troubleshooting multisource ingestion and reconciliation.

glide.identification_engine.multisource_recompute.max_ci_limitprotects performance by limiting how many CIs can be processed during a recompute operation.

Capturing CMDB 360 data fromnon-CMDB classesisnot supported, which is why no property applies to that option.

This mapping aligns withData Foundations and CMDB governance best practices, ensuring CMDB 360 is enabled safely, transparently, and at scale.

Automatic relationship creation is fundamental to maintaining aservice-aware and trustworthy CMDB. InServiceNow, this capability is primarily delivered byDiscoveryandService Mapping.

Discovery(Option C) automatically identifies infrastructure components—such as servers, network devices, and storage—and createstechnical relationshipsbetween them (for example, “runs on,” “connected to,” or “depends on”). These relationships form the backbone of infrastructure dependency mapping.

Service Mapping(Option B) builds on Discovery by creatingapplication- and service-level relationships. It maps how application components interact across servers, databases, and middleware, resulting in accurateApplication Servicemodels aligned with CSDM. These relationships are created and maintained automatically as the environment changes.

Option A (IntegrationHub ETL) focuses on data ingestion and transformation; it does not inherently create or maintain relationships unless explicitly scripted. Option D (Workflow Studio) orchestrates processes and automations but does not discover or infer CI relationships.

Therefore, the ServiceNow solutions that create automatic relationships areService MappingandDiscovery, makingOptions B and Ccorrect.