Free Practice Questions for the ServiceNow CIS-Data Foundations (CMDB and CSDM) CIS-DF Exam (2026 Updated)

The fastest and most supportable time-to-value option is the SCCM Service Graph Connector . Service Graph Connectors are purpose-built integrations for bringing third-party source data into the CMDB using ServiceNow-supported mappings, Identification and Reconciliation Engine processing, source tracking, and standardized class alignment. For SCCM specifically, the SCCM Service Graph Connector avoids the technical debt of building custom JDBC imports, transform maps, and scripts. Import sets and transform maps can work, but they require more implementation effort and create higher risk if IRE is not correctly invoked. IntegrationHub ETL with RTE is a stronger pattern than raw imports, but for SCCM the dedicated Service Graph Connector is still the fastest and most governed solution. SCCM Usage Metering Spoke is not the CMDB ingestion tool for Windows computer CI data. Therefore, D is correct.

Custom CMDB class tables should begin with u_cmdb_ci . The u_ portion identifies a customer-created table, while cmdb_ci preserves the standard CMDB naming convention and clearly indicates that the table extends the Configuration Item hierarchy.

For example, appropriate custom class names may resemble u_cmdb_ci_custom_router or u_cmdb_ci_special_switch. The uploaded guide uses these exact naming patterns when discussing custom-class consolidation and the technical debt created by unnecessary custom classes.

Using only cmdb_ci would incorrectly suggest an out-of-box ServiceNow table. Prefixes such as u_ci_cmdb and ci_cmdb do not follow the standard hierarchy convention. Before creating any custom class, the administrator should still verify that a suitable supported class is not already available through the CMDB CI Class Models application.

=========

CMDB Data Manager provides policy-driven lifecycle governance for configuration items. The organization should configure Life Cycle Stage automation in Data Manager so that a qualifying lifecycle change on a parent CI is propagated consistently to the relevant child CIs.

This approach creates a controlled and auditable lifecycle process. It avoids relying on custom scripts or disconnected import logic and ensures that lifecycle transitions are applied according to defined conditions and CI relationships.

A Transform Map is intended to transform and import source data. It is not the appropriate mechanism for continuously cascading lifecycle changes between related CIs. Creating a new CI class would also be incorrect because lifecycle management is a behaviour applied to existing CI classes rather than a separate CI type.

CMDB Data Manager is specifically designed to automate CI lifecycle activities such as retirement, archival, deletion, certification, and attestation. Therefore, Data Manager lifecycle automation is the governed solution.

CMDB Query Builder provides purpose-built Export Query and Import Query functions for transferring saved query definitions between ServiceNow instances. The administrator selects the saved query, exports its definition as an XML file, and the receiving team imports that file using the Import Query function. The imported definition then appears in the destination instance’s Saved Queries tab.

Exporting the query as a report would transfer report configuration rather than the complete Query Builder canvas and relationship definition. A generic record-level XML export is not the prescribed Query Builder workflow.

ServiceNow also documents transfer through an update set, but identifies that process as an alternative maintained for backward compatibility. Because the question asks for the direct and recommended Query Builder approach, Option A is the best answer.

Within the CMDB class dictionary in ServiceNow, attributes can be inherited from parent classes or defined directly on a specific class. To identify attributes created specifically for the Windows Server class, administrators must use the Added tab.

The Added tab displays attributes that are unique to the selected class and not inherited from parent classes (such as Server or Computer). This is essential for understanding class-specific extensions—like Windows-only configuration details—that were introduced to support platform requirements, discovery enhancements, or organizational needs.

The All tab shows every attribute available to the class, including inherited and added attributes, which makes it difficult to isolate class-specific additions. The Child tab focuses on attributes inherited by subclasses, not attributes introduced at the current class level. The Derived tab shows attributes calculated or derived from other data, not necessarily those created specifically for the class.

Using the Added tab supports best practices for configuration transparency, impact analysis during upgrades, and governance—especially important in Data Foundations to minimize unnecessary customization and maintain upgrade-safe designs.

Therefore, the correct answer is B – Added.

The CMDB Data Manager capability in ServiceNow is designed to support CMDB governance, specifically around data lifecycle management. Its primary purpose is to ensure that CI records are retained, archived, and deleted in accordance with defined retention policies, regulatory requirements, and organizational data governance standards.

As CMDBs mature, they naturally accumulate obsolete, retired, or decommissioned CIs. If these records are not properly managed, they negatively impact CMDB health, reporting accuracy, discovery reconciliation, and performance. CMDB Data Manager addresses this by automating the archival and deletion of records once lifecycle conditions and retention thresholds are met.

Option A is incorrect because encryption of archived records is handled by platform-level security and data protection features, not CMDB Data Manager. Option B is also incorrect because relationship rule enforcement is managed through CSDM guidance, CMDB relationship rules, and identification/reconciliation logic—not by CMDB Data Manager.

By automating retention-based archival and cleanup, CMDB Data Manager helps organizations maintain a lean, compliant, and high-quality CMDB, which directly supports CMDB Health metrics such as correctness and compliance.

Therefore, the correct and verified answer is Option C.

The correct answer is Service Graph Connector . Service Graph Connectors are ServiceNow-supported ingestion solutions designed to bring third-party data into the CMDB using governed, repeatable, and upgrade-safer patterns. They are built to align with CMDB class models, Identification and Reconciliation Engine processing, source tracking, and ServiceNow data quality practices. This reduces custom scripting, unsupported mappings, and long-term maintenance burden. A generic vendor-provided integration may work, but it can introduce technical debt if it bypasses IRE, writes directly to CMDB tables, or uses unsupported mappings. Import Sets and Transform Maps can be used, but they require careful scripting and governance to avoid duplicates. Table API is the riskiest option because direct table writes can bypass CMDB identification and reconciliation logic. Therefore, Service Graph Connector is the best method to minimize technical debt.

=========

Agent Client Collector (ACC) → Collects inventory and telemetry from devices using an installed agent, especially where agentless discovery is not practical.

ServiceNow Discovery → Automatically identifies devices and applications on the network and populates the CMDB with accurate, up-to-date information.

Service Graph Connectors → Facilitates integration between ServiceNow and external systems to import and synchronize CMDB data.

Service Mapping → Builds the complete topology of services and shows how they are supported by underlying infrastructure and applications.

Each ingestion product has a specific role in CMDB Data Foundations. ServiceNow Discovery is primarily agentless and discovers infrastructure, applications, and relationships across the network. Agent Client Collector is agent-based and is useful for devices that are intermittently connected, remote, restricted, or difficult to scan through traditional Discovery. Service Graph Connectors are prebuilt, governed integrations used to bring third-party data into the CMDB while aligning with IRE and ServiceNow class models. Service Mapping focuses on service topology by identifying how application services depend on infrastructure and application components. The key distinction is that Discovery and ACC collect technical inventory, Service Graph Connectors integrate external sources, and Service Mapping builds service dependency models.

=========

In ServiceNow, the Duplicate CI Remediator is designed to resolve duplicate records while preserving the most authoritative data from each source. Data Foundations guidance clearly states that automated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often contain valuable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-date technical data, making it the correct CI to retain as the primary record. However, the manually imported CI has a critical relationship to a business application, which is essential for impact analysis, incident prioritization, and CSDM alignment. Deleting this CI without preserving the relationship would result in loss of business context and reduced CMDB value.

The Duplicate CI Remediator supports selective merging, allowing administrators to retain one CI while merging specific attributes or relationships from the duplicate. Option C reflects this best practice by retaining the discovered CI and merging the relationship from the manually imported CI, ensuring both technical accuracy and business relevance are preserved.

Options A and D would result in the loss of important relationship data, while Option B would discard the discovered CI, violating the principle that discovery should be the authoritative source for technical attributes.

Therefore, Option C is the correct and Data Foundations–aligned answer.

Managing CI classes and Principal Class designation is a schema-level CMDB activity that directly impacts how CIs appear in ITSM processes such as Incident, Change, and Problem. In ServiceNow, these activities require specific administrative privileges to ensure governance, security, and upgrade safety.

The sn_cmdb_admin role is required because it provides administrative access to CMDB structures, including CI class hierarchy management, Principal Class configuration, and overall CMDB governance. Without this role, users cannot add, remove, or govern CI classes effectively.

The personalize_dictionary role is also required because adding or removing CI classes involves dictionary-level changes. CI classes are implemented as tables that extend the CMDB schema, and modifying the Principal Class filter relies on dictionary metadata. This role grants permission to create, modify, or remove class definitions safely.

The sn_csdm_admin role focuses on managing CSDM constructs (domains, services, lifecycle alignment) but does not grant dictionary or schema modification rights. The cmdb_query_builder role is used only for querying and reporting and does not allow structural changes.

Therefore, the two required roles are personalize.dictionary and sn_cmdb_admin, making Options A and B correct.

Managing CMDB data volume is a key Data Foundations governance objective. 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 Policies are the mechanism designed to address this challenge. They define when CI records should be archived or deleted based on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that only relevant, active CIs remain 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 determine what should be removed or retained.

Archive policies work in conjunction with CMDB Data Manager to enforce lifecycle-based retention and cleanup, making them the correct and verified answer.

Therefore, Option C – Archive Policies is correct.

Principal Classes are a key CMDB configuration concept used to control which CI classes are selectable in reference fields across ITSM processes. This helps reduce noise, prevent incorrect CI selection, and improve data quality.

In ServiceNow, Principal Classes are designated within the CI Class Manager. This tool allows CMDB administrators to manage the CI class hierarchy, define ownership, and explicitly mark classes as principal. Once a class is marked as principal, its CIs become available in CI reference fields such as those on Incident, Change, and Problem forms.

Option A (CMDB Workspace) provides operational and analytical views but does not control schema-level class behavior. Option C (System Properties) does not manage class designation. Option D (CMDB Data Manager) governs lifecycle and data quality policies, not reference field behavior.

By configuring Principal Classes in the CI Class Manager, organizations ensure that only relevant, high-value CI classes are exposed to end users, aligning with Data Foundations best practices.

Therefore, the correct answer is B – CI Class Manager.

The correct answer is Pinned Classes . In CI Class Manager, pinning a class is used to keep frequently managed CI classes easily accessible. A CI Class Owner who regularly manages the Windows Server class does not need to search for it repeatedly through the full class hierarchy. By pinning the class, the owner can return to it quickly, improving administrative efficiency and reducing navigation overhead. “CI Favorites” is not the correct CI Class Manager feature in this context, and “Search CI Classes” can locate a class but does not streamline ongoing repeated management in the same way. Search is useful for one-time discovery, while pinned classes are specifically useful for recurring ownership and class administration tasks. Therefore, the feature that best supports this requirement is Pinned Classes.

=========

CSDM significantly enhances Change Management by providing service-aware context, enabling better planning, risk assessment, and stakeholder communication.

One key benefit is the ability to identify blackout windows (Option A). Through CSDM-aligned Business Services, Service Offerings, and service calendars, Change Managers can clearly see when services are unavailable for change due to business constraints, regulatory requirements, or peak usage periods. This helps prevent changes from being scheduled during high-risk windows.

Another critical benefit is the ability to understand the impact of the change on services (Option D). CSDM establishes clear relationships between infrastructure CIs, Application Services, and Business Services. When a change is proposed, these relationships enable accurate impact analysis, allowing Change Managers to assess risk based on business criticality rather than just technical scope.

