{"id":15615,"date":"2026-09-18T06:10:19","date_gmt":"2026-09-18T06:10:19","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15615"},"modified":"2026-09-18T06:10:19","modified_gmt":"2026-09-18T06:10:19","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part3-q41-60","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part3-q41-60\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part3 Q41-60"},"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 41<\/b><\/h3>\n<p><b>Which ServiceNow component is used to define reusable application logic that can be accessed from multiple 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;\">Client Script<\/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;\">Dictionary Entry<\/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 Script Include is designed to store reusable server-side JavaScript that can be called from multiple parts of a ServiceNow application. This promotes code reuse and prevents developers from duplicating the same business logic in several Business Rules, Script Actions, or scheduled jobs. Script Includes can contain functions or classes and can be configured as client callable when they need to communicate with client-side code through GlideAjax. UI Policies and Client Scripts primarily control client-side behavior, while Dictionary Entries define field metadata. Using Script Includes effectively helps create modular, maintainable, and easier-to-test application logic.<\/span><\/p>\n<h3><b>Question 42<\/b><\/h3>\n<p><b>Which Client Script type is triggered when the value of a specified field changes?<\/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;\">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;\">onDisplay<\/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 onChange Client Script executes whenever the value of its configured field changes on a form. It is commonly used when changing one field should dynamically affect another field. For example, changing a category could modify available choices or display additional information. An onLoad Client Script executes when the form opens, while an onSubmit Client Script executes when the user attempts to submit the form. Client Scripts operate in the user&#8217;s browser, so they should primarily be used for user-interface behavior. Security-sensitive requirements should be enforced using server-side mechanisms such as ACLs or appropriate server-side validation.<\/span><\/p>\n<h3><b>Question 43<\/b><\/h3>\n<p><b>Which table is commonly used as the parent table when creating task-based application records?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys_user<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">cmdb_ci<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">task<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys_dictionary<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Task table is a foundational ServiceNow table that provides common fields and functionality for many task-oriented records. Tables such as Incident, Problem, and Change Request extend the Task table and inherit its common fields and behavior. This table-extension model allows developers to reuse standard functionality instead of recreating fields such as number, short description, assignment group, assigned to, and state. The sys_user table stores user records, cmdb_ci is associated with configuration items, and sys_dictionary stores dictionary metadata. Understanding table inheritance is important when designing custom applications because extending the correct parent table can provide useful platform capabilities.<\/span><\/p>\n<h3><b>Question 44<\/b><\/h3>\n<p><b>What does the <\/b><b>current<\/b><b> object generally represent in a server-side Business Rule?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The current record being processed<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The current logged-in user&#8217;s browser<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The system property configuration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The application&#8217;s navigation menu<\/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;\">In a server-side Business Rule, the <\/span><span style=\"font-weight: 400;\">current<\/span><span style=\"font-weight: 400;\"> object represents the record that is currently being processed. Developers use it to read and modify fields on the record and to access information relevant to the database operation. For example, <\/span><span style=\"font-weight: 400;\">current.short_description<\/span><span style=\"font-weight: 400;\"> can access the short description field of the current record. The <\/span><span style=\"font-weight: 400;\">previous<\/span><span style=\"font-weight: 400;\"> object can be used in appropriate Business Rule contexts to access values from the previous version of the record. Understanding these objects is fundamental to Business Rule development. They allow developers to write logic that responds directly to changes occurring on the record being processed.<\/span><\/p>\n<h3><b>Question 45<\/b><\/h3>\n<p><b>Which ServiceNow feature allows developers to create custom fields on an application table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Jobs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary Overrides<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Form Layouts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary Entries<\/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;\">Dictionary Entries define metadata for fields in ServiceNow tables and are involved when creating and configuring fields. Through the dictionary, developers can define characteristics such as field type, length, default value, reference table, and other properties. Creating a custom field through the appropriate application or table configuration results in a corresponding dictionary definition. Form Layouts control where existing fields appear on forms but do not create the underlying field. Scheduled Jobs execute scripts at specified times, while Dictionary Overrides modify inherited field behavior in extended tables. Understanding dictionary configuration is essential for creating consistent and correctly defined application data structures.<\/span><\/p>\n<h3><b>Question 46<\/b><\/h3>\n<p><b>Which API should be used when a server-side script needs to retrieve system properties?<\/b><\/p>\n<ol>\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;\">GlideAjax<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAggregate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideDateTime<\/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;\">GlideSystem, commonly represented by the <\/span><span style=\"font-weight: 400;\">gs<\/span><span style=\"font-weight: 400;\"> object in server-side scripts, provides many platform-level functions, including access to system properties. Developers can use methods such as <\/span><span style=\"font-weight: 400;\">gs.getProperty()<\/span><span style=\"font-weight: 400;\"> to retrieve configured system property values. System properties are useful for storing configurable values without hard-coding them directly into application scripts. GlideAjax is intended for client-to-server communication, GlideAggregate performs aggregate database operations, and GlideDateTime handles date and time values. Using properties allows administrators to modify application behavior through configuration rather than requiring developers to change and redeploy scripts whenever a configurable value needs adjustment.<\/span><\/p>\n<h3><b>Question 47<\/b><\/h3>\n<p><b>What is the primary purpose of a UI Action?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create database indexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add interactive actions such as buttons or menu items<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Validate imported records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define reference qualifiers<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">UI Actions allow developers to add interactive elements such as buttons, links, and context-menu options to ServiceNow forms and lists. They can execute client-side or server-side logic depending on their configuration. A UI Action might allow an agent to close a record, create a related record, or perform another application-specific operation. Database indexes are configured separately, imported records are handled through Import Sets and Transform Maps, and reference qualifiers control available choices in reference fields. UI Actions are therefore particularly useful when users need an explicit interface control to trigger an application operation directly from a form or list.<\/span><\/p>\n<h3><b>Question 48<\/b><\/h3>\n<p><b>Which object can be used in a Business Rule to access values from the record before it was changed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">current<\/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;\">previous<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">producer<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">previous<\/span><span style=\"font-weight: 400;\"> object provides access to the record&#8217;s values before the current database operation changed them, in Business Rule contexts where it is available. Developers can use it to compare old and new values and determine whether a particular field changed. For example, logic can compare <\/span><span style=\"font-weight: 400;\">current.state<\/span><span style=\"font-weight: 400;\"> with <\/span><span style=\"font-weight: 400;\">previous.state<\/span><span style=\"font-weight: 400;\"> to detect a state transition. The <\/span><span style=\"font-weight: 400;\">current<\/span><span style=\"font-weight: 400;\"> object represents the record being processed, while <\/span><span style=\"font-weight: 400;\">gs<\/span><span style=\"font-weight: 400;\"> provides GlideSystem functionality. The <\/span><span style=\"font-weight: 400;\">producer<\/span><span style=\"font-weight: 400;\"> object is associated with specific record producer contexts. Comparing current and previous values is a common technique for implementing conditional Business Rule behavior.<\/span><\/p>\n<h3><b>Question 49<\/b><\/h3>\n<p><b>Which feature allows an application to expose server-side functionality to client-side scripts through asynchronous calls?<\/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 Policy<\/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 Override<\/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 can expose server-side functionality to client-side scripts through GlideAjax. This architecture allows the browser to request information or processing from the server without placing sensitive database logic directly in the client script. The Script Include performs the required server-side operation and returns an appropriate result. Developers should carefully validate parameters and avoid exposing unnecessary functionality. UI Policies control form behavior, Transform Maps handle imported data transformations, and Dictionary Overrides adjust inherited field configuration. Client-callable Script Includes are especially useful when client-side functionality requires information that can only or more safely be obtained on the server.<\/span><\/p>\n<h3><b>Question 50<\/b><\/h3>\n<p><b>Which ServiceNow mechanism is primarily used to define application navigation and group related modules?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application Menu<\/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;\">Script Include<\/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;\">An Application Menu organizes navigation in ServiceNow and groups related modules under a common application area. Developers can create an application menu and then associate modules with it so users can easily access relevant tables, lists, forms, reports, or custom functionality. Business Rules execute server-side logic when records are processed, Script Includes provide reusable server-side code, and Data Policies enforce data requirements. Proper navigation design improves application usability by presenting users with only the modules relevant to their responsibilities. Access to modules can also be controlled through roles and other configuration settings.<\/span><\/p>\n<h3><b>Question 51<\/b><\/h3>\n<p><b>Which method is commonly used to insert a new record with a GlideRecord object?<\/b><\/p>\n<ol>\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;\">addRecord()<\/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;\">saveRecord()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> method is used with GlideRecord to create a new record in the database. A developer typically creates a GlideRecord object for the target table, assigns values to the desired fields, and then calls <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The method returns the sys_id of the newly inserted record when successful. Developers should ensure that required fields and validation requirements are satisfied before insertion. Methods such as <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> are used for existing records, while <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> retrieves records. Understanding the difference between insert and update operations is essential when developing server-side scripts that create or modify application data.<\/span><\/p>\n<h3><b>Question 52<\/b><\/h3>\n<p><b>What is the main purpose of an application property?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Store configurable values that can be changed without modifying application code<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replace all ACL rules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create database tables automatically<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define client-side events<\/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 properties provide a configurable place to store values used by application logic. Instead of hard-coding values such as thresholds, feature settings, identifiers, or behavior switches directly into scripts, developers can retrieve them from properties. This makes applications more flexible because administrators can change configuration without modifying source code. Server-side scripts commonly retrieve properties through GlideSystem methods such as <\/span><span style=\"font-weight: 400;\">gs.getProperty()<\/span><span style=\"font-weight: 400;\">. Application properties do not replace ACLs, automatically create database tables, or define client-side events. Properly designed property usage separates configuration from logic and can make applications easier to maintain across development, testing, and production environments.<\/span><\/p>\n<h3><b>Question 53<\/b><\/h3>\n<p><b>Which ServiceNow feature is commonly used to automate repetitive application processes 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;\">Dictionary Entry<\/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;\">Database Index<\/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 low-code approach for automating processes using triggers, actions, conditions, and subflows. Developers and administrators can create automated workflows without writing extensive custom JavaScript for every step. For example, a flow can trigger when a record is created and then update records, send notifications, request approvals, or interact with supported integrations. Dictionary Entries describe field metadata, Reference Qualifiers control reference choices, and database indexes improve query performance. Flow Designer is especially useful when automation requirements can be satisfied through available actions and configuration, reducing the amount of custom code that must be maintained.<\/span><\/p>\n<h3><b>Question 54<\/b><\/h3>\n<p><b>Which API is designed to work with date and time values in ServiceNow server-side scripts?<\/b><\/p>\n<ol>\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;\">GlideDateTime<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAjax<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAggregate<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideDateTime is a ServiceNow API used to work with date and time values in server-side scripts. It provides methods for creating, comparing, formatting, and manipulating date-time information. Developers can use it when application logic needs to calculate durations, compare timestamps, or adjust date-time values. Proper handling of ServiceNow date-time values is important because the platform stores and displays dates according to specific time-zone behavior. GlideUser provides user-related information, GlideAjax supports client-to-server communication, and GlideAggregate performs database aggregation. Using GlideDateTime rather than manually manipulating date strings helps reduce errors in date-related application logic.<\/span><\/p>\n<h3><b>Question 55<\/b><\/h3>\n<p><b>Which configuration determines whether a field is displayed, hidden, read-only, or mandatory based on conditions on a form?<\/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;\">Import Set<\/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 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 can dynamically control field behavior on a form based on specified conditions. They can make fields mandatory, visible, or read-only without requiring custom JavaScript for straightforward scenarios. UI Policies are evaluated on the client side and are useful for improving form usability and guiding users through data entry. Import Sets temporarily stage imported data, Transform Maps determine how that data is transformed into target records, and Script Includes contain reusable server-side logic. Developers should remember that UI Policies are not a substitute for security controls because client-side behavior can be bypassed. Server-side validation and ACLs should protect important data requirements.<\/span><\/p>\n<h3><b>Question 56<\/b><\/h3>\n<p><b>What is the purpose of coalescing in a Transform Map?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It determines whether an imported record should update an existing record or create a new one<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It encrypts imported data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It automatically creates user roles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It schedules the import to run later<\/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;\">Coalescing identifies fields that ServiceNow should use to determine whether an imported row matches an existing target record. When the coalescing value matches an existing record, the import can update that record rather than creating a duplicate. If no matching record is found, the transformation can create a new record according to the configured mapping and rules. This makes coalescing particularly important when importing data from external systems where unique identifiers must be preserved. It does not encrypt data, create roles, or schedule imports. Correctly selecting a stable and appropriate coalescing field helps maintain data integrity and prevent unnecessary duplicate records.<\/span><\/p>\n<h3><b>Question 57<\/b><\/h3>\n<p><b>Which feature is intended to execute server-side code at a specified time or recurring schedule?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UI Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled Script Execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reference Qualifier<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Scheduled Script Executions allow developers to execute server-side JavaScript at a specified time or on a recurring schedule. They can be used for maintenance tasks, periodic data processing, automated cleanup, or other background operations that should not depend on a user&#8217;s interaction with a form. Client Scripts run in the user&#8217;s browser, UI Actions are triggered by user interactions, and Reference Qualifiers filter reference-field choices. Scheduled scripts should be designed carefully, particularly when processing large datasets, because inefficient queries or unnecessary loops can affect system performance. Developers should also consider whether Flow Designer or another automation mechanism better fits the requirement.<\/span><\/p>\n<h3><b>Question 58<\/b><\/h3>\n<p><b>What is the primary role of an ACL condition or script?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Determine whether a user is authorized to perform a protected operation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a new table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Modify email templates<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configure 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;\">ACL conditions and scripts help determine whether a user is authorized to access a protected table, record, or field operation. ACL evaluation can consider the user&#8217;s roles, record conditions, and scripted logic before allowing operations such as read, write, create, or delete. This makes ACLs an important server-side security mechanism. Developers should avoid relying solely on client-side controls such as UI Policies or Client Scripts for security because those mechanisms primarily affect the interface. Application navigation is configured separately, email templates control message formatting, and table creation is handled through application and table configuration tools.<\/span><\/p>\n<h3><b>Question 59<\/b><\/h3>\n<p><b>Which ServiceNow API is commonly used to securely query records while respecting access controls?<\/b><\/p>\n<ol>\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;\">GlideAjax<\/span><\/li>\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<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">GlideRecordSecure provides GlideRecord-like functionality while enforcing the platform&#8217;s access controls when records are accessed. This can be useful when server-side code needs to retrieve data while respecting the permissions of the user executing the operation. Standard GlideRecord is widely used for database operations, but developers must understand how security is enforced for the particular execution context. GlideAjax handles client-to-server communication, GlideDateTime handles date and time operations, and GlideAggregate performs aggregation queries. Security-aware database access is especially important when custom applications process information that may be restricted based on roles, records, or fields.<\/span><\/p>\n<h3><b>Question 60<\/b><\/h3>\n<p><b>Which development practice generally makes ServiceNow application code easier to maintain?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicating the same logic in multiple Business Rules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hard-coding every configurable value<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Using reusable functions and centralized application logic<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Performing database queries inside unnecessary nested loops<\/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;\">Reusable and centralized application logic generally improves maintainability because developers can modify functionality in one location rather than updating many duplicated scripts. Script Includes are often useful for implementing reusable server-side functions and classes. Configuration values can be stored in properties when appropriate, while database queries should be carefully designed to avoid unnecessary processing. Duplicating logic across multiple Business Rules can lead to inconsistent behavior and make troubleshooting more difficult. Similarly, inefficient database operations can create performance problems. Good ServiceNow development practices emphasize modular design, reuse, clear naming, appropriate security controls, and efficient database access.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 41 Which ServiceNow component is used to define reusable application logic that can be accessed from multiple server-side scripts? UI Policy Client Script Script Include Dictionary Entry Correct Answer: 3 Explanation A Script Include is designed to store reusable server-side JavaScript that can [&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\/15615"}],"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=15615"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15615\/revisions"}],"predecessor-version":[{"id":15651,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15615\/revisions\/15651"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}