✔UI Policiesare the best way to implement dynamic form behavior such asmaking fields mandatory, hiding/showing fields, and setting values based on conditions.

Making " Resolution Code " mandatory when " State " is changed to " Resolved "

This requires aUI Policythat:

Condition:State = Resolved

Action:Set " Resolution Code " field toMandatory = True

Hiding the " Major Incident " checkbox unless the logged-in user has the " Major Incident Manager " role

This requires anotherUI Policythat:

Condition:User does NOT have the rolemajor_incident_manager

Action:Hide the field

Option A (Dictionary Design)

The dictionary defines the structure of fields butdoes not control dynamic form behaviorlike field visibility or conditions.

Option B (Field Limiter)

There is no such feature called " Field Limiter " in ServiceNow.

Option D (UI Design)

" UI Design " is not a recognized concept in ServiceNow.UI Policiesare used for form behavior changes.

Option E (Form Constraint)

There is no " Form Constraint " feature in ServiceNow; ACLs and UI Policies control field behavior instead.