ServiceNow Updated CAD Exam Questions and Answers by jayla

ServiceNow Studio is used to develop and manage application artifacts within a scoped application, including server-side logic that runs when database operations occur. “Customizing system behavior through database actions” points directly to server-side automation triggered by record operations such as insert, update, delete, and query. The platform feature designed for that purpose is Business Rules, which execute on the server in response to database events and can validate data, set field values, enforce policies, or initiate additional processing. While Studio can also include other file types such as Client Scripts, UI Policies, and ACLs, those are not primarily described as “database actions.” Client Scripts and UI Policies are primarily UI and client behavior controls, and ACLs control security access. Business Rules are the canonical mechanism for database-triggered behavior and are the best match to the question’s wording. Therefore, the file type aligned to customizing system behavior through database actions is Business Rules (sys_script).

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

The following is true for a Script Include with a Protection Policy value of Protected:

The Protection Policy is applied only if the application is downloaded from the ServiceNow App Store. This is true because the Protection Policy is a feature that allows developers to protect their Script Includes from being viewed or modified by other users when they distribute their applications through the ServiceNow App Store. The Protection Policy is only enforced when the application is installed from the App Store, not when it is developed or tested on the instance.

The following are not true for a Script Include with a Protection Policy value of Protected:

Any user with the protected_edit role can see and edit the Script Include. This is false because the protected_edit role is not related to the Protection Policy, but to the Access Control (ACL) rules. The protected_edit role allows users to edit protected fields on a table, such as the script field on the sys_script table, which stores the Business Rules. The Protection Policy does not use roles to control access to the Script Includes, but a cryptographic key that is generated when the application is published to the App Store.

The Protection policy option can only be enabled by a user with the admin role. This is false because the Protection policy option can be enabled by any user who has the application_admin role for the scoped application that contains the Script Include. The application_admin role grants full access to the application development and administration within the scope of the application.

The Protection Policy is applied only if the glide.app.apply_protection system property value is true. This is false because the glide.app.apply_protection system property is not related to the Protection Policy, but to the Application Restricted Caller Access (ARCA) feature. The ARCA feature allows developers to restrict the access to the Script Includes from other applications based on the caller’s scope. The glide.app.apply_protection system property determines whether the ARCA feature is enabled or disabled on the instance. References: Script Includes, Protect Script Includes, Application Restricted Caller Access