Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn't exist In a Business Rule, the following returns true if the currently logged in user has the admin role:
* gs.hasRole('admin'). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole('admin') will return true if the current user has the admin role, and false otherwise.
The following do not return true if the currently logged in user has the admin role in a Business Rule:
* g_form.hasRoleExactly('admin'). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly('admin') will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.
* g_form.hasRole('admin'). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole('admin') will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.
* gs.hasRoleExactly('admin'). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object.
There is no method that checks if the current user has exactly the specified role and no other roles in the gs object. References: Business Rules, GlideSystem, GlideForm

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator
/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

In ServiceNow, Access Controls (ACLs) are used to manage permissions for various database operations on tables and their records. The primary operations that can be controlled include:
* Create:
* Description: Permission to insert new records into a table.
* Control: ACLs can be defined to allow or deny users the ability to create records based on roles, conditions, or scripts.
* Update:
* Description: Permission to modify existing records in a table.
* Control: ACLs can restrict who can update records, ensuring that only authorized users can make changes.
Other Operations:
* Read: Controls the ability to view records in a table.
* Delete: Manages the permission to remove records from a table.
Incorrect Options:
* Execute: Not a standard database operation controlled by ACLs in ServiceNow.
* Query: While querying is part of the read operation, ACLs specifically control the read access rather than the query process itself.

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. References: UI Actions, Field Types