Question 300
A CMDB administrator must resolve both independent failures: (1) An update payload identifies an existing CI but an administrator expects reconciliation rules to apply to first-time inserts identically. (2) Cloud inventory and Discovery report different operating system versions for the same CI. Which coordinated plan satisfies both requirements?
Explanation
Correct Answer
Both controls are required. For condition (1), test first-time insertion and later matched updates separately: allow identification and IRE data-source rules to decide inserts, and use reconciliation authorization for existing-CI attribute updates. IRE identification decides new versus existing CIs; standard reconciliation rules apply to updates of matched CIs, not identically to the first insertion of a new CI. Verify: A new allowed CI is inserted once, then only an authorized update source changes protected attributes on the matched CI. For condition (2), use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. Verify independently: The reviewer sees both source values and identifies the currently selected value.
Incorrect Answers
Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. Both required outcomes must be verified separately.
Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. It should instead use: Test first-time insertion and later matched updates separately: allow identification and IRE data-source rules to decide inserts, and use reconciliation authorization for existing-CI attribute updates. Both required outcomes must be verified separately.
Part (1) answers a different need: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. It should instead use: Test first-time insertion and later matched updates separately: allow identification and IRE data-source rules to decide inserts, and use reconciliation authorization for existing-CI attribute updates. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. Both required outcomes must be verified separately.