Question 100
A ServiceNow team is evaluating transform-to-class correctness. An import source sends device_type values server, router and database, but its transform map targets a single generic CI class. What should it implement?
- Design a governed IntegrationHub ETL mapping that transforms the source into appropriate CI classes and uses IRE.
- Map each source device type to the appropriate destination class before running the IRE identification step.
- Map source associations into valid cmdb_rel_ci relationship types with the correct source and target CI identities.
- Call CMDBTransformUtil in an onBefore transform script with the intended data source and suppress duplicate raw target insertion.
Explanation
Correct Answer
B:The Identification and Reconciliation Engine checks identity before a CI is created, preventing a raw import from duplicating the record. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
Incorrect Answers
A:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
C:Typed CMDB relationships connect CI endpoints with an explicit supported relationship type and direction. That does not establish IRE-based matching instead of uncontrolled duplicate insertion.
D:CI deduplication depends on stable identifiers and relationships, not just visually matching names. The missing change involves mapping each source device type to the appropriate destination class before running the IRE identification step.
Question 101
An import source sends device_type values server, router and database, but its transform map targets a single generic CI class. After the implementation, what evidence most directly demonstrates the intended result?
- After a supported upgrade, verify the custom mapped field still works without reapplying overwritten platform customizations.
- Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
- Inspect one representative CI per incoming type and verify its target subclass and inherited attributes.
- Confirm the connector's computer identity records match existing computers and update last-discovered appropriately.
Explanation
Correct Answer
C:Inspect one representative CI per incoming type and verify its target subclass and inherited attributes. That distinguishes a functioning transform-to-class correctness path from a configuration that was merely entered.
Incorrect Answers
A:This inspects an observable outcome of upgrade-resistant configuration: After a supported upgrade, verify the custom mapped field still works without reapplying overwritten platform customizations.
B:Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs. It does not inspect one representative CI per incoming type and verify its target subclass and inherited attributes.
D:Confirm the connector's computer identity records match existing computers and update last-discovered appropriately. It does not inspect one representative CI per incoming type and verify its target subclass and inherited attributes.
Question 102
The transform-to-class correctness implementation shows an unexpected result: Router rows appear as generic computers after import despite source device_type indicating router. Which underlying defect should be corrected?
- The mapping path does not traverse the real entry endpoint and service connections.
- The transformation never created proper typed CI relationships from the input associations.
- The transform class field map is not applying the device type to the appropriate target class.
- The script failed to ignore the transform's separate direct insert after IRE processing.
Explanation
Correct Answer
C:The transform class field map is not applying the device type to the appropriate target class.
Incorrect Answers
A:The mapping path does not traverse the real entry endpoint and service connections.
B:The transformation never created proper typed CI relationships from the input associations. That does not establish the transform class field map is not applying the device type to the appropriate target class.
D:The script failed to ignore the transform's separate direct insert after IRE processing. The different cause concerns the transform class field map is not applying the device type to the appropriate target class.
Question 103
An import source sends device_type values server, router and database, but its transform map targets a single generic CI class. To both implement the requested technical change and maintain the result under future drift, select TWO complementary actions.
- Assign a service owner to periodically certify manually curated dependencies.
- Test and version source-to-class translation rules before bulk import.
- Retain the one generic CI class for every device type and only version-control the existing transform script without changing its destination class logic.
- Map each source device type to the appropriate destination class before running the IRE identification step.
- Agree which item types are assets, CIs, both or neither before mapping the inventory.
Explanation
Correct Answers
B:Long-term integrity for transform-to-class correctness depends on Test and version source-to-class translation rules before bulk import.
D:Map each source device type to the appropriate destination class before running the IRE identification step.
Incorrect Answers
A:It preserves the manual critical dependency decision when data sources, policies or operational owners change. The combined controls instead need test and version source-to-class translation rules before bulk import.
C:Version control does not fix the incorrectly generic destination class. The device_type must select the supported CI subclass, and representative mapping tests must protect that classification.
E:Agree which item types are assets, CIs, both or neither before mapping the inventory. The combined controls instead need test and version source-to-class translation rules before bulk import.
Question 104
During the import-set ire invocation design review, the team describes this situation: A custom import-set transform inserts server rows with coalesce disabled and the team expects CI identification to prevent duplicate creation. Which change should be selected?
- Map source associations into valid cmdb_rel_ci relationship types with the correct source and target CI identities.
- Map each source device type to the appropriate destination class before running the IRE identification step.
- Call CMDBTransformUtil in an onBefore transform script with the intended data source and suppress duplicate raw target insertion.
- Configure the supported connector using its guided connection and source mappings instead of building an unnecessary custom table.
Explanation
Correct Answer
C:CI deduplication depends on stable identifiers and relationships, not just visually matching names. The needed intervention is call CMDBTransformUtil in an onBefore transform script with the intended data source and suppress duplicate raw target insertion.
Incorrect Answers
A:Typed CMDB relationships connect CI endpoints with an explicit supported relationship type and direction. It would leave correct matching and consolidation of CI identities without the specified safeguard.
B:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. It would leave correct matching and consolidation of CI identities without the specified safeguard.
D:Configure the supported connector using its guided connection and source mappings instead of building an unnecessary custom table. It would leave correct matching and consolidation of CI identities without the specified safeguard.
Question 105
A custom import-set transform inserts server rows with coalesce disabled and the team expects CI identification to prevent duplicate creation. A governance reviewer wants outcome evidence rather than a configuration screenshot. Which observation is decisive?
- Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
- Replay identical rows and confirm the IRE result updates the existing CI rather than creating a second row.
- Inspect one representative CI per incoming type and verify its target subclass and inherited attributes.
- Ingest a sample source record and compare its purchase-order value and provenance with the destination field.
Explanation
Correct Answer
B:Replay identical rows and confirm the IRE result updates the existing CI rather than creating a second row. That distinguishes a functioning import-set ire invocation path from a configuration that was merely entered.
Incorrect Answers
A:Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs. That check cannot demonstrate IRE-based matching instead of uncontrolled duplicate insertion.
C:Inspect one representative CI per incoming type and verify its target subclass and inherited attributes. That check cannot demonstrate IRE-based matching instead of uncontrolled duplicate insertion.
D:Ingest a sample source record and compare its purchase-order value and provenance with the destination field. That check cannot demonstrate IRE-based matching instead of uncontrolled duplicate insertion.
Question 106
After deployment for import-set ire invocation, the team sees: Every import run duplicates servers because a transform map writes directly to cmdb_ci_server after IRE already handled the payload. What explains this failure?
- The script failed to ignore the transform's separate direct insert after IRE processing.
- The mapping path does not traverse the real entry endpoint and service connections.
- The prior implementation modified upgrade-sensitive base integration code instead of an extension path.
- The dependent identification relationship is incomplete or identifies an incorrect parent.
Explanation
Correct Answer
A:The script failed to ignore the transform's separate direct insert after IRE processing.
Incorrect Answers
B:The mapping path does not traverse the real entry endpoint and service connections. The evidence points to the script failed to ignore the transform's separate direct insert after IRE processing.
C:The prior implementation modified upgrade-sensitive base integration code instead of an extension path. That mechanism cannot explain IRE-based matching instead of uncontrolled duplicate insertion.
D:The dependent identification relationship is incomplete or identifies an incorrect parent. That mechanism cannot explain IRE-based matching instead of uncontrolled duplicate insertion.
Question 107
A custom import-set transform inserts server rows with coalesce disabled and the team expects CI identification to prevent duplicate creation. Which continuing operational safeguard most directly protects the intended outcome?
- Validate parent resolution before sending child payloads and quarantine unresolved dependencies.
- Periodically reconcile connector permissions and account additions against the managed cloud inventory.
- Keep one supported transform path and inspect the log and returned CI sys_id for idempotency.
- Track integration customization separately from platform-managed application files and test upgrades.
Explanation
Correct Answer
C:Keep one supported transform path and inspect the log and returned CI sys_id for idempotency.
Incorrect Answers
A:Validate parent resolution before sending child payloads and quarantine unresolved dependencies. It would leave keep one supported transform path and inspect the log and returned CI sys_id for idempotency without the specified safeguard.
B:Periodically reconcile connector permissions and account additions against the managed cloud inventory. It would leave keep one supported transform path and inspect the log and returned CI sys_id for idempotency without the specified safeguard.
D:Track integration customization separately from platform-managed application files and test upgrades. It would leave keep one supported transform path and inspect the log and returned CI sys_id for idempotency without the specified safeguard.
Question 108
A ServiceNow team is evaluating dependent relationship construction. An application-process feed reports process identities and host serials separately; the target class uses dependent identification. What should it implement?
- Use supported ServiceNow Discovery with appropriate schedules, credentials and network reachability to populate infrastructure CIs.
- Map each source device type to the appropriate destination class before running the IRE identification step.
- Resolve the host CI and send the typed hosting relationship with the dependent process in the IRE payload.
- Call CMDBTransformUtil in an onBefore transform script with the intended data source and suppress duplicate raw target insertion.
Explanation
Correct Answer
C:Resolve the host CI and send the typed hosting relationship with the dependent process in the IRE payload.
Incorrect Answers
A:Use supported ServiceNow Discovery with appropriate schedules, credentials and network reachability to populate infrastructure CIs. The missing change involves resolve the host CI and send the typed hosting relationship with the dependent process in the IRE payload.
B:The Identification and Reconciliation Engine checks identity before a CI is created, preventing a raw import from duplicating the record. The missing change involves resolve the host CI and send the typed hosting relationship with the dependent process in the IRE payload.
D:CI deduplication depends on stable identifiers and relationships, not just visually matching names. The missing change involves resolve the host CI and send the typed hosting relationship with the dependent process in the IRE payload.
Question 109
An application-process feed reports process identities and host serials separately; the target class uses dependent identification. After the implementation, what evidence most directly demonstrates the intended result?
- Query the relationship table or Unified Map to confirm direction and type between a container and contained device.
- Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
- Confirm the connector's computer identity records match existing computers and update last-discovered appropriately.
- Replay identical rows and confirm the IRE result updates the existing CI rather than creating a second row.
Explanation
Correct Answer
B:Confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
Incorrect Answers
A:Query the relationship table or Unified Map to confirm direction and type between a container and contained device. It does not confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
C:Confirm the connector's computer identity records match existing computers and update last-discovered appropriately. It does not confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
D:The Identification and Reconciliation Engine matches incoming payloads before creating or updating CI records. It does not confirm the same process name on two different hosts remains two distinct correctly hosted process CIs.
Question 110
The dependent relationship construction implementation shows an unexpected result: The process is rejected or merged because its parent-host information does not resolve to a CI. Which underlying defect should be corrected?
- The dependent identification relationship is incomplete or identifies an incorrect parent.
- The transform class field map is not applying the device type to the appropriate target class.
- The script failed to ignore the transform's separate direct insert after IRE processing.
- Compliance identifiers were not modeled on the relevant CI or related object using structured relationships.
Explanation
Correct Answer
A:The dependent identification relationship is incomplete or identifies an incorrect parent.
Incorrect Answers
B:The transform class field map is not applying the device type to the appropriate target class. The evidence points to the dependent identification relationship is incomplete or identifies an incorrect parent.
C:The failure is in the import-set ire invocation path, not simply a reason to rerun an unrelated dashboard.
D:Compliance identifiers were not modeled on the relevant CI or related object using structured relationships. The evidence points to the dependent identification relationship is incomplete or identifies an incorrect parent.
Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests