Identification rules are configured through CMDB CI Class Manager . These rules define how the Identification and Reconciliation Engine determines whether an incoming CI already exists or whether a new CI record should be created. For server records, identification rules usually rely on attributes such as serial number, name, hostname, hardware identifiers, or other class-specific criteria. If these rules are weak or missing, duplicate server records can be created during Discovery, Service Graph Connector imports, or other integrations. The CMDB Health Dashboard detects health issues such as duplicates, but it is not where identification rules are configured. CMDB Workspace provides operational access to CMDB capabilities, but CI Class Manager is the correct configuration location. CMDB Data Manager governs lifecycle policies, not IRE identification logic. Therefore, the correct answer is B.
=========