CIS-DF 試験問題を無料オンラインアクセス

A CMDB Administrator identifies duplicate CIs. One was created by a manual import, and the other was created by automated discovery. The discovered CI has the latest IP address, while the manually imported CI has an accurate relationship to a critical business application.
How does the Administrator use the Duplicate CI Remediator to resolve this issue?

• A.Retain the discovered CI, but merge the relationship from the manually imported CI
• B.Retain the discovered CI and delete the manually imported CI
• C.Merge the two CIs automatically, retaining all attributes from the discovered CI
• D.Retain the manually imported CI and delete the discovered CI

The CMDB Administrator group aims to display meaningful results on the CMDB Health Dashboard - Compliance Scorecard for server records that are not on the latest patch.
What must be configured to achieve this goal?

• A.Technical Service Offerings, Dynamic CI Groups, CMDB Groups
• B.Stale, Orphan, Duplicate
• C.Certification Policies, Data Filters, Scheduled Jobs
• D.Certification Filter, Certification Template, Audit

A Windows administration team needs to organize Windows Server CIs for targeted Incident Management and Change Management workflows.
Which approaches can the team use to create logical groupings within CMDB groups?
(Choose two options.)

• A.Use tag-based queries to automatically assign Windows Server CIs to a named CMDB group.
• B.Manually select specific Windows Server instances and assign them to a named CMDB group.
• C.Use reconciliation rules to assign CIs to groups based on data-source priority.
• D.Use encoded queries to dynamically filter and group Windows Server CIs based on specific attribute conditions.

The CMDB Health Dashboard is based on three Key Performance Indicators: Correctness, Compliance, and Completeness . Each KPI includes several sub-metrics.
Drag the sub-metrics to the KPI. Some options may not apply.

正解：

Explanation:
Completeness # Required
Compliance # Audit
Correctness # Orphan
The CMDB Health Dashboard helps administrators measure whether the CMDB is trustworthy, usable, and aligned with governance expectations. The three main CMDB Health KPIs are Completeness , Compliance , and Correctness , and each KPI evaluates a different aspect of CMDB data quality.
Completeness focuses on whether required or expected fields are populated on CI records. A CI may exist in the CMDB, but if important fields such as owner, support group, location, serial number, or environment are missing, the record is not complete enough to support operational processes. Therefore, Required belongs under Completeness .
Compliance focuses on whether CIs follow defined rules, policies, and governance requirements. The Audit sub-metric is associated with Compliance because audits check whether records meet expected standards and whether governance controls are being followed.
Correctness focuses on whether the CI data is accurate and logically valid. Orphan belongs under Correctness because an orphan CI lacks expected relationships or context. For example, a server without expected dependencies or service relationships may reduce the accuracy of impact analysis and operational reporting.
The other visible options, such as Stability , Suggested , and Certify , are not the best fit for the three answer slots shown in this question.

A Configuration Manager responsible for a specific region wants to use the CMDB Health Dashboard to improve the data quality of the CMDB for that region. The Configuration Manager only sees the overall score and scores grouped by CI class.
How can the Configuration Manager get a score for regionally relevant CIs?

• A.On the CMDB Health settings, activate the option Group scores by region
• B.Customize the CMDB Health Dashboard scheduled jobs to group the results by region
• C.Create CMDB Groups with type Health by region