CIS-DF Exam Dumps - ServiceNow CIS-Data Foundations (CMDB and CSDM) Questions and Answers

In CSDM, Technology Services (and their Service Offerings) represent how technical capabilities are delivered and consumed by internal teams. When a server team requests a catalog item for infrastructure services (e.g., VM provisioning, storage, OS builds), the role responsible for initiating the request and defining requirements is the Technology 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 Owners focus on how applications are delivered and supported, not on defining infrastructure catalog items. Enterprise Architects provide standards and guidance but do not initiate or define catalog request requirements.

Thus, the correct role is B – Technology Service Owners.

CI Analyst → Manages assigned CI tables, keeps records updated, and resolves tasks related to CMDB records

Service or Product Owner → Accountable for managing all elements that make up a portfolio throughout their entire lifecycle

Configuration Manager / CMDB Admin → Obtains the highest-level role for CMDB privileges

CMDB Process Owner → Has read-only access to CMDB data and to basic user interfaces such as CMDB reports and dashboards

The correct answer is Technology Management Service Offering, also called a Technical Service Offering. In CSDM-aligned configuration, Technical Service Offerings can be related to Dynamic CI Groups so that operational ownership values are synchronized to the member CIs. This includes the Support Group, which is used by ITSM processes for routing incidents, problems, and operational work. A Dynamic CI Group alone defines CI membership, but it does not provide the service-offering ownership context by itself. A Technology Management Service represents the broader technical service, while the offering is the consumable operational layer that carries support and management group information. CI Class Manager is used for class and schema configuration, not for automatically maintaining CI support groups. Therefore, the correct mechanism is the Technology Management Service Offering.

=========

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.

=========

In ServiceNow, Service Graph Connectors deliver data ingestion patterns using protected, upgrade-safe artifacts, including script transforms. When a customer customizes a script transform provided by a Service Graph Connector, ServiceNow follows standard update set and upgrade behavior to protect customer customizations.

During a subsequent upgrade, if the out-of-box (default) script transform definition changes, ServiceNow does not overwrite the customized version. Instead, the platform records a skipped 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 is B – A skipped change is created and no change is made to the script transform definition.

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.

Health Inclusion Rules determine which CI records are included in CMDB Health calculations. Health Inclusion Rules The Configuration Manager can configure conditions for the relevant CI classes so that only managed, operationally relevant, or management-ready CIs contribute to the Completeness KPI.

For example, an inclusion rule can limit the calculation based on lifecycle stage, operational status, environment, discovery source, or another class attribute that identifies managed CIs. This prevents unmanaged, retired, transitional, or incomplete populations that are not yet under governance from distorting the organization’s health score.

A custom business rule is unnecessary and would introduce avoidable customization and maintenance effort. The score also does not have to include the entire CMDB because each health metric can have a separately controlled evaluation scope. Therefore, configuring Health Inclusion Rules i

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

=========

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.

=========