Question 660
A ServiceNow administrator finds: An update set preview identifies a conflicting form field but a release engineer ignores the warning and commits. 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 update set preview identifies a conflicting form field but a release engineer ignores the warning and commits. The appropriate control is: Preview imported update sets in the destination instance, identify collisions and missing dependencies, and resolve problems before commit. It addresses the risk that committing an unreviewed set can overwrite newer configuration or fail because referenced components are absent. Check effectiveness with: A subproduction preview has resolved collisions and the committed change passes targeted functionality and rollback checks.
Incorrect Answers
Update set scope selection and capture of configuration: A change created in the wrong update set or absent from capture can lead to incomplete promotion and production drift. That may be useful independently, but the missing requirement here is Preview and resolve update set conflicts.
Script includes glideajax and integration contracts: An overly permissive callable script can reveal private records or accept unsafe parameters from a client or external system. Here the decisive check is Preview and resolve update set conflicts, not that separate capability.
Update set promotion dependency and rollback tracking: Out-of-order promotion or lost source identities can create untraceable production differences and make rollback unsafe. The observed issue still requires Preview and resolve update set conflicts; the proposed alternative tests another control.