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.

Managing CMDB data volume is a keyData Foundations governanceobjective. Over time, CMDBs naturally accumulate retired, obsolete, or decommissioned CIs. If these records are not properly managed, they degrade CMDB performance, reduce reporting accuracy, and negatively impact discovery reconciliation and health scores.
Archive Policiesare the mechanism designed to address this challenge. They definewhen CI records should be archived or deletedbased on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that onlyrelevant, active CIsremain in the operational CMDB, keeping data volume manageable and performant.
Business Rules (Option A) are used to enforce logic during record creation or updates, not for long-term data volume control. Scheduled Jobs (Option B) may execute tasks, but without archive policies they have no governance logic to determinewhatshould be removed or retained.
Archive policies work in conjunction withCMDB Data Managerto enforce lifecycle-based retention and cleanup, making them the correct and verified answer.
Therefore,Option C - Archive Policiesis correct.

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.

When usingImport Sets and Transform Mapsto ingest data into the CMDB, it is critical that records are processed through theIdentification and Reconciliation Engine (IRE)to prevent duplicates and enforce source precedence. InServiceNow, this is achieved by invoking the IREafterthe transform logic has completed.
TheonAftertransform 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.
TheonBeforeandonStartscripts execute too early-before data mapping is complete-making them unsuitable for IRE processing. TheonCompletescript 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 anonAfter scriptis a critical Data Foundations safeguard when this ingestion method is chosen.
Therefore, the correct answer isC - onAfter.

This question tests understanding of how theIdentification and Reconciliation Engine (IRE)evaluates incoming CI data againstIdentification Rulesand theirpriority orderinServiceNow.
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 beidentified and matched, the incoming record must satisfyone complete identifier entryexactly as defined for that class.
CI1 (Name match only)
Although thenamematches an existing Hardware CI,name aloneis alow-priority identifier (300)and isnot sufficientto uniquely identify a Hardware CI unless no higher-priority identifiers existandthe identifier entry criteria are fully satisfied. In practice, Hardware identification relies onserial number-based identifiers, not name-only matching, to avoid false positives. Therefore, CI1cannot be confidently matchedand is inserted as anew record.
CI2 (IP address match)
IP address is not part of any Hardware identification ruleshown. IP address is typically used for discovery correlation or network relationships, not as a primary Hardware identifier. Since no identifier entry includes IP address, CI2does not match any valid identification ruleand is also inserted as anew record.
Becauseneither CI satisfies a valid identifier entry,both records are inserted as new CIs.