https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/form-administration/concept/c_FormDesign.html The Form Designer is a graphical interface for creating and customizing forms. The following statements are true for the Form Designer:
To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. This will add the field to the form view without changing the table definition.
To create a new field on a form's table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. This will create a new column on the table and add the field to the form view.
To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. This will remove the field from the form view but not from the table definition.
The following statement is false for the Form Designer:
To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form. This is incorrect because sections are not available in the Field Types tab. To add a section, click the Add Section button on the toolbar or right-click on the form and select Add Section. Reference: Introduction to App Engine Studio for Developers, ServiceNow Studio Overview, Form Designer

In ServiceNow, when developing within a privately-scoped application, certain logging methods are recommended for use in server-side scripts to ensure proper logging and debugging. The GlideSystem (gs) object provides several methods for this purpose:
* gs.debug():
* Description: Logs messages at the "Debug" level.
* Usage: gs.debug('Debug message here');
* Purpose: Useful for logging detailed information during development and troubleshooting. These messages are typically only visible when the system's logging level is set to "Debug."
* gs.error():
* Description: Logs messages at the "Error" level.
* Usage: gs.error('Error message here');
* Purpose: Used to log error messages that indicate a problem that might still allow the application to continue running.
* gs.warn():
* Description: Logs messages at the "Warning" level.
* Usage: gs.warn('Warning message here');
* Purpose: Used to log potentially harmful situations that are not necessarily errors but may require attention.
* gs.info():
* Description: Logs messages at the "Information" level.
* Usage: gs.info('Information message here');
* Purpose: Used to log informational messages that highlight the progress of the application at a coarse-grained level.
Deprecated or Unsupported Methods in Scoped Applications:
* gs.log():
* Description: This method is not supported in scoped applications. It is restricted to the global scope and is not accessible from a private scope. Therefore, it should be avoided in privately- scoped applications.
Reference: Logging for Scoped Applications - ServiceNow Elite
gs.logError():
Description: This method is not a standard GlideSystem logging method in ServiceNow. The appropriate method to log errors is gs.error().
Reference: For more detailed information, please refer to the official ServiceNow documentation on Scoped GlideSystem Logging Methods.

Roles are used to control access to applications and modules in the application navigator. Each application menu or module has a role field that specifies which role is required to view it. Users who do not have the specified role or a role that contains it will not see the application menu or module. Roles can also be used to control access to other features and capabilities in ServiceNow, such as tables, fields, scripts, and workflows.
Reference = Enable or disable an application menu or module, Grant a role access to applications and modules, Controlling access to applications and modules.

When a new application table is created and the option to create a module is used, ServiceNow creates a list module for that table in the application menu. The default module name is based on the plural form of the application or table label, so users see a natural list-style module name in the Application Navigator. The
"U_" or "X_" style prefixes relate to technical table names and scoped naming, not to the user-facing module title. The same name as the application is normally used for the application menu, not the list module. This is why option B is the correct CAD answer.

The data type of a field determines the format, validation, and display of the field value on a form. When selecting a data type for a field, you should consider the purpose and function of the field. The statements A, C, and D are correct for selecting a data type for a field. For example:
* Use the Choice data type to limit options in a field: The Choice data type allows you to create a field that has a predefined set of options for the user to select from. The options can be displayed as a drop-down list, radio buttons, or checkboxes. For example, you can use the Choice data type for a field that indicates the priority of a task.
* Use the Phone Number data type to automate phone number data validation: The Phone Number data type allows you to create a field that accepts and validates phone numbers. The field will automatically format the phone number according to the user's locale and country code. For example, you can use the Phone Number data type for a field that stores the contact number of a user.
* Use the string data type for a free-form text field: The string data type allows you to create a field that accepts any text input from the user. The field can have a maximum length of 255 characters. For example, you can use the string data type for a field that captures the short description of an incident.
The statement B is not correct for selecting a data type for a field. There is no Data data type in ServiceNow.
To enter the date and time of day, you should use the Date/Time data type. The Date/Time data type allows you to create a field that accepts and displays a date and time value. The field will use a calendar widget and a time picker to help the user enter the value. For example, you can use the Date/Time data type for a field that records the due date of a task.
References:
* [Field types]
* [Date/Time field type]