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. References: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes

See list of triggers on right hand side of this webpage: https://docs.servicenow.com/en-US/bundle/tokyo- application-development/page/administer/flow-designer/reference/flow-triggers.html The trigger types in Flow Designer are Application, Record, Schedule, and Topic. Outbound Email is not a trigger type, but an action type that can be used in a flow to send an email message1. References: Flow Designer Trigger Types

In ServiceNow, to display data from another table within a form, the Reference field type is used. A Reference field creates a relationship between the current table and another table by storing a unique identifier (sys_id) of a record from the referenced table. This allows users to select a record from the referenced table and access its data within the form. Therefore, the correct answer is B.
The other field types do not provide this functionality:
* A. Phone Number: This field type is designed to store phone numbers and does not create relationships between tables.
* C. Date: This field type is used to store date values and does not reference records from other tables.
* D. String: This field type stores text strings and does not facilitate querying records from another table.
For more detailed information, refer to the official ServiceNow documentation on Field Types.

The statements that must evaluate to true for a user to pass an Access Control are:
Conditions configured in the Access Control must evaluate to true.
The user has one of the roles specified in the Required roles related list.
Scripts configured in the Access Control must evaluate to true.
An Access Control is a rule that determines whether a user can access a particular object or operation in ServiceNow. An Access Control consists of three elements: Conditions, Roles, and Script. Each element specifies a requirement that the user must meet to access the object or operation. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Therefore, for a user to pass an Access Control, all three elements must evaluate to true.
The other statements are not required for a user to pass an Access Control. Other matching Access Controls for the records do not need to evaluate to true, as only one matching Access Control needs to return true for access to be granted. The user does not need to be granted access through a business rule, as business rules are not part of Access Controls and do not affect their evaluation. Reference: Access control rules, Access Controls