When using the Data Pill Picker, use which keys to dot-walk (6 fields in other tables?
Correct Answer: D
When using theData Pill Pickerin Flow Designer,dot-walkingis used to access fields inrelated tables. The shortcut fordot-walkingin theData Pill Pickeris:#Ctrl<and Ctrl> Dot-walkingallows users toaccess fields in referenced records. For example, if you have anIncidentrecord with aCallerfield (which references thesys_usertable), you candot- walkto theCaller's emailusing: What is Dot-Walking?CopyEdit incident.caller.email This is useful whenbuilding conditions, flows, and reportsin ServiceNow. A). Arrows- Arrow keys are used for navigation, but they do not support dot-walking. B). Plus, Minus- These keys arenot used for dot-walkingin ServiceNow. C). Ctrl C, Ctrl- These are copy-paste shortcuts, unrelated to dot-walking. E). Shift F4, Shift F5- These do not have any function related to dot-walking. ServiceNow Dot-Walking & Data Pill Picker ServiceNow CSA Training Module:"Using Dot-Walking in Flow Designer and Reporting" Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:
Question 192
What is the difference between a UI Policy and Data Policy?
Correct Answer: C
In ServiceNow, UI Policies and Data Policies serve different but complementary purposes in controlling data behavior and enforcing business rules. UI Policies: UI Policies are client-side rules that dynamically change form behavior based on user interactions. They enable administrators to show/hide fields, make fields read-only, or set fields as mandatory dynamically. UI Policies only apply when a user is interacting with a form through the ServiceNow UI (Client-side execution). These policies do not enforce rules if data is added via an Import Set, API, or background script. Data Policies: Data Policies enforce rules server-side, meaning they apply regardless of how data is entered (e.g., form submission, Import Sets, SOAP/REST API calls, or Business Rules). They ensure data integrity by making fields mandatory, setting read-only properties, or applying other restrictions. Data Policies can apply conditions globally, unlike UI Policies, which work only in the UI context. Key Differences: Feature UI Policy Data Policy Scope Affects only forms (Client-side) Affects all data entry points (Server-side) Execution Location Runs in the browser Runs on the server Triggers User interaction on the form Any data entry method (Forms, Import Sets, API, etc.) Enforcement Works only when using the UI Applies even when data is added outside the UI Why Option C is Correct: "Data Policies run regardless of how data is entered into ServiceNow" → Correct, because Data Policies enforce rules whether the data is entered via UI, API, Import Sets, or other means. "UI Policies are used for form interactions" → Correct, because UI Policies apply only to client-side form behavior. Why Other Options are Incorrect: Option A: Incorrect. UI Policies are not set by web services; they are applied when interacting with forms. Option B: Incorrect. While some Data Policies can be converted into UI Policies, the reverse is not true in all cases. Option D: Incorrect. UI Policies and Data Policies operate independently, and Data Policies do not depend on UI Policies running first. Reference: For official documentation, refer to: ServiceNow Docs - UI Policies ServiceNow Docs - Data Policies ServiceNow Community - UI Policy vs Data Policy
Question 193
What is the name of the conversational bot platform that provides assistance to help users obtain information, make decisions, and perform common tasks?
Correct Answer: C
Theconversational bot platforminServiceNowthat helps usersobtain information, make decisions, and perform common tasksis calledVirtual Agent. What is Virtual Agent?Virtual Agent is achatbot frameworkin ServiceNow that allows users to interact with the system usingnatural language processing (NLP). It automates responses, guides users through processes, and integrates with ServiceNow workflows to resolve requests efficiently. Conversational AI & Automation Uses AI andNatural Language Understanding (NLU)to interpret user input and provide relevant responses. Predefined Topics & Custom Topics Comes with pre-built conversation topics (e.g., resetting passwords, requesting IT help) and allows organizations to create custom topics. Multi-Channel Support Works with platforms likeMicrosoft Teams, Slack, ServiceNow Chat, and web portals. Self-Service Capabilities Enables users to resolve issueswithoutcontacting the Service Desk, improving efficiency. Integration with ServiceNow Workflows Can trigger workflows tocreate incidents, update records, retrieve knowledge articles, or complete approvals. A). Answer Agent Incorrect: There is no feature named "Answer Agent" in ServiceNow. B). Live Feed Incorrect:Live Feedis a social collaboration tool in ServiceNow that allows users to post updates and interact with others, similar to a message board. It does not provide AI-based conversational assistance. D). Connect Chat Incorrect:Connect Chatis ServiceNow's real-timecollaborative chat system, used for direct communication between users and support agents, but it isnot an AI-driven Virtual Agent. Key Features of Virtual Agent:Why Other Options Are Incorrect? ServiceNow Product Documentation - Virtual Agent Virtual Agent Overview Setting Up Virtual Agent ServiceNow Conversational Interfaces Virtual Agent vs. Connect Chat References from ServiceNow CSA Documentation:
Question 194
A change request has been approved and assigned to you as the system administrator to change the Incident number prefix from the default of "INC" to the company standard IN." What are the next steps to be taken''
Correct Answer: A
In ServiceNow, Number Maintenance is the application used to manage and modify numbering schemes for different tables, including the Incident table. Since the default prefix for Incident numbers is "INC", an administrator can modify it to a company-specific prefix (e.g., "IN") by following these steps: Steps to Change the Incident Number Prefix: Navigate to the Number Maintenance Application: Go to All → System Definition → Number Maintenance Search for the Incident table (task.number record for Incident). Modify the Prefix: Open the existing Incident numbering record. Change the Prefix from "INC" to "IN". Ensure the Next Number field is correctly set (e.g., "IN0001001"). Save the Changes: Click Update to apply the new prefix. All newly created incidents will now follow the new format (IN0001001). Existing incidents are NOT affected-only newly created records will reflect the new prefix. Why Option A (Number Maintenance) is Correct? ✅ The Number Maintenance application is the correct place to modify prefixes for tables like Incident. Why Other Options Are Incorrect? ❌ B. Create a Business Rule that modifies the prefix before the Insert operation → Incorrect Business Rules do not control number generation. Number generation is managed by Number Maintenance at the system level. ❌ C. The prefix of an incident cannot be changed because it is a built-in feature → Incorrect The prefix CAN be changed using the Number Maintenance application. Only existing records retain their original prefix; new records follow the updated format. ❌ D. Submit a Change Request to ServiceNow Technical Support → Incorrect This is not necessary, as administrators can make this change directly through Number Maintenance. Reference from Certified System Administrator (CSA) Documentation: ServiceNow Docs - Number Maintenance Configuration https://docs.servicenow.com ServiceNow Learning - Customizing Numbering Schemes ServiceNow Developer Portal - Number Prefix Best Practices
Question 195
Farm a form, what would you click, to modify the order of the fields on the form? Choose 2 answers