Option B (root cause determination) is primarily a Problem Management function. Option C (dynamic routing of changes) is driven by workflow and approval logic, not directly by CSDM.

Therefore, the correct answers are A – Identify blackout windows and D – Understand the impact of the change on services.

The CMDB Data Foundations Dashboard identifies foundational CMDB data-quality deficiencies, including hardware CIs that lack important identification attributes such as serial numbers. A missing serial number is particularly serious because serial number is commonly included in Hardware identification rules. Without it, Discovery and external integrations may fail to match an incoming device to its existing record, resulting in duplicate CIs.

The dashboard exposes the affected population and provides remediation playbooks that help administrators analyse the responsible data sources, correct existing records, and establish controls to ensure that serial numbers continue to be populated.

CI Class Manager is used to configure class structures and identification rules, but it is not the dashboard used to locate the full population of affected CIs. CMDB Data Manager governs lifecycle policies, while the CSDM dashboard focuses on service-model alignment.

=========

The correct answer is Use the CMDBTransformUtil API in the transform script . Import Sets and Transform Maps can create duplicate CIs if they write directly into CMDB tables without routing the data through the Identification and Reconciliation Engine. The CMDBTransformUtil API is used in transform scripting to process incoming CI data through the CMDB identification and reconciliation logic. This allows ServiceNow to evaluate existing CIs using configured identification rules and then update the correct CI rather than creating a duplicate record. Coalesce rules are not sufficient for CMDB ingestion because they rely on simple field matching and do not apply the full IRE logic. “Comparison rules” is not the correct mechanism. A system property alone is also not the recommended implementation pattern for vendor shipment import data. Therefore, CMDBTransformUtil is the correct method to prevent duplicate CI creation through import sets.

The correct option is Allow fallback to parent’s rules . In CI identification, ServiceNow evaluates the configured identification rule for the target class first. If the Tomcat rule cannot find a match using its class-specific criterion attributes, fallback behavior allows the Identification and Reconciliation Engine to attempt matching against the parent class identification rule. Since Tomcat is a more specific application class, falling back to the parent Application identification rule helps prevent unnecessary duplicate records when a match cannot be made at the subclass level. “Applies to” defines the class or scope for the identifier entry. “Independent” controls whether a rule is evaluated independently rather than through parent inheritance. “Criterion attributes” are the fields used for matching, not the fallback setting. Therefore, the correct configuration is Allow fallback to parent’s rules .

=========

The correct answer is Service Delivery . In CSDM, the Service Delivery domain focuses on how services are technically delivered and operated. It includes the modeling of technical services, technical service offerings, application services, infrastructure CIs, and the relationships that connect them. The scenario specifically asks about Infrastructure CIs, Technology Management Offerings, Technical Service Offerings, and Application Services, which are all part of the technical operating model for delivering services. Foundation is used for base reference data such as locations, groups, companies, and users. Design and Planning focuses on business applications, capabilities, and planning artifacts. Service Consumption focuses on how consumers access and consume services. Build and Integration is associated with development and deployment activities. Because the question is about technical service relationships and operational service delivery, Service Delivery is the correct CSDM domain.

=========

In Data Foundations, “Ingest” is not limited to Discovery. It includes establishing reliable sources and mechanisms to populate and maintain CMDB attributes—especially those that Discovery cannot provide. Warranty expiration dates are a classic example of non-discoverable data: they typically come from procurement systems, asset repositories, vendors, or contract tools rather than from device interrogation.

The correct approach is to maintain these attributes via a scheduled data import from an authoritative external source. This ensures ongoing accuracy and consistency at scale. A scheduled import allows you to define a repeatable integration pattern, apply data quality checks, and keep warranty data current as vendors and procurement records change—without relying on manual updates that inevitably drift over time.

Option A is incorrect because the CMDB Reconciliation Engine resolves conflicts between multiple data sources and applies precedence rules; it does not create the warranty values out of thin air. Reconciliation helps decide which source wins when updates occur, but you still need a source feed providing the warranty attribute values. Option B is also not recommended because creating a new CI class just to hold non-discoverable attributes fragments the model and complicates reporting and processes. Best practice is to keep the attributes on the appropriate hardware CI classes (or related normalized structures, when applicable) and manage them through governed ingestion from authoritative systems. Therefore, C is the best method.

This scenario hinges on how the Identification and Reconciliation Engine (IRE) in ServiceNow evaluates identification rules.

The identification rule for the Apache Web Server class includes Version as part of the identifier criteria, along with Class and Configuration file. Identification rules must match all criterion attributes exactly for an incoming record to be identified as an existing CI and reconciled.

Yesterday’s discovery created an Apache Web Server CI with a specific version value. When Apache is upgraded and discovery is rerun, the Version attribute changes. Because Version is part of the identifier, the incoming record no longer matches the existing CI’s identifier entry. As a result, the IRE cannot identify the existing CI as the same configuration item.

When identification fails and no matching identifier entry is found, the IRE proceeds to insert a new CI record rather than updating the existing one. This behavior is intentional and protects the CMDB from incorrectly reconciling records that no longer meet identification criteria.

Option A is incorrect because reconciliation only occurs after successful identification.

Option C is incorrect because reclassification is unrelated to identification criteria.

Option D is incorrect because this is not an error condition; it is expected IRE behavior.

This example highlights a best practice caution: volatile attributes (such as Version) should generally not be used as identifier attributes, as they can cause unintended CI duplication during upgrades.

CSDM is designed to connect technology delivery to business consumption so organizations can answer questions like “who is impacted?” quickly and consistently. In a critical incident, the healthcare provider needs to identify impacted users in business terms—clinicians, admin teams, specific sites, or departments—rather than only listing technical components.

