The CMDB Data Foundations Dashboard is designed to help administrators identify priority data issues and take structured remediation actions. When several metrics have low scores, the correct approach is not to randomly clean records or manipulate scoring rules. Instead, the administrator should prioritize the most important issues and use the recommended remediation guidance.
Option A is correct because Data Foundations emphasizes prioritizing metrics with Critical and High priority first. These metrics usually represent the most important issues affecting CMDB trust, operational readiness, service visibility, and downstream ITSM processes such as Incident, Change, and Problem Management. Focusing on the highest-priority metrics ensures remediation effort is aligned with business and operational risk.
Option C is also correct because the dashboard provides Remediation Playbooks linked to specific metrics. These playbooks give structured guidance for analyzing the issue, identifying impacted records, correcting the data, and improving governance so the problem does not return. This is the preferred Data Foundations approach because it supports repeatable, auditable, and best-practice remediation.
Option B is not recommended because changing exclusions simply to improve the score can hide poor data quality rather than fix it. Exclusion rules should only be used when records are legitimately out of scope. Option D may be valid in some lifecycle cleanup scenarios, but blindly removing non-operational or retired CIs is not the primary recommended action for improving dashboard health.
