Question 410
A ServiceNow administrator finds: A custom fulfillment task extends task but its administrator assumes parent fields are unrelated. 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 custom fulfillment task extends task but its administrator assumes parent fields are unrelated. The appropriate control is: Use supported table inheritance deliberately, recognizing which fields, security rules and processes are shared with parent task records. It addresses the risk that an inherited field change can unintentionally affect multiple child tables or create incompatible workflow assumptions. Check effectiveness with: A schema test shows parent and child records have expected shared fields while child-specific behavior stays appropriately scoped.
Incorrect Answers
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. That mechanism alone cannot establish Table extension and inherited task fields 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 Table extension and inherited task fields.
Reference fields relationships and dot walking: Treating display labels as stable identifiers or misusing dot-walking can produce wrong record joins and unintentional disclosure. The observed issue still requires Table extension and inherited task fields; the proposed alternative tests another control.