In ServiceNow, the Caller Access field is used to define the level of access that external scripts or applications have to a particular script include or application resource. The valid options for the Caller Access field are:
* None: No special restrictions are applied; the resource is accessible as defined by other security settings.
* Caller Restriction: Limits access to the resource, allowing only specified callers or applications to invoke it.
* Caller Tracking: Enables tracking of which callers are accessing the resource, providing an audit trail for monitoring purposes.
Options such as "Accessible from," "Allow Configuration," and "Caller Permission" are not valid selections for the Caller Access field.
For more detailed information, refer to the official ServiceNow documentation on Restricted Caller Access Privileges.

There is no "copy" button on the application record (at least I couldn't see one). Also, see here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/reference/r_ManagingApplications.html

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts

The statement that is not true for Modules is that every Module must be associated with a table. A Module is the functionality within an Application Menu that opens a content page in the content frame or a separate tab or window. A Module can be associated with a table, a list, a form, a report, a script, or any other type of page. For example, the Open Module under the Incident Application Menu opens a list of incident records from the Incident table, while the Overview Module under the Performance Analytics Application Menu opens a dashboard page with various charts and widgets. The other statements are true for Modules. Access to Modules is controlled with roles, as each Module can have one or more roles specified in its definition that determine who can see and access it. Modules open content pages, as they are links to different types of pages that provide information and functionality to users. Every Module must be part of an Application Menu, as they are the second-level navigation options for Applications. Reference: Modules

g_scratchpad is a server-to-client data transfer object used primarily in the classic web UI rendering pipeline. A common, documented pattern is to populate g_scratchpad in a Display Business Rule (server- side) and then read those values in client-side scripts (such as Client Scripts or UI Scripts) while the form is being rendered in the browser. This avoids extra server calls when you need a small set of precomputed values or flags, such as whether the current user meets a condition, whether a related record exists, or which UI behavior should be enabled. It is not used to "populate properties for a Display Business Rule" as an end in itself; rather, the Display Business Rule is the place where developers often set g_scratchpad. It is also not a concept for defining constructors/destructors for table classes. While similar patterns can exist across experiences, g_scratchpad is specifically recognized as a web client bridging mechanism tied to server-side display processing, which matches option B.