CAD Practice Exam Questions with Answers Certified Application Developer - ServiceNow Certification

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. You can use Application Access to control the following database operations:

Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option.

Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option.

Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option.

Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option.

The one database operation that cannot be controlled with Application Access is Query. Query is not an operation, but a method of the GlideRecord class that is used to retrieve records from the database on the server-side. Query is not part of the Application Access rules, but it is affected by the Access Controls and the user’s roles.

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html

In the Automated Test Framework (ATF) of ServiceNow, the "Impersonate" test step is used to simulate actions as a specific user. This is crucial for testing functionalities that depend on user roles, permissions, or specific user contexts.

Key Points:

Purpose: The "Impersonate" step allows the test to execute subsequent steps as if performed by the specified user, ensuring that role-based permissions and access controls are accurately tested.

Usage: To add an "Impersonate" step:

Open your test in ATF.

Click on "Add Test Step."

Select "Impersonate User."

Choose the user you want to impersonate for the test.

Considerations: Ensure that the user being impersonated has the necessary roles and permissions for the actions being tested. Additionally, be aware that impersonation affects both server-side and client-side operations during the test.

An Access Control list (ACL) defines what data users can access and how they can access it in ServiceNow tables1. The ACL evaluates the user roles and the conditions defined in the ACL rules to determine the user’s access level2. In this case, the ACL rules for the table are as follows:

table.None read Access Control for users with the admin and itil roles: This means that users with the admin or itil roles cannot read any field in the table unless there is a more specific rule that grants them access3.

table. * read Access Control for users with the admin role: This means that users with the admin role can read all fields in the table.

table. field3 read Access Control for users with the itil role: This means that users with the itil role can read only the field3 in the table.

Therefore, a user with the itil role can read only the field3 in the table, and not the other fields.

References = 1: Access Control Lists - ServiceNow Docs 2: How ACL Rules Are Evaluated - ServiceNow Docs 3: Access Control List Rules - ServiceNow Docs : Wildcard in ACL Rules - ServiceNow Docs : Field-Level ACL Rules - ServiceNow Docs

The purpose of application scoping is NOT to provide a way of tracking the user who developed an application. Application scoping does not store or display information about the user who created or modified an application or its artifacts. The purpose of application scoping is to provide a relationship between application artifacts, provide a namespace to prevent cross-application name collisions, and provide controls for how scripts from another scope can alter tables in a scoped application. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

ServiceNow supports publishing an application to an application repository, an Update Set, or the ServiceNow Store. These methods allow the application to be installed on other instances or shared with other users.

Publish an application to the application repository

4 Ways to Publish a ServiceNow Application

Publish applications to the ServiceNow Store

Application developers can specify which ServiceNow page a user sees after submitting a new record using the Record Producer UI by writing a script in the Record Producer’s Script field: producer.redirect = “”;. This script sets the redirect property of the producer object to the URL of the desired page. For example, producer.redirect = “home.do”; will redirect the user to the homepage after submitting the record. The other options are not valid ways to specify the redirect page for a Record Producer. Reference: Populate record producer data and redirect users

"If there are no spreadsheets or existing tables to use for your application, you can create and customize a new table." see this quote in link below:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/create-table.html

Also see:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/task/gac-create-table-from-scratch.html

Also, no search results if search on "Now Experience Table Creator".

A benefit of creating an Application Properties page for each application you develop is that Application Properties allow a developer or admin to make changes to an application’s behavior without modifying application artifacts. Application Properties are system properties that store configuration information for a specific application. They can be used to control various aspects of the application, such as feature flags, default values, thresholds, or URLs. By creating an Application Properties page, you can group and display all the properties related to your application in one place and make them easy to access and update. This way, you can avoid hard-coding static data in your application code and make your application more flexible and maintainable. Reference: Working with System Properties, Organizing your ServiceNow System Properties

A Module in ServiceNow is a navigational element within an Application Menu that directs users to specific records, lists, forms, or reports.

Option A (Correct): Modules always belong to an Application Menu, providing structured navigation.

Option B (Incorrect): Modules can link to pages, reports, and URLs, not just tables.

Option C (Incorrect): Modules can open forms, lists, dashboards, and external URLs.

Option D (Incorrect): Modules can be restricted by roles, limiting visibility and access.

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.

Definition of a Spoke:A "spoke" is a scoped application or component of an application that contains Flow Designer actions and integrations. Spokes provide reusable functionality and are typically used to extend the capabilities of Flow Designer.

Why It’s Called a Spoke:

Spokes are part of the ServiceNow Flow Designer framework.

They contain predefined actions that are reusable across multiple flows. For example, an "Email Spoke" might include actions for sending emails or managing email configurations.

