UI Policiesare the preferred method to dynamically control the visibility, read-only state, or mandatory status of form fieldswithout requiring a page reload.
Best Practicesuggests usingUI Policiesover Client Scripts whenever possible because UI Policies execute on the client side and are easier to manage.
Theydo not require scriptingin most cases and provide asimple rule-based approach.
Explanation of Incorrect Options:
Client Scripts (A)# Used for executing JavaScript logic in the browser, but making fields mandatory or hidden should be done via UI Policies.
Business Rules (C)# Run on the server-side and do not directly affect form fields in real-time.
UI Actions (D)# Used for creating buttons, links, or context menu actions;not for modifying field properties.
Reference:
ServiceNow Docs - UI Policies

Assignment Rulesin ServiceNow automaticallyassign tasks(such as incidents, service requests, or change requests) to theappropriate group or individualbased on predefined criteria.
Acritical, high-priority service requestis created.
TheAssignment Rulechecks conditions (e.g., priority, category, requester, etc.).
The systemassignsthe request to the correctassignment group or individual.
How Assignment Rules Work:Example Scenario:
If an incident isPriority 1 (P1)and the category isNetwork, an assignment rule canautomatically route it to the
"Network Support" group.
A: User Policy
No such feature exists in ServiceNow for task assignments.
B: UI Policy
UI Policies controlform behavior (visibility, field conditions, etc.), not assignment logic.
C: Predictive Intelligence
Predictive Intelligence usesmachine learningto suggest assignments, butAssignment Rulesare the primary mechanism for automatic task allocation.
Reference:ServiceNow CSA Documentation - Configuring Assignment Rules
ServiceNow Official Documentation - Automating Task Assignments(https://docs.servicenow.com) Final answer: D. Assignment Rule