{"id":15622,"date":"2026-09-18T06:08:48","date_gmt":"2026-09-18T06:08:48","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15622"},"modified":"2026-09-18T06:08:48","modified_gmt":"2026-09-18T06:08:48","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part10-q181-200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part10-q181-200\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part10 Q181-200"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/cad-exam-dumps\"><b>ServiceNow CAD Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 181<\/b><\/h3>\n<p><b>Which ServiceNow object is used to define a reusable server-side function that can be called from multiple scripts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Script Include<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Action<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Script Include is used to store reusable server-side JavaScript logic. Developers can create functions, methods, or classes inside Script Includes and call them from different server-side components. This approach reduces duplicate code and makes application logic easier to maintain. Script Includes can be used by Business Rules, Script Actions, Scheduled Script Executions, and other server-side scripts. They can also be configured as client-callable when appropriate, allowing client-side code to communicate with server-side logic through GlideAjax. UI Policies and Client Scripts primarily control client-side behavior, while UI Actions provide user interface controls.<\/span><\/p>\n<h3><b>Question 182<\/b><\/h3>\n<p><b>Which method should generally be used to save changes made to an existing GlideRecord?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">save()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">commit()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">update()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">modify()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> method is used to save changes made to an existing record. After retrieving a record and modifying one or more fields, calling <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> writes those changes back to the database. For example, a script can retrieve an incident, change its state, and then call <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> to save the new value. The <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> method is used to create a new record, while <\/span><span style=\"font-weight: 400;\">deleteRecord()<\/span><span style=\"font-weight: 400;\"> can remove an existing record. Methods such as <\/span><span style=\"font-weight: 400;\">save()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">commit()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">modify()<\/span><span style=\"font-weight: 400;\"> are not the standard GlideRecord method for updating a record in ServiceNow.<\/span><\/p>\n<h3><b>Question 183<\/b><\/h3>\n<p><b>Which component allows developers to create a custom REST endpoint within ServiceNow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scripted REST API<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transform Map<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Scripted REST API allows developers to create custom REST endpoints within ServiceNow. It provides control over the HTTP resources, methods, request processing, and responses exposed by the application. Developers can use server-side JavaScript to implement custom integration logic and return structured responses such as JSON. Client Scripts are used for browser-side form behavior, UI Policies control field states, and Transform Maps process imported data. Scripted REST APIs are useful when external applications need to interact with ServiceNow using a custom interface that is not fully covered by the platform&#8217;s standard REST APIs.<\/span><\/p>\n<h3><b>Question 184<\/b><\/h3>\n<p><b>What is the primary purpose of a REST Message in ServiceNow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create table inheritance<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define and send requests to an external REST service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To control form field visibility<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create ACL records<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A REST Message is used to configure and communicate with external REST web services. Developers can define an endpoint, HTTP methods, authentication settings, request parameters, headers, and other integration details. REST Messages can then be called from server-side scripts using APIs such as RESTMessageV2. This makes them useful for integrating ServiceNow with external systems. They are not designed for controlling form visibility, defining table inheritance, or creating ACLs. Proper authentication, error handling, and response processing should be considered when building REST integrations to ensure reliable and secure communication.<\/span><\/p>\n<h3><b>Question 185<\/b><\/h3>\n<p><b>Which method is commonly used to create a new record with GlideRecord?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">insert()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">create()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">newRecordSave()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">addRecord()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> method creates a new record in the specified table. A typical process involves creating a GlideRecord object, initializing or assigning field values, and then calling <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The method returns the <\/span><span style=\"font-weight: 400;\">sys_id<\/span><span style=\"font-weight: 400;\"> of the newly created record when the insertion succeeds. <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> is used to save modifications to an existing record. Developers should ensure that required fields and business rules are properly considered before inserting records. The methods <\/span><span style=\"font-weight: 400;\">create()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">newRecordSave()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">addRecord()<\/span><span style=\"font-weight: 400;\"> are not the standard GlideRecord methods for inserting a record into a ServiceNow table.<\/span><\/p>\n<h3><b>Question 186<\/b><\/h3>\n<p><b>Which configuration determines the fields and their order displayed on a ServiceNow form?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form Layout<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Business Rule<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ACL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transform Map<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Form Layout determines which fields appear on a form and the order in which those fields are displayed. Developers and administrators can use form configuration to organize fields into sections and create a more usable interface. Form Layout itself does not determine database security, execute server-side logic, or transform imported data. Business Rules handle server-side processing, ACLs control access, and Transform Maps handle data transformation during imports. For more advanced form customization, Form Designer and related UI configuration tools can also be used. A logical form layout helps users find and enter information efficiently.<\/span><\/p>\n<h3><b>Question 187<\/b><\/h3>\n<p><b>Which API can be used to make a server-side call from a Client Script without directly exposing database access to the browser?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideRecord<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAjax<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAggregate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideSystem<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideAjax enables a Client Script to communicate with a server-side Script Include. This architecture allows server-side processing or data retrieval to remain on the server rather than placing direct database operations in client-side code. The Script Include must be configured appropriately for client calls, and the client can send parameters through GlideAjax and process the response. GlideRecord is primarily a server-side database API, while GlideAggregate performs aggregate queries and GlideSystem provides server-side system functionality. GlideAjax is therefore an important mechanism for implementing controlled client-to-server communication in ServiceNow applications.<\/span><\/p>\n<h3><b>Question 188<\/b><\/h3>\n<p><b>Which feature is designed to restrict the records shown in a reference field based on conditions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reference Qualifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notification<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Reference Qualifier controls which records are available for selection in a reference field. It can restrict the list according to conditions, making it easier for users to select relevant records. For example, a qualifier could limit a user reference field to active users belonging to a particular department. Reference Qualifiers can be static or dynamic depending on the application&#8217;s requirements. Data Policies enforce data requirements, UI Actions provide buttons or links, and Notifications communicate information to users. Reference Qualifiers primarily improve selection and usability and should not be treated as a replacement for ACL-based security.<\/span><\/p>\n<h3><b>Question 189<\/b><\/h3>\n<p><b>Which Business Rule timing is commonly used when a developer needs to modify the current record before it is saved?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Before<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">After<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Async<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Display<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Before Business Rule runs before the current record is saved to the database. It is commonly used to modify field values, enforce server-side business logic, or set calculated values on the record before the database operation occurs. Because the changes are made before the record is written, the modified values can be saved as part of the same transaction. After Business Rules execute after the record is saved, Async Business Rules process work asynchronously, and Display Business Rules execute when records are loaded for display. Choosing Before timing is appropriate when changes need to be applied directly to the current record before saving.<\/span><\/p>\n<h3><b>Question 190<\/b><\/h3>\n<p><b>Which object provides access to fields and controls on the current ServiceNow form in client-side scripts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideRecord<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideSystem<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideForm<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAggregate<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideForm, represented by the <\/span><span style=\"font-weight: 400;\">g_form<\/span><span style=\"font-weight: 400;\"> object, provides client-side methods for interacting with the current ServiceNow form. Developers can use it to retrieve and change field values, control field visibility, set fields as mandatory or read-only, display messages, and perform other form-level operations. GlideRecord is primarily a server-side database API, GlideSystem provides server-side system functionality, and GlideAggregate performs aggregate database queries. Since Client Scripts run in the browser, GlideForm is the appropriate API for modifying the current form&#8217;s behavior. It is one of the most frequently used APIs in client-side ServiceNow development.<\/span><\/p>\n<h3><b>Question 191<\/b><\/h3>\n<p><b>Which feature can be used to define mandatory, read-only, or visible field behavior based on conditions without writing custom JavaScript?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Script Include<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Script Execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REST Message<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A UI Policy can dynamically control whether fields are mandatory, visible, or read-only based on conditions. This provides a declarative way to manage common form behavior without writing custom Client Script code. UI Policies are evaluated on the client side and can improve maintainability when the required behavior is straightforward. Script Includes store reusable server-side logic, Scheduled Script Executions run background scripts at specified times, and REST Messages support external integrations. Developers should generally prefer declarative configuration when it can satisfy the requirement because it can reduce custom code and make application behavior easier to maintain.<\/span><\/p>\n<h3><b>Question 192<\/b><\/h3>\n<p><b>Which ServiceNow feature is commonly used to run server-side JavaScript at a specified time or recurring schedule?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Script Execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Scheduled Script Executions allow developers to run server-side JavaScript according to a defined schedule. They can be configured to execute once, periodically, or according to other scheduling requirements. They are useful for background maintenance, data processing, scheduled integrations, and automated record updates. Unlike Client Scripts and UI Policies, Scheduled Script Executions do not depend on a user opening or interacting with a form. UI Actions are user-triggered interface controls. Developers should consider transaction volume and system performance when scheduling large operations, particularly when processing significant numbers of database records.<\/span><\/p>\n<h3><b>Question 193<\/b><\/h3>\n<p><b>What does the <\/b><b>deleteRecord()<\/b><b> method do in GlideRecord?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deletes the current record<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deletes the entire table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Removes a field from the table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cancels a Business Rule<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">deleteRecord()<\/span><span style=\"font-weight: 400;\"> method deletes the current record represented by the GlideRecord object. A script generally queries or retrieves a record, moves to the appropriate record using <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> or <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\">, and then calls <\/span><span style=\"font-weight: 400;\">deleteRecord()<\/span><span style=\"font-weight: 400;\">. Because deleting records can have significant consequences, developers should ensure that the correct records are selected before executing deletion logic. The method does not delete an entire table, remove fields, or disable Business Rules. In production applications, deletion logic should be carefully controlled and tested, especially when records are related to other tables or are subject to auditing and retention requirements.<\/span><\/p>\n<h3><b>Question 194<\/b><\/h3>\n<p><b>Which ServiceNow feature is primarily responsible for controlling who can access a table or field?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ACL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form Layout<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An Access Control List, or ACL, controls whether users are authorized to perform specific operations on tables and fields. ACLs can govern actions such as read, write, create, and delete. They may use roles, conditions, and scripts to determine whether access should be granted. Client Scripts and UI Policies can modify what users see or interact with on forms, but they are not substitutes for security controls. Form Layout controls presentation only. ACLs should therefore be used whenever an application requirement involves protecting data or restricting user access to records and fields.<\/span><\/p>\n<h3><b>Question 195<\/b><\/h3>\n<p><b>Which Flow Designer component is intended to package reusable automation that can be called by multiple flows?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notification<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Subflow<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary Entry<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form Layout<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Subflow is designed to package reusable automation logic that can be invoked from multiple flows or other subflows. It can accept inputs and produce outputs, allowing developers to create modular automation components. This reduces duplication because common process steps can be maintained in one location rather than recreated in every flow. Notifications handle communication, Dictionary Entries define field metadata, and Form Layout controls form presentation. Subflows are especially useful when the same business process needs to be executed from different triggers or workflows. Reusable automation also makes changes easier because common logic can be updated centrally.<\/span><\/p>\n<h3><b>Question 196<\/b><\/h3>\n<p><b>Which method can be used to determine whether a GlideRecord query returned another record during iteration?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">next()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">insert()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">update()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">initialize()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> method is commonly used to iterate through records returned by a GlideRecord query. It moves the GlideRecord object to the next available record and returns a Boolean result indicating whether a record was available. A typical pattern is <\/span><span style=\"font-weight: 400;\">while (gr.next())<\/span><span style=\"font-weight: 400;\">, which processes each record in the result set. <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> creates a new record, <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> saves changes to an existing record, and <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\"> prepares a GlideRecord object for creating a new record. Understanding <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> is essential when processing multiple database records in server-side ServiceNow scripts.<\/span><\/p>\n<h3><b>Question 197<\/b><\/h3>\n<p><b>Which ServiceNow capability is commonly used to capture configuration changes and move them between instances?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Jobs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Update Sets<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notifications<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reference Qualifiers<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Update Sets capture many types of configuration changes made in a ServiceNow instance and allow those changes to be transferred to another instance. They are commonly used when moving development changes from one environment to another, such as from development to test or production. Developers should review an Update Set before committing and transferring it to ensure the expected configuration records have been captured. Update Sets are not designed primarily for scheduled execution, notifications, or reference filtering. For application development, other deployment approaches such as source control or application repository mechanisms may also be used depending on the platform configuration.<\/span><\/p>\n<h3><b>Question 198<\/b><\/h3>\n<p><b>Which API is most appropriate for retrieving a count of records grouped by a field?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideForm<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAggregate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAjax<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideUser<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideAggregate is designed for aggregate database operations, including counting records and grouping results by fields. For example, a developer could use it to count incidents grouped by priority or state without retrieving every individual incident record. This can be more efficient than querying all records and manually calculating the counts in JavaScript. GlideForm is used for client-side form manipulation, GlideAjax supports client-to-server communication, and GlideUser provides information about the current user. Using GlideAggregate appropriately can improve performance when an application needs summarized database information rather than complete record data.<\/span><\/p>\n<h3><b>Question 199<\/b><\/h3>\n<p><b>Which type of Client Script runs when a user changes the value of a specified field?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">onLoad<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">onSubmit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">onChange<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">onDisplay<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An onChange Client Script executes when the value of a specified field changes on a form. It is commonly used to dynamically update other fields, display messages, perform client-side validation, or change form behavior based on the selected value. An onLoad Client Script runs when the form initially loads, while an onSubmit Client Script runs when the user attempts to submit the form. Choosing the correct Client Script type is important because each one has a different execution point. Developers should also avoid unnecessary client-side processing to maintain responsive form performance.<\/span><\/p>\n<h3><b>Question 200<\/b><\/h3>\n<p><b>Which statement correctly describes a ServiceNow application scope?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It prevents an application from containing tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It provides boundaries for application artifacts and controls cross-application access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It only affects the application&#8217;s user interface<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It automatically grants all users access to application data<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Application scope provides boundaries around application artifacts, logic, and data and helps control how applications interact with one another. Scoped applications can contain tables, scripts, modules, Business Rules, Script Includes, and other components. When one application needs to access resources belonging to another scope, appropriate cross-scope permissions or privileges may be required. Scope is therefore important for reducing unintended interference between applications and establishing clear ownership of application components. It does not prevent applications from having tables, only affect the user interface, or automatically grant users access to application data. Security is separately managed through roles, ACLs, and other controls.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 181 Which ServiceNow object is used to define a reusable server-side function that can be called from multiple scripts? UI Policy Script Include Client Script UI Action Correct Answer: 2 Explanation A Script Include is used to store reusable server-side JavaScript logic. Developers [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15622"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=15622"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15622\/revisions"}],"predecessor-version":[{"id":15644,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15622\/revisions\/15644"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}