A CMDB Configuration Manager is reviewing the metrics on theCMDB Health Dashboard – Correctness Scorecardfor...

InServiceNow, eachCMDB Health metriccan independently definewhich CIs are in scopefor evaluation. This scoping is controlled primarily throughHealth Inclusion Rules, not CMDB Groups.

In this scenario, theDuplicatemetric evaluates all60,000 Server CIs, indicating no inclusion rule is restricting its scope. In contrast, theOrphanmetric evaluates only50,000 Server CIs, which means10,000 servers are intentionally excludedfrom that metric’s evaluation.

This difference is explained by aHealth Inclusion ruleconfigured specifically for theOrphan metricon the Server class. Health Inclusion rules allow administrators to define conditions—such as lifecycle state, environment, discovery source, or operational status—that determine whether a CI should be included in a specific health calculation. For example, retired servers or servers in build states may be excluded from orphan checks.

CMDB Groups are not used by the CMDB Health Engine to determine metric scope; they are used for reporting, assignment, and operational grouping. Therefore, Options A and D are incorrect. Option C is also incorrect because the Duplicate metric clearly evaluates the full population of 60,000 servers.

Thus, the scope difference is correctly explained by theOrphan metric having a Health Inclusion rule configured, makingOption Bthe verified answer.