Helping Hand Questions for CIS-DF

Business Application records represent logical applications from a portfolio, ownership, investment, risk, and lifecycle perspective. They are principally used by Application Portfolio Management and Enterprise Architecture to support application rationalization .

Rationalization enables an organization to evaluate applications based on factors such as business value, technical fitness, cost, risk, lifecycle status, capability alignment, and functional redundancy. Decision-makers can then determine whether an application should be invested in, tolerated, migrated, consolidated, replaced, or retired.

Application availability is normally monitored through operational Application Services and their supporting infrastructure rather than through the logical Business Application record. Change impact analysis also relies mainly on Application Services, service maps, and relationships to affected infrastructure CIs.

Because Business Applications belong to the Design and Planning context and provide strategic portfolio information, application rationalization is the appropriate business-decision use case

Bottom of Form

The correct answer is CMDB Workspace. Service Graph Connector Central is designed to improve visibility into Service Graph Connector activity and source contribution within the CMDB operating experience. Since the objective is to understand data sources contributing to the CMDB, the functionality is surfaced in CMDB Workspace rather than a separate Service Graph Connector Workspace or Discovery Admin Workspace. CMDB Workspace is the central workspace for managing CMDB data quality, source visibility, health, governance, and operational CMDB activities. Discovery Admin Workspace is focused on Discovery configuration and operations, not central CMDB source insight. Therefore, once the Service Graph Connector Central plugin is installed, the related tab is available in CMDB Workspace.

=========

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 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.