Access Control debug information identifies whether each element of an Access Control granted or denied access. The elements appear in the debug information in the order of evaluation. In which order are the elements of an Access Control evaluated?
Correct Answer: C
"The sequence is ROLES first, then condition, then script." - Chuck Tomasi says so at this link:https://www.servicenow.com/community/grc-forum/order-of-execution-of-an-acl/m-p/1311962/highlight/tru
Question 112
For Application Access there is a configuration option called Allow access to this table via web services. Which one of the following statements is true when this option is selected?
Correct Answer: B
Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. By selecting the Allow access to this table via web services option, you can enable other application scopes to access your data tables using web services, such as SOAP or REST. However, the user performing the query via web services must have the correct permissions to access the table's records. The user must have the appropriate roles and access controls to perform the operations on the table, such as create, read, write, or delete. The other statements are not true when this option is selected. This option does not restrict the ability to delete records via web services, nor does it allow records to be always read. The access to the records depends on the user's permissions and the web service method. This option also does not restrict access only to SOAP web services, but applies to both SOAP and REST web services. Finally, this option is not the only way to enable web service access to the table's records. Even when this option is not selected, users with the correct permissions can use web services to access the table's records, as long as they specify the application scope in the web service request. References: Application Access Web service access to scoped applications
Question 113
Which one of the following client-side scripts apply to Record Producers?
Correct Answer: D
Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies
Question 114
Which one of the following is NOT a UI Action type?
Correct Answer: A
A UI Action is a button, link, or choice that can be clicked by a user to perform an action, such as submitting a form or running a script. The following are UI Action types: List choice. This is a UI Action that appears as a choice list on a list of records. It can be used to perform an action on multiple records at once, such as deleting or updating them. Form button. This is a UI Action that appears as a button on a form. It can be used to perform an action on the current record, such as saving or approving it. List banner button. This is a UI Action that appears as a button on the banner of a list of records. It can be used to perform an action on the entire list, such as exporting or printing it. The following is not a UI Action type: Form choice. This is not a UI Action type, but a field type. A form choice is a field that displays a choice list on a form. It can be used to select a value from a predefined set of options, such as priority or state. Reference: UI Actions, Field Types
Question 115
The source control operation used to store local changes on an instance for later application is called a(n) <blank>.
Correct Answer: C
The source control operation used to store local changes on an instance for later application is called a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be pushed to a remote repository. Developers can use stashes to save their work in progress without committing it to the local repository or discarding it. Stashes can be applied later to restore the changes to the working directory, or dropped if they are no longer needed. References: [ServiceNow Docs - Stash local changes], [ServiceNow Docs - Source control]
