Question 500
A ServiceNow administrator finds: A recurring employee import inserts a fresh user row every night because no stable coalesce field is defined. The intended correction must preserve access controls, business process consistency and the supported platform configuration. Which administrative change most directly addresses this specific failure?
Explanation
Correct Answer
The decisive detail is: A recurring employee import inserts a fresh user row every night because no stable coalesce field is defined. The appropriate control is: Define reviewed transform maps, source-to-target field mappings and coalesce keys to update intended records instead of creating duplicates. It addresses the risk that incorrect coalesce keys or skipped field mappings can overwrite unrelated records or multiply business identities. Check effectiveness with: Repeatable import tests update the same intended target row rather than inserting a duplicate, with reference fields verified.
Incorrect Answers
Cmdb relationship modeling and service impact: Incorrect relationships can make impact analysis miss critical dependent applications or falsely identify unrelated services as affected. That mechanism alone cannot establish Transform maps field mappings and coalescing for this question.
Data sources import sets and staged ingestion: Importing directly into production business records without staging can corrupt authoritative data or expose malformed content. That may be useful independently, but the missing requirement here is Transform maps field mappings and coalescing.
Transform error handling and import remediation: A successful file upload does not mean transformations passed or that target relationships and mandatory values are correct. The observed issue still requires Transform maps field mappings and coalescing; the proposed alternative tests another control.