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

The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

The Guided Application Creator (GAC) is a tool that helps you create applications on the ServiceNow platform by guiding you through the steps of defining the data model, user interface, and logic. When using the GAC, you can designate data tables in three ways:

Upload an existing PDF: You can upload a PDF file that contains the table schema and sample data. The GAC will parse the PDF and create the table and fields based on the file content.

Create a new table on the platform: You can create a new table on the platform by specifying the table name, label, and description. You can also add fields, indexes, and relationships to the table using the GAC.

Upload an existing spreadsheet: You can upload a spreadsheet file that contains the table schema and sample data. The GAC will parse the spreadsheet and create the table and fields based on the file content.

The other options are not valid ways to designate data tables when using the GAC. You cannot upload an existing word processing document or use a freeform database. You can use an existing table on the platform, but you cannot designate it as a data table. You can only use it as a reference table for lookup fields.

In ServiceNow, the Event Registry is a table that contains a record for every event recognized by the system. It allows ServiceNow to respond when these events are generated. By registering events, the system can automate activities such as triggering notifications or executing script actions when specific events occur. Therefore, the correct answer is A.

The other options are not accurate descriptions of the Event Registry:

B. The Event Log which lists all Events that have been generated: This describes the Event Log, not the Event Registry.

C. A Workflow which is launched every time an Event is generated; used to debug Events: This is not how the Event Registry functions.

D. The method used in server-side scripts to generate Events and pass parameters: This describes the gs.eventQueue() method, not the Event Registry.

For more detailed information, refer to the official ServiceNow documentation on the Event Registry.

The following is true for GlideUser (g_user) methods:

Can be used in Client Scripts, UI Policies, and UI Actions. This is true because GlideUser (g_user) methods are part of the client-side scripting APIs that provide information about the current user and the user’s preferences. Client Scripts, UI Policies, and UI Actions are all types of client-side scripts that run in the web browser and manipulate the user interface.

The following are not true for GlideUser (g_user) methods:

Can be used in Client Scripts and UI Policies only. This is false because GlideUser (g_user) methods can also be used in UI Actions, which are another type of client-side scripts that can be triggered by a user’s click on a button, link, or choice.

Can be used in Business Rules only. This is false because GlideUser (g_user) methods cannot be used in Business Rules, which are server-side scripts that run on the ServiceNow platform and manipulate the database. Business Rules use a different API to access the current user information, which is GlideSystem (gs).

Can be used in Business Rules, and Scripts Includes. This is false because GlideUser (g_user) methods cannot be used in Business Rules or Script Includes, which are both server-side scripts. Script Includes are reusable units of code that can be called from any server-side script. Script Includes also use GlideSystem (gs) to access the current user information. References: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository]

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.

Application Files are ServiceNow artifacts comprising an application. An application is a group of files and data that work together to provide a service or functionality. An application file is a specific type of file that belongs to an application, such as a table, a script, a form, a business rule, a UI action, etc. Application files define the structure, logic, and interface of the application. An XML export of an application’s table records, XML exports of an application’s Update Set, and CSV files containing data imported into an application are not examples of application files, as they are data formats that can be used to transfer or store information related to an application, but not the application itself. Reference: Application Files

One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more. References: [Use the REST API Explorer - Product Documentation: Tokyo - ServiceNow], [Introduction to Scripted REST APIs - ServiceNow Developers]