Free CAD Exam Braindumps (page: 7)

Page 6 of 70

Which roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control? (Choose two.)

  1. source_control
  2. source_control_admin
  3. admin
  4. git_admin

Answer(s): A,C

Explanation:

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.


Reference:

Source Control, Source Control Roles


https://docs.servicenow.com/bundle/orlando-application- development/page/build/applications/task/ t_LinkAnApplicationToSourceControl.html



When configuring the content of an Email Notification, which syntax should be used to reference the properties of an event triggering the Notification?

  1. ${event. <property name>}
  2. ${current. <property name>}
  3. ${property name>.getDisplayValue()}
  4. ${gs.<property name>}

Answer(s): A

Explanation:

https://www.servicenow.com/community/it-service-management-forum/email-notification/m- p/695221


Reference:

https://community.servicenow.com/community? id=community_QUESTION NO :&sys_id=e017cbe5db1cdbc01dcaf3231f9619a3
When configuring the content of an Email Notification, the following syntax should be used to reference the properties of an event triggering the Notification:
event.<propertyname>.Thisisthecorrectsyntaxtoaccessthepropertiesoftheeventrecordthattriggeredth eEmailNotification,suchasevent.name,event.parm1,orevent.parm2.Forexample,{event.parm1} will display the value of the first parameter of the event.

The following syntaxes are not correct for referencing the properties of an event triggering the Notification:
current.<propertyname>.Thisisthesyntaxtoaccessthepropertiesofthecurrentrecordthatisassociatedwi ththeevent,suchascurrent.number,current.shortd escription,orcurrent.state.Forexample,{current.shor t_description} will display the short description of the current record. ${property name>.getDisplayValue()}. This is the syntax to access the display value of a property of the current record, such as current.state.getDisplayValue(), current.assigned_to.getDisplayValue(), or current.category.getDisplayValue(). For example, current.state.getDisplayValue() will display the state of the current record in a human-readable format, such as New, In Progress, or Closed. ${gs.<property name>}. This is the syntax to access the properties of the GlideSystem (gs) object, which provides methods for performing system operations, such as gs.now(), gs.getUserID(), or gs.getProperty(). For example, gs.now() will display the current date and time of the system.


Email Notifications, Email Notification Variables



Which one of the following is true for a Script Include with a Protection Policy value of Protected?

  1. Any user with the protected_edit role can see and edit the Script Include
  2. The Protection policy option can only be enabled by a user with the admin role
  3. The Protection Policy is applied only if the glide.app.apply_protection system property value is true
  4. The Protection Policy is applied only if the application is downloaded from the ServiceNow App Store

Answer(s): D

Explanation:

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.


Reference:

Script Includes, Protect Script Includes, Application Restricted Caller Access



Which one of the following is true for GlideUser (g_user) methods?

  1. Can be used in Client Scripts and UI Policies only
  2. Can be used in Business Rules only
  3. Can be used in Client Scripts, UI Policies, and UI Actions
  4. Can be used in Business Rules, and Scripts Includes

Answer(s): C

Explanation:

The following is true for GlideUser (g_user) methods:
Can be used in Client Scripts, UI Policies, and UI Actions. This is true because GlideUser (g_user) methods are part of the client-side scripting APIs that provide information about the current user and the user's preferences. Client Scripts, UI Policies, and UI Actions are all types of client-side scripts that run in the web browser and manipulate the user interface. The following are not true for GlideUser (g_user) methods:
Can be used in Client Scripts and UI Policies only. This is false because GlideUser (g_user) methods can also be used in UI Actions, which are another type of client-side scripts that can be triggered by a user's click on a button, link, or choice.
Can be used in Business Rules only. This is false because GlideUser (g_user) methods cannot be used in Business Rules, which are server-side scripts that run on the ServiceNow platform and manipulate the database. Business Rules use a different API to access the current user information, which is GlideSystem (gs).
Can be used in Business Rules, and Scripts Includes. This is false because GlideUser (g_user) methods cannot be used in Business Rules or Script Includes, which are both server-side scripts. Script Includes are reusable units of code that can be called from any server-side script. Script Includes also use GlideSystem (gs) to access the current user information.


Reference:

Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes


https://developer.servicenow.com/dev.do#!/reference/api/newyork/client/c_GlideUserAPI






Post your Comments and Discuss ServiceNow® CAD exam with other Community members:

CAD Discussions & Posts