Question 70
A CMDB engineer applied the control: 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. This was meant to resolve: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which result most directly confirms the implementation works?
Explanation
Correct Answer
This observation directly validates the implemented control. 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. The decisive expected result is: 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
This checks a different technical dependency: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures. The case requires proof of “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”, which establishes the relevant condition: 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.
That observation would verify a control associated with: Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish the needed acceptance outcome. The direct evidence is “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”, testing: 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.
“The seeded beyond-threshold server is flagged by the correct class-effective rule and a refreshed server clears that metric without silently changing the threshold” could occur while the stated failure remains unresolved. It tests: CI update and the applicable class rule (default 60 days); it is not an automatic confirmation that the physical server was decommissioned. The required validation instead is “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”, because 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.