CAD Exam Dumps - ServiceNow Certified Application Developer Questions and Answers

This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.

GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.

GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.

The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/guided-app-creator.html

In ServiceNow, when an event is generated using the gs.eventQueue() method, the system can respond in several ways:

B. Email Notification: Events can trigger email notifications. By associating an event with a notification, the system can send emails to specified recipients when the event occurs.

E. Script Action: Script Actions are server-side scripts that execute in response to events. They allow developers to define custom behaviors that should occur when specific events are fired.

The other options are not appropriate responses to events generated by gs.eventQueue():

A. UI Policy: UI Policies are used to dynamically change the behavior of fields on forms in the user interface and are not triggered by events.

C. Client Script: Client Scripts run on the client side (in the user's browser) and are not directly triggered by server-side events.

D. Scheduled Script Execution (Scheduled Job): Scheduled Jobs are scripts that run at specified times or intervals and are not triggered by events.

For more detailed information, refer to the official ServiceNow documentation on Responding to Events.

A Module Link type defines how the module opens in the content pane when the user clicks on it in the navigation pane1. The URL (from Arguments) link type allows you to specify a URL that opens the Application Properties page for the selected application2. The URL can include arguments that are evaluated at runtime, such as the application name or scope3.

References = 1: Module link types - ServiceNow Docs 2: Application properties - ServiceNow Docs 3: URL (from Arguments) - ServiceNow Docs

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.html

A spoke is a scoped application containing Flow Designer content dedicated to a particular application or record type. Flow Designer provides a set of core actions to automate Now Platform® processes. You can add application-specific core actions by activating the associated spoke.

Recurring checks, like finding task records that are unassigned, are implemented using platform automation that runs on a schedule. ServiceNow provides two common development-aligned places for this type of logic. Scheduled Script Execution is a scheduled job mechanism that runs server-side scripts at defined intervals. Developers use it to query tables (such as Task) and take actions like updating fields, creating follow-up records, or sending notifications when conditions are met. This matches option C. For low-code automation, Flow Designer also supports scheduled triggers, allowing developers to run a flow at specific times or on a repeating schedule to perform checks and actions. This matches option A (Scheduled Flows). Discovery Schedules are specific to the Discovery feature set for scanning infrastructure and are not used for general task management checks. “System Schedules” is not the standard construct where custom recurring business logic is authored for application development; the platform’s scheduled logic is typically implemented through scheduled jobs (including script executions) and scheduled flow triggers.

The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:

source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.

admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.

The following roles do not grant access to source control repository operations:

source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.

git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration. References: Source Control, Source Control Roles