Option D (“Service Offerings by Department or Location”) is the most CSDM-aligned data because it reflects who consumes the service and how that consumption is segmented. In CSDM, a Business Service / Service Offering represents what customers consume, and the offering can be associated with organizational constructs such as department, business unit, or location. For healthcare, this is especially valuable because impact is often location-based (hospital site, clinic) and role-based (patient intake, scheduling, ward operations). Using service offerings and their consumer mapping helps quickly identify likely impacted user groups and prioritize communications and workarounds.

Option A (environment attribute) helps differentiate production vs non-production and can support prioritization, but it does not identify impacted users. Option B is historical context, not a reliable mechanism to determine current impacted users. Option C is useful operationally for listing impacted configuration items, but it is ITSM task data, not specifically CSDM consumer modeling. CSDM’s value here is linking the technical disruption to the business consumer view via service offerings and consumption segmentation.

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.

Service Mapping creates and maintains an Application Service by discovering the application’s entry point and tracing its dependencies across the supporting infrastructure. The resulting service map can include application components, servers, databases, middleware, load balancers, and communication relationships. This produces the service-aware topology required for impact analysis, incident investigation, and change-risk assessment.

ServiceNow Discovery identifies infrastructure CIs and can create technical relationships between discovered components, but Discovery alone does not normally build the complete, application-centric service topology requested in the question. Agent Client Collector gathers inventory and telemetry from devices through an installed agent, while Event Management processes and correlates operational events and alerts.

The study material identifies Service Mapping as the capability that builds Application Service topology and shows how services are supported by underlying applications and infrastructure. It also describes top-down Service Mapping as the recommended high-fidelity approach for mission-critical Application Services.

=========

Design Domain → Enterprise Architect(s), Data Steward(s), Process Owner(s), Platform Owner

Foundation Domain → Enterprise Architect(s), Platform Owner

Portfolio Domain → Service Owner(s), Platform Owner

Technical Domain → Technology Service Owner(s), Application Service Owner(s), Platform Owner

CSDM governance requires the correct domain owners because each domain represents a different type of data accountability. The Design Domain is architecture-heavy and requires Enterprise Architects, Data Stewards, Process Owners, and the Platform Owner to ensure planning data is accurate and aligned. The Foundation Domain depends on shared platform reference data, so Enterprise Architects and the Platform Owner are key stakeholders. The Portfolio Domain is concerned with service ownership and service portfolio accountability, so Service Owners and the Platform Owner are the primary governance roles. The Technical Domain governs operational service and application service data, so Technology Service Owners, Application Service Owners, and the Platform Owner are needed. This division prevents one team from owning all CSDM data incorrectly and creates clear accountability.

=========

CMDB 360/Multisource CMDB retains information about the values contributed by individual data sources. When reconciliation logic is modified, the administrator can perform a recompute operation so the latest rules are applied to the stored source contributions without waiting for every external system to send the data again.

This enables administrators to test and refine source-precedence or dynamic reconciliation rules and then recalculate the resulting CI attribute values using the available historical source data. The capability is particularly useful when correcting an inappropriate source-priority rule or implementing dynamic rules such as Most Reported or Last Updated.

CMDB 360 does not eliminate identification rules, permanently lock records, or automatically archive records based on quarterly reporting behaviour. Identification remains necessary to match incoming data to the correct CI, while reconciliation determines which authorized source controls an attribute.

=========

In CSDM version 5, enterprise-wide capability tracking is firmly positioned within the Design and Planning domain. This domain is specifically intended to support Enterprise Architecture, Portfolio Management, and Strategic Planning use cases, making it the correct choice for an Enterprise Architect working across the organization.

The Design and Planning (Design) domain focuses on answering “what the business needs and how it should be designed” before services are built or delivered. It includes core concepts such as Business Capabilities, Value Streams, Information Objects, Business Applications, and Architectural relationships. Business capabilities represent what an organization does to achieve its objectives, independent of organizational structure, technology, or implementation. This abstraction is essential for enterprise architects, especially in highly regulated industries like financial services, where strategic alignment and impact analysis are critical.

The other domains do not fit this requirement:

Foundation provides shared reference data (companies, locations, users) but does not model enterprise capabilities.

Build and Integration focuses on application development, CI/CD pipelines, and integration layers.

Service Consumption is concerned with customers, offerings, and how services are consumed.

Service Delivery models the operational and technical delivery of services, including infrastructure and runtime environments.

From a Data Foundations and CSDM governance perspective, tracking enterprise capabilities in the Design and Planning domain ensures:

Clear separation between strategy, design, and operations

Alignment with ITIL 4 strategy and planning practices

Strong support for impact analysis, rationalization, and transformation initiatives

Therefore, Design and Planning (D) is the correct and fully aligned CSDM 5 domain for tracking enterprise capabilities.

The CMDB Data Foundations Dashboard is paired with Get Well Playbooks that guide administrators through structured remediation. The “Services Have Owners Identified” playbook focuses on closing ownership gaps for services, which is a governance and data correction activity.

Fix Data (Option A) is used to correct missing or incorrect values, such as populating owner fields, assigning responsible groups, or updating relationships. In this playbook, Fix Data actions are required to actually remediate the issue by assigning owners to services.

Govern Data (Option D) is also required because ownership is not a one-time correction—it must be enforced and sustained. Govern Data establishes policies, ownership accountability, and controls (such as certifications or attestations) to ensure services continue to have owners over time and do not regress.

Analyze Data (Option B) is used to understand patterns and root causes, but it does not remediate the issue. Report Data (Option C) provides visibility and communication, not corrective action.

Therefore, the remediation plays that apply to the Services Have Owners Identified playbook are Fix Data and Govern Data, making Options A and D correct.

