Question 30 A government agency reconciles cloud server records imported from infrastructure discovery and a financial asset feed. Records are duplicated because source-specific names are used as the only matching key. How should the team proceed without weakening data integrity? Configure source and attribute reconciliation behavior with explicit update authority Revise class identification logic to include stable identity attributes and test with representative payloads Establish the authoritative source for the operating-system attribute using reconciliation controls Define and test an identification rule using stable, class-appropriate identifiers Explanation Correct Answer B:Display names are often nonunique or mutable, whereas identifiers should preserve one CI across renames. Incorrect Answers A: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 records are duplicated because source-specific names are used as the only matching key, making Revise class identification logic to include stable identity attributes and test with representative payloads the better choice. C:Field ownership prevents a financial integration from replacing a recent technical discovery value. D:Stable identity criteria let IRE match a known CI even when a nonidentity label differs across sources.
Question 31 A government agency reconciles cloud server records imported from infrastructure discovery and a financial asset feed. A source is allowed to create new CIs but should not update a protected field of existing CIs. Which option matches this operational need? Revise class identification logic to include stable identity attributes and test with representative payloads Configure source and attribute reconciliation behavior with explicit update authority Let supported IRE matching determine whether to create a new CI using approved identification rules Validate proposed identification rules against collision and nonmatch samples before activating them Explanation Correct Answer B:An insertion does not imply unlimited rights to overwrite protected fields after the CI is matched. Incorrect Answers A:Source-specific names are used as the only matching key, because display names are often nonunique or mutable. C:A governed insertion follows identity evaluation instead of blindly overwriting another device. D:Identity changes can corrupt multiple integrations.
Question 32 A government agency reconciles cloud server records imported from infrastructure discovery and a financial asset feed. A deployment changes identification logic and might merge unrelated virtual instances. What should the implementation specialist do next? Configure source and attribute reconciliation behavior with explicit update authority Validate proposed identification rules against collision and nonmatch samples before activating them Route the supported ingestion through IRE-aware processing and validate match outcomes Establish the authoritative source for the operating-system attribute using reconciliation controls Explanation Correct Answer B:Identity changes can corrupt multiple integrations; testing both false positives and false negatives reduces that risk. Incorrect Answers A:An insertion does not imply unlimited rights to overwrite protected fields after the CI is matched. C:A direct table insert can create duplicates because it never applies the identity rules used by approved CI data sources. D:Field ownership prevents a financial integration from replacing a recent technical discovery value.
Question 33 A managed service provider receives CMDB updates from a cloud API and from an agent-based discovery integration. The cloud API uses an immutable provider instance ID for each VM. Which implementation should the CMDB team select? Include the stable cloud instance identifier in the appropriate identification strategy Diagnose the identification rule and source-native keys before changing reconciliation settings Use reconciliation precedence or source authorization for the disputed attribute Route the supported ingestion through IRE-aware processing and validate match outcomes Explanation Correct Answer A:Provider identity can distinguish machines that reuse a hostname or public IP after rebuilds. Incorrect Answers B:Duplicate creation is an identity-match failure, not simply a lower-priority source update. C:The CMDB should enforce a declared attribute authority rather than accepting whichever message arrives last. D:A direct table insert can create duplicates because it never applies the identity rules used by approved CI data sources.
Question 34 A managed service provider receives CMDB updates from a cloud API and from an agent-based discovery integration. Discovery and the cloud API disagree over an attribute and the organization has selected a preferred source. Which action best addresses the specific requirement? Diagnose the identification rule and source-native keys before changing reconciliation settings Configure source and attribute reconciliation behavior with explicit update authority Inspect supported IRE processing results and identification diagnostics Use reconciliation precedence or source authorization for the disputed attribute Explanation Correct Answer D:The CMDB should enforce a declared attribute authority rather than accepting whichever message arrives last. Incorrect Answers A:Duplicate creation is an identity-match failure, not simply a lower-priority source update. B:An insertion does not imply unlimited rights to overwrite protected fields after the CI is matched. C:Matching evidence distinguishes existing-record updates from CI insertions and exposes the rule responsible.
Question 35 A managed service provider receives CMDB updates from a cloud API and from an agent-based discovery integration. A nightly sync creates a new CI whenever a server changes its display name. What should the administrator verify or change? Diagnose the identification rule and source-native keys before changing reconciliation settings Inspect supported IRE processing results and identification diagnostics Check the payload's normalized identifier and class matching prerequisites in IRE diagnostics Include the stable cloud instance identifier in the appropriate identification strategy Explanation Correct Answer A:Duplicate creation is an identity-match failure, not simply a lower-priority source update. Incorrect Answers B:Matching evidence distinguishes existing-record updates from CI insertions and exposes the rule responsible. C:Missing or differently formatted identifier attributes can prevent an otherwise legitimate match. D:While Include the stable cloud instance identifier in the appropriate identification strategy is suitable if the cloud API uses an immutable provider instance ID for each VM because provider identity can distinguish machines that reuse a hostname or public IP after rebuilds, the presented problem is a nightly sync creates a new CI whenever a server changes its display name, making Diagnose the identification rule and source-native keys before changing reconciliation settings the better choice.
Question 36 A managed service provider receives CMDB updates from a cloud API and from an agent-based discovery integration. The operations team wants to know whether an incoming payload matched a CI or inserted a new one. Which choice most directly solves this issue? Include the stable cloud instance identifier in the appropriate identification strategy Inspect supported IRE processing results and identification diagnostics Use reconciliation precedence or source authorization for the disputed attribute Check the payload's normalized identifier and class matching prerequisites in IRE diagnostics Explanation Correct Answer B:Matching evidence distinguishes existing-record updates from CI insertions and exposes the rule responsible. Incorrect Answers A:Provider identity can distinguish machines that reuse a hostname or public IP after rebuilds. C:While Use reconciliation precedence or source authorization for the disputed attribute is suitable if discovery and the cloud API disagree over an attribute and the organization has selected a preferred source because the CMDB should enforce a declared attribute authority rather than accepting whichever message arrives last, the presented problem is the operations team wants to know whether an incoming payload matched a CI or inserted a new one, making Inspect supported IRE processing results and identification diagnostics the better choice. D:Missing or differently formatted identifier attributes can prevent an otherwise legitimate match.
Question 37 A healthcare group is piloting a new CMDB feed in an isolated instance with duplicate-prone device records. The feed must identify an existing device before deciding which fields to update. Which option matches this operational need? Check the payload's normalized identifier and class matching prerequisites in IRE diagnostics Define authoritative sources for important fields rather than relying on last-writer-wins Use IRE identification first and then apply its reconciliation controls Let supported IRE matching determine whether to create a new CI using approved identification rules Explanation Correct Answer C:Matching identity and authorizing field writes are separate phases of governed CI ingestion. Incorrect Answers A:Missing or differently formatted identifier attributes can prevent an otherwise legitimate match. B:While Define authoritative sources for important fields rather than relying on last-writer-wins is suitable if a project asks to let every incoming source overwrite location and ownership because uncontrolled writes make reliable device ownership and location impossible to audit, the presented problem is the feed must identify an existing device before deciding which fields to update, making Use IRE identification first and then apply its reconciliation controls the better choice. D:A governed insertion follows identity evaluation instead of blindly overwriting another device.
Question 38 A healthcare group is piloting a new CMDB feed in an isolated instance with duplicate-prone device records. A record has the right serial number but an incorrect lower-level class. What should the implementation specialist do next? Use IRE identification first and then apply its reconciliation controls 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 Define and test an identification rule using stable, class-appropriate identifiers Explanation Correct Answer B:Class hierarchy and identity rules jointly determine whether the input represents the intended CI. Incorrect Answers A:Matching identity and authorizing field writes are separate phases of governed CI ingestion. C:Missing or differently formatted identifier attributes can prevent an otherwise legitimate match. D:Stable identity criteria let IRE match a known CI even when a nonidentity label differs across sources.
Question 39 A healthcare group is piloting a new CMDB feed in an isolated instance with duplicate-prone device records. A project asks to let every incoming source overwrite location and ownership. What is the most defensible ServiceNow approach? Review the target class and class-specific identifier rules before importing more records Use IRE identification first and then apply its reconciliation controls Define the authoritative ownership mapping and reconcile only the appropriate source writes Define authoritative sources for important fields rather than relying on last-writer-wins Explanation Correct Answer D:Uncontrolled writes make reliable device ownership and location impossible to audit. Incorrect Answers A:Class hierarchy and identity rules jointly determine whether the input represents the intended CI. B:Matching identity and authorizing field writes are separate phases of governed CI ingestion. C:Business stewardship should not change unpredictably with the order of integration messages.
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.