A recent CMDB relationship import has introduced an unexpected dependency issue affecting Phoenix Commerce. A production database outage is occurring, but the expected Checkout Application Service is missing from the simulated impact path. The Application Service itself is approved and operational, while Discovery has successfully populated the underlying infrastructure CIs.
In this hands-on investigation, you will work through an Incident, Application Services, CI Relationships, Import Sets, and Dependency Views to determine why the expected application impact is not being identified. You will compare the relationship records created by Discovery with the relationships introduced by the recent import and examine the staging data and transform mappings that produced the affected relationship.
The investigation requires you to identify the incorrect relationship, determine how its Parent and Child assignments affect the Depends on::Used by relationship semantics, and remediate the imported record without replacing or rebuilding the approved Application Service. After making the correction, you will validate the simulated dependency path to confirm that the Checkout Application Service is once again reachable from the database outage.
Finally, you will select the remediation decision that best reflects the investigation findings. This lab focuses on understanding how relationship direction within the CMDB can affect dependency and impact analysis, while requiring you to use evidence from multiple ServiceNow areas rather than relying on a single obvious clue.