{"id":15619,"date":"2026-09-18T06:09:29","date_gmt":"2026-09-18T06:09:29","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15619"},"modified":"2026-09-18T06:09:29","modified_gmt":"2026-09-18T06:09:29","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part7-q121-140","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part7-q121-140\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part7 Q121-140"},"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 121<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to define conditions that determine when a Business Rule should execute?<\/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;\">Business Rule Condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary Override<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form View<\/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 Business Rule Condition determines whether a Business Rule should execute for a particular record operation. Developers can configure conditions based on field values so that the script runs only when the required criteria are met. This is important for performance because unnecessary Business Rule execution can increase server processing. For example, a rule might run only when a record&#8217;s state changes to a particular value. UI Actions provide user interface controls, Dictionary Overrides modify inherited field behavior, and Form Views control presentation. Carefully designed conditions help keep server-side application logic efficient, predictable, and easier to maintain.<\/span><\/p>\n<h3><b>Question 122<\/b><\/h3>\n<p><b>Which method is commonly used to check whether a GlideRecord field value has changed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">changes()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">isChanged()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">hasChanged()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">valueChanged()<\/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;\">changes()<\/span><span style=\"font-weight: 400;\"> method can be used in appropriate server-side Business Rule contexts to determine whether a field value has changed during the current transaction. This is particularly useful when a Business Rule should perform an action only when a specific field changes. For example, logic may need to execute only when the state or priority of a record is modified. Developers can also use methods such as <\/span><span style=\"font-weight: 400;\">changesTo()<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">changesFrom()<\/span><span style=\"font-weight: 400;\"> for more specific comparisons. Using these methods helps avoid unnecessary processing when unrelated fields are updated and makes Business Rule behavior more precise.<\/span><\/p>\n<h3><b>Question 123<\/b><\/h3>\n<p><b>Which API is commonly used to access information about the current user in server-side scripts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideDateTime<\/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;\">GlideUser<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideRecord<\/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;\">GlideUser provides functionality for working with information about the current user and user-related context. Through the <\/span><span style=\"font-weight: 400;\">gs.getUser()<\/span><span style=\"font-weight: 400;\"> interface, developers can access information such as roles, user identity, and other user properties. This can be useful when application logic needs to behave differently depending on the current user&#8217;s context. GlideDateTime handles date and time values, GlideAggregate performs aggregate database operations, and GlideRecord is primarily used for querying and manipulating records. Developers should distinguish between checking user information for application behavior and enforcing security, which should generally be handled through ACLs.<\/span><\/p>\n<h3><b>Question 124<\/b><\/h3>\n<p><b>Which ServiceNow feature is designed to allow a user to create a record through a simplified form?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Record Producer<\/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;\">Script Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Job<\/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 Record Producer provides a simplified interface that allows users to create records in a target table. Record Producers are commonly used in Service Catalog scenarios where users should provide a limited set of information rather than interact directly with a full table form. The supplied values can be mapped to fields on the target record, and additional scripts or logic can be used when necessary. Transform Maps handle imported data, Script Actions respond to events, and Scheduled Jobs execute code at configured times. Record Producers are useful for creating user-friendly entry points into application processes.<\/span><\/p>\n<h3><b>Question 125<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to define custom REST endpoints that external systems can call?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REST API Explorer<\/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;\">Scripted REST API<\/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: 3<\/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 in ServiceNow. Developers can define resources, HTTP methods, request parameters, authentication requirements, and server-side scripts that determine how requests are processed. This is useful when external systems need access to application-specific functionality that is not provided by standard ServiceNow APIs. A REST Message is primarily used for outbound communication from ServiceNow to external systems, while REST API Explorer helps developers test and explore available APIs. Script Includes store reusable server-side logic and may be used internally by Scripted REST API resources.<\/span><\/p>\n<h3><b>Question 126<\/b><\/h3>\n<p><b>Which HTTP status code generally indicates that a REST request was successful and returned a resource?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">404<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">201<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">500<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">401<\/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;\">HTTP status code 201 generally indicates that a request successfully created a resource. It is commonly returned by APIs after successful POST operations that create a new record or resource. Status 404 indicates that the requested resource could not be found, 500 represents a server-side error, and 401 generally indicates that authentication is required or failed. The exact response codes depend on the API implementation, but understanding standard HTTP status codes is important when developing ServiceNow integrations. Developers should inspect both the response status and response body when troubleshooting REST integrations.<\/span><\/p>\n<h3><b>Question 127<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to configure reusable logic that can be called from a Client Script using GlideAjax?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Callable Script Include<\/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;\">Data Policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">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;\">A Client Callable Script Include is specifically configured so that client-side scripts can communicate with server-side logic through GlideAjax. This allows the browser to request information or processing from the server without exposing the complete server-side implementation to the client. The Script Include can receive parameters, perform server-side processing, and return an appropriate response. Business Rules execute based on record operations, UI Actions provide interactive controls, and Data Policies enforce data requirements. Client Callable Script Includes should be designed carefully so that only necessary functionality is exposed and user-provided parameters are properly validated.<\/span><\/p>\n<h3><b>Question 128<\/b><\/h3>\n<p><b>What is the primary purpose of an application menu in ServiceNow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define database indexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Group related modules for navigation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Execute Business Rules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Store integration credentials<\/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;\">An Application Menu groups related modules and provides an organized navigation area for users. Modules can point to lists, forms, reports, dashboards, or other application functionality. Proper application navigation makes it easier for users to find the features relevant to their responsibilities. Application Menus do not execute Business Rules, define database indexes, or store integration credentials. Access to modules can also be restricted using roles and other configuration options. When developing a custom application, developers should organize modules logically so users can navigate the application efficiently without being exposed to unnecessary functionality.<\/span><\/p>\n<h3><b>Question 129<\/b><\/h3>\n<p><b>Which ServiceNow feature allows an administrator to restrict access to a module based on user roles?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application Menu module roles<\/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;\">Dictionary Entry<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Script Action<\/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 modules can be configured with roles that determine which users can access them through the application navigator. This helps control the visibility of navigation options for different user groups. However, module visibility should not be treated as the primary security mechanism for protecting data. ACLs must still enforce access to tables, records, and fields. Transform Maps process imported data, Dictionary Entries define field metadata, and Script Actions respond to events. Proper ServiceNow security generally uses navigation restrictions for usability while relying on server-side ACLs for actual authorization and data protection.<\/span><\/p>\n<h3><b>Question 130<\/b><\/h3>\n<p><b>Which feature is used to define a condition that filters records available in a reference field?<\/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;\">Reference Qualifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Script<\/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 filters the records that users can select in a reference field. It can be configured with conditions or scripted logic depending on the complexity of the requirement. For example, a reference field might be configured to display only active users or records associated with a specific department. Reference Qualifiers improve usability by reducing irrelevant choices. They should not be considered a complete security control because filtering choices does not necessarily prevent access to records through other methods. UI Actions create interactive controls, Scheduled Scripts perform scheduled processing, and Notifications communicate information to users.<\/span><\/p>\n<h3><b>Question 131<\/b><\/h3>\n<p><b>Which ServiceNow API is commonly used to retrieve a record&#8217;s field value as stored in the database?<\/b><\/p>\n<ol>\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;\">getValue()<\/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;\">getStoredValue()<\/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;\">getValue()<\/span><span style=\"font-weight: 400;\"> method is commonly used to retrieve the underlying stored value of a field. This is particularly important for reference fields, where the stored value is typically a sys_id while the display value may be a user&#8217;s name or another human-readable value. Developers can use <\/span><span style=\"font-weight: 400;\">getDisplayValue()<\/span><span style=\"font-weight: 400;\"> when they need the value shown to users. Understanding the difference between stored and display values is important for scripting, integrations, and database operations. Using the appropriate method prevents problems when scripts require an internal identifier rather than the human-readable value displayed on a form.<\/span><\/p>\n<h3><b>Question 132<\/b><\/h3>\n<p><b>Which feature allows developers to create a custom action that can be used 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 Override<\/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;\">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 extends Flow Designer by providing specialized functionality that can be called from flows. Developers can define inputs, processing logic, and outputs for the action, allowing it to become a reusable building block for automation. This is useful when standard Flow Designer actions cannot meet a particular application requirement. Dictionary Overrides modify inherited field behavior, Client Scripts control browser-side behavior, and Form Sections organize fields on forms. Custom Actions can help maintain clean architecture by encapsulating specialized logic rather than embedding large amounts of custom code directly into individual flows.<\/span><\/p>\n<h3><b>Question 133<\/b><\/h3>\n<p><b>Which ServiceNow component is most appropriate for executing logic when a record is inserted or updated on the server?<\/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;\">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;\">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;\">Business Rules are designed for server-side logic that runs when database operations occur, including inserts and updates. Developers can configure a Business Rule to execute Before, After, or Async depending on the requirement. This makes Business Rules suitable for enforcing business logic, calculating values, creating related records, or responding to changes. Client Scripts and UI Policies execute primarily in the browser and are focused on form behavior, while Form Layout controls presentation. Developers should avoid using server-side Business Rules for logic that only needs client-side interaction because unnecessary server processing can affect application performance.<\/span><\/p>\n<h3><b>Question 134<\/b><\/h3>\n<p><b>Which method is used to initialize a GlideRecord for creating a new record?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">prepare()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">initialize()<\/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;\">newRecord()<\/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;\">initialize()<\/span><span style=\"font-weight: 400;\"> method prepares a GlideRecord object for creating a new record. After initializing the object, developers can assign values to fields and then call <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> to create the record in the database. A typical pattern is to create a GlideRecord for the target table, call <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\">, set the required fields, and then call <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The other listed methods are not the standard GlideRecord method used for this purpose. Developers should distinguish between creating a new record and retrieving an existing one because the appropriate GlideRecord workflow differs.<\/span><\/p>\n<h3><b>Question 135<\/b><\/h3>\n<p><b>Which ServiceNow feature is used to organize reusable application components such as tables, scripts, and modules into an application?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application scope<\/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;\">Transform Map<\/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;\">Application scope provides boundaries around application components and helps organize related tables, scripts, modules, and other application files. Scoped applications can control how their resources interact with components belonging to other scopes. This helps create modular applications and reduces unintended dependencies. Notifications handle communication, Transform Maps process imported data, and Data Policies enforce data requirements. Scope is particularly important when building applications intended to be maintained independently or distributed through application mechanisms. Developers should understand cross-scope access because scoped applications may require explicit privileges when interacting with resources outside their own scope.<\/span><\/p>\n<h3><b>Question 136<\/b><\/h3>\n<p><b>Which feature can be used to automatically send an email when a specified record condition is met?<\/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;\">Dictionary Entry<\/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;\">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;\">A Notification can be configured to send email when specified record conditions or events occur. Developers or administrators can define recipients, conditions, message content, and other notification settings. Notifications can use record fields to personalize the message and can also respond to events generated by application logic. Dictionary Entries define field metadata, Form Layout controls presentation, and Reference Qualifiers filter records available in reference fields. Notifications should be designed carefully to avoid excessive messages, particularly for records that are frequently updated. Appropriate conditions and event-driven designs can make notifications more useful and manageable.<\/span><\/p>\n<h3><b>Question 137<\/b><\/h3>\n<p><b>Which ServiceNow feature is intended to provide a visual interface for building and configuring application logic with minimal scripting?<\/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;\">GlideRecord<\/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;\">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;\">Flow Designer provides a visual, low-code environment for creating application automation with triggers, actions, conditions, and subflows. It allows developers and administrators to automate business processes without writing custom JavaScript for every step. For example, a flow can respond to a record event, perform updates, request approval, and send notifications. GlideRecord is a server-side database API, Script Includes store reusable server-side logic, and Business Rules execute server-side logic based on record operations. Flow Designer is especially useful when an automation requirement can be implemented using standard actions and supported integrations.<\/span><\/p>\n<h3><b>Question 138<\/b><\/h3>\n<p><b>Which API is commonly used to format and manipulate date and time values?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideDateTime<\/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: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideDateTime is designed for working with date and time values in ServiceNow server-side scripts. It provides methods for comparing dates, adding or subtracting time, formatting values, and handling date-time calculations. This API is useful for applications that calculate deadlines, durations, schedules, or timestamps. GlideRecord is used for database operations, GlideAjax provides client-to-server communication, and GlideUser handles user-related information. Developers should use the platform&#8217;s date and time APIs rather than manually manipulating date strings whenever possible because ServiceNow has specific time-zone and date storage behavior that can otherwise lead to incorrect calculations.<\/span><\/p>\n<h3><b>Question 139<\/b><\/h3>\n<p><b>Which security mechanism should be used to enforce access to a specific field regardless of how the user accesses the data?<\/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;\">Field-level ACL<\/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;\">Client Script<\/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 field-level ACL is the appropriate mechanism for enforcing access to a specific field at the platform security level. It can determine whether a user is allowed to read or modify a field based on roles, conditions, or scripts. This protection is stronger than simply hiding a field with a UI Policy or removing it from a Form Layout because those are primarily presentation mechanisms. Client Scripts also operate in the browser and should not be relied upon for security. Developers should test field-level ACLs carefully to ensure that protected information remains inaccessible through supported access paths.<\/span><\/p>\n<h3><b>Question 140<\/b><\/h3>\n<p><b>Which deployment approach allows developers to move application configuration changes while preserving a record of those changes?<\/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;\">Reference Qualifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/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 provide a mechanism for capturing supported configuration changes and moving them between ServiceNow instances. They also provide a record of the configuration changes included in the deployment package. This is useful in development environments where changes need to move through testing before reaching production. Developers should review Update Sets carefully for dependencies and captured records before deployment. UI Policies, Reference Qualifiers, and Client Scripts are individual application components rather than deployment mechanisms. Depending on the development model and ServiceNow version, source control and application repository capabilities may also be used for managing application development and deployment.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 121 Which ServiceNow feature allows developers to define conditions that determine when a Business Rule should execute? UI Action Business Rule Condition Dictionary Override Form View Correct Answer: 2 Explanation A Business Rule Condition determines whether a Business Rule should execute for a [&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\/15619"}],"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=15619"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15619\/revisions"}],"predecessor-version":[{"id":15647,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15619\/revisions\/15647"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}