Free ServiceNow CAD Practice Exam with Questions & Answers | Set: 2

In ServiceNow, a Record Producer allows users to create records in a specific table through the Service Catalog. After a user submits a Record Producer, developers may want to redirect the user to a specific page. This can be achieved by setting the producer.redirect property within the Script field of the Record Producer.

For example:

javascript

CopyEdit

producer.redirect = ' incident.do?sys_id= ' + current.sys_id;

This script redirects the user to the newly created incident record after submission.

Option A is incorrect because configuring the module that opens the Record Producer does not control the post-submission behavior.

Option C is unnecessary for simple redirection purposes; creating an application property to store the URL adds unnecessary complexity.

Option D is incorrect because using window.redirect in a Business Rule is not appropriate; Business Rules run on the server side and do not have access to the client-side

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_ApplicationPicker.html

The Protection Policy field on a Script Include controls whether installed application code can be viewed or edited after distribution. “Protected” is intended to protect intellectual property by preventing customers who install or download the application from seeing the Script field content in plain text. It is not activated merely because an admin enables a field, because a user has protected_edit, or because a general system property is set. In CAD terms, this feature matters when distributing custom application code, especially Store-delivered applications, where the developer wants to hide implementation details from consuming instances. Therefore, option A is the correct exam-aligned answer.

================

The statement that is true for this script fragment is that the method returns true if the currently logged in user has the x_my_app_user role or the admin role. The g_user.hasRole() method is a client-side method that checks whether the current user has a specified role or set of roles. If no role is specified, it returns true if the user has any role. If one or more roles are specified, it returns true if the user has any one of the specified roles. However, this method always returns true if the user has the admin role, regardless of the role parameter. Therefore, in this case, the method returns true if the user has either the x_my_app_user role or the admin role. Reference: User Object Cheat Sheet, Checking user permissions

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.

The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.

Roles are used to control access to applications and modules in the application navigator. Each application menu or module has a role field that specifies which role is required to view it. Users who do not have the specified role or a role that contains it will not see the application menu or module. Roles can also be used to control access to other features and capabilities in ServiceNow, such as tables, fields, scripts, and workflows.

References = Enable or disable an application menu or module, Grant a role access to applications and modules, Controlling access to applications and modules.

Scheduled Script Executions (formerly known as Scheduled Jobs) are used to run server-side logic at specific intervals, such as querying or updating records automatically. Option B describes a valid server-side scheduled use case.

From ServiceNow Docs (https://developer.servicenow.com/):

“Scheduled Script Executions allow you to define JavaScript logic that runs on a schedule to automate tasks such as checking data integrity, generating reports, or reassigning records.”

Client-side logic like in options A, C, and D must use Client Scripts or UI Policies, not Scheduled Jobs.

In ServiceNow, UI Actions are elements such as buttons, links, and context menu items that allow users to perform actions on records or lists. The three valid UI Action types are:

1. List Banner Button (Option A)

Description: A button that appears in the list view header, allowing users to trigger an action affecting multiple records at once.

Example: A " Bulk Approve " button that processes selected records.

2. Form Button (Option B)

Description: A button that appears on a form, allowing users to trigger actions related to the current record.

Example: A " Submit for Approval " button on an incident form.

3. Record Navigation Button (Option D)

Description: A button that helps users navigate between related records.

Example: A " Go to Parent Record " button that redirects users to a linked record.

Incorrect Options:

Form Choice (Option C):

Not a UI Action type. Choices are typically used in choice fields (dropdowns) rather than UI actions.

List Choice (Option E):

Not a valid UI Action type. Similar to " Form Choice, " it pertains to field options rather than UI elements.

Workflow Action (Option F):

Workflows are process automation tools, not UI Actions. They are not directly related to buttons or links that users interact with.

Application developers configure ServiceNow using industry standard JavaScript to extend and add functionality. JavaScript is a scripting language that enables developers to create dynamic and interactive web pages, as well as manipulate data and logic on the server-side. ServiceNow provides various APIs and frameworks for developers to use JavaScript to customize and enhance the functionality of their applications, such as client scripts, UI policies, business rules, script includes, UI actions, and more. References: [ServiceNow Docs - JavaScript in ServiceNow] , [ServiceNow Docs - Scripting in ServiceNow]