Question 420
After correcting this ServiceNow CMDB scenario—a platform team wants server-owner information recommended for all Linux servers but not necessarily dictionary-mandatory for every CI.—which result proves the intended outcome?
Explanation
Correct Answer
Class-scoped health results confirm the recommendation. This result demonstrates the expected effect of the implementation: Configure the recommended field rule for the relevant server class in CI Class Manager. Recommended fields support class-targeted completeness monitoring without redefining universal mandatory schema.
Incorrect Answers
Attribute provenance explains the discrepancy. That evidence belongs to a different situation: Security wants to know why the CMDB currently shows an old firmware value when a newer source reports a different one.
Sibling and child comparisons verify precedence. That evidence belongs to a different situation: A reconciliation definition at a parent class conflicts with a more specific rule for one descendant attribute.
Side-by-side display validates traceability. That evidence belongs to a different situation: An organization wants multiple source attributes preserved for audit even when the CMDB chooses a reconciled winner.