Question 230
A ServiceNow Data Foundations rollout has two blockers. First: A relationship health report contains edges with missing parent CI references. Second: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which complete two-part implementation addresses both?
Explanation
Correct Answer
Both controls are required. For condition (1), investigate and repair orphan relationships in the relationship health results. Relationship integrity is separate from a CI having complete attributes. Verify: The corrected edge links two valid CIs and no longer appears as orphan. For condition (2), check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation. When a de-duplication task exceeds its configured threshold the wizard restricts main-CI selection and does not reconcile conflicting attributes or relationships; raising the setting above 5000 cannot restore those functions. Verify independently: An oversized task is handled without pretending it supports normal field/relationship merging, and any split or alternate process has an auditable main-CI outcome.
Incorrect Answers
Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. It should instead use: Investigate and repair orphan relationships in the relationship health results. Both required outcomes must be verified separately.
Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A CMDB policy draft was created but the scheduled processor never executes it. It should instead use: Check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation. Both required outcomes must be verified separately.
Part (1) answers a different need: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. It should instead use: Investigate and repair orphan relationships in the relationship health results. Part (2) answers a different need: A CMDB policy draft was created but the scheduled processor never executes it. It should instead use: Check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation. Both required outcomes must be verified separately.