Question 430
A ServiceNow administrator finds: A subtask needs a different default priority but an admin changes the parent task dictionary globally. 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 subtask needs a different default priority but an admin changes the parent task dictionary globally. The appropriate control is: Apply dictionary overrides and choice configurations only at the intended table level, reviewing effects on inherited fields and existing records. It addresses the risk that changing inherited dictionary settings at the wrong scope can cause child tables to lose required controls or valid choices. Check effectiveness with: A table-by-table test verifies field defaults and constraints in the intended extension without changing unrelated task forms.
Incorrect Answers
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 mechanism alone cannot establish Dictionary overrides and field-level configuration 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. That may be useful independently, but the missing requirement here is Dictionary overrides and field-level configuration.
Reference fields relationships and dot walking: Treating display labels as stable identifiers or misusing dot-walking can produce wrong record joins and unintentional disclosure. Here the decisive check is Dictionary overrides and field-level configuration, not that separate capability.