The recommended action for managing the lifecycle of stale CIs, such as removing servers that have not been updated, is to use the CMDB Data Manager. This tool allows an administrator to create policies, including an archive policy. An archive policy can be configured with specific conditions (e.g., class is Linux Server, 'Updated' is more than six months ago) to automatically move matching records from primary tables to archive tables. This is the standard, out-of-the-box method for managing data retention and maintaining CMDB health, preferable to custom scripts.

A. A business rule is event-driven (e.g., runs on record update/insert) and is not the appropriate tool for a scheduled, proactive cleanup task based on a time condition.

C. While a scheduled job could execute a script to perform this task, it is a custom solution. The recommended best practice is to use the purpose-built CMDB Data Manager policies.

1. ServiceNow Product Documentation. (2024). CMDB Data Manager. Retrieved from ServiceNow Docs. The overview states

"Use CMDB Data Manager to create policies to manage the life cycle of CIs. For example

you can create a policy to automatically retire

archive

or delete stale CIs of a specific class."

2. ServiceNow Product Documentation. (2024). Create a CMDB Data Manager policy. Retrieved from ServiceNow Docs. This page provides step-by-step instructions for creating policies

including archive policies

based on conditions like the last update time.