Question 330
A ServiceNow configuration project has two acceptance conditions. The first issue is: The governance team needs a recommended support group field for one class without making it universally mandatory. The second is: A data steward needs to know which source last updated a reconciled CI attribute. Which paired approach is suitable?
Explanation
Correct Answer
Both controls are required. For condition (1), configure a class-specific recommended field through CI Class Manager health settings. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. Verify: The class receives a recommended-field completeness score while record creation is not globally blocked. For condition (2), review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. CMDB 360 shows per-source reported values and the current CMDB selection; data-source history depends on actual source reporting and reconciliation configuration, not merely on a populated CI display field. Verify independently: The steward can inspect the competing reported attribute values, identify the selected CMDB value and corroborate its source history.
Incorrect Answers
Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A child network-device class needs stricter identification than its broad parent network class. It should instead use: Review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. Both required outcomes must be verified separately.
Part (1) answers a different need: A source stopped reporting network devices three weeks ago even though their CIs still exist. It should instead use: Configure a class-specific recommended field through CI Class Manager health settings. Part (2) answers a different need: A child network-device class needs stricter identification than its broad parent network class. It should instead use: Review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. Both required outcomes must be verified separately.
Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A source stopped reporting network devices three weeks ago even though their CIs still exist. It should instead use: Configure a class-specific recommended field through CI Class Manager health settings. Both required outcomes must be verified separately.