Why should you not switch from probes to patterns if Discovery is already running with probes?

Switching from probes to patterns in a running Discovery environment is a significant decision that can impact the integrity of the Configuration Management Database (CMDB). One of the main reasons to avoid this switch is the potential for creating duplicate Configuration Items (CIs) in the CMDB.

When Discovery uses probes, it collects data based on specific scripts and methods designed to identify and classify devices and applications in the network. If you switch to patterns, which operate differently by utilizing a more structured approach to identify and manage CIs, there may be overlapping functionalities. This overlap can lead to the same CI being discovered by both the probes and patterns, resulting in duplicates. Duplicates in the CMDB can compromise data integrity, confuse reporting, and make asset management more complicated, as well as potentially leading to compliance issues.

In contrast, the other choices, while they touch on important considerations about system performance and functionality, do not capture the primary risk associated with changing the foundation of Discovery once it is already in operation. Maintaining a clean and accurate CMDB is crucial for effective IT service management, which underscores the importance of avoiding this switch to prevent duplicates.