Free ServiceNow CIS-DF Practice Exam with Questions & Answers | Set: 2

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.

A Business Application represents a logical application from a portfolio, ownership, investment, risk, and lifecycle perspective. Following an acquisition, Business Application records allow the combined organization to compare overlapping applications, identify redundant functionality, establish authoritative application ownership, and decide which applications should be retained, consolidated, migrated, replaced, or retired.

An Application Service represents a deployed and operational instance of an application, such as a production or development service. The Application class represents executable software components running on infrastructure, while Incident is a process record and not part of application portfolio modelling.

Business Applications belong to the CSDM Design and Planning domain and support application portfolio management and rationalization. Therefore, they are the appropriate records for unifying and evaluating the applications inherited through the acquisition.

=========

When the Identification and Reconciliation Engine encounters multiple existing records that satisfy the applicable identification criteria, it must select a record for processing while identifying the duplicate condition for later remediation. For this automatic IRE processing behaviour, the record with the most recent update date is selected for the incoming update.

This should not be confused with the Duplicate CI Remediator’s guided selection of a Main CI . During manual remediation, factors such as the oldest creation date, number of related records, historical task references, and business relationships can influence which CI should ultimately be retained. That is a separate governance process from the IRE’s immediate handling of incoming data.

Option A incorrectly selects the newest-created record, while Option C applies a main-record retention principle to the wrong stage of processing. IRE first identifies incoming records using identification rules and then applies reconciliation rules to control authorized updates and source precedence. This governed processing is what prevents uncontrolled insertion and overwriting of CI records.

=========

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

Comprehensive and Detailed Explanation (200–300 words)

Within ServiceNow Data Foundations, CMDB Data Manager provides multiple policy types to support governance, data quality, and lifecycle management of configuration items (CIs). The scenario described—confirming that servers recorded in the CMDB physically exist in the data center—is a classic example of existence validation and ownership confirmation, which is exactly the purpose of an Attestation policy.

An Attestation policy is designed to request a human validation from a responsible individual or group (such as a data center manager, platform owner, or infrastructure team). The policy generates attestation tasks that require reviewers to explicitly confirm whether a CI is valid, accurate, and still exists. This aligns directly with CMDB governance best practices and ITIL 4 Service Configuration Management, where periodic verification ensures trust in the CMDB as a system of record.

The other policy types do not meet this requirement:

Certification is typically used to validate compliance with defined data standards (e.g., mandatory fields populated), not physical existence.

Delete, Archive, and Retire are lifecycle actions, used after a CI has already been identified as obsolete or no longer required.

None of these options involve human confirmation of real-world existence.

From a CSDM and Data Foundations perspective, attestation supports:

CMDB accuracy and credibility

Audit and regulatory compliance (especially critical in financial services)

Clear accountability for CI ownership and validation

Therefore, when the goal is to confirm that servers actually exist, the correct and fully aligned CMDB Data Manager policy type is Attestation (E).

Archive and Retire are the correct CMDB Data Manager end-of-life policy types from the listed options. End-of-life governance in CMDB focuses on handling CI records that are no longer operationally active or no longer required in the active CMDB. A Retire policy is used when CIs should be moved out of active operational status while preserving lifecycle accuracy. An Archive policy is used when records should be removed from active operational use but retained for recovery, audit, or compliance purposes. Disposed and Lost are typically lifecycle status values used in asset or CI lifecycle tracking, not CMDB Data Manager policy types in this context. Decommission describes an operational lifecycle action or state transition, but it is not the Data Manager policy type being tested here. Therefore, the valid end-of-life policy types are Archive and Retire.

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

The CMDB Health Dashboard organizes data quality into practical, action-oriented metrics:

Audits validate correctness by comparing CI values against defined expectations (rules, policies, certifications).

Duplicate CIs represent redundant records and should be reduced to improve trust and reporting accuracy.

Orphan CIs lack required relationships or key context, limiting impact analysis and service visibility.

Recommended fields are not mandatory but add diagnostic value during incidents and problem investigations.

Required fields are enforced by the platform and closely tied to Identification & Reconciliation remediation.

Stale CIs signal aging data that no longer reflects the current environment.

This mapping aligns with CMDB Data Foundations best practices and how the Health Dashboard is designed to guide prioritization and remediation.

Task behaviour for CIs that fail a CMDB Health condition is configured through Health Metrics . The Orphan metric evaluates whether CIs have the required relationships or contextual connections defined for their class. Its metric configuration determines how the condition is evaluated and supports the generation of remediation work for unhealthy records.

The CMDB Health Dashboard displays calculated results and scorecards, but it is primarily a reporting and investigation interface rather than the underlying metric-configuration location. CI Class Manager is used to manage CI classes, attributes, identification rules, and related class-level settings. System Properties control broader platform behaviour and are not the specific location for configuring task handling for the Orphan metric.

Because task creation is tied to the applicable health condition and its remediation behaviour, the administrator configures it through Health Metrics .

=========

Top of Form