ServiceNow Updated CAD Exam Questions and Answers by aylin

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.

The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.

Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module."

The following is true for the Override application menu roles configuration option when configuring a module:

Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.

The following are not true for the Override application menu roles configuration option when configuring a module:

Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.

Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. Admin is a role

To link a ServiceNow application to a Git repository, you need to provide the user name, URL, and password of the Git account that hosts the repository12. The URL is the address of the Git repository that you want to link to the application. The user name and password are the credentials that you use to access the Git account. Alternatively, you can use a personal access token instead of a password for increased security3.

References = 1: Link an application to source control - ServiceNow Docs 2: Publish an application to the application repository - ServiceNow 3: Linking an application to Git using a personal access token instead of a password - ServiceNow