Why Other Options Are Incorrect:

Option B (Flow): This refers to an individual flow, not the application containing reusable actions.

Option C (Bundle): There is no such term as "Bundle" specific to Flow Designer in ServiceNow.

Option D (Action): While flows contain actions, the scoped application that houses these actions is referred to as a spoke.

ServiceNow Developer Documentation on Flow Designer Spokes?.

When evaluating Access Controls, ServiceNow searches and evaluates:

From the most specific match to the most generic match. This is the correct answer because ServiceNow follows a top-down approach when evaluating Access Control (ACL) rules, which are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. ServiceNow starts with the most specific match, which is the field-level ACL rule, then moves to the table-level ACL rule, and finally to the global or * ACL rule. ServiceNow grants access if any of the ACL rules evaluates to true, and denies access if all of the ACL rules evaluate to false.

The following are not correct descriptions of how ServiceNow searches and evaluates Access Controls:

Only for matches on the current table. This is not correct because ServiceNow does not only look for matches on the current table, but also on the parent tables and the global or * table. For example, if there is no ACL rule for the incident table, ServiceNow will look for an ACL rule for the task table, which is the parent table of the incident table, and then for the global or * table, which is the parent table of all tables.

Only for matches on the current field. This is not correct because ServiceNow does not only look for matches on the current field, but also on the table that contains the field and the global or * table. For example, if there is no ACL rule for the short_description field on the incident table, ServiceNow will look for an ACL rule for the incident table, and then for the global or * table.

From the most generic match to the most specific match. This is not correct because ServiceNow does not follow a bottom-up approach when evaluating Access Controls, but a top-down approach, as explained above. References: Access Control Rules, ACL Evaluation Order

https://developer.servicenow.com/dev.do#!/learn/learning-plans/paris/new_to_servicenow/app_store_learnv2_securingapps_paris_access_controls_evaluation_order

ServiceNow provides several methods to install applications onto an instance, each suited to different scenarios:

Import an Application from an XML File (Option A):

Description: Developers can export an application as an XML file and then import it into another ServiceNow instance.

Use Case: This method is commonly used for moving applications between instances, such as from development to production.

Procedure:

Navigate to "System Applications" > "Applications."

Click on the "Import" button.

Upload the XML file of the application.

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

"Restricted caller access [sys_restricted_caller_access] records track cross-scope applications or scripts that request access to an application, application resource, or event in the Now Platform." <<== this is the third sentence down in the following link: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/restricted-caller-access-privilege.html

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.

References = Enable or disable an application menu or module, Grant a role access to applications and modules, Controlling access to applications and modules.

To include specific records from a table (often referred to as seed data) when distributing an application in ServiceNow, developers must add these records to the application as application files. This ensures that when the application is installed on another instance, the specified records are included.

Option C is correct because using the "Create Application Files" feature allows developers to select specific records to include in the application package. This process creates application files for the selected records, ensuring they are installed along with the application on other instances.

Options A, B, and D are incorrect:

A: The activation status of Table A and whether it extends the Task table do not determine whether its records are included during installation.

B: Having an automatic number counter and setting a table property do not control the inclusion of records in the application package.

D: The System Clone > Exclude Tables list pertains to cloning operations and does not affect application installation.

For detailed guidance on including table records in application deployments, refer to the official ServiceNow documentation:

SERVICENOW.COM

"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

"Add instructional text and other design elements to your forms by using form annotations in Form Builder." https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/form-builder/task/create-form-annotations.html

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

Inherited fields in ServiceNow are fields that are part of a parent table and automatically become part of child tables through inheritance. This structure is foundational in the ServiceNow data model, ensuring that child tables maintain a consistent relationship with their parent tables.

Here’s why inherited fields cannot be deleted from a child table:

System Design:ServiceNow employs a table inheritance model where child tables derive fields and properties from parent tables. Deleting inherited fields from a child table would break the integrity of the data model, as those fields are shared across multiple tables.

Impact on Functionality:Many inherited fields, such as sys_created_on or sys_updated_by, are integral to the functionality of the platform. Removing them could disrupt workflows, reporting, and auditing capabilities.

Alternative Approach:If you want to hide or restrict access to inherited fields in a child table, you can use ACLs (Access Control Lists) to prevent users from viewing or modifying these fields. Another option is to use UI Policies or Client Scripts to control their visibility on forms.

Developer Note:Attempting to delete inherited fields violates ServiceNow’s core principles of maintaining a robust and unified data structure. The platform enforces these rules to ensure consistent behavior across all tables in the hierarchy.

ServiceNow Developer Documentation on Table Inheritance?.

Best practices outlined on SN Pro Tips regarding scoped application development and table structures?.

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

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html

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

The Weight field in an Email Notification determines which notification is sent when multiple notifications are triggered for the same record and recipients. Only the notification with the highest weight is sent. A weight value of zero means the notification is always sent when the notification’s When to send criteria is met. A weight value of -1 means that no email should be sent3. References: Email Notification Weight

Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:

gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole(‘admin’) will return true if the user is an administrator, and false otherwise.

current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.

The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/useful-scripts/reference/r_DisplayFieldMessages.html

Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only

A possible reason to build a custom app is to fulfill a specific use case on internal processes. For example, you may want to digitize a manual process that is not covered by an existing ServiceNow solution, such as managing inventory, tracking expenses, or scheduling events. Building a custom app on the Now Platform can help you automate workflows, improve data quality, and provide better user experiences. The other options are not valid reasons to build a custom app. To avoid using a code repository like GitHub or GitLab is not a reason to build a custom app, as you can still use source control integration with your custom app development. To create a custom integration for a 3rd party system is not a reason to build a custom app, as you can use integration tools such as IntegrationHub or REST APIs to connect with external systems without creating an app. To replace ServiceNow base tables is not a reason to build a custom app, as it is not recommended to modify or delete base tables that are essential for ServiceNow functionality. Reference: Build Custom Apps in ServiceNow – eBook

In the SOAP Message feature set, we indicate variables using the following syntax: S{variable_name}. This allows us to pass a variable with the specified name from the SOAP message record to the web service function.

Tutorial: Handling a SOAP Response in ServiceNow | John Andersen

ServiceNow SOAP - Cheat Sheet Cheat Sheet by bibingokuldas - Download …

 When configuring a REST Message, the Endpoint is:

The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?q=London.

The following are not correct definitions of the Endpoint when configuring a REST Message:

The commands to the REST script to stop execution. This is not correct because the commands to the REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.

Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.

The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found, or 500 Internal Server Error. References: REST Messages, Scripted REST APIs

The Create Branch operation is available from both Studio and the Git Repository. This operation allows you to create a new branch from an existing branch in your Git repository. You can use branches to work on different features or versions of your application without affecting the main branch. Reference: [Create a branch]

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_DefaultDesignAccessPermissions.html

The baseline behavior of a table in a privately-scoped application is that all application scopes can read from the table. A privately-scoped application is an application that restricts write access to its tables and resources to scripts within the same scope. However, read access is allowed by default for all scopes, unless the administrator explicitly denies it using an Access Control rule. This allows for data sharing between different applications while maintaining data integrity and security. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_flowdesigner_tokyo_flow_designer/app_store_learnv2_flowdesigner_tokyo_notifications_in_flow_designer/app_store_learnv2_flowdesigner_tokyo_inbound_email_and_flows

"By default, the system generates a watermark label at the bottom of each notification email to allow matching incoming email to existing records." https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/concept/c_WorkingWithWatermarks.html

 The correct combination of statements is a, b, and d. These are possible reasons to build custom applications on ServiceNow:

To replace outdated, inadequate, custom business applications and processes. Building custom applications on ServiceNow can help digitize and automate manual or legacy processes that are not covered by existing ServiceNow solutions. This can improve efficiency, data quality, user experience, and innovation.

To extend service delivery and management to all enterprise departments. Building custom applications on ServiceNow can help provide consistent and scalable services across different functions and teams in the organization. This can enhance collaboration, visibility, productivity, and customer satisfaction.

To extend the value of ServiceNow. Building custom applications on ServiceNow can help leverage the capabilities and benefits of the Now Platform®, such as low-code development tools, workflow automation engine, AI-powered insights, security operations, etc. This can increase agility, resilience, performance, and value.

The statement c is not a valid reason to build custom applications on ServiceNow:

To allow users full access to all ServiceNow tables, records, and fields. Building custom applications on ServiceNow does not imply granting users full access to all data and objects in ServiceNow. Access control rules still apply to custom applications and their components to ensure security and compliance. Reference: Build Custom Apps in ServiceNow – eBook

Flow Designer variables can store record data and complex data using the following data types:

Integer: A whole number that can be used in mathematical operations.

Array: A collection of items that can be accessed by their index or iterated over using a For each action.

String: Any kind of text, such as email addresses or the text contents of a file.

Define and Use Data Types in a Flow (Flow Designer)

Variable data types - Power Automate | Microsoft Learn

Product Documentation | ServiceNow

In ServiceNow, Access Controls (ACLs) are used to manage permissions for various database operations on tables and their records. The primary operations that can be controlled include:

Create:

Description: Permission to insert new records into a table.

Control: ACLs can be defined to allow or deny users the ability to create records based on roles, conditions, or scripts.

Update:

