ServiceNow Updated CAD Exam Questions and Answers by zayan

Created UI policy on incident form, action set's cmdb_ci field as mandatory and script as not. result, field was not mandatory.

A UI Policy’s Actions execute before the UI Policy’s Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met. References: [ServiceNow Docs - UI policy actions], [ServiceNow Docs - UI policy scripts]

When evaluating Access Controls, ServiceNow searches and evaluates:

From the most specific match to the most generic match. This is the correct answer because ServiceNow follows a top-down approach when evaluating Access Control (ACL) rules, which are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. ServiceNow starts with the most specific match, which is the field-level ACL rule, then moves to the table-level ACL rule, and finally to the global or * ACL rule. ServiceNow grants access if any of the ACL rules evaluates to true, and denies access if all of the ACL rules evaluate to false.

The following are not correct descriptions of how ServiceNow searches and evaluates Access Controls:

Only for matches on the current table. This is not correct because ServiceNow does not only look for matches on the current table, but also on the parent tables and the global or * table. For example, if there is no ACL rule for the incident table, ServiceNow will look for an ACL rule for the task table, which is the parent table of the incident table, and then for the global or * table, which is the parent table of all tables.

Only for matches on the current field. This is not correct because ServiceNow does not only look for matches on the current field, but also on the table that contains the field and the global or * table. For example, if there is no ACL rule for the short_description field on the incident table, ServiceNow will look for an ACL rule for the incident table, and then for the global or * table.

From the most generic match to the most specific match. This is not correct because ServiceNow does not follow a bottom-up approach when evaluating Access Controls, but a top-down approach, as explained above. References: Access Control Rules, ACL Evaluation Order

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

Creating an Application Properties page in ServiceNow provides a centralized location where developers or administrators can configure settings that influence the behavior of an application. This approach offers several benefits:

Dynamic Configuration: By exposing certain parameters through an Application Properties page, administrators can adjust the application's behavior in response to changing requirements or environments without altering the underlying code or application artifacts.

Simplified Maintenance: Having a dedicated properties page reduces the need for direct modifications to scripts or configurations, thereby minimizing the risk of introducing errors. It also streamlines the process of updating settings, as changes can be made through the user interface.

Enhanced Flexibility: Developers can design applications with configurable options, allowing for greater adaptability across different