Question 440
A ServiceNow administrator finds: An administrator deletes an unused-looking table column without checking whether an integration maps to it. 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: An administrator deletes an unused-looking table column without checking whether an integration maps to it. The appropriate control is: Inspect schema maps, relationship references and field use before changing core data structures or retiring custom attributes. It addresses the risk that a removed field may still drive flows, reports, import maps or integrations even if it is absent from visible forms. Check effectiveness with: A dependency review identifies and tests every known consumer before the approved schema change is promoted.
Incorrect Answers
Reference fields relationships and dot walking: Treating display labels as stable identifiers or misusing dot-walking can produce wrong record joins and unintentional disclosure. That mechanism alone cannot establish Schema maps and impact analysis for table changes for this question.
Tables records and fields in the data schema: Duplicating core tables or choosing incorrect data types makes reporting, integrations and updates inconsistent. Here the decisive check is Schema maps and impact analysis for table changes, not that separate capability.
Dictionary overrides and field-level configuration: Changing inherited dictionary settings at the wrong scope can cause child tables to lose required controls or valid choices. The observed issue still requires Schema maps and impact analysis for table changes; the proposed alternative tests another control.