Question 40 A healthcare group is piloting a new CMDB feed in an isolated instance with duplicate-prone device records. An existing CI cannot be matched from one source despite a matching manufacturer serial. Which implementation should the CMDB team select? Define authoritative sources for important fields rather than relying on last-writer-wins Review the target class and class-specific identifier rules before importing more records Check the payload's normalized identifier and class matching prerequisites in IRE diagnostics Inspect reconciliation authorizations and source precedence for that CI attribute Explanation Correct Answer C:Missing or differently formatted identifier attributes can prevent an otherwise legitimate match. Incorrect Answers A:Uncontrolled writes make reliable device ownership and location impossible to audit. B:Class hierarchy and identity rules jointly determine whether the input represents the intended CI. D:Inspect reconciliation authorizations and source precedence for that CI attribute applies to the distinct condition that one CI is identified correctly but a source cannot update an attribute despite new input, where identification chooses the existing record.
Question 41 A utilities business consolidates network equipment from multiple regional acquisition systems into one ServiceNow CMDB. Two routers have the same hostname but different serial numbers. What should the administrator verify or change? Examine reconciliation rule configuration and the specific source identity in the payload Define the authoritative ownership mapping and reconcile only the appropriate source writes Ensure identification distinguishes the two actual devices using appropriate identifiers Establish the authoritative source for the operating-system attribute using reconciliation controls Explanation Correct Answer C:Hostname alone is not a reliable unique equipment identity across independent networks. Incorrect Answers A:Source labels and attribute authority must align for the expected writer to be allowed. B:Business stewardship should not change unpredictably with the order of integration messages. D:Field ownership prevents a financial integration from replacing a recent technical discovery value.
Question 42 A utilities business consolidates network equipment from multiple regional acquisition systems into one ServiceNow CMDB. Two sources disagree about which support group manages a router. Which choice most directly solves this issue? Ensure identification distinguishes the two actual devices using appropriate identifiers Define the authoritative ownership mapping and reconcile only the appropriate source writes Let supported IRE matching determine whether to create a new CI using approved identification rules Use reconciliation precedence or source authorization for the disputed attribute Explanation Correct Answer B:Business stewardship should not change unpredictably with the order of integration messages. Incorrect Answers A:Hostname alone is not a reliable unique equipment identity across independent networks. C:A governed insertion follows identity evaluation instead of blindly overwriting another device. D:The CMDB should enforce a declared attribute authority rather than accepting whichever message arrives last.
Question 43 A utilities business consolidates network equipment from multiple regional acquisition systems into one ServiceNow CMDB. A vendor sends an update containing a device that does not exist in the CMDB. How should the team proceed without weakening data integrity? Define the authoritative ownership mapping and reconcile only the appropriate source writes Let supported IRE matching determine whether to create a new CI using approved identification rules Use IRE identification first and then apply its reconciliation controls Examine reconciliation rule configuration and the specific source identity in the payload Explanation Correct Answer B:A governed insertion follows identity evaluation instead of blindly overwriting another device. Incorrect Answers A:Business stewardship should not change unpredictably with the order of integration messages. C:Matching identity and authorizing field writes are separate phases of governed CI ingestion. D:While Examine reconciliation rule configuration and the specific source identity in the payload is suitable if a matched CI receives an update that violates the intended attribute source priority because source labels and attribute authority must align for the expected writer to be allowed, the presented problem is a vendor sends an update containing a device that does not exist in the CMDB, making Let supported IRE matching determine whether to create a new CI using approved identification rules the better choice.
Question 44 A utilities business consolidates network equipment from multiple regional acquisition systems into one ServiceNow CMDB. A matched CI receives an update that violates the intended attribute source priority. Which option matches this operational need? Examine reconciliation rule configuration and the specific source identity in the payload Let supported IRE matching determine whether to create a new CI using approved identification rules Configure source and attribute reconciliation behavior with explicit update authority Ensure identification distinguishes the two actual devices using appropriate identifiers Explanation Correct Answer A:Source labels and attribute authority must align for the expected writer to be allowed. Incorrect Answers B:A governed insertion follows identity evaluation instead of blindly overwriting another device. C:While Configure source and attribute reconciliation behavior with explicit update authority is suitable if a source is allowed to create new CIs but should not update a protected field of existing CIs because an insertion does not imply unlimited rights to overwrite protected fields after the CI is matched, the presented problem is a matched CI receives an update that violates the intended attribute source priority, making Examine reconciliation rule configuration and the specific source identity in the payload the better choice. D:Hostname alone is not a reliable unique equipment identity across independent networks.
Question 45 An energy company receives CMDB information from Discovery, endpoint management and an external cloud inventory tool; each identifies the same host. The audit team wants visibility into which integrated source supplied a particular field. What is the most defensible ServiceNow approach? Compare source-native identifiers and the multisource evidence against the identified CI Check reconciliation authority in addition to the available source records Enable the supported CMDB 360 or multisource view for the relevant CI and review contributing sources Maintain the reconciled winning value while retaining source-specific evidence for comparison Explanation Correct Answer C:Multisource evidence shows differences among source records rather than flattening every observation into an untraceable value. Incorrect Answers A:Source-level comparisons help determine whether apparent duplicates are separate machines or competing descriptions. B:While Check reconciliation authority in addition to the available source records is suitable if a network engineer asks why one supplier feed failed to update a source-owned router field because stored source observations do not grant that source permission to replace the operational value, the presented problem is the audit team wants visibility into which integrated source supplied a particular field, making Enable the supported CMDB 360 or multisource view for the relevant CI and review contributing sources the better choice. D:Multisource history can expose conflicting observations without changing declared attribute authority.
Question 46 An energy company receives CMDB information from Discovery, endpoint management and an external cloud inventory tool; each identifies the same host. A secondary feed reports a conflicting service owner but should not override authoritative ownership. Which implementation should the CMDB team select? Validate source identification and import mapping before relying on multisource attribution Maintain the reconciled winning value while retaining source-specific evidence for comparison Use CMDB 360 to inspect available source contributions for the identified CI Compare source-native identifiers and the multisource evidence against the identified CI Explanation Correct Answer B:Multisource history can expose conflicting observations without changing declared attribute authority. Incorrect Answers A:While Validate source identification and import mapping before relying on multisource attribution is suitable if one new data feed reports values for a CI but not the expected source identity because traceability requires trustworthy source labeling or comparisons will misidentify where data originated, the presented problem is a secondary feed reports a conflicting service owner but should not override authoritative ownership, making Maintain the reconciled winning value while retaining source-specific evidence for comparison the better choice. C:A single reconciled field alone cannot show the set of conflicting external observations. D:Source-level comparisons help determine whether apparent duplicates are separate machines or competing descriptions.
Question 47 An energy company receives CMDB information from Discovery, endpoint management and an external cloud inventory tool; each identifies the same host. A steward wants to confirm the source record before merging near-duplicate host entries. Which action best addresses the specific requirement? Correlate reconciliation rules with retained source observations for the affected record Use CMDB 360 to inspect available source contributions for the identified CI Compare source-native identifiers and the multisource evidence against the identified CI Enable the supported CMDB 360 or multisource view for the relevant CI and review contributing sources Explanation Correct Answer C:Source-level comparisons help determine whether apparent duplicates are separate machines or competing descriptions. Incorrect Answers A:Source history alone shows attempted values. B:A single reconciled field alone cannot show the set of conflicting external observations. D:Multisource evidence shows differences among source records rather than flattening every observation into an untraceable value.
Question 48 An energy company receives CMDB information from Discovery, endpoint management and an external cloud inventory tool; each identifies the same host. A newly onboarded source is not visible in the expected multisource view. What should the administrator verify or change? Enable the supported CMDB 360 or multisource view for the relevant CI and review contributing sources Maintain the reconciled winning value while retaining source-specific evidence for comparison Verify the source is configured for the supported multisource collection and inspect its integration results Validate source identification and import mapping before relying on multisource attribution Explanation Correct Answer C:A new feed does not automatically yield reliable source-level history unless the required collection and mappings are enabled. Incorrect Answers A:Multisource evidence shows differences among source records rather than flattening every observation into an untraceable value. B:Multisource history can expose conflicting observations without changing declared attribute authority. D:Traceability requires trustworthy source labeling or comparisons will misidentify where data originated.
Question 49 A hospital is reviewing CMDB 360 evidence because cloud and on-premises discovery feeds show different values for critical application servers. The incident team needs to understand why the current CI reflects one operating-system version. How should the team proceed without weakening data integrity? Review the contributing source records and reconciliation precedence in CMDB 360 Inspect source-specific records in the supported multisource CMDB view Validate source identification and import mapping before relying on multisource attribution Use CMDB 360 to inspect available source contributions for the identified CI Explanation Correct Answer A:Multisource visibility explains why the displayed value follows one authoritative source rather than another. Incorrect Answers B:Comparing contributing records pinpoints disagreement instead of assuming the current CI is the only observation. C:Traceability requires trustworthy source labeling or comparisons will misidentify where data originated. D:A single reconciled field alone cannot show the set of conflicting external observations.
Question 50 A hospital is reviewing CMDB 360 evidence because cloud and on-premises discovery feeds show different values for critical application servers. Auditors want to compare vendor inventory claims without changing the operational CI. Which option matches this operational need? Use source-specific multisource evidence instead of overwriting the authoritative CI fields Use CMDB 360 to inspect available source contributions for the identified CI Review the contributing source records and reconciliation precedence in CMDB 360 Compare stable identification keys and the source-level record history for the same CI Explanation Correct Answer A:Comparing observations is safer than changing production identity and status merely to view alternatives. Incorrect Answers B:A single reconciled field alone cannot show the set of conflicting external observations. C:Multisource visibility explains why the displayed value follows one authoritative source rather than another. D:Identity continuity is established through matching attributes, not the mutable display name.