{"id":15625,"date":"2026-09-18T06:08:23","date_gmt":"2026-09-18T06:08:23","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15625"},"modified":"2026-09-18T06:08:23","modified_gmt":"2026-09-18T06:08:23","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part12-q221-240","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part12-q221-240\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part12 Q221-240"},"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 221<\/b><\/h3>\n<p><b>Which ServiceNow API is used to retrieve the display value of a field?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">getValue()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">getDisplayValue()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">getLabel()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">getFieldValue()<\/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 <\/span><span style=\"font-weight: 400;\">getDisplayValue()<\/span><span style=\"font-weight: 400;\"> method is used with GlideRecord to retrieve the human-readable display value of a field. This is especially useful for reference fields because the database may store a <\/span><span style=\"font-weight: 400;\">sys_id<\/span><span style=\"font-weight: 400;\"> while the user sees a meaningful name. For example, a reference field may store a user&#8217;s unique identifier but display the user&#8217;s name. <\/span><span style=\"font-weight: 400;\">getValue()<\/span><span style=\"font-weight: 400;\"> retrieves the underlying field value, while <\/span><span style=\"font-weight: 400;\">getDisplayValue()<\/span><span style=\"font-weight: 400;\"> retrieves the value intended for display. Developers should understand the difference between these methods when working with reference fields, choice fields, and other data types where stored values and displayed values may differ.<\/span><\/p>\n<h3><b>Question 222<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to create a custom button on a form that performs an action?<\/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;\">Business Rule<\/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 can create buttons, links, or contextual actions on ServiceNow forms and lists. A UI Action can execute client-side or server-side logic depending on its configuration. For example, developers can create a button that changes a record&#8217;s state, creates a related record, or performs another custom operation. UI Policies control field behavior, Business Rules execute server-side logic based on database operations, and Data Policies enforce data requirements. UI Actions are therefore appropriate when the requirement involves giving users a visible control that triggers a specific operation.<\/span><\/p>\n<h3><b>Question 223<\/b><\/h3>\n<p><b>Which Business Rule type is executed when a record is displayed to a user?<\/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;\">Display<\/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;\">A Display Business Rule runs when a record is loaded for display. It can be used to prepare server-side information that needs to be made available to client-side scripts through mechanisms such as the <\/span><span style=\"font-weight: 400;\">g_scratchpad<\/span><span style=\"font-weight: 400;\"> object. Display Business Rules execute before the form is presented to the user. Before Business Rules run before a database operation, After Business Rules execute after the record is saved, and Async Business Rules process work asynchronously. Developers should use Display Business Rules carefully and only when server-side information is needed during form loading because unnecessary processing can increase form-load time.<\/span><\/p>\n<h3><b>Question 224<\/b><\/h3>\n<p><b>Which object is commonly used to access the current user&#8217;s roles in server-side scripting?<\/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;\">GlideUser<\/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;\">GlideAggregate<\/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;\">GlideUser provides functionality for working with information about the current user in ServiceNow. Depending on the scripting context, developers can use user-related methods to determine information such as roles, groups, or user identity. This can be useful when implementing business logic that depends on the current user&#8217;s context. GlideForm is primarily a client-side form API, GlideRecord is used for database operations, and GlideAggregate performs aggregate queries. However, role checks in server-side logic should complement, rather than replace, proper ACL configuration when the requirement involves enforcing data security.<\/span><\/p>\n<h3><b>Question 225<\/b><\/h3>\n<p><b>What is the main purpose of a Data Lookup?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To automatically determine field values based on matching conditions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create database tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To execute scheduled scripts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define ACL permissions<\/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;\">Data Lookup allows ServiceNow to automatically populate or determine field values based on predefined matching conditions. For example, a lookup can determine a value for one field based on another field or a combination of values. This reduces the need for users to manually enter information and can help standardize data. Data Lookup is different from a Transform Map, which is primarily used during data import processing. ACLs control security, Scheduled Script Executions run server-side scripts on a schedule, and tables define data structures. Proper lookup configuration can improve consistency and reduce repetitive user input.<\/span><\/p>\n<h3><b>Question 226<\/b><\/h3>\n<p><b>Which method is commonly used to check whether a GlideRecord query contains another record during iteration?<\/b><\/p>\n<ol>\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;\">insert()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">update()<\/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 <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> method is used to move through the records returned by a GlideRecord query. It returns true when another record is available and positions the GlideRecord object on that record. A common pattern is <\/span><span style=\"font-weight: 400;\">while (gr.next())<\/span><span style=\"font-weight: 400;\">, which processes each returned record one at a time. The <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> method executes the query but does not itself iterate through the results. <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> creates a new record, while <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> saves modifications to an existing record. Understanding the distinction between <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> is essential for correctly processing database results in ServiceNow scripts.<\/span><\/p>\n<h3><b>Question 227<\/b><\/h3>\n<p><b>Which feature provides reusable server-side JavaScript logic that can be called by multiple application components?<\/b><\/p>\n<ol>\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;\">Form Layout<\/span><\/li>\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;\">UI 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 Script Include stores reusable server-side JavaScript logic. It can contain functions, classes, and methods that can be called from different server-side application components. This promotes code reuse and prevents developers from duplicating the same logic in multiple Business Rules or other scripts. Script Includes can also be configured for client-side access when appropriate, allowing GlideAjax to communicate with them. Form Layout controls field arrangement, Notifications send messages, and UI Policies control client-side field behavior. Centralizing reusable logic in Script Includes generally makes applications easier to maintain, test, and update.<\/span><\/p>\n<h3><b>Question 228<\/b><\/h3>\n<p><b>Which component is used to enforce security at the field level?<\/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;\">Field 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;\">A field-level Access Control List, or field ACL, can control whether a user is allowed to perform operations such as reading or writing a particular field. Field ACLs are an important security mechanism because they enforce access at the platform level. UI Policies and Client Scripts can change how fields appear or behave on forms, but they should not be used as security controls because client-side logic can be bypassed. Form Layout only controls presentation. Developers should configure appropriate field-level ACLs whenever an application requires certain fields to be accessible only to authorized users or roles.<\/span><\/p>\n<h3><b>Question 229<\/b><\/h3>\n<p><b>Which ServiceNow component can be used to run JavaScript periodically without requiring a user to interact with the system?<\/b><\/p>\n<ol>\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;\">Scheduled Script Execution<\/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;\">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 server-side JavaScript to run according to a defined schedule. They can execute once or repeatedly at configured intervals and are useful for background processing, maintenance activities, data updates, and scheduled integrations. Client Scripts require a user interface interaction, while UI Actions are normally triggered by users and UI Policies control form behavior. Scheduled processing should be designed carefully because large database operations can consume system resources. Developers should also consider query efficiency and transaction volume when creating recurring scheduled scripts.<\/span><\/p>\n<h3><b>Question 230<\/b><\/h3>\n<p><b>Which ServiceNow feature is used to define fields, their data types, and other metadata?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary<\/span><\/li>\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;\">UI Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Flow Designer<\/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 Dictionary contains metadata that defines tables and fields within ServiceNow. Dictionary Entries can specify field types, lengths, default values, reference relationships, attributes, and other characteristics. Developers and administrators use dictionary configuration to define how data is structured and behaves at the field level. Notifications are used for communication, UI Actions create user-triggered controls, and Flow Designer is used for process automation. Understanding dictionary configuration is important because many platform behaviors depend on field metadata. Developers should make dictionary changes carefully because they can affect forms, lists, scripts, integrations, and existing data.<\/span><\/p>\n<h3><b>Question 231<\/b><\/h3>\n<p><b>Which API is commonly used to log informational messages from server-side scripts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">g_form<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">gr<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">currentForm<\/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 <\/span><span style=\"font-weight: 400;\">gs<\/span><span style=\"font-weight: 400;\"> object represents GlideSystem and provides various server-side system functions. Developers can use methods such as <\/span><span style=\"font-weight: 400;\">gs.info()<\/span><span style=\"font-weight: 400;\"> to write informational messages to the system log during development and troubleshooting. GlideSystem also provides functionality related to users, properties, messages, dates, and other platform services. The <\/span><span style=\"font-weight: 400;\">g_form<\/span><span style=\"font-weight: 400;\"> object is associated with GlideForm and is primarily used on the client side. <\/span><span style=\"font-weight: 400;\">gr<\/span><span style=\"font-weight: 400;\"> is commonly used as a developer-created variable name for GlideRecord but is not a system API itself. Server-side logging can be valuable when debugging application logic and identifying unexpected execution behavior.<\/span><\/p>\n<h3><b>Question 232<\/b><\/h3>\n<p><b>Which feature is designed to automate business processes using a visual, low-code interface?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Flow Designer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary<\/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: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Flow Designer provides a visual, low-code environment for building automated business processes. Developers and administrators can use triggers, actions, conditions, subflows, and other components to automate tasks and processes. Flow Designer can integrate with ServiceNow applications and, where configured, external systems. Dictionary configuration defines field metadata, ACLs provide security, and Form Layout controls form presentation. Flow Designer is particularly useful when automation requirements can be implemented without extensive custom scripting. Custom actions and subflows can also extend its capabilities for more specialized application requirements.<\/span><\/p>\n<h3><b>Question 233<\/b><\/h3>\n<p><b>Which method can be used to remove a GlideRecord from the database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">remove()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">deleteRecord()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">erase()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">deleteRow()<\/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 <\/span><span style=\"font-weight: 400;\">deleteRecord()<\/span><span style=\"font-weight: 400;\"> method is used to delete the current record represented by a GlideRecord object. Before calling this method, developers should make sure that the GlideRecord points to the intended record. Deletion operations should be used carefully because removing records can affect related data and application processes. The methods <\/span><span style=\"font-weight: 400;\">remove()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">erase()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">deleteRow()<\/span><span style=\"font-weight: 400;\"> are not the standard GlideRecord method for deleting a record. In production applications, developers should consider whether records should actually be deleted or whether another approach, such as marking them inactive, is more appropriate.<\/span><\/p>\n<h3><b>Question 234<\/b><\/h3>\n<p><b>Which ServiceNow feature is used to define conditions and actions that control field behavior on forms?<\/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;\">REST Message<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Import Set<\/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: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">UI Policies allow developers to define conditions that dynamically control field behavior on forms. They can make fields mandatory, visible, or read-only depending on the current form state. UI Policies provide a declarative alternative to custom JavaScript for many common client-side requirements. REST Messages are used for external integrations, Import Sets bring external data into ServiceNow, and Script Includes store reusable server-side logic. Developers should prefer UI Policies when they can satisfy a requirement without custom scripting because declarative configurations are generally easier to understand and maintain.<\/span><\/p>\n<h3><b>Question 235<\/b><\/h3>\n<p><b>Which statement about a reference field is correct?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It stores a relationship to a record in another table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It can only contain numeric values<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It is always a calculated field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It cannot use qualifiers<\/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 field establishes a relationship between a record and a record in another ServiceNow table. Internally, the field generally stores the referenced record&#8217;s unique identifier, while the user interface displays the referenced record&#8217;s display value. Reference fields can also use Reference Qualifiers to restrict which records are available for selection. They are widely used to create relationships between users, groups, departments, companies, configuration items, and other records. Reference fields are not limited to numeric values and are not automatically calculated fields. Proper reference configuration helps maintain consistent relationships within an application&#8217;s data model.<\/span><\/p>\n<h3><b>Question 236<\/b><\/h3>\n<p><b>Which feature can be used to define reusable operations within Flow Designer?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Custom Action<\/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;\">ACL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form Section<\/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 Custom Action allows developers to create reusable operations for Flow Designer when the required functionality is not provided by an existing action. Custom Actions can define inputs, processing steps, and outputs that can be used within flows. They help organizations encapsulate specialized business logic while allowing process designers to use that functionality through the Flow Designer interface. Dictionary Entries define field metadata, ACLs control security, and Form Sections organize fields on forms. Custom Actions are useful for extending Flow Designer while keeping automation logic modular and reusable.<\/span><\/p>\n<h3><b>Question 237<\/b><\/h3>\n<p><b>Which API is used to make outbound REST calls from server-side ServiceNow scripts?<\/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;\">RESTMessageV2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideUser<\/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: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">RESTMessageV2 is a server-side API used to make outbound REST calls from ServiceNow. Developers can use it to configure and send HTTP requests to external REST services, including setting endpoints, HTTP methods, headers, parameters, and authentication information. The response can then be processed by the ServiceNow script. GlideForm is used for client-side form operations, GlideUser provides user-related information, and GlideAggregate performs aggregate database queries. REST integrations should include appropriate authentication, error handling, timeout considerations, and response validation to ensure reliable communication with external systems.<\/span><\/p>\n<h3><b>Question 238<\/b><\/h3>\n<p><b>What is the purpose of an application scope in ServiceNow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To provide boundaries for application artifacts and control cross-scope access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To automatically encrypt every field<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To prevent all users from accessing the application<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To replace ACLs<\/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;\">Application scope provides boundaries around application components and helps control how applications interact with one another. Scoped applications can contain tables, scripts, modules, Business Rules, Script Includes, and other artifacts. When one application needs to access resources in another scope, cross-scope privileges or permissions may be required. Scope does not automatically encrypt fields, block all users, or replace ACLs. ACLs remain an important part of application security. Understanding scope is especially important when developing applications intended to coexist with other applications on the same ServiceNow instance.<\/span><\/p>\n<h3><b>Question 239<\/b><\/h3>\n<p><b>Which Client Script type executes when a user changes a specified field value?<\/b><\/p>\n<ol>\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;\">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. It is commonly used to dynamically modify other fields, display messages, validate information, or trigger client-side behavior based on a user&#8217;s selection. onLoad executes when the form initially opens, while onSubmit runs when the user attempts to save or submit the form. Selecting the correct Client Script type is important because each type has a different execution trigger. Developers should also ensure that onChange scripts do not perform unnecessary processing, especially on forms where users frequently modify fields.<\/span><\/p>\n<h3><b>Question 240<\/b><\/h3>\n<p><b>Which component is used to map source fields to target fields during an Import Set transformation?<\/b><\/p>\n<ol>\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;\">Transform Map<\/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;\">Script Include<\/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 Transform Map defines how data from an Import Set staging table is transferred and transformed into a target ServiceNow table. Field mappings specify which source fields correspond to which target fields. Transform Maps can also include scripts, coalesce configuration, and other transformation rules. Business Rules handle server-side record processing, UI Actions provide user interface controls, and Script Includes store reusable server-side logic. Transform Maps are essential when importing external data because they allow developers to control how incoming information is converted and stored in the target table while helping prevent incorrect mappings and duplicate records.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 221 Which ServiceNow API is used to retrieve the display value of a field? getValue() getDisplayValue() getLabel() getFieldValue() Correct Answer: 2 Explanation The getDisplayValue() method is used with GlideRecord to retrieve the human-readable display value of a field. This is especially useful for [&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\/15625"}],"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=15625"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15625\/revisions"}],"predecessor-version":[{"id":15642,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15625\/revisions\/15642"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15625"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15625"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}