{"id":15623,"date":"2026-09-18T06:08:33","date_gmt":"2026-09-18T06:08:33","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15623"},"modified":"2026-09-18T06:08:33","modified_gmt":"2026-09-18T06:08:33","slug":"servicenow-cad-practice-test-questions-and-exam-dumps-part11-q201-220","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/servicenow-cad-practice-test-questions-and-exam-dumps-part11-q201-220\/","title":{"rendered":"ServiceNow CAD Practice Test Questions and Exam Dumps Part11 Q201-220"},"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 201<\/b><\/h3>\n<p><b>Which ServiceNow API is primarily used to retrieve and manipulate database records on the server?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideForm<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideAjax<\/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;\">GlideUser<\/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;\">GlideRecord is the primary server-side API for interacting with records stored in ServiceNow tables. Developers can use it to query records, retrieve specific records, insert new records, update existing records, and delete records. Common methods include <\/span><span style=\"font-weight: 400;\">addQuery()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\">. GlideForm is mainly used for client-side form manipulation, GlideAjax supports communication between client and server, and GlideUser provides information about the current user. Developers should use GlideRecord carefully and construct efficient queries to avoid unnecessary database operations that could negatively affect application performance.<\/span><\/p>\n<h3><b>Question 202<\/b><\/h3>\n<p><b>Which type of Client Script is executed when a form is first opened?<\/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;\">onCellEdit<\/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 onLoad Client Script executes when a ServiceNow form is loaded in the user&#8217;s browser. It is commonly used to initialize fields, set field states, display information, or perform other client-side actions when the form opens. An onChange Client Script runs when a specific field value changes, while an onSubmit Client Script runs when the user attempts to submit the form. onCellEdit is associated with editing values directly in lists. Developers should use the appropriate Client Script type based on when the required behavior should occur. Using onLoad unnecessarily for complex operations can affect form loading performance.<\/span><\/p>\n<h3><b>Question 203<\/b><\/h3>\n<p><b>Which component is used to define server-side logic that executes before a record is saved?<\/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;\">Before 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<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A Before Business Rule executes before the current record is written to the database. It is commonly used to modify values on the current record, perform server-side validation, calculate values, or enforce business logic before saving. Because it runs as part of the database transaction, changes made to the <\/span><span style=\"font-weight: 400;\">current<\/span><span style=\"font-weight: 400;\"> record can be saved without requiring another update operation. Client Scripts and UI Policies operate primarily on the client side, while UI Actions provide user-triggered controls. Before Business Rules should be kept efficient because they execute during the user&#8217;s transaction and can directly affect transaction performance.<\/span><\/p>\n<h3><b>Question 204<\/b><\/h3>\n<p><b>Which ServiceNow feature allows a developer to define reusable automation logic that can be called from multiple flows?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dictionary Entry<\/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;\">Subflow<\/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 Subflow in Flow Designer is designed to package reusable automation logic that can be called from multiple flows or other subflows. Subflows can define inputs and outputs, making them suitable for common business processes that need to be reused in different situations. This approach reduces duplicated configuration and makes automation easier to maintain. Dictionary Entries define field metadata, UI Policies control client-side field behavior, and Form Layout controls form presentation. By creating reusable Subflows, developers can centralize common process logic and update it in one location when business requirements change.<\/span><\/p>\n<h3><b>Question 205<\/b><\/h3>\n<p><b>Which method is used to initialize a GlideRecord object before creating a new record?<\/b><\/p>\n<ol>\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;\">prepare()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">createRecord()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">start()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\"> method prepares a GlideRecord object for creating a new record. After initializing the object, a developer can assign values to fields and then use <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\"> to create the record in the database. A typical sequence is to create the GlideRecord object, call <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\">, set field values, and call <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The other listed methods are not standard GlideRecord methods for preparing a new record. Proper initialization helps ensure that the developer is working with a new record rather than unintentionally modifying an existing one retrieved through a query.<\/span><\/p>\n<h3><b>Question 206<\/b><\/h3>\n<p><b>Which ServiceNow feature controls whether a user can read or modify a specific field?<\/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;\">UI Action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access Control List<\/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: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An Access Control List, or ACL, can control access to tables and individual fields. ACLs can define whether users are allowed to perform operations such as read, write, create, or delete. Depending on the configuration, ACLs can evaluate roles, conditions, and scripts. Form Layout only controls which fields are presented and their arrangement, while UI Actions provide interactive controls and Notifications send messages. Security should be implemented with ACLs rather than relying on client-side mechanisms such as UI Policies or Client Scripts. Proper ACL design is essential when protecting sensitive application data.<\/span><\/p>\n<h3><b>Question 207<\/b><\/h3>\n<p><b>Which API is commonly represented by the <\/b><b>g_form<\/b><b> object?<\/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;\">GlideForm<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GlideRecord<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">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;\">The <\/span><span style=\"font-weight: 400;\">g_form<\/span><span style=\"font-weight: 400;\"> object represents GlideForm and is used in client-side scripts to interact with the current ServiceNow form. Developers can use GlideForm methods to retrieve and set field values, control field visibility, make fields mandatory or read-only, display messages, and perform other client-side operations. GlideRecord is primarily a server-side database API, GlideSystem provides server-side system functionality, and GlideAggregate performs aggregate database queries. Since Client Scripts run in the user&#8217;s browser, GlideForm is the standard API for manipulating the current form. Developers should use the appropriate GlideForm method for each form requirement.<\/span><\/p>\n<h3><b>Question 208<\/b><\/h3>\n<p><b>What is the main purpose of a Transform Map?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define how imported data maps to a target table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create user roles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To configure form buttons<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To manage application scopes<\/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 Transform Map defines how data from an Import Set staging table is transformed and transferred into a target ServiceNow table. It can contain field mappings, scripts, coalesce settings, and other transformation logic. Transform Maps are commonly used when importing data from external systems, spreadsheets, or other sources. They help ensure that source information is correctly mapped to the appropriate target fields. User roles, form buttons, and application scopes are configured through different platform components. Proper Transform Map configuration is especially important when importing large datasets because incorrect mappings can create inaccurate or duplicate records.<\/span><\/p>\n<h3><b>Question 209<\/b><\/h3>\n<p><b>Which method is used to add a condition to a GlideRecord query?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">setCondition()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">addQuery()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">where()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">filterQuery()<\/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;\">addQuery()<\/span><span style=\"font-weight: 400;\"> method adds conditions to a GlideRecord query. For example, a developer can use <\/span><span style=\"font-weight: 400;\">gr.addQuery(&#8216;active&#8217;, true)<\/span><span style=\"font-weight: 400;\"> to return only active records. Multiple conditions can be added to create more specific queries. After defining the conditions, the <\/span><span style=\"font-weight: 400;\">query()<\/span><span style=\"font-weight: 400;\"> method executes the database query, and <\/span><span style=\"font-weight: 400;\">next()<\/span><span style=\"font-weight: 400;\"> can then be used to iterate through the returned records. The other listed methods are not standard GlideRecord methods for adding query conditions. Efficient query construction is important because retrieving unnecessary records can consume database and server resources and negatively affect application performance.<\/span><\/p>\n<h3><b>Question 210<\/b><\/h3>\n<p><b>Which feature is designed to send automated messages to users when specified conditions or events occur?<\/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;\">Notifications are used to send automated messages to users or groups when defined conditions or events occur. A Notification can specify recipients, subject information, message content, conditions, and other configuration options. Notifications can be triggered by record changes or by events generated within ServiceNow. Dictionary Entries define field metadata, Form Layout controls form presentation, and Reference Qualifiers restrict records available in reference fields. Developers should configure Notification conditions carefully to ensure users receive relevant information without generating excessive or unnecessary messages.<\/span><\/p>\n<h3><b>Question 211<\/b><\/h3>\n<p><b>Which method is used to retrieve a record by its <\/b><b>sys_id<\/b><b> using GlideRecord?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">find()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">get()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">retrieve()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">lookup()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The GlideRecord <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\"> method can retrieve a specific record using its <\/span><span style=\"font-weight: 400;\">sys_id<\/span><span style=\"font-weight: 400;\">. For example, <\/span><span style=\"font-weight: 400;\">gr.get(sys_id)<\/span><span style=\"font-weight: 400;\"> attempts to retrieve the record whose unique identifier matches the supplied value. Once the record has been retrieved, its fields can be read or modified depending on the purpose of the script. The <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\"> method can also be used with an appropriate field and value combination. Methods such as <\/span><span style=\"font-weight: 400;\">find()<\/span><span style=\"font-weight: 400;\">, <\/span><span style=\"font-weight: 400;\">retrieve()<\/span><span style=\"font-weight: 400;\">, and <\/span><span style=\"font-weight: 400;\">lookup()<\/span><span style=\"font-weight: 400;\"> are not the standard GlideRecord method for this purpose. Using <\/span><span style=\"font-weight: 400;\">get()<\/span><span style=\"font-weight: 400;\"> is especially useful when a script already knows the unique identifier of a record.<\/span><\/p>\n<h3><b>Question 212<\/b><\/h3>\n<p><b>Which feature allows an external application to call custom endpoints hosted by ServiceNow?<\/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;\">Scripted REST API<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client Script<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data 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;\">A Scripted REST API allows developers to expose custom REST endpoints from ServiceNow. Developers can define resources, HTTP methods, request processing, authentication requirements, and response handling. Server-side scripts can process incoming requests and return structured responses, often in JSON format. This makes Scripted REST APIs useful for integrations where external applications need to interact with custom ServiceNow functionality. UI Policies, Client Scripts, and Data Policies serve different purposes and are not designed to expose REST endpoints. Developers should also consider authentication, authorization, validation, and error handling when designing custom REST services.<\/span><\/p>\n<h3><b>Question 213<\/b><\/h3>\n<p><b>Which option is used to package configuration changes so they can be transferred between ServiceNow instances?<\/b><\/p>\n<ol>\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;\">Update 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;\">Data 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;\">Update Sets are commonly used to capture configuration changes and move those changes between ServiceNow instances. They are useful in development environments where changes need to be promoted from development to testing and eventually to production. An Update Set can capture many configuration records, such as Business Rules, Client Scripts, UI Policies, and other application components. Import Sets are used for bringing data into ServiceNow, while Transform Maps control how imported data is processed. Data Policies enforce data requirements. Developers should review Update Sets carefully before transferring or committing them.<\/span><\/p>\n<h3><b>Question 214<\/b><\/h3>\n<p><b>Which ServiceNow API is used to retrieve aggregate information such as record counts?<\/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;\">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;\">GlideElement<\/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;\">GlideAggregate is used to perform aggregate database queries, including counts, sums, averages, minimums, and maximums. It can also support grouping results by fields. For example, a developer could use GlideAggregate to count incidents grouped by priority rather than retrieving every incident and calculating the count manually. This can be more efficient for reporting-style server-side operations. GlideForm is used for client-side form manipulation, GlideAjax supports client-to-server communication, and GlideElement represents a field element. Choosing GlideAggregate for summary queries can reduce unnecessary record processing and improve the efficiency of server-side scripts.<\/span><\/p>\n<h3><b>Question 215<\/b><\/h3>\n<p><b>Which Client Script type can prevent a form from being submitted when a validation condition is not met?<\/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;\">onCellEdit<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An onSubmit Client Script executes when the user attempts to submit a form. It can perform client-side validation and return <\/span><span style=\"font-weight: 400;\">false<\/span><span style=\"font-weight: 400;\"> when a requirement is not satisfied, preventing the form from being submitted. For example, an onSubmit script could verify that related information has been entered before allowing the record to save. onLoad runs when the form opens, while onChange runs when a specified field changes. Client-side validation improves the user experience, but it should not be considered a security mechanism. Important security and data-integrity requirements should also be enforced server-side.<\/span><\/p>\n<h3><b>Question 216<\/b><\/h3>\n<p><b>What is the primary purpose of a Data Policy?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To enforce data requirements across records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create navigation modules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To send email notifications<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To define REST endpoints<\/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 Data Policy is used to enforce data requirements for records and fields. Depending on its configuration, it can make fields mandatory or enforce other data-related rules, including in contexts beyond the standard user interface. This makes Data Policies useful when a requirement should apply consistently to data entering the platform rather than only to a particular form. UI Policies are primarily concerned with client-side form behavior. Notifications send messages, modules provide navigation, and Scripted REST APIs expose custom web services. Data Policies can therefore help maintain data quality and consistency across different methods of entering information.<\/span><\/p>\n<h3><b>Question 217<\/b><\/h3>\n<p><b>Which object represents the current record in a Business Rule?<\/b><\/p>\n<ol>\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;\">current<\/span><\/li>\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_form<\/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;\">current<\/span><span style=\"font-weight: 400;\"> object represents the record that caused a Business Rule to execute. Developers can use <\/span><span style=\"font-weight: 400;\">current<\/span><span style=\"font-weight: 400;\"> to access field values and, where appropriate, modify the record during server-side processing. The <\/span><span style=\"font-weight: 400;\">previous<\/span><span style=\"font-weight: 400;\"> object provides access to values from the previous version of a record in applicable contexts. <\/span><span style=\"font-weight: 400;\">g_form<\/span><span style=\"font-weight: 400;\"> is the GlideForm object used by client-side scripts, while <\/span><span style=\"font-weight: 400;\">gs_form<\/span><span style=\"font-weight: 400;\"> is not the standard object for representing a Business Rule&#8217;s current record. Understanding <\/span><span style=\"font-weight: 400;\">current<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">previous<\/span><span style=\"font-weight: 400;\"> is important when implementing Business Rules that need to compare old and new values or perform actions based on record changes.<\/span><\/p>\n<h3><b>Question 218<\/b><\/h3>\n<p><b>Which feature allows developers to create a user-friendly interface for creating records in a target table through the Service Catalog?<\/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;\">UI Macro<\/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;\">Scheduled Script Execution<\/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 allows users to create records in a target table through a Service Catalog-style interface. Instead of navigating directly to the underlying table form, the user fills out a simplified catalog form containing variables. Those variables can then be mapped to fields on the target record. Record Producers are useful for creating incidents, requests, cases, or other supported records through a streamlined user experience. Business Rules handle server-side processing, UI Macros provide reusable interface elements, and Scheduled Script Executions perform background processing. Record Producers are particularly useful when organizations want to simplify record creation for less technical users.<\/span><\/p>\n<h3><b>Question 219<\/b><\/h3>\n<p><b>Which method is used to save a newly created GlideRecord to the database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">insert()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">update()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">saveRecord()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">commitRecord()<\/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;\">insert()<\/span><span style=\"font-weight: 400;\"> method saves a newly created GlideRecord as a new database record. A developer typically creates a GlideRecord object for the desired table, calls <\/span><span style=\"font-weight: 400;\">initialize()<\/span><span style=\"font-weight: 400;\">, assigns values to fields, and then calls <\/span><span style=\"font-weight: 400;\">insert()<\/span><span style=\"font-weight: 400;\">. The method creates the record and returns its <\/span><span style=\"font-weight: 400;\">sys_id<\/span><span style=\"font-weight: 400;\"> when successful. The <\/span><span style=\"font-weight: 400;\">update()<\/span><span style=\"font-weight: 400;\"> method is normally used to save modifications to an existing record. <\/span><span style=\"font-weight: 400;\">saveRecord()<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">commitRecord()<\/span><span style=\"font-weight: 400;\"> are not standard GlideRecord methods for creating records. Developers should verify required fields and business logic before inserting records to maintain data quality.<\/span><\/p>\n<h3><b>Question 220<\/b><\/h3>\n<p><b>Which feature controls the modules and navigation options displayed within an application menu?<\/b><\/p>\n<ol>\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;\">Application Menu<\/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: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An Application Menu organizes related modules and provides navigation options for an application. Modules can point users to lists, forms, reports, dashboards, or other application functionality. Access to modules can also be controlled through roles when required. ACLs handle data security, Transform Maps handle imported data transformation, and Script Includes store reusable server-side logic. Application menus are therefore an important part of the user experience because they provide an organized way for users to access application functionality. Developers should design navigation logically so that users can quickly locate the features relevant to their roles and responsibilities.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full ServiceNow CAD Exam Dumps and Practice Test Dumps. &nbsp; Question 201 Which ServiceNow API is primarily used to retrieve and manipulate database records on the server? GlideForm GlideAjax GlideRecord GlideUser Correct Answer: 3 Explanation GlideRecord is the primary server-side API for interacting with records stored in ServiceNow tables. Developers can use it to [&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\/15623"}],"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=15623"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15623\/revisions"}],"predecessor-version":[{"id":15643,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15623\/revisions\/15643"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}