# UI Policies are the best way to implement dynamic form behavior such as making fields mandatory, hiding
/showing fields, and setting values based on conditions.
* Making "Resolution Code" mandatory when "State" is changed to "Resolved"
* This requires a UI Policy that:
* Condition: State = Resolved
* Action: Set "Resolution Code" field to Mandatory = True
* Hiding the "Major Incident" checkbox unless the logged-in user has the "Major Incident Manager" role
* This requires another UI Policy that:
* Condition: User does NOT have the role major_incident_manager
* Action: Hide the field
* Option A (Dictionary Design) #
* The dictionary defines the structure of fields but does not control dynamic form behavior like 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 Policies are 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.
Reference: ServiceNow UI Policy Documentation (Platform Configuration)

In ServiceNow, when building filter conditions using theCondition Builder, there are three key components:
Field (Filter Criteria):The specific database field you are filtering on.
Operator:A choice list that defines the condition (e.g., "is", "contains", "starts with").
Value:The value you are checking against.
Among these components,the Operator is always a choice list, as it provides predefined options for filtering.
The Operator determines how the Field and Value should be compared. For example:
"State is Active"(where "is" is the Operator)
"Priority is greater than 2"(where "is greater than" is the Operator)
Other components, such as Filter Criteria (fields) and Match Criteria, do not always function as choice lists.
Reference:
ServiceNow Condition Builder Documentation
ServiceNow CSA Training Material

TheServiceNow platformprovides variousinterfacesfor users to interact with the system based on their role and requirements. These interfaces cater to different use cases, such as web-based, mobile, and portal-based access.
Now Mobile Apps (A) -Correct
ServiceNow providesNow Mobile applicationsfor bothiOS and Android.
These apps allow users to access self-service options, request services, check approvals, and complete tasks from mobile devices.
Apps includeNow Mobile, Field Service Mobile, and Mobile Agent.
Service Portals (D) -Correct
Service Portalsprovide auser-friendly web interfacethat allows users tosubmit requests, search for knowledge, and interact with catalog itemsin a simplified way.
Service Portals are customizable and used forself-service and customer-facing interactions.
Now Platform User Interfaces (E) -Correct
This includes the standardUI16 (Current Web Interface), UI Builder for custom interfaces, and theClassic UIfor legacy systems.
Users can access ServiceNow throughdesktop web browsers, mobile web interfaces, and UI frameworks.
B: Agent Control Center(Incorrect)
No such predefined interface exists in ServiceNow as "Agent Control Center." C: Back Office Dashboard(Incorrect) This is not a standard ServiceNow interface but may be a custom-built dashboard.
F: Field Service Taskboard(Incorrect)
This is afeaturewithinField Service Management (FSM), not a platform-wide interface.
ServiceNow User Interfaces Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user- interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html Now Mobile App:https://docs.servicenow.com/en-US/bundle/utah-now-mobile/page/administer/service-now- mobile/concept/now-mobile-overview.html Types of Interfaces in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation: