IT Certification Exam Questions & Answers

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/gac-tables.html

https://developer.servicenow.com/dev.do#!/reference/api/rome/client

Reference:
A module is a navigation item that provides access to a feature or functionality in ServiceNow. Modules must have a link type, which determines how the module behaves when clicked. The following is a list of link types:
Assessment. This is a link type that opens an assessment, which is a survey or questionnaire that measures the effectiveness of a process or service.
List of Records. This is a link type that opens a list of records from a table or a saved filter.
Separator. This is a link type that creates a horizontal line to separate modules in the application menu.
Timeline Page. This is a link type that opens a timeline page, which is a graphical representation of the duration and sequence of events or tasks.
The following are not link types, but other module attributes or field types:
List of Records, Separator, Catalog Type, Roles. These are not link types, but a combination of a link type (List of Records), a module attribute (Separator), a field type (Catalog Type), and a user attribute (Roles).
List of Records, Content Page, Order, URL (from arguments:). These are not link types, but a combination of a link type (List of Records), a module attribute (Content Page), a field name (Order), and a link type argument (URL).
Assessment, List of Records, Content Page, Roles. These are not link types, but a combination of a link type (Assessment), a link type (List of Records), a module attribute (Content Page), and a user attribute (Roles). References: Modules, Create a Module

https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_securingapps_rome_application_access
https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ExampleDenyingAllDesignAccess.html

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ScriptProtectionPolicy.html The following is true for a Script Include with a Protection Policy value of Protected:
The Protection Policy is applied only if the application is downloaded from the ServiceNow App Store. This is true because the Protection Policy is a feature that allows developers to protect their Script Includes from being viewed or modified by other users when they distribute their applications through the ServiceNow App Store. The Protection Policy is only enforced when the application is installed from the App Store, not when it is developed or tested on the instance.
The following are not true for a Script Include with a Protection Policy value of Protected:
Any user with the protected_edit role can see and edit the Script Include. This is false because the protected_edit role is not related to the Protection Policy, but to the Access Control (ACL) rules. The protected_edit role allows users to edit protected fields on a table, such as the script field on the sys_script table, which stores the Business Rules. The Protection Policy does not use roles to control access to the Script Includes, but a cryptographic key that is generated when the application is published to the App Store.
The Protection policy option can only be enabled by a user with the admin role. This is false because the Protection policy option can be enabled by any user who has the application_admin role for the scoped application that contains the Script Include. The application_admin role grants full access to the application development and administration within the scope of the application.
The Protection Policy is applied only if the glide.app.apply_protection system property value is true. This is false because the glide.app.apply_protection system property is not related to the Protection Policy, but to the Application Restricted Caller Access (ARCA) feature. The ARCA feature allows developers to restrict the access to the Script Includes from other applications based on the caller’s scope. The glide.app.apply_protection system property determines whether the ARCA feature is enabled or disabled on the instance. References: Script Includes, Protect Script Includes, Application Restricted Caller Access

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

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

“Application developers must select an application as their current scope context.” https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_SelectAnAppFromTheAppPicker.html

Explanation
A spoke is a scoped application containing Flow Designer content dedicated to a particular application or record type. Flow Designer provides a set of core actions to automate Now Platform processes. You can add application-specific core actions by activating the associated spoke.

The server-side API debug log method available for scoped applications is gs.info(). This method logs informational messages that describe the progress of the application. Older methods such as gs.print() and gs.log() are not available in scoped applications. The gs.debuglog() method does not exist. The gs.info(), gs.warn(), gs.error(), and gs.debug() methods work in both scoped applications and global, and are therefore more versatile going forward in future versions. Reference: Debugging best practices

https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221

Explanation/Reference: https://developer.servicenow.com/dev.do#!/reference/api/newyork/client/c_GlideUserAPI

Extending an existing table such as the Task table when creating a new application has several benefits, such as:
You can repurpose existing fields by simply changing the label. For example, you can change the Short description field to Summary or Title for your new table.
You can use existing fields with no modifications. For example, you can use the Assigned to, Priority, and State fields for your new table without changing anything.
Existing logic from the parent table will be automatically applied to the new table. For example, you can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table.
The only option that is not true is d) All of the parent table records are copied to the new table. Extending a table does not copy any records from the parent table to the new table. It only creates a new table that inherits the fields and logic from the parent table.
References:
[Extend a table]
[Task table]