Question 160
Two change requests must be delivered together. Requirement A: An Orphan correctness score flags CIs missing configured ownership attributes or required relationship types, but operators assume every flagged CI is decommissioned. Requirement B: An executive requests one CMDB health score but support teams need practical remediation actions. Select the plan that resolves both.
Explanation
Correct Answer
Both controls are required. For condition (1), inspect the CI class Orphan rule attribute and relationship criteria, verify the flagged CI against the actual source records and assign remediation without automatically deleting it. The CMDB Health Orphan correctness metric uses class-specific attribute and/or missing-relationship rules; a flagged CI is not necessarily a deleted, stale or physically decommissioned asset. Verify: A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted. For condition (2), link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks. An aggregate score becomes useful when failures are traceable to actionable work items. Verify independently: Each critical failed metric has a named owner, affected CI sample and due date.
Incorrect Answers
Part (1) answers a different need: An administrator deletes a duplicate CI record directly and loses change relationships attached to it. It should instead use: Inspect the CI class Orphan rule attribute and relationship criteria, verify the flagged CI against the actual source records and assign remediation without automatically deleting it. Part (2) answers a different need: A large batch of duplicate devices needs repeatable treatment across the same CI class. It should instead use: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks. Both required outcomes must be verified separately.
Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A large batch of duplicate devices needs repeatable treatment across the same CI class. It should instead use: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks. Both required outcomes must be verified separately.
Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: An administrator deletes a duplicate CI record directly and loses change relationships attached to it. It should instead use: Inspect the CI class Orphan rule attribute and relationship criteria, verify the flagged CI against the actual source records and assign remediation without automatically deleting it. Both required outcomes must be verified separately.