Question 90 A software provider imports hosted service components through a partner-supplied API connector into the CMDB. A new source API version renames an identifier field and duplicate CIs appear. What is the most defensible ServiceNow approach? Update the identity field mapping and retest IRE matching with old and new payloads Use supported connector or ETL extension patterns instead of modifying internal platform tables Configure an IntegrationHub ETL mapping for supported entity and relationship transformations Map and normalize the source identifier into the correct target CI attribute in the ETL Explanation Correct Answer A:Identifier drift can make an unchanged real-world component appear new to the CMDB. Incorrect Answers B:Supported integration surfaces reduce technical debt and ease future ServiceNow application updates. C:Hierarchical source mapping must preserve which components belong to which service rather than flattening everything into one attribute. D:Accurate identifier mapping prevents a legitimate device from being treated as a newly created CI.
Question 91 A software provider imports hosted service components through a partner-supplied API connector into the CMDB. The custom integration must be deployable and maintainable across platform upgrades. Which implementation should the CMDB team select? Update the identity field mapping and retest IRE matching with old and new payloads Inspect relationship mapping outputs and valid endpoint CI identification in the integration logs Respect existing reconciliation rules and document the source's allowed attributes Use supported connector or ETL extension patterns instead of modifying internal platform tables Explanation Correct Answer D:Supported integration surfaces reduce technical debt and ease future ServiceNow application updates. Incorrect Answers A:Identifier drift can make an unchanged real-world component appear new to the CMDB. B:Relationships require identified parent and child records, not merely successful source API calls. C:A new ETL pipeline should not silently bypass stewardship priorities established for protected fields.
Question 92 A software provider imports hosted service components through a partner-supplied API connector into the CMDB. Integration runs complete but do not populate expected component relationships. Which action best addresses the specific requirement? Review a sample integration run and update the ETL mapping deliberately Inspect relationship mapping outputs and valid endpoint CI identification in the integration logs Use supported connector or ETL extension patterns instead of modifying internal platform tables Configure an IntegrationHub ETL mapping for supported entity and relationship transformations Explanation Correct Answer B:Relationships require identified parent and child records, not merely successful source API calls. Incorrect Answers A:Schema changes should be tested against expected output fields rather than silently accepted into unrelated CI columns. C:While Use supported connector or ETL extension patterns instead of modifying internal platform tables is suitable if the custom integration must be deployable and maintainable across platform upgrades because supported integration surfaces reduce technical debt and ease future ServiceNow application updates, the presented problem is integration runs complete but do not populate expected component relationships, making Inspect relationship mapping outputs and valid endpoint CI identification in the integration logs the better choice. D:Hierarchical source mapping must preserve which components belong to which service rather than flattening everything into one attribute.
Question 93 A public-sector IT team uses a staged integration to ingest firewall inventory from a security platform. One import batch contains model numbers as strings and integer-like identifiers as inconsistent formats. Which choice most directly solves this issue? Check identifiers and IRE-aware ETL mapping against known instrument samples Respect existing reconciliation rules and document the source's allowed attributes Compare source cardinality, join or transform expansion, and IRE results for the failed batch Normalize field types and identity values in the ETL before CI matching Explanation Correct Answer D:Consistent field types and canonical identifiers prevent preventable mismatch errors in IRE. Incorrect Answers A:A successful ETL run is not proof that its identifier mapping matched existing CIs. B:While Respect existing reconciliation rules and document the source's allowed attributes is suitable if a proposed integration will overwrite every security owner field regardless of source confidence because a new ETL pipeline should not silently bypass stewardship priorities established for protected fields, the presented problem is one import batch contains model numbers as strings and integer-like identifiers as inconsistent formats, making Normalize field types and identity values in the ETL before CI matching the better choice. C:A transformation can multiply rows even when the incoming asset feed contains a unique device list.
Question 94 A public-sector IT team uses a staged integration to ingest firewall inventory from a security platform. A proposed integration will overwrite every security owner field regardless of source confidence. How should the team proceed without weakening data integrity? Compare source cardinality, join or transform expansion, and IRE results for the failed batch Respect existing reconciliation rules and document the source's allowed attributes Use supported connector or ETL extension patterns instead of modifying internal platform tables Run a supported ETL sample test and inspect the resulting classes, identifiers and relationships Explanation Correct Answer B:A new ETL pipeline should not silently bypass stewardship priorities established for protected fields. Incorrect Answers A:While Compare source cardinality, join or transform expansion, and IRE results for the failed batch is suitable if a batch unexpectedly transforms 900 inputs into 1,800 CIs because a transformation can multiply rows even when the incoming asset feed contains a unique device list, the presented problem is a proposed integration will overwrite every security owner field regardless of source confidence, making Respect existing reconciliation rules and document the source's allowed attributes the better choice. C:Supported integration surfaces reduce technical debt and ease future ServiceNow application updates. D:Controlled sample validation catches mapping defects without polluting the operational CMDB.
Question 95 A public-sector IT team uses a staged integration to ingest firewall inventory from a security platform. A batch unexpectedly transforms 900 inputs into 1,800 CIs. Which option matches this operational need? Run a supported ETL sample test and inspect the resulting classes, identifiers and relationships Compare source cardinality, join or transform expansion, and IRE results for the failed batch Normalize field types and identity values in the ETL before CI matching Check identifiers and IRE-aware ETL mapping against known instrument samples Explanation Correct Answer B:A transformation can multiply rows even when the incoming asset feed contains a unique device list. Incorrect Answers A:Controlled sample validation catches mapping defects without polluting the operational CMDB. C:Consistent field types and canonical identifiers prevent preventable mismatch errors in IRE. D:A successful ETL run is not proof that its identifier mapping matched existing CIs.
Question 96 A public-sector IT team uses a staged integration to ingest firewall inventory from a security platform. The team needs to simulate mappings on known firewall records before activation. What should the implementation specialist do next? Normalize field types and identity values in the ETL before CI matching Respect existing reconciliation rules and document the source's allowed attributes Inspect IntegrationHub ETL integration execution and CMDB integration dashboard diagnostics Run a supported ETL sample test and inspect the resulting classes, identifiers and relationships Explanation Correct Answer D:Controlled sample validation catches mapping defects without polluting the operational CMDB. Incorrect Answers A:Consistent field types and canonical identifiers prevent preventable mismatch errors in IRE. B:A new ETL pipeline should not silently bypass stewardship priorities established for protected fields. C:Run-level transformation errors pinpoint bad schema paths before downstream consumers trust the imported records.
Question 97 A transportation operator tracks non-networked safety equipment that cannot be found by automated network Discovery. A physical emergency radio has no interrogable management interface but still needs accountable ownership. Which implementation should the CMDB team select? Create a governed manual CI of the appropriate class with validated identity and stewardship Schedule owner attestation or an approved Data Manager verification task Maintain the correct accountable owner and support-group references for the record Require distinct approved asset identifiers and reject shared dummy identity keys Explanation Correct Answer A:Lack of discovery connectivity does not remove the need to represent a business-critical configuration item accurately. Incorrect Answers B:Attestation supplies human validation of equipment state that network scanning cannot establish. C:Maintain the correct accountable owner and support-group references for the record applies to the distinct condition that the renewal owner changes. D:Reused placeholder identifiers defeat correct CI matching and undermine the inventory's audit value.
Question 98 A transportation operator tracks non-networked safety equipment that cannot be found by automated network Discovery. A manually created device is occasionally reported by a source feed after relocation. Which action best addresses the specific requirement? Map barcode identities to existing manually maintained CIs and test deduplication Require distinct approved asset identifiers and reject shared dummy identity keys Create a governed manual CI of the appropriate class with validated identity and stewardship Reconcile the incoming source identity with the existing manual CI before creating another record Explanation Correct Answer D:Stable identifiers let later automated sources enrich a manually created record instead of duplicating it. Incorrect Answers A:Automated enrichment should converge on the same physical inventory rather than fork it. B:Reused placeholder identifiers defeat correct CI matching and undermine the inventory's audit value. C:Lack of discovery connectivity does not remove the need to represent a business-critical configuration item accurately.
Question 99 A transportation operator tracks non-networked safety equipment that cannot be found by automated network Discovery. The owner must periodically verify whether non-discoverable equipment is still in service. What should the administrator verify or change? Create a governed manual CI of the appropriate class with validated identity and stewardship Schedule owner attestation or an approved Data Manager verification task Maintain the correct accountable owner and support-group references for the record Reconcile the incoming source identity with the existing manual CI before creating another record Explanation Correct Answer B:Attestation supplies human validation of equipment state that network scanning cannot establish. Incorrect Answers A:Lack of discovery connectivity does not remove the need to represent a business-critical configuration item accurately. C:Business stewardship and technical administration are different dimensions of CI ownership. D:While Reconcile the incoming source identity with the existing manual CI before creating another record is suitable if a manually created device is occasionally reported by a source feed after relocation because stable identifiers let later automated sources enrich a manually created record instead of duplicating it, the presented problem is the owner must periodically verify whether non-discoverable equipment is still in service, making Schedule owner attestation or an approved Data Manager verification task the better choice.
Question 100 A transportation operator tracks non-networked safety equipment that cannot be found by automated network Discovery. A team suggests using one generic placeholder serial for every offline safety unit. Which choice most directly solves this issue? Validate an approved unique lab equipment ID before matching or creating the CI Require distinct approved asset identifiers and reject shared dummy identity keys Schedule owner attestation or an approved Data Manager verification task Reconcile the incoming source identity with the existing manual CI before creating another record Explanation Correct Answer B:Reused placeholder identifiers defeat correct CI matching and undermine the inventory's audit value. Incorrect Answers A:An uncertain identity must not be resolved by reusing a common placeholder field. C:While Schedule owner attestation or an approved Data Manager verification task is suitable if the owner must periodically verify whether non-discoverable equipment is still in service because attestation supplies human validation of equipment state that network scanning cannot establish, the presented problem is a team suggests using one generic placeholder serial for every offline safety unit, making Require distinct approved asset identifiers and reject shared dummy identity keys the better choice. D:Stable identifiers let later automated sources enrich a manually created record instead of duplicating it.