The Common Service Data Model (CSDM) organizes CMDB data into domains that reflect how services are planned, delivered, and consumed. Correct placement of objects is essential for reporting, ownership, and downstream ITSM, ITOM, and IRM use cases.

Design and Planning domain → Business Process

Business Processes describe how the business operates and what capabilities are required. These are planning constructs used to design services and applications before they are built or delivered.

Foundation domain → Business Application

Business Applications are foundational reference objects that represent what applications exist and who owns them . They anchor ownership, lifecycle, and governance but are not directly operational.

Service Delivery domain → Application Service

Application Services represent running, operational technical services (often created via Service Mapping). They are central to Incident, Change, and Event Management, making them part of Service Delivery.

Sell / Consume domain → Business Service

Business Services represent what is offered to customers or consumers . They define value delivery, SLAs, and consumption context, which is why they belong in the Sell/Consume domain.

This mapping aligns with CSDM v5 guidance and ensures clear separation between planning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMDB.

In CSDM 5, production line monitoring systems (such as SCADA, MES, IoT telemetry platforms, and operational monitoring tools) are technical systems responsible for operating, monitoring, and supporting services, not for designing them or consuming them. These systems directly align with the Service Delivery (Manage Technical) domain.

The Service Delivery domain is used to model how services are technically delivered and operated, including the infrastructure, platforms, and operational technologies that ensure availability, performance, and reliability. In a manufacturing context, production line monitoring systems continuously observe equipment health, throughput, alerts, and operational metrics—making them part of the technical service delivery layer.

Option A (Build and Integration) applies to CI/CD pipelines and system construction activities. Option B (Foundation) focuses on base CIs such as locations, people, and organizations. Option C (Service Consumption) models how customers or consumers use services, which is not applicable here. Option D (Design and Planning) is used for service architecture and planning artifacts, not live operational systems.

Therefore, production line monitoring systems correctly belong in Service Delivery (Manage Technical), making Option E the correct answer.

A Technology Management Service Offering associated with the applicable Dynamic CI Group synchronizes operational group information to its member CIs. The fields designed for this synchronization include Managed by Group and Support Group .

Therefore, Linux Server CIs included in the offering’s CI population receive Enterprise IT Services as their Managed by Group. The CI Class Manager value can provide class-level ownership or governance context, but the service-offering alignment actively maintains the operational group value on the related member CIs.

The conflicting values do not cause Discovery or ingestion to fail. ServiceNow applies the configured group-synchronization mechanism rather than leaving the field empty. Change Management Team is assigned to the Change Group field, not the Managed by Group field, so Option D does not answer the question.

Consequently, the Managed by Group assigned to the discovered Linux Server instances is Enterprise IT Services.

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.

=========

The correct answer is C. Service Graph Connectors are ServiceNow-supported integrations when used as delivered or configured within supported boundaries. When an administrator customizes the mappings, the implementation moves away from the supported out-of-box connector behavior. This creates upgrade and support implications because ServiceNow cannot guarantee that customized mappings will remain compatible with future connector updates. The customer becomes responsible for validating, maintaining, and troubleshooting those customizations. Option A is not the primary consequence because customized fields are not simply protected by a special CMDB tag. Option B is incorrect because custom mapping does not automatically block connector execution pending approval. The key risk is supportability and technical debt, making C the correct answer.

=========

In CMDB governance, different CMDB Data Manager policy types serve different validation and enforcement purposes. When the objective is to allow an assigned individual to review and update specific fields on a CI record, the correct policy type is Certification.

A Certification policy creates actionable tasks that require the assignee to validate and, if necessary, correct specific CI attributes, such as lifecycle status, support group, environment, or ownership. During certification, the user can directly update CI fields to bring the record into compliance with defined standards.

Attestation (Option C) only asks the user to confirm that a CI still exists or is still valid; it does not require or enable attribute-level updates. Audit (Option A) is used for reporting and evidence collection, not remediation. Compliance (Option D) measures adherence to rules but does not itself generate editable remediation tasks.

Certification is therefore the primary mechanism used when human validation and correction of CI data is required—making it a cornerstone of CMDB data quality management.

Hence, the correct answer is B – Certification.

CMDB groups can represent either a deliberately selected set of CIs or a dynamically maintained population. For a static grouping, administrators can manually select the required Windows Server CIs and associate them with the named group.

For a dynamic grouping, an encoded query or equivalent CMDB query condition can identify records based on class and attribute criteria. For example, the query can select active Windows Server CIs in a particular location, environment, or support group. As CI records begin or cease to meet the conditions, group membership can be updated accordingly.

Tag-based mapping is principally associated with cloud-native Application Service mapping rather than the standard mechanism described for CMDB group membership. Reconciliation rules determine which source can update CI attributes; they do not assign CIs to operational groups based on source priority. Dynamic CI groups are designed to maintain membership through defined filtering criteria.

=========

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.

The CMDB and CSDM Data Foundations Dashboards are obtained from the ServiceNow Store as a free application. This is different from the standard CMDB Health Dashboard, which is part of the platform CMDB capability. The Data Foundations Dashboards provide guided visibility into CMDB and CSDM readiness, maturity, and remediation opportunities through metrics and playbooks. They are intended to help organizations improve CMDB quality and CSDM alignment without building custom dashboards from scratch. Option A is incorrect because this specific dashboard application is not simply active by default. Option B is incorrect because it is not a paid Store application. Option C is incorrect because the correct source is the ServiceNow Store, not Innovation Lab. Therefore, the correct answer is D.

=========

In Data Foundations, “Insight” includes measuring CMDB health in ways that are actionable—so teams can identify where data is degrading and prioritize remediation. Stale CIs (records that are no longer current, not updated, or no longer exist in the environment) are a common source of CMDB risk: they distort reporting, mislead impact analysis, and create noise for operational processes. Reducing staleness supports higher trust in the CMDB and better decision-making.

On the CMDB Health Dashboard, stale CI concerns align most closely with Compliance because staleness is fundamentally about whether CIs continue to meet defined governance expectations over time—such as update frequency, lifecycle status controls, and adherence to rules that indicate whether records are still valid. Compliance scorecards typically highlight rule-based adherence to standards (for example, policies or health rules indicating that certain CI types must be recently updated or must not exceed staleness thresholds). This makes Compliance the right place to monitor and improve staleness.

By contrast, Completeness focuses on whether required attributes are populated (for example, owner, environment, support group). Correctness focuses on whether values are accurate and relationships make sense. While stale records can indirectly affect correctness, the dashboard tracking of “stale” is primarily treated as a governance adherence issue—whether the CMDB is being maintained according to lifecycle and freshness expectations—therefore it is surfaced through the Compliance scorecard.

To specifically improve data quality related to CSDM, the most effective and prescribed action is to use the CSDM Data Foundations Dashboard. In ServiceNow, this dashboard is purpose-built to assess and improve CSDM alignment, not just general CMDB hygiene.

The CSDM Data Foundations Dashboard focuses on service modeling readiness, highlighting gaps such as missing service ownership, incomplete relationships between Business Applications and Application Services, unmanaged services, and misaligned lifecycle states. It provides Get Well Playbooks that guide administrators through structured remediation using Analyze Data, Fix Data, and Govern Data plays—directly tied to CSDM outcomes.

Option C (default CMDB Health Dashboard) is valuable, but it measures generic CMDB data quality dimensions (completeness, correctness, compliance) and does not specifically evaluate CSDM constructs or service modeling maturity. Option B (ServiceNow Health Scan) provides platform-wide configuration and performance recommendations, but it is not focused on CMDB or CSDM data quality.

Therefore, to improve CSDM-specific data quality, the administrator should use the CSDM Data Foundations Dashboard, making Option A the correct answer.

CMDB 360, also known as Multisource CMDB, is designed to provide visibility into how multiple discovery or integration sources contribute data to the same CI. Its value is not simply identifying duplicate or orphan CIs; those are handled through CMDB Health and de-duplication capabilities. CMDB 360 helps administrators compare source contributions and understand conflicts or gaps across those sources. A key insight is gaps in attribute data, where one source supplies certain CI attributes while another source does not. Another key insight is different attribute values from different data sources, which helps identify reconciliation problems, source precedence issues, and inconsistent discovery results. This is central to improving data trust because the CMDB often receives data from Discovery, SCCM, cloud connectors, manual imports, and third-party systems. Therefore, the correct insights are gaps in attribute data and different attribute values across sources.

The Unified Map in ServiceNow provides a consolidated view of services and their underlying components, integrating Discovery and Service Mapping data. To make this view actionable, Service Owners can apply filters to focus on relevant elements and reduce visual noise.

Filtering by CI type (Option A) is a core capability. It allows the Service Owner to show or hide categories such as servers, databases, load balancers, or applications—making it easier to analyze specific layers of the service.

Filtering by Business Criticality (Option D) is also available and highly valuable. This enables Service Owners to prioritize views around high-impact components, ensuring attention is focused on CIs that pose the greatest risk to service delivery.

Option B (Discovery source) is not typically exposed as a Unified Map filter because the map focuses on operational and service context, not ingestion provenance. Option C (Managed by group) is a governance attribute and is not a standard visual filter within the Unified Map.

Thus, the correct filter options are A – CI type and D – Business criticality.

The Crawl stage establishes the initial CSDM foundation and design information required to create a usable CMDB. This includes identifying applications, their ownership, associated Application Services, foundational reference data, and essential relationships.

The Application Owner provides authoritative information concerning the Business Application, including ownership, lifecycle, criticality, purpose, and portfolio context. The Application Service Owner provides operational knowledge about the deployed Application Services, their environments, support arrangements, and relationships to underlying CIs.

The guide explains that Crawl addresses the Foundation and Design domains. Foundation establishes organizations, locations, users, groups, products, and core CI information, while Design introduces Business Applications, capabilities, processes, Information Objects, ownership, and architecture context.

Business Service Managers and Technology Service Owners become more central as business-facing and technical services mature during later stages. Customer Service Managers are primarily associated with service consumption. Therefore, B is correct.

=========

The correct answer is 75 because the Windows Server class has its own dynamic reconciliation rule configured as most reported for the Disk Space field. Even though the parent Server class uses the lowest value rule, the more specific class rule on Windows Server takes precedence for Windows Server records. In CMDB 360 / Multisource CMDB, dynamic reconciliation evaluates values from multiple contributing sources and selects the value according to the configured reconciliation strategy. Here, 75 GB is reported by two sources: Thycotic and ServiceNow. The other values, 50 GB and 80 GB, are each reported only once. Because the rule is “most reported,” the value appearing most frequently across sources is selected. Therefore, 75 GB is added to the CMDB.

=========

This question hinges on understanding class-specific Dynamic Reconciliation Rules in CMDB 360 / Multisource CMDB within ServiceNow.

Although two different dynamic rules are configured, the rule applied depends on the CI class being evaluated:

For the Server class, the configured rule is Largest value for the RAM attribute.

For the Windows Server class, the rule Most reported would apply—but only if the CI were evaluated as a Windows Server.

The question explicitly asks for the resulting RAM value for a Server CI, not a Windows Server CI. Therefore, the Largest value rule governs the outcome.

Looking at the multisource values:

2,048 MB (LANDesk)

4,096 MB (Tivoli)

4,096 MB (ServiceNow)

8,192 MB (Altiris)

Under the Largest value dynamic reconciliation rule, the IRE selects the maximum numeric value, regardless of how frequently it is reported or which source provided it.

