{"id":15626,"date":"2026-09-18T06:08:10","date_gmt":"2026-09-18T06:08:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15626"},"modified":"2026-09-18T06:08:10","modified_gmt":"2026-09-18T06:08:10","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part13-q241-260","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part13-q241-260\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part13 Q241-260"},"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 241<\/b><\/h3>\n<p><b>Which ServiceNow object is primarily used to define reusable server-side logic that can be called from other server-side 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 designed to store reusable server-side JavaScript logic in ServiceNow. Instead of writing the same functionality repeatedly in Business Rules, Scripted REST APIs, or other server-side components, developers can place the logic inside a Script Include and call it when required. Script Includes can contain functions, classes, or utility methods. They execute on the server and can also be configured as client-callable when used with GlideAjax. Proper use of Script Includes improves application maintainability, reduces duplicated code, and provides a centralized location for commonly used business logic.<\/span><\/p>\n<h3><b>Question 242<\/b><\/h3>\n<p><b>Which method is commonly used with GlideRecord to retrieve a single record using its <\/b><b>sys_id<\/b><b>?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">get()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">query()<\/span><\/li>\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;\">addQuery()<\/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;\">get()<\/span><span style=\"font-weight: 400;\"> method is commonly used when a developer needs to retrieve a specific record using its unique <\/span><span style=\"font-weight: 400;\">sys_id<\/span><span style=\"font-weight: 400;\"> or another uniquely identifying field. For example, <\/span><span style=\"font-weight: 400;\">gr.get(sys_id)<\/span><span style=\"font-weight: 400;\"> retrieves the corresponding record and positions the GlideRecord object on that record. This differs from <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\">, which executes a query that can return multiple records. The <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> method is then generally used to iterate through records returned by a query. Using <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\"> is convenient when the exact record is already known and only one record needs to be accessed.<\/span><\/p>\n<h3><b>Question 243<\/b><\/h3>\n<p><b>Which Client Script type executes when a user changes the value of a field on a form?<\/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;\">onCellEdit<\/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. Developers commonly use it to dynamically respond to user input, such as making another field mandatory, changing a field&#8217;s visibility, setting a default value, or validating related information. The script can use the <\/span><span style=\"font-weight: 400;\">g_form<\/span><span style=\"font-weight: 400;\"> object to manipulate fields on the current form. An onLoad Client Script runs when the form loads, while an onSubmit Client Script runs when the user attempts to submit the form. Choosing the correct Client Script type helps ensure the desired behavior occurs at the appropriate point.<\/span><\/p>\n<h3><b>Question 244<\/b><\/h3>\n<p><b>What is the main purpose of a Transform Map in ServiceNow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To control user authentication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create UI buttons<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define field mappings between an import set and a target table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To schedule recurring scripts<\/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;\">A Transform Map defines how data from an Import Set is transformed and loaded into a target ServiceNow table. It can map source fields to target fields and can also contain transformation logic, scripts, and coalesce settings. During the transformation process, ServiceNow uses the Transform Map to determine how imported data should be processed. This makes Transform Maps especially useful when importing information from external systems or files such as CSV data. Import Sets provide the staging area, while Transform Maps determine how that staged data is converted into records in the destination table.<\/span><\/p>\n<h3><b>Question 245<\/b><\/h3>\n<p><b>Which object provides methods for manipulating the current form from a Client Script?<\/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, commonly accessed through 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 set field values, make fields mandatory, hide or display fields, disable fields, show messages, and perform other form-related operations. GlideForm runs in the browser and is therefore primarily associated with Client Scripts and other client-side components. GlideRecord, in contrast, is primarily a server-side API for querying and manipulating database records. Understanding the distinction between client-side APIs such as GlideForm and server-side APIs such as GlideRecord is important for ServiceNow application development.<\/span><\/p>\n<h3><b>Question 246<\/b><\/h3>\n<p><b>What is the primary purpose of an Access Control (ACL) rule?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To control access to data and operations<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To import external data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create scheduled jobs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define application navigation<\/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;\">Access Control rules, commonly called ACLs, determine whether users can access specific ServiceNow resources and perform particular operations. ACLs can control access at different levels, including tables, records, fields, and operations such as read, write, create, and delete. ServiceNow evaluates applicable ACL rules when determining whether a user is allowed to perform an action. Roles, conditions, and scripts can be involved in ACL evaluation. ACLs are an important part of application security because they help ensure users can only access or modify information for which they have appropriate permissions.<\/span><\/p>\n<h3><b>Question 247<\/b><\/h3>\n<p><b>Which API is commonly used to perform database queries and manipulate records on the ServiceNow server?<\/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;\">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;\">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;\">GlideRecord is the primary server-side API used to interact with records stored in ServiceNow tables. Developers can use GlideRecord to query records, insert new records, update existing records, and delete records. Common methods include <\/span><span style=\"font-weight: 400;\">addQuery()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">deleteRecord()<\/span><span style=\"font-weight: 400;\">. GlideRecord should generally be used carefully because inefficient database queries can affect application performance. Developers should apply appropriate query conditions and avoid unnecessary database operations. GlideForm is used for client-side form manipulation, while GlideAjax is primarily used to communicate from client-side scripts to server-side Script Includes.<\/span><\/p>\n<h3><b>Question 248<\/b><\/h3>\n<p><b>What does the <\/b><b>coalesce<\/b><b> option in a Transform Map determine?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which fields appear on a form<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which users receive notifications<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How application scopes are created<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How incoming records are matched to existing records<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Coalescing in a Transform Map determines how incoming import data is matched against existing records in the target table. When a field is marked as a coalesce field, ServiceNow uses that field to determine whether an imported row corresponds to an existing record. If a matching record is found, the existing record can be updated. If no match is found, a new record can be inserted, depending on the transformation configuration. Coalescing is particularly useful when importing data repeatedly from external systems because it helps prevent unnecessary duplicate records and allows existing records to be maintained.<\/span><\/p>\n<h3><b>Question 249<\/b><\/h3>\n<p><b>Which Business Rule type executes after a database operation has been completed?<\/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;\">Display<\/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<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An After Business Rule executes after the database operation has been completed. It is commonly used when a developer needs to perform additional server-side processing based on a record that has already been inserted, updated, or deleted. Before Business Rules execute before the database action and are often used to modify values before they are saved. Async Business Rules execute asynchronously after the database operation, allowing processing to occur without making the user wait for completion. Display Business Rules execute when a record is being prepared for display and are commonly used to make server-side information available to client-side scripts.<\/span><\/p>\n<h3><b>Question 250<\/b><\/h3>\n<p><b>Which ServiceNow component is used to create custom buttons, links, or menu items on forms and lists?<\/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;\">UI Policy<\/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;\">Data Policy<\/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 Action is used to create interactive buttons, links, and menu items within ServiceNow forms and lists. UI Actions can execute server-side or client-side scripts depending on their configuration. For example, a developer could create a button that changes a record&#8217;s state, creates a related record, or performs a custom operation. UI Policies are instead used to dynamically control form field behavior, while Dictionary Entries define metadata about fields. Data Policies enforce data requirements during record operations. UI Actions therefore provide a flexible mechanism for adding custom user interactions to ServiceNow applications.<\/span><\/p>\n<h3><b>Question 251<\/b><\/h3>\n<p><b>Which method executes a GlideRecord query after query conditions have been defined?<\/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;\">query()<\/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;\">initialize()<\/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;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> method executes the database query after query conditions have been established. Developers commonly use <\/span><span style=\"font-weight: 400;\">addQuery()<\/span><span style=\"font-weight: 400;\"> to specify conditions and then call <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> to retrieve matching records. Once the query has executed, the <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> method is normally used to iterate through the returned records. For example, a script can create a GlideRecord object, add a condition, execute <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\">, and then process each matching record with <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\">. Understanding this sequence is fundamental to writing effective server-side ServiceNow scripts and helps developers retrieve only the records needed for processing.<\/span><\/p>\n<h3><b>Question 252<\/b><\/h3>\n<p><b>What is the primary purpose of a ServiceNow application scope?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To increase database storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To automatically create users<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define application boundaries and control access to application artifacts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To replace all ACLs<\/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;\">Application scope establishes boundaries around an application and its artifacts in ServiceNow. It helps identify which application owns tables, scripts, modules, and other components. Scope also provides protection between applications and controls how application artifacts can be accessed across scope boundaries. Cross-scope access may require explicit permissions or configuration. Application scope is therefore important for developing modular applications and preventing unintended interference between different applications. It does not replace ACLs, because ACLs continue to control user access to data and operations. Scope primarily concerns application boundaries and artifact ownership rather than end-user authorization.<\/span><\/p>\n<h3><b>Question 253<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to package application changes for movement between instances?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Update Set<\/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;\">Data Lookup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reference Qualifier<\/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;\">Update Sets are commonly used to capture configuration changes made in one ServiceNow instance so those changes can be moved to another instance. Developers can create an update set, make application configuration changes, complete the update set, and then transfer it to another instance for testing or deployment. Update Sets can capture many configuration records, but not every type of data or configuration should automatically be assumed to be included. Developers should review captured changes before deployment. Proper update-set management helps maintain controlled development and promotion processes across development, test, and production environments.<\/span><\/p>\n<h3><b>Question 254<\/b><\/h3>\n<p><b>Which API is commonly used with GlideAjax to retrieve server-side information from a client-side script?<\/b><\/p>\n<ol>\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;\">GlideForm<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideRecordSecure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Script Include<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideAjax is commonly used when a client-side script needs to communicate with server-side logic. The server-side logic is typically placed in a Script Include configured to be client callable. The Client Script creates a GlideAjax request, passes parameters, and requests the server-side function. The Script Include processes the request and returns the required information. This approach allows developers to retrieve server-side information without directly using GlideRecord from the browser. It is useful for dynamically retrieving data, validating information, or calculating values that require server-side access while keeping database operations on the server.<\/span><\/p>\n<h3><b>Question 255<\/b><\/h3>\n<p><b>What does a Reference Qualifier primarily control?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which records are available for selection in a reference field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which users can log into ServiceNow<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which Business Rules execute first<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Which tables can be extended<\/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 Reference Qualifier controls which records are available for selection in a reference field. It applies filtering conditions to the referenced table so users see only relevant records. For example, a reference field for selecting a user could be configured to show only active users belonging to a particular department. Reference Qualifiers can be static, dynamic, or scripted depending on the application&#8217;s requirements. They improve usability and data quality by preventing users from selecting irrelevant records. However, a Reference Qualifier should not be treated as a replacement for security controls such as ACLs.<\/span><\/p>\n<h3><b>Question 256<\/b><\/h3>\n<p><b>Which Flow Designer component is designed to provide a reusable sequence of automation that can be called from multiple flows?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Trigger<\/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;\">Data Pill<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Condition<\/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 in Flow Designer provides a reusable sequence of actions that can be invoked from multiple flows or other automation. This allows developers to avoid duplicating the same sequence of actions across different flows. A Subflow can accept inputs and produce outputs, making it suitable for reusable business processes. For example, a common approval or notification process could be implemented once as a Subflow and then reused in multiple flows. This improves maintainability because changes to shared logic can be made in one location rather than requiring developers to modify multiple independent flows.<\/span><\/p>\n<h3><b>Question 257<\/b><\/h3>\n<p><b>Which method is 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;\">update()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">query()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">next()<\/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 target ServiceNow table. Typically, a developer first creates a GlideRecord object, calls <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\">, sets the required field values, and then calls <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> method is generally used to save changes to an existing record rather than create a new one. <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> retrieves records, while <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> moves through records returned by a query. Developers should ensure that required fields and appropriate values are supplied before calling <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> so that the new record can be created successfully.<\/span><\/p>\n<h3><b>Question 258<\/b><\/h3>\n<p><b>Which Client Script type is intended to run when a form is initially loaded?<\/b><\/p>\n<ol>\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;\">onSubmit<\/span><\/li>\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;\">onCellEdit<\/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 onLoad Client Script executes when a ServiceNow form is initially loaded. It is commonly used to configure the form based on the current record, user information, or other client-side conditions. For example, an onLoad script might hide a field, set a field value, or display a message when the form opens. An onChange script responds to changes in a particular field, while an onSubmit script executes when the user attempts to save the form. Choosing the correct Client Script type ensures that client-side logic executes at the appropriate stage of the user&#8217;s interaction with the form.<\/span><\/p>\n<h3><b>Question 259<\/b><\/h3>\n<p><b>Which ServiceNow feature is specifically designed to enforce field requirements and conditions for data operations across different interfaces?<\/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;\">Data Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Macro<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application Menu<\/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 Data Policy is used to enforce data requirements and conditions when records are created or updated. Unlike a UI Policy, which primarily controls behavior on a form, a Data Policy can help enforce requirements beyond a particular user interface. This makes Data Policies useful when consistent data requirements need to be applied across different methods of entering or updating information. For example, a field can be required when certain conditions are met. Data Policies contribute to data consistency and quality while UI Policies are more focused on dynamically controlling field behavior on forms.<\/span><\/p>\n<h3><b>Question 260<\/b><\/h3>\n<p><b>Which ServiceNow API provides access to system-level functions such as logging messages and retrieving system information?<\/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;\">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;\">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;\">GlideSystem, commonly accessed through the <\/span><span style=\"font-weight: 400;\">gs<\/span><span style=\"font-weight: 400;\"> object, provides server-side methods for interacting with the ServiceNow system environment. Developers use GlideSystem for functions such as logging messages, obtaining user information, checking roles, generating messages, and accessing various system-level utilities. Common examples include <\/span><span style=\"font-weight: 400;\">gs.info()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">gs.error()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">gs.getUser()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">gs.hasRole()<\/span><span style=\"font-weight: 400;\">. GlideSystem is different from GlideRecord, which focuses on database records, and GlideForm, which operates on forms in the client. Understanding GlideSystem is important because many server-side scripts rely on its methods for system interaction and debugging.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 241 Which ServiceNow object is primarily used to define reusable server-side logic that can be called from other server-side scripts? UI Policy Script Include Client Script UI Action Correct Answer: 2 Explanation A Script Include is designed to store reusable server-side JavaScript logic [&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\/15626"}],"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=15626"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15626\/revisions"}],"predecessor-version":[{"id":15641,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15626\/revisions\/15641"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15626"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15626"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15626"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}