Free CAD Exam Dumps

Client-side scripts manage what?

Correct Answer:C
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html

Identify characteristic(s) of a Record Producer. Choose 3 answers

Correct Answer:ACE
A Record Producer is a type of service catalog item that allows users to create records on a specified table. A Record Producer has the following characteristics:
✑ Graphics can be included on the user interface: You can add images, icons, or
banners to the Record Producer to make it more appealing and informative for the user. You can also use HTML and CSS to customize the layout and style of the Record Producer.
✑ You can script behaviors of fields in the user interface: You can use Client Scripts
and UI Policies to control the behavior and appearance of the fields on the Record Producer. For example, you can use Client Scripts to validate the field inputs, perform calculations, or populate default values. You can also use UI Policies to show or hide fields, make fields mandatory or read-only, or set field values based on conditions.
✑ Each field prompts the user with a question rather than a field label: You can use
the Variable Question field to define the question that prompts the user for the field value. The question can be more descriptive and user-friendly than the field label. For example, you can use the question “What is the name of the project?” instead of the field label “Name”.
The other statements are not true for Record Producers. Record Producers do not always insert records into the Requested Item [sc_req_item] table. They can insert records into any table that is specified in the Record Producer properties. Record Producers also do not have to be scripted. They can use the default script that maps the variable values to the record fields, or they can use a custom script that defines the logic for creating the record. References:
✑ [Record Producers]
✑ [Record Producer properties]
✑ [Record Producer scripts]

When configuring an Access Control which has no condition or script, which one of the following statements is NOT true?

Correct Answer:D
Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.
The statements A, B, and C are true for Access Controls that have no condition or script. For example:
✑ table.* will grant access to every field in a record. This means that the user can
view and edit all the fields on the record, regardless of their role or any other criteria.
✑ table.None will grant access to every record on the table. This means that the user
can view and edit all the records on the table, regardless of their role or any other criteria.
✑ table.field will grant access to a specific field in a record. This means that the user
can view and edit only that field on the record, regardless of their role or any other criteria.
The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.
References:
✑ [Access Control rules]
✑ [Create an Access Control rule]

When configuring a module, what does the Override application menu roles configuration option do?

Correct Answer:A
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
Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0716421

Which of the following statements is true about Guided Application Creator?

Correct Answer:D
The welcome screen appears every time a new application is created through the Guided Application Creator. The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app. Reference: Guided App Creator