The Most reported logic (which would result in 4,096 MB) does not apply here because that rule is configured for a different class (Windows Server).

This scenario illustrates an important CMDB 360 principle: Dynamic reconciliation is evaluated per class, and child-class rules do not override parent-class rules unless the CI is actually classified under that child class.

The correct answers are C and D. Identification and reconciliation rules are essential because they control how incoming CI data is matched to existing records and how updates from different sources are reconciled. This prevents duplicate CIs and ensures that authoritative sources update the correct attributes. CI Class Manager is also required because it provides governance over CI class structure, attributes, and inheritance. Standardized CI classes prevent each source from classifying the same real-world object differently. Option A is the cause of the problem, not the solution. Option B introduces avoidable technical debt because custom scripts are harder to govern, maintain, and upgrade. A Data Foundations-aligned solution uses standard class governance plus IRE rules to enforce consistency across all sources.

=========

In Data Foundations, “govern” is not only about defining standards—it also includes implementing repeatable controls that keep CMDB data clean over time. CMDB Data Manager is the ServiceNow capability built specifically for policy-driven CI lifecycle operations such as deletion, archival, and attestation. Rather than relying on one-off scripts or manual cleanup, Data Manager applies consistent lifecycle rules at scale, which is a core expectation of CMDB Data Foundations governance.

The place to administer these lifecycle policies is within CMDB Workspace, under the Management area, where the Data Manager tools expose a dedicated Policies experience. From there, a Data Manager can create new policies, publish them, and manage existing policies used to automate lifecycle processing. This aligns with the intent of “keeping the CMDB healthy and efficient” because it operationalizes governance through automated, standardized actions and controlled approvals where needed.

By contrast, CI Class Manager is primarily for managing CI class definitions and class-level settings (for example, class configuration related to identification, reconciliation, and health rules), not for publishing CI lifecycle automation policies. “CMDB 360” is oriented toward exploring CI/service context, and “Service Operations Workspace” is designed for operational workflows rather than CMDB lifecycle policy administration.

The correct answer is Relationship Map. In CMDB Workspace, the Relationship Map is used to visualize how Configuration Items are connected through CMDB relationships. This is useful when a Configuration Manager needs to understand dependency paths, parent-child relationships, hosted-on relationships, application-to-infrastructure relationships, or other CI-to-CI connections. Unified Map is more service-oriented and is typically used to understand the composition of a service and related operational context. Business Service Map is focused on service-level visualization rather than general CI relationship inspection. Since the question asks specifically how CIs are connected to each other, the most precise tool is the Relationship Map.

The Unified Map is designed to provide enhanced visual insight and analysis across the CMDB by consolidating configuration item (CI) relationships from multiple sources—such as Discovery, Service Mapping, and manual relationships—into a single, interactive view. While traditional Service Mapping maps are optimized for modeling and understanding application-to-infrastructure dependencies, the Unified Map extends this capability with more flexible visualization and exploration features.

Option B is correct because the Unified Map allows users to zoom in and out, enabling both high-level overviews and detailed inspections of complex CI relationships. This capability is particularly valuable in large enterprise environments where services may span hundreds or thousands of infrastructure components. Zoom functionality supports impact analysis, troubleshooting, and architectural reviews without overwhelming the user with unnecessary detail.

Option C is also correct because the Unified Map supports filtering of map nodes based on user preferences. Administrators and analysts can filter by CI class, relationship type, lifecycle state, or other attributes, allowing them to focus on what is most relevant to their task—such as identifying only production CIs, security-relevant components, or a specific technology stack. This aligns strongly with Data Foundations principles by improving usability and decision-making without altering underlying data.

Option A is incorrect because modifying the number of levels displayed is a characteristic more closely associated with Service Mapping configuration rather than an added Unified Map capability. Option D is incorrect because visibility into an application and its host is a core Service Mapping function, not an enhancement unique to the Unified Map.

In summary, the Unified Map adds value by improving interactivity, flexibility, and user-driven insight across the CMDB.

Identification rules can be reviewed and configured through CI Class Manager and the CI Identifiers module .

CI Class Manager provides the modern class-centric interface for managing a CMDB class. It consolidates class hierarchy information, attributes, identification rules, reconciliation settings, principal-class configuration, and recommended relationships. This allows an administrator to understand an identification rule in the context of the class to which it applies.

The CI Identifiers module provides direct access to identification-rule definitions used by the Identification and Reconciliation Engine. These rules specify the attribute combinations that determine whether incoming data represents an existing CI or requires creation of a new CI.

API Integrations does not define IRE identification criteria. “IRE Application” is not the applicable class-level configuration location presented by the platform for this task.

=========

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.

The CMDB Data Foundations Dashboard is designed to help administrators identify priority data issues and take structured remediation actions. When several metrics have low scores, the correct approach is not to randomly clean records or manipulate scoring rules. Instead, the administrator should prioritize the most important issues and use the recommended remediation guidance.

Option A is correct because Data Foundations emphasizes prioritizing metrics with Critical and High priority first. These metrics usually represent the most important issues affecting CMDB trust, operational readiness, service visibility, and downstream ITSM processes such as Incident, Change, and Problem Management. Focusing on the highest-priority metrics ensures remediation effort is aligned with business and operational risk.

Option C is also correct because the dashboard provides Remediation Playbooks linked to specific metrics. These playbooks give structured guidance for analyzing the issue, identifying impacted records, correcting the data, and improving governance so the problem does not return. This is the preferred Data Foundations approach because it supports repeatable, auditable, and best-practice remediation.

Option B is not recommended because changing exclusions simply to improve the score can hide poor data quality rather than fix it. Exclusion rules should only be used when records are legitimately out of scope. Option D may be valid in some lifecycle cleanup scenarios, but blindly removing non-operational or retired CIs is not the primary recommended action for improving dashboard health.

