Pass4Future also provide interactive practice exam software for preparing ServiceNow Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Exam effectively. You are welcome to explore sample free ServiceNow CIS-DF Exam questions below and also try ServiceNow CIS-DF Exam practice test software.
Do you know that you can access more real ServiceNow CIS-DF exam questions via Premium Access? ()
The CMDB Configuration Manager is using the CI Class Manager to define group ownership of CI classes and needs to leverage the ownership value specified in the CI Class Manager.
When creating a CMDB Data Manager policy, which group reference field should be set?
Answer : B
Comprehensive and Detailed Explanation (200--300 words):
In ServiceNow CMDB governance, the CI Class Manager allows administrators to assign ownership and accountability at the class level. This ownership is used by governance tools---especially CMDB Data Manager---to automatically determine who receives tasks and actions related to data lifecycle management.
The group reference field that aligns with class ownership and is consumed by CMDB Data Manager policies is the Managed By Group. This field represents the team responsible for the technical stewardship and lifecycle management of CIs within that class.
When CMDB Data Manager executes policies such as retention, archival, or cleanup, it uses the Managed By Group to assign tasks to the appropriate data owners. This ensures governance actions are routed to the correct accountable team without manual intervention.
Approval Group, Support Group, and Change Group serve different purposes. Approval Group is used for workflow approvals, Support Group is used for operational ticket routing, and Change Group supports Change Management governance. None of these reflect data ownership at the class level.
Therefore, to leverage CI class ownership defined in the CI Class Manager within CMDB Data Manager policies, the correct field is Managed By Group, making Option B the verified answer.
The CMDB Administrator group aims to display meaningful results on the CMDB Health Dashboard -- Compliance Scorecard for server records that are not on the latest patch.
What must be configured to achieve this goal?
Answer : D
Comprehensive and Detailed Explanation (200--300 words):
In ServiceNow, the Compliance dimension of the CMDB Health Dashboard is driven by Data Certification. To surface meaningful compliance results---such as identifying servers that are not on the latest patch---the platform requires a combination of Certification Policies, Data Filters, and Scheduled Jobs.
Certification Policies define what data must be validated and which attributes are subject to compliance checks (for example, patch level, OS version, or last update date). Data Filters scope the population---such as server classes only---ensuring the compliance evaluation targets the correct CIs. Scheduled Jobs automate when certifications run, keeping compliance scores current and reflective of the latest state.
Options A and C are incorrect because audits and stale/orphan/duplicate checks relate to other health dimensions (correctness and completeness), not compliance. Option B focuses on service modeling and group alignment, which does not directly drive compliance scoring for patch currency.
Therefore, configuring Certification Policies, Data Filters, and Scheduled Jobs is required to accurately measure and display patch compliance on the CMDB Health Dashboard.
A CMDB Administrator is using the Duplicate CI Remediator to address a de-duplication task. On the first tab of the wizard, the Main CI is selected.
Which attributes are used to identify the Main CI? (Choose two)
Answer : A, B
Comprehensive and Detailed Explanation (200--300 words):
In ServiceNow, the Duplicate CI Remediator is a governed tool designed to safely resolve duplicate Configuration Items while preserving the most valuable and authoritative record. The first step in the remediation wizard is identifying the Main CI, which will be retained after remediation.
ServiceNow uses two primary attributes to help determine the best candidate for the Main CI:
Oldest Created (Option A)
The oldest CI is often preferred because it typically has a longer operational history, may be referenced by historical incidents, changes, problems, or audits, and is more likely to be embedded in downstream processes and reports. Retaining the oldest CI helps avoid breaking historical references.
Most Related Items (Option B)
A CI with the most relationships (for example, links to applications, services, incidents, or other CIs) is generally the most valuable from a business and operational context perspective. Preserving these relationships is critical for impact analysis, Change Management, and CSDM-aligned service modeling.
Options C (Newest Created) and D (Least Related Items) are not used as selection criteria because newer or weakly-related CIs typically contain less historical and relational value and are better candidates for removal or merging.
By prioritizing Oldest Created and Most Related Items, the Duplicate CI Remediator aligns with CMDB Data Foundations best practices, ensuring minimal data loss, preserved business context, and safer de-duplication outcomes.
Therefore, the correct answers are A and B.
A Configuration Manager has configured multiple data sources that are all authorized to update the same class and the same set of class attributes in the CMDB.
What can the Configuration Manager do to control which data source should be the authoritative source of truth for a specific class or set of class attributes?
Answer : A
Comprehensive and Detailed Explanation (200--300 words):
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.
A CMDB Administrator has installed a Service Graph Connector and customized a script transform.
What will happen on subsequent upgrades if the default definition of the script transform is updated?
Answer : B
Comprehensive and Detailed Explanation (200--300 words):
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.
