ServiceNow Updated CIS-DF Exam Questions and Answers by sunny

The Run tab in the CSDM Data Foundations Dashboard focuses on enabling operationalized, risk-aware use cases, including Integrated Risk Management (IRM) and Entity Scoping. These use cases require organizations to understand what data is processed, where it resides, and which technical components are involved, rather than only service impact for ITSM.

Information Objects play a central role at this stage.

Option A is correct because Business Applications related to Information Objects allow organizations to identify what types of data (PII, PCI, PHI, regulated data) are processed by each business application. This relationship is essential for risk classification, regulatory compliance, and audit scoping in IRM. Without it, risk assessments lack data sensitivity context.

Option D is also correct because Logical CIs (such as databases, schemas, or data stores) related to Information Objects establish where sensitive data is stored or processed at 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 for service impact and Change/Incident Management, but it is more aligned to service operations rather than risk and data-centric scoping, which is the focus of the Run playbooks for IRM.

Therefore, the correct answers are A and D, as they directly support IRM entity scoping, regulatory analysis, and risk visibility through CSDM-aligned data modeling.

In a mature Configuration Management implementation within ServiceNow, CI operational attributes are leveraged to automate Change Management workflows and reduce manual effort.

When a CI is selected on a Change record, ServiceNow evaluates the CI’s Change Group attribute. If this field is populated on the CI, the platform automatically copies its value into the Change Group field on the Change form. This ensures that change ownership and governance are immediately aligned with the responsible technical team.

The Change Group is distinct from the Assignment Group, which is used primarily in Incident and Task routing. Managed by Group represents lifecycle ownership and is used by CMDB governance tools, while Approval Group controls approval workflows but is not auto-populated from CI selection.

This behavior demonstrates the value of accurate CI attributes: once populated consistently, they enable automatic field population, reduced manual errors, and faster processing across ITSM workflows.

Therefore, the correct answer is A – Change Group.

When using Import Sets and Transform Maps to ingest data into the CMDB, it is critical that records are processed through the Identification and Reconciliation Engine (IRE) to prevent duplicates and enforce source precedence. In ServiceNow, this is achieved by invoking the IRE after the transform logic has completed.

The onAfter transform script is the correct place to call the IRE API. At this stage, the transformed data has already been mapped and prepared, allowing the IRE to correctly identify whether a CI already exists and reconcile updates according to defined rules.

The onBefore and onStart scripts execute too early—before data mapping is complete—making them unsuitable for IRE processing. The onComplete script runs after the entire import job finishes and is not intended for per-record CI identification and reconciliation.

Because Import Sets can bypass IRE if not configured correctly, using an onAfter script is a critical Data Foundations safeguard when this ingestion method is chosen.

Therefore, the correct answer is C – onAfter.

In the CMDB class hierarchy, Server is a generic parent class, while Linux Server and Windows Server are more specific child classes. When ServiceNow Discovery detects sufficient evidence (such as OS signatures) to move a CI from a generic class to a more specialized one, this action is called a Class Upgrade.

A Class Upgrade occurs when a CI is reclassified down the hierarchy into a more specific subclass, enriching the record with additional attributes, behaviors, and discovery patterns appropriate to that class. This is a standard and expected behavior in mature CMDB implementations and aligns with Data Foundations best practices.

A Class Switch would imply lateral movement between unrelated classes, which is not what happens here. A Class Downgrade would move a CI from a specific class back to a more generic one, typically when discovery confidence is reduced—not the case in this scenario.

By performing class upgrades automatically, Discovery improves CMDB accuracy, reporting precision, and service mapping quality without manual intervention.

Therefore, the correct answer is C – Class Upgrade.