Question 420
A ServiceNow administrator finds: A developer stores the caller's display name in a text field instead of a reference to the user record. 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 developer stores the caller's display name in a text field instead of a reference to the user record. The appropriate control is: Use reference fields and supported relationships to link authoritative records, resolving display values and dot-walk paths without copying sensitive data. It addresses the risk that treating display labels as stable identifiers or misusing dot-walking can produce wrong record joins and unintentional disclosure. Check effectiveness with: A test links a record to the intended referenced sys_id and authorized views resolve the expected fields without modifying sources.
Incorrect Answers
Tables records and fields in the data schema: Duplicating core tables or choosing incorrect data types makes reporting, integrations and updates inconsistent. That mechanism alone cannot establish Reference fields relationships and dot walking for this question.
Schema maps and impact analysis for table changes: A removed field may still drive flows, reports, import maps or integrations even if it is absent from visible forms. That may be useful independently, but the missing requirement here is Reference fields relationships and dot walking.
Table extension and inherited task fields: An inherited field change can unintentionally affect multiple child tables or create incompatible workflow assumptions. Here the decisive check is Reference fields relationships and dot walking, not that separate capability.