What is the outcome if a host in the CMDB is found to be in an obsolete state during Service Mapping?

What is the outcome if a host in the CMDB is found to be in an obsolete state during Service Mapping?

• A. The host is immediately removed from the CMDB.
• B. The hosting service is flagged for review.
• C. The obsolete host is automatically updated to a new version.
• D. The status is logged but no immediate action is taken.

Answer: (D)

When a host in the Configuration Management Database (CMDB) is identified as being in an obsolete state during Service Mapping, the primary outcome is that the status is logged but no immediate action is taken. This reflects a careful and methodical approach to managing configuration items within the CMDB. In a ServiceNow context, marking a host as obsolete indicates that the system has recognized it as outdated or no longer relevant for current operations. However, a direct removal or other aggressive measures might not be ideal, especially if there are dependencies or a historical context that needs to be preserved for auditing or operational purposes. As such, logging the status provides a record that can be reviewed later without disrupting current services. This approach allows administrators to strategically assess the situation and decide on appropriate actions at a later time, rather than acting impulsively. It supports a more comprehensive review process where decisions can be made based on the overall impact of the obsolete host on services and infrastructure.

When a host in the Configuration Management Database (CMDB) is identified as being in an obsolete state during Service Mapping, the primary outcome is that the status is logged but no immediate action is taken. This reflects a careful and methodical approach to managing configuration items within the CMDB.

In a ServiceNow context, marking a host as obsolete indicates that the system has recognized it as outdated or no longer relevant for current operations. However, a direct removal or other aggressive measures might not be ideal, especially if there are dependencies or a historical context that needs to be preserved for auditing or operational purposes. As such, logging the status provides a record that can be reviewed later without disrupting current services.

This approach allows administrators to strategically assess the situation and decide on appropriate actions at a later time, rather than acting impulsively. It supports a more comprehensive review process where decisions can be made based on the overall impact of the obsolete host on services and infrastructure.