CMDB Data Manager is the governance capability designed to control the lifecycle of CI records through policy-driven actions. Its policy types include Retire, Archive, Delete, Attestation, and Certification. These policies enable obsolete or no-longer-relevant records to be identified and processed consistently rather than removed through uncontrolled scripts or manual cleanup.

Archive policies remove eligible records from active operational use while retaining them for a defined recovery or compliance period. Delete policies permanently remove records after applicable lifecycle and retention requirements are satisfied. Retire policies transition CIs out of active operational status. The guide identifies automated archival and deletion according to retention policies as a primary purpose of CMDB Data Manager.

The CMDB Health and Data Foundations dashboards identify problems but do not perform lifecycle removal themselves. CI Class Manager governs classes, while de-duplication templates address duplicates specifically. Therefore, B is correct.

=========

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.

Service Mapping (Top-down) → Recommended for mission-critical application services that require a precise approach using patterns

Tag-Based → Best fit to map cloud-native, container-based, or virtual machine environments

Service Mapping (Connection Suggestions) → Ideal for custom-built applications and leverages application fingerprinting to generate service maps in a timely manner

Dynamic CI Group → Ideal for small application services that can be easily grouped using filters and CMDB queries

In Data Foundations (CMDB + CSDM), an Application Service should be created using an approach that balances accuracy, speed, and maintainability, because the service map becomes the foundation for impact analysis, service visibility, and operational workflows.

Service Mapping (Top-down) is best for mission-critical services because it uses structured entry points and patterns to precisely discover infrastructure, dependencies, and communication paths. This produces high-fidelity maps suitable for strict governance, controlled change, and reliable outage impact analysis.

Tag-Based mapping is best for cloud-native and dynamic environments (containers, elastic virtual machines, and cloud resources) because tags/labels are the most stable identifiers in rapidly changing estates. It aligns well with modern cloud governance where ownership, environment, and service affiliation are expressed through standardized tagging strategies.

Service Mapping (Connection Suggestions) fits custom-built applications because it leverages observed connection data and application fingerprinting to propose likely dependencies. This accelerates service map creation when traditional pattern-first modeling would take longer, helping teams reach usable service visibility faster while still allowing validation and refinement.

Dynamic CI Group is ideal for smaller services where a full discovered map may be unnecessary. It groups CIs using filters and CMDB queries, providing a lightweight way to define “what’s in the service” for reporting, ownership, and basic impact without heavy mapping overhead.

A Web Server is an application or software CI hosted on an underlying physical or virtual Server CI. The standard ServiceNow relationship is therefore Runs on::Runs .

From the Web Server’s direction, the relationship reads Web Server runs on Server . From the reverse direction, the Server runs Web Server . This bidirectional relationship allows users and platform processes to traverse the relationship correctly during incident investigation, service impact analysis, change planning, and service mapping.

“Uses::Used by” represents a broader dependency or consumption relationship and does not accurately express direct software hosting. “Runs::Runs on” reverses the standard relationship direction presented in the question.

Discovery can identify the running software and its host and create the relationship automatically as part of the ingestion process. Therefore, the correct relationship is Web Server > Runs on::Runs > Server.

=========

The CMDB aligns to business processes by giving the organization a trusted operational data foundation. First, it enhances decision-making and operational efficiency because Incident, Problem, Change, Risk, Security, and Service Management teams can assess impact, ownership, dependency, and priority using reliable CI and relationship data. Second, it provides a centralized view of configuration items and relationships , which is the core function of the CMDB. That centralized relationship model is what makes service impact analysis, change risk assessment, outage analysis, and operational routing possible. Tracking software licenses is primarily an IT Asset Management and Software Asset Management concern, not the main CMDB business-process alignment value. Extending service delivery management to all enterprise departments is too broad and belongs more to enterprise service management strategy than core CMDB alignment. Therefore, A and C are correct.

=========

A CMDB delivers business value when it enables better outcomes across IT and enterprise service delivery—especially when aligned with CSDM so services, offerings, and supporting technology are connected in a consumable model. Two major business values are improved operational execution and improved business continuity.

Option C is a direct business value: a trusted CMDB improves incident and change management by providing accurate CI details, relationships, and service context. This supports faster triage and assignment, better prioritization, and higher-quality impact analysis for changes. When incidents and changes are informed by dependable configuration data, organizations reduce downtime, avoid unnecessary escalations, and make safer change decisions—benefits that the business experiences as higher service quality and fewer disruptions.

Option D is also a core business value: CMDB strengthens operational resiliency by enabling clearer dependency understanding and faster response to failures. Resiliency improves when teams can quickly identify what’s impacted, understand upstream/downstream relationships, and plan mitigation steps using known service-to-technology mappings. In regulated or mission-critical environments, this translates into better continuity, reduced risk exposure, and improved compliance reporting.

Option A can be beneficial, but it is more of a technical/operational mechanism than a primary “business value” statement in Data Foundations framing. Option B is primarily the domain of IT Asset Management and financial systems; while CMDB can relate to assets, it is not the system of record for financial management. Hence, the best two business values are streamlining incident and change management and strengthening operational resiliency.

The correct answer is Configuration File Path . When the same application can be installed more than once on the same server, the identification rule must use an attribute that can distinguish one installed instance from another. Configuration File Path is stronger than file name because the same file name can exist in multiple installation directories. It is also stronger than version because multiple instances may run the same version. Port can help in some cases, but ports may be reused, changed, or not consistently available for every application pattern. Class is too broad because it only identifies the type of CI, not the specific application instance. A path-based criterion is more precise because it identifies where that application instance is installed on the server. Therefore, Configuration File Path is the best criterion attribute for preventing incorrect matches between multiple instances.

=========