CAD Exam Questions and Answers | Exam-Dumps (Page: 7)

QUESTION: 49

Which one of the following is NOT required to link a ServiceNow application to a Git repository?

Password
URL
User name
Application name

Answer(s): D

Explanation:

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application.

Reference:

[Link an application to a Git repository]

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

Reveal Solution Next Question

QUESTION: 50

Which Report Type(s) can be created by right-clicking on a column header in a table's list?

Bar Chart, Pie Chart, Histogram, and Line
Bar Chart
Bar Chart, Pie Chart, and Histogram
Bar Chart and Pie Chart

Answer(s): D

Explanation:

The Bar Chart and Pie Chart report types can be created by right-clicking on a column header in a table's list. These report types show how individual pieces of data relate to the whole using proportional bars or slices. You can also choose different aggregation methods such as count, sum, average, min, max, or percent.

Reference:

[Create reports from lists]

Reveal Solution Next Question

QUESTION: 51

Which one of the following is NOT a method used for logging messages in a server-side script for a privately- scoped application?

gs.log()
gs.error()
gs.warn()
gs.debug()

Answer(s): A

Explanation:

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.

Reference:

https://community.servicenow.com/community? id=community_QUESTION NO :&sys_id=bd71cb29db98dbc01dcaf3231f9619c6

Reveal Solution Next Question

QUESTION: 52

If the Create module field is selected when creating a table, what is the new module's default behavior?

Open an empty form so new records can be created
Open a link to a wiki article with instructions on how to customize the behavior of the new module
Display an empty homepage for the application
Display a list of all records from the table

Answer(s): D

Explanation:

When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.

Reference:

Create a table
Module properties

Reveal Solution Next Question

QUESTION: 53

How must Application Access be configured to prevent all other private application scopes from creating configuration records on an application's data tables?

You must create Access Controls to prevent all other application scopes from creating configuration records on an application's data tables rather than using Application Access
Set the Accessible from field value to All application scopes and de-select the Can create option
Set the Accessible from field value to This application scope only and de-select the Allow access to this table via web services option
Set the Accessible from field value to This application scope only

Answer(s): D

Explanation:

Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. By setting the Accessible from field value to This application scope only, you can restrict the access to your data tables to only your application scope. This means that other application scopes cannot create, read, write, or delete records on your data tables, unless they have explicit permissions through Access Controls or other means.

Reference:

Application Access
[Application scope]

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

Reveal Solution Next Question

QUESTION: 54

What are some of the benefits of extending an existing table such as the Task table when creating a new application?

a) You can repurpose existing fields by simply changing the label.
b) Use existing fields with no modifications.

c) Existing logic from the parent table will be automatically applied to the new table. d) All of the parent table records are copied to the new table.

a, b, c, and d
a and b
b and c
a, b, and c

Answer(s): D

Explanation:

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.

Reference:

[Extend a table]
[Task table]

Reveal Solution Next Question

QUESTION: 55

When configuring an Access Control which has no condition or script, which one of the following statements is NOT true?

table.*will grant access to every field in a record
table.None will grant access to every record on the table
table.field will grant access to a specific field in a record
table.id will grant access to a specific record on the table

Answer(s): D

Explanation:

Access Controls are rules that define who can access what data and how they can access it.
When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.
The statements A, B, and C are true for Access Controls that have no condition or script. For example:
table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria. table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria. table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria. The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.

Reference:

[Access Control rules]
[Create an Access Control rule]

Reveal Solution Next Question

QUESTION: 56

Which of the following methods are useful in Access Control scripts?

g_user.hasRole() and current.isNewRecord()
gs.hasRole() and current.isNewRecord()
g_user.hasRole() and current.isNew()
gs.hasRole() and current.isNew()

Answer(s): B

Explanation:

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.

Reference:

[Access Control scripts]

[GlideSystem methods]
[GlideRecord methods]

http://servicenowmypath.blogspot.com/2017/

Reveal Solution Next Question

ServiceNow CAD Exam (page: 7) ServiceNow Certified Application Developer - Training and Certification Updated on: 15-Feb-2026

QUESTION: 49

Explanation:

Reference:

QUESTION: 50

Explanation:

Reference:

QUESTION: 51

Explanation:

Reference:

QUESTION: 52

Explanation:

Reference:

QUESTION: 53

Explanation:

Reference:

QUESTION: 54

Explanation:

Reference:

QUESTION: 55

Explanation:

Reference:

QUESTION: 56

Explanation:

Reference:

ServiceNow CAD Exam (page: 7)
ServiceNow Certified Application Developer - Training and Certification
Updated on: 15-Feb-2026