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

Delete and archive policies are designed for end-of-life CMDB lifecycle governance. They should apply to records that are no longer active operational CIs and have reached an appropriate retired state. End of Life - Retired is the correct lifecycle state because it indicates that the CI has completed its useful operational lifecycle and can be governed through archival or deletion according to retention rules. Applying delete or archive policies to Inventory - Available records would be dangerous because those CIs may still be valid and usable. “In any lifecycle state” is wrong because unrestricted archival or deletion can remove active, dependent, or operationally important records. “Missing - Stolen” is more aligned with asset disposition and exception handling, not the standard CMDB Data Manager delete/archive target state. Therefore, these policies should affect servers in End of Life - Retired.

=========

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.

=========

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.

=========

A healthy and trusted CMDB that aligns with Data Foundations principles—covering accurate data ingestion, strong governance, and service-aware relationships—directly strengthens the insight available to Change Management. When discovered infrastructure data is integrated with well-maintained non-discoverable attributes (such as assignment groups, support groups, and ownership), the CMDB becomes a reliable source of truth for evaluating change risk and impact.

Option B is correct because Service Mapping establishes relationships between configuration items (CIs) and business services. This enables change practitioners to perform impact analysis, identifying which services, applications, and downstream components may be affected by a proposed change. Rather than relying on assumptions or tribal knowledge, change records can reference real dependency data, improving risk assessment, scheduling decisions, and stakeholder communication. This aligns directly with CSDM and CMDB best practices, where service context is essential for informed decision-making.

Option D is also correct because accurate, governed non-discoverable data—such as support and assignment groups—allows Change Management processes to dynamically route work. When a change is associated with a CI or service, the system can automatically populate the appropriate assignment group based on CMDB relationships. This improves efficiency, reduces manual errors, and ensures accountability across federated support models.

Options A and C are incorrect because a CMDB, regardless of maturity, cannot guarantee zero downtime, nor does it eliminate the need for human governance, approvals, and risk-based decision-making. Data Foundations enhance insight and control—not unchecked automation or absolute outcomes.

The correct approach is controlled consolidation rather than preserving unnecessary custom classes or deleting records indiscriminately. CI Class Manager should be used to review the class hierarchy, identify suitable out-of-box ServiceNow classes, and govern the target data model. The existing CIs should then be moved or reclassified into those standard classes, with custom attributes mapped carefully to corresponding standard or approved extended attributes.

Retaining fragmented classes preserves the exact reporting and integration problems described in the scenario. Deleting the custom classes and manually recreating every CI is unnecessarily destructive and risks losing relationships, historical references, source information, and task associations.

Data Foundations recommends using existing supported classes wherever possible and extending an appropriate class only when the required model does not exist. Standardized classes improve inheritance, reporting, identification, reconciliation, Discovery integration, and upgrade compatibility.

=========

In Data Foundations, “Insight” focuses on turning configuration data into actionable visibility. CMDB 360 (often associated with Multisource CMDB capabilities) provides a guided experience in CMDB Workspace for exploring CI data and running queries across sources. Within this experience, Saved Queries are managed directly under the CMDB 360 area of CMDB Workspace because they are part of the CMDB 360 query-and-analysis workflow.

A CMDB 360 Saved Query is not the same as a generic CMDB Query Builder query created from classic navigation modules. The CMDB 360 experience typically uses a tile/window approach where users can view existing saved queries, create new queries, modify them, and run them to retrieve CMDB 360 data aligned to multisource reporting and analysis. Keeping saved queries on the CMDB 360 tab makes them easy to discover and reuse for repeatable insights (for example, coverage and source comparisons, CI data quality checks by source, and targeted investigation of records).

The Insights tab in CMDB Workspace is generally used to understand adoption and health-related insights about CMDB features, not as the primary location for creating CMDB 360 multisource saved queries. “Coverage” is a specific lens/view and does not represent the saved-query creation workspace. “CMDB Query Builder” is a related capability, but the question explicitly asks where CMDB 360/Multisource Saved Queries are viewed and created in CMDB Workspace , which is the Saved queries window on the CMDB 360 tab.

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.

The correct answer is Basic Info because the class icon is a class-level property, not an attribute, relationship, or CI list configuration. In CI Class Manager, the Basic Info tab is where administrators manage core metadata for a CI class, including class name, label, description, table details, principal class settings, and visual representation such as the class icon. The Suggested Relationships tab is used to define or review recommended relationship patterns between CI classes. The CI List tab is used to view records belonging to the class. The Attributes tab is used to review or manage inherited and class-specific attributes. Since the question specifically asks where the UNIX Server class icon can be changed, the correct location is the Basic Info tab.

=========

The Correctness scorecard evaluates whether CI data accurately represents the real environment. It includes the Duplicate , Orphan , and Staleness metrics.

Duplicate identifies cases where the same real-world configuration item is represented by multiple CMDB records. Orphan identifies CIs that lack expected relationships or supporting context. Staleness identifies records that have not been updated within the configured period and may no longer represent active infrastructure.

The other choices belong to different CMDB Health KPIs. Audit belongs to Compliance because it evaluates whether CI values satisfy defined standards or desired-state conditions. Required and Recommended belong to Completeness because they measure whether mandatory and useful attributes are populated.

Therefore, Duplicate, Orphan, and Staleness are the metrics shown under Correctness.

=========

The correct answer is that all related CIs are displayed in the Affected CIs related list. A Dynamic CI Group is used to represent a dynamically maintained set of CIs based on defined membership criteria. In this case, the group contains all Windows servers. When the group is referenced on a Change form, the practical purpose is to apply the Change to the group members rather than manually selecting each Windows Server CI. The Affected CIs related list is the correct place to represent the individual CIs impacted by the Change. Impacted Services are derived from service relationships and impact calculations, not simply from group membership. Therefore, referencing the Dynamic CI Group causes its related member CIs to be represented as affected CIs for the Change.

=========