To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.
The following options are not the best ways to see what application artifacts will be in a published application:
Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.
Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.
Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. Reference: Publish an Application, Application Files

https://developer.servicenow.com/dev.do#!/reference/api/rome/client
The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user's preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user's role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.
Reference:
[GlideUser object (g_user)]
[Workflow scripts]
[Business Rules]
Script Includes
[GlideSystem object (gs)]

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.
The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.
References:
[Workflow overview]
[Workflow context]

The syntax used in a Record Producer script to access values from Record Producer form fields is producer.variable_name. A Record Producer is a type of catalog item that allows users to create records on any table from the service catalog. A Record Producer script is a server-side script that runs when a Record Producer is submitted, and can be used to set values or perform actions on the generated record. The producer object is a global object that represents the Record Producer form and its variables. The variable_name is the name of the variable defined in the Record Producer. References: [ServiceNow Docs - Record producers], [ServiceNow Docs - Record producer script]

A Read-only protection policy allows the Script Include logic to be visible but prevents changes to the script on the instance where the application is installed. This is different from "Protected," which is stronger and is intended to hide the script contents. It is also different from "None," which allows other application developers to customize the Script Include. The CAD topic here is application file protection and intellectual- property management in distributed applications. Read-only is useful when developers want consumers to inspect the implementation for transparency or troubleshooting but do not want them to modify the script values. Therefore, option C accurately describes Read-only protection behavior.