Description: Permission to modify existing records in a table.

Control: ACLs can restrict who can update records, ensuring that only authorized users can make changes.

Other Operations:

Read: Controls the ability to view records in a table.

Delete: Manages the permission to remove records from a table.

Incorrect Options:

Execute: Not a standard database operation controlled by ACLs in ServiceNow.

Query: While querying is part of the read operation, ACLs specifically control the read access rather than the query process itself.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/platform-events/reference/r_ScriptActions.html

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/t_IncludeApplicationData.html

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 Module Link type defines how the module opens in the content pane when the user clicks on it in the navigation pane1. The URL (from Arguments) link type allows you to specify a URL that opens the Application Properties page for the selected application2. The URL can include arguments that are evaluated at runtime, such as the application name or scope3.

References = 1: Module link types - ServiceNow Docs 2: Application properties - ServiceNow Docs 3: URL (from Arguments) - ServiceNow Docs

In ServiceNow, Application Files are configuration records that define the various components and logic that constitute an application. These include artifacts such as:

Business Rules

Client Scripts

UI Actions

Script Includes

Tables and Fields

Workflows

These artifacts collectively define the functionality and behavior of the application. When an application is developed, ServiceNow automatically creates and manages these Application Files to represent the application's components.

Option C is correct because Application Files are the fundamental building blocks that comprise a ServiceNow application, representing its various components and configurations.

Options A, B, and D are incorrect:

A: XML exports of an Update Set represent changes made to an instance but are not synonymous with Application Files.

B: CSV files are typically used for data import/export and do not represent the configuration components of an application.

D: An XML export of table records pertains to data within a table, not the configuration artifacts that define application behavior.

Application Files are ServiceNow artifacts comprising an application. An application is a group of files and data that work together to provide a service or functionality. An application file is a specific type of file that belongs to an application, such as a table, a script, a form, a business rule, a UI action, etc. Application files define the structure, logic, and interface of the application. An XML export of an application’s table records, XML exports of an application’s Update Set, and CSV files containing data imported into an application are not examples of application files, as they are data formats that can be used to transfer or store information related to an application, but not the application itself. Reference: Application Files

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

The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

gs.print() and gs.log() are older and not available in scoped applications, whereas gs.debug(), gs.info(), gs.warn(), gs.error() work in both scoped applications and global are therefore are more versatile going forward in future versions.

https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html

In ServiceNow, the Event Registry is a table that contains a record for every event recognized by the system. It allows ServiceNow to respond when these events are generated. By registering events, the system can automate activities such as triggering notifications or executing script actions when specific events occur. Therefore, the correct answer is A.

The other options are not accurate descriptions of the Event Registry:

B. The Event Log which lists all Events that have been generated: This describes the Event Log, not the Event Registry.

C. A Workflow which is launched every time an Event is generated; used to debug Events: This is not how the Event Registry functions.

D. The method used in server-side scripts to generate Events and pass parameters: This describes the gs.eventQueue() method, not the Event Registry.

For more detailed information, refer to the official ServiceNow documentation on the Event Registry.

You must script and configure all required behaviors Provided link has this statement: Extending an existing ServiceNow table means the new table inherits the parent table's columns as well as its business logic.

The following statements apply when extending an existing table:

The parent table’s Access Controls are evaluated when determining access to the new table’s records and fields. This is true because Access Control (ACL) rules are inherited from the parent table to the child table, unless the child table has its own ACL rules that override the parent table’s rules. ACL rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions.

The new table inherits the functionality built into the parent table. This is true because the new table inherits the business logic and the relationships from the parent table, such as Business Rules, Script Includes, UI Actions, UI Policies, and Reference Fields. Business logic and relationships are used to define the behavior and the structure of the data on the ServiceNow platform.

The new table inherits all of the fields from the parent table. This is true because the new table inherits the columns and the attributes from the parent table, such as Field Name, Data Type, Default Value, and Mandatory. Columns and attributes are used to define the properties and the characteristics of the data on the ServiceNow platform.

The following statement does not apply when extending an existing table:

You must script and configure all required behaviors. This is false because you do not have to script and configure all required behaviors when extending an existing table, as some of the behaviors are already inherited from the parent table, as explained above. However, you can script and configure additional or customized behaviors for the new table, such as adding new fields, creating new Business Rules, or modifying existing UI Actions. References: Table Extension, Access Control Rules

"A table that extends another table is called a child class, and the table it extends is the parent class" - this is about halfway down in this link below: https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.html

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. References: Publish an Application, Application Files

"By default, all application scope scripts can read the table's records but cannot perform any other database operations." https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/servicenow_administrator/app_store_learnv2_securingapps_tokyo_application_access_database_settings

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