Question 810
A service desk cannot identify which application service depends on a failed database because the CI relationships are absent. Before changing the configuration, which evidence should the administrator examine FIRST?
Explanation
Correct Answer
Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. The CMDB tracks configuration items and their relationships; a server CI, business service and incident record serve different purposes. The appropriate response is: Represent configuration items in appropriate CMDB classes and validate core attributes and relationships rather than using generic text records for every device and service. Scenario: A service desk cannot identify which application service depends on a failed database because the CI relationships are absent.
Incorrect Answers
Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This evidence is relevant to Table extension and inherited task fields, not the most diagnostic first check for this failure. Examine: Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. Scenario: A service desk cannot identify which application service depends on a failed database because the CI relationships are absent.
Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. This evidence is relevant to CMDB Identification and Reconciliation Engine source trust, not the most diagnostic first check for this failure. Examine: Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. Scenario: A service desk cannot identify which application service depends on a failed database because the CI relationships are absent.
Inspect captured customer updates, excluded data records, local target changes, preview/commit logs, post-deployment data requirements and rollback plan. This evidence is relevant to Update set exclusions and collision resolution, not the most diagnostic first check for this failure. Examine: Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. Scenario: A service desk cannot identify which application service depends on a failed database because the CI relationships are absent.


