CIS-DF Exam Dumps - Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

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 Foundation tab covers the shared reference and foundational data upon which the remaining CSDM domains depend. This includes organizational and reference structures such as companies, business units, locations, users, groups, product models, and related foundational records.

Product models establish standardized product definitions. Locations provide reusable geographical and physical context for CIs and services. Business units establish organizational context and accountability. If these records are duplicated, incomplete, or modeled inconsistently, later service modeling becomes unreliable.

The guide distinguishes Foundation from Design and Planning, Build and Integration, Service Consumption, and Service Delivery. It identifies Foundation as the area containing shared reference data such as companies, locations, and users.

Crawl, Walk, Run, and Fly are progressive implementation stages. They do not replace the Foundation dashboard category that directly assesses these shared reference-data domains.

=========

CMDB 360, also known as Multisource CMDB, preserves source-specific CI information instead of retaining only the final reconciled value. Administrators can therefore examine the latest values contributed by individual sources and identify missing, inconsistent, or conflicting attribute values. This source-level history also allows the platform to recalculate the winning CMDB value after reconciliation logic changes, without requiring each source to submit its data again.

Option B is therefore correct because stored multisource data supports recomputation following a reconciliation-rule change. Option D is correct because CMDB 360 records the latest source contribution and makes it available for comparison and analysis.

Option A is misleading. Standard IRE reconciliation rules can use discovery sources even when CMDB 360 is not enabled; CMDB 360 enhances visibility and recomputation but is not what makes basic source-priority rules possible. Option C describes the broader role of CMDB Health or Data Foundations dashboards rather than CMDB 360. The guide identifies source-value gaps and differing source values as the principal insights delivered by CMDB 360.

=========

The correct answer is Run. The Run stage of CSDM maturity focuses on operationalizing the service model so that it supports real ITSM and operational processes. Technology Management Services and Technical Service Offerings are used to represent technical services delivered by internal technology teams. When these offerings are connected to Dynamic CI Groups, operational ownership data such as Support Group and Managed By Group can be populated and maintained on associated CIs. This is beyond the basic Crawl and Walk stages, which focus on foundational CMDB data and initial service modeling. It is also not Fly, which represents more advanced optimization and enterprise-level maturity. Because the scenario is about using Technical Service Offerings to drive operational support alignment for CIs, it belongs to the Run stage.

=========

When organizations transition from legacy CMDB status fields (such as custom install status or operational status values) to CSDM-aligned lifecycle status fields, the goal is to map old values to standardized lifecycle stages without disrupting existing processes. In ServiceNow, this is achieved through the Life Cycle Mapping table.

The Life Cycle Mapping table is specifically designed to translate legacy or custom status values into CSDM lifecycle stages and statuses. This allows organizations to preserve historical data and integrations while progressively adopting CSDM standards. By modifying this table, administrators can define how existing status values correspond to CSDM lifecycle stages such as Plan, Build, Deploy, Operate, and Retire .

The Life Cycle Stages table (Option A) defines the standard stages themselves and should not be modified, as these are core to CSDM governance. Life Cycle Stage Status (Option C) defines valid statuses within a stage and is also part of the standardized model. Life Cycle Controls (Option D) enforce governance rules but do not perform value translation.

Therefore, to safely transition from legacy status fields to CSDM lifecycle statuses, the correct and supported approach is to modify the Life Cycle Mapping table, making Option B the correct answer.

IRE applies identification logic to determine whether incoming data represents an existing record or requires the creation of a new record. This makes Option A correct: properly configured identifiers reduce duplicate creation by matching incoming data to existing records before insertion.

IRE also applies reconciliation controls after identification. Reconciliation rules establish which data sources are authorized to update particular classes or attributes and define source precedence when multiple sources provide competing values. Therefore, Option D is correct because an unauthorized or lower-priority source can be prevented from overwriting controlled data.

IRE does not generally prevent an authorized ingestion source from inserting a genuinely new record when no match exists, so Option B is too broad. Option C is incorrect because identification is based on identifier attributes and identification rules, not simply on whether relationships exist.

The guide describes IRE as the mechanism that uniquely identifies records, reduces duplicate creation, applies source precedence, and protects records from unauthorized overwrites.

=========

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 Data Quality Scheduled Job because CMDB data quality checks are not simply visual or manual activities. Scheduled jobs are used to execute recurring evaluations that calculate and refresh quality indicators for CI records. These jobs support CMDB health and data quality by periodically checking records against configured rules, such as stale records, missing required attributes, compliance conditions, or correctness-related metrics. CMDB Workspace is the interface where users can review and act on CMDB information, but it is not itself the mechanism that performs scheduled quality evaluation. Business rules can enforce logic during insert or update actions, but they are not the normal mechanism for recurring CMDB data quality calculation. Therefore, the Data Quality Scheduled Job is the best answer.

=========