Free Practice Questions for ServiceNow CAD Exam

The Guided Application Creator in ServiceNow provides several methods for creating tables within a new application. These options cater to different requirements and data sources:

Extend a Table (Option A):

Description: Create a new table that inherits fields and behaviors from

In ServiceNow, Application Files are configuration records that define the various components and logic that constitute an application. These include artifacts such as:

Business Rules

Client Scripts

UI Actions

Script Includes

Tables and Fields

Workflows

These artifacts collectively define the functionality and behavior of the application. When an application is developed, ServiceNow automatically creates and manages these Application Files to represent the application ' s components.

Option C is correct because Application Files are the fundamental building blocks that comprise a ServiceNow application, representing its various components and configurations.

Options A, B, and D are incorrect:

A: XML exports of an Update Set represent changes made to an instance but are not synonymous with Application Files.

B: CSV files are typically used for data import/export and do not represent the configuration components of an application.

D: An XML export of table records pertains to data within a table, not the configuration artifacts that define application behavior.

In ServiceNow, tables can extend other tables, inheriting all fields and functionalities from the parent table. These inherited fields are integral to the structure and behavior of the child table.

A. No, inherited fields cannot be deleted from a child table: This is correct. Inherited fields are part of the child table ' s schema due to its extension of the parent table. Removing these fields would disrupt the inherent structure and relationships defined by the table hierarchy.

B. Yes, but only if they are text fields: This is incorrect. The data type of the field does not permit the deletion of inherited fields.

C. Yes, select the red X in the left-most column in the table definition: This is incorrect. Inherited fields do not have a delete (red X) option in the table definition, as they are not directly created on the child table.

D. Yes, but only if there has never been any saved field data: This is incorrect. The presence or absence of data does not affect the ability to delete inherited fields.

To modify the structure of inherited fields, consider the following approaches:

Field Visibility: Use client scripts or UI policies to hide the inherited fields on forms where they are not needed. This approach maintains data integrity while tailoring the user interface to specific requirements.

Form Layout Configuration: Adjust the form layout to remove inherited fields from specific views, ensuring they are not displayed to users in contexts where they are irrelevant.

These methods allow customization of the user experience without altering the underlying table schema or violating the inheritance principles established in the data model.

The Bar Chart and Pie Chart report types can be created by right-clicking on a column header in a table’s list. These report types show how individual pieces of data relate to the whole using proportional bars or slices. You can also choose different aggregation methods such as count, sum, average, min, max, or percent. Reference: [Create reports from lists]

https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_scripting_rome_debugging_client_scripts

The following are debugging strategies for client-side scripts, which run in the web browser and manipulate the user interface:

g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.

Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.

jslog(). This is a client-side API that writes a message to the browser console.

The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:

gs.log(). This is a server-side API that writes a message to the system log. References: Client-Side Scripting APIs, Debugging Client Scripts

A Record Producer in ServiceNow is a specific type of catalog item that enables users to create records in a particular table through a simplified interface. They are often used to allow users to create task-based records, such as incidents or change requests, from the Service Catalog.

servicenow.com

Key characteristics of Record Producers include:

Graphics can be included on the user interface: Developers can enhance the user experience by adding images or icons to the Record Producer form, making it more intuitive and visually appealing.

Each field prompts the user with a question rather than a field label: Instead of standard field labels, Record Producers can present fields as questions to guide users in providing the necessary information. This approach makes the form more user-friendly and context-specific.

You can script behaviors of fields in the user interface: Developers have the flexibility to add client-side scripts to control the behavior of fields on the Record Producer form. This capability allows for dynamic interactions, such as showing or hiding fields based on user input or pre-populating fields with specific data.

Option A is incorrect because records created by a Record Producer are inserted into the table specified during its configuration, not necessarily the Requested Item [sc_req_item] table. Option C is incorrect because scripting is not mandatory for Record Producers; they can function without additional scripting, although scripting can be used to enhance functionality when needed.

ServiceNow ACLs (Access Control Lists) determine whether a user can perform an operation (read, write, create, delete, etc.) on a table, record, or field. When an ACL includes multiple types of checks, the platform evaluates them in a defined sequence. ServiceNow documentation describes permission evaluation using rule types and indicates that Role checks are evaluated first, followed by additional rule criteria such as conditions, and finally scripts when present. This order matters for both security and performance. Role evaluation is typically fastest and can short-circuit further checks. If the user does not meet the role requirement, the platform does not need to evaluate the condition or run a script. Conditions are then evaluated to confirm record-based or context-based requirements. If the ACL still requires deeper logic beyond roles and conditions, a script can be executed last to decide access (often setting an answer value or returning true/false depending on the ACL type). Therefore, among the provided choices, the correct sequence is Roles → Conditions → Script.

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideRecordScoped/concept/c_GlideRecordScopedAPI.html

there are only two types of UX options: Mobile and Classic. Classic is defined as " manage records via lists and form "