Online CIS-DF Questions Video

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 contextual side panel is the correct work area because it displays detailed information about the selected node in Unified Map. When a Service Owner selects the home node or a related CI/service node, the contextual side panel provides supporting operational context such as active Incidents, planned Changes, related records, and other actionable details. This is exactly the requirement in the question: the Service Owner does not merely need to see topology; they need related work items connected to the selected node. The Map itself displays relationships and topology, but it does not provide the detailed related-record panel by itself. The toolbox provides map interaction tools, and content controls influence what layers or types of content are displayed. Neither of those is the correct place to review related Incidents and Changes for a selected node. Therefore, the correct answer is Contextual side panel.

Archive and Retire are the correct CMDB Data Manager end-of-life policy types from the listed options. End-of-life governance in CMDB focuses on handling CI records that are no longer operationally active or no longer required in the active CMDB. A Retire policy is used when CIs should be moved out of active operational status while preserving lifecycle accuracy. An Archive policy is used when records should be removed from active operational use but retained for recovery, audit, or compliance purposes. Disposed and Lost are typically lifecycle status values used in asset or CI lifecycle tracking, not CMDB Data Manager policy types in this context. Decommission describes an operational lifecycle action or state transition, but it is not the Data Manager policy type being tested here. Therefore, the valid end-of-life policy types are Archive and Retire.

In Data Foundations, “Insight” is about using health metrics to understand whether the CMDB is trustworthy and operationally usable. The CMDB Health Dashboard organizes health into scorecards that group related checks. When leadership asks for Duplicate CIs, Orphan CIs, and Stale CIs, they are asking about the CMDB’s ongoing hygiene and adherence to governance expectations—not simply whether fields are filled in.

These three metrics align best with Compliance because they represent whether CI records comply with rules that keep the CMDB clean and current over time:

Duplicate CIs indicate the identification and governance controls are not consistently preventing multiple records for the same real-world item.

Orphan CIs indicate relationship governance gaps—records exist without expected relationships or context, reducing their operational value and often signaling incomplete ingestion or lifecycle control issues.

Stale CIs indicate lifecycle management gaps—records are not being updated, attested, retired, or archived appropriately, which increases risk and noise in operational processes.

By contrast, Completeness focuses on whether required attributes are populated (owners, support group, environment, etc.). Correctness focuses on whether values and relationships are accurate and logically valid. While duplicates/orphans/stale can affect correctness indirectly, the dashboard’s grouping for these hygiene and lifecycle-oriented measures is best represented by Compliance, which is why B is the correct answer.