ServiceNow Updated CAD Exam Questions and Answers by zaid

The statements that must evaluate to true for a user to pass an Access Control are:

Conditions configured in the Access Control must evaluate to true.

The user has one of the roles specified in the Required roles related list.

Scripts configured in the Access Control must evaluate to true.

An Access Control is a rule that determines whether a user can access a particular object or operation in ServiceNow. An Access Control consists of three elements: Conditions, Roles, and Script. Each element specifies a requirement that the user must meet to access the object or operation. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Therefore, for a user to pass an Access Control, all three elements must evaluate to true.

The other statements are not required for a user to pass an Access Control. Other matching Access Controls for the records do not need to evaluate to true, as only one matching Access Control needs to return true for access to be granted. The user does not need to be granted access through a business rule, as business rules are not part of Access Controls and do not affect their evaluation. Reference: Access control rules, Access Controls

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.

ServiceNow notifications can sometimes be triggered close together for the same record and the same recipients, which can lead to redundant or conflicting messages. To control this, the Notification record includes a Weight field. ServiceNow documentation explains that when multiple notifications are generated for the same target table record and the recipients overlap, the system compares the notifications using the Weight value and sends only the notification with the highest weight. This allows administrators and developers to prioritize the most important notification when multiple are eligible to fire. A common example in the documentation is when an incident is updated (triggering an “commented” notification) and then closed shortly after (triggering a “closed” notification). If both would go to the same user, ServiceNow will select the one with the higher weight, ensuring users receive the most relevant final message instead of multiple emails. This behavior is the intended purpose of Weight: reduce notification noise and prevent conflicts by giving precedence to the highest-weight notification.

In ServiceNow, the gs object provides a range of methods for logging messages on the server side. However, the availability of these methods can vary depending on whether the application is global or scoped.

gs.info(): This method is available in scoped applications and is used to log informational messages to the system log. It provides a way to record general information during script execution.

Options A (gs.log()), B (gs.print()), and D (gs.debugLog()) are not available in scoped applications. These methods are either restricted to global applications or do not exist in the ServiceNow API.

For more detailed information, refer to the official ServiceNow documentation on server-side scripting: