The CMDB Health Dashboard allows for granular control over the scope of its metrics using Health Inclusion Rules. These rules define a specific subset of CIs within a class to be evaluated for a particular health test. The scenario shows the Duplicate metric evaluating all 60,000 servers, while the Orphan metric evaluates only 50,000. This indicates that a Health Inclusion Rule is applied specifically to the Orphan metric for the Server class, filtering the CIs included in its calculation based on defined conditions.

A. The Orphan metric has a CMDB Group configured for the Server class: CMDB Groups are for logical organization and reporting, not for defining the evaluation scope of a specific health metric.

C. The Duplicate metric has a Health Inclusion rule configured for the Server class: This would cause the Duplicate metric to evaluate fewer than 60,000 CIs, which contradicts the information provided.

D. The Duplicate metric has a CMDB Group configured for the Server class: CMDB Groups are not the mechanism used to scope individual health metric calculations.

1. ServiceNow Product Documentation, "Create a CMDB health inclusion rule," CMDB, Utah. "Use health inclusion rules to include only a specific set of CIs of a class in the health calculations of a health metric."

2. ServiceNow Product Documentation, "CMDB Health," CMDB, Utah. "You can create an inclusion rule for a specific health test, such as the duplicate CIs test, and for a specific CI class, such as the Server class."