Question #1
Which of the following statements is true for the Form Designer?
a) To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form.
b) 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.
c) To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button.
d) To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form.
- A . a, b, c, and d
- B . b, c, and d
- C . a, b, and d
- D . a, b, and c
Correct Answer: D
D
Explanation:
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
D
Explanation:
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
Question #2
Which of the following are configured in an Email Notification?
a) Who will receive the notification.
b) What content will be in the notification.
c) When to send the notification.
d) How to send the notification.
- A . a, b and c
- B . a, b, and d
- C . b, c and d
- D . a, c and d
Correct Answer: A
A
Explanation:
https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html
Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0712569
An Email Notification is a record that defines the content and conditions for sending an email message from the ServiceNow platform. The following are configured in an Email Notification: Who will receive the notification. This is specified by the Recipients related list, which can include users, groups, email addresses, or scripts that return email addresses.
What content will be in the notification. This is specified by the Subject and Message HTML fields, which can include variables, scripts, or templates to dynamically generate the email content. When to send the notification. This is specified by the When to send tab, which defines the conditions and events that trigger the email notification. The following is not configured in an Email Notification:
How to send the notification. This is not a configuration option for an Email Notification. The platform uses the SMTP protocol to send email messages, and the email properties control the email server settings and behavior.
Reference: Email Notifications, Get Started with Notifications
A
Explanation:
https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html
Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0712569
An Email Notification is a record that defines the content and conditions for sending an email message from the ServiceNow platform. The following are configured in an Email Notification: Who will receive the notification. This is specified by the Recipients related list, which can include users, groups, email addresses, or scripts that return email addresses.
What content will be in the notification. This is specified by the Subject and Message HTML fields, which can include variables, scripts, or templates to dynamically generate the email content. When to send the notification. This is specified by the When to send tab, which defines the conditions and events that trigger the email notification. The following is not configured in an Email Notification:
How to send the notification. This is not a configuration option for an Email Notification. The platform uses the SMTP protocol to send email messages, and the email properties control the email server settings and behavior.
Reference: Email Notifications, Get Started with Notifications
Question #3
To see what scripts, reports, and other application artifacts will be in a published application:
- A . Enter the name of the Application in the Global search field
- B . Open the list of Update Sets for the instance
- C . Examine the Application Files Related List in the application to be published
- D . Open the artifact records individually to verify the value in the Application field
Correct Answer: B
B
Explanation:
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.
Reference: Publish an Application, Application Files
B
Explanation:
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.
Reference: Publish an Application, Application Files
Question #4
Which one of the following is NOT a debugging strategy for client-side scripts?
- A . g_form.addInfoMessage()
- B . Field Watcher
- C . jslog()
- D . gs.log()
Correct Answer: D
D
Explanation:
https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_scripting_rome_debugging_client_scripts The following are debugging strategies for client-sidescripts, which run in the web browser and manipulate the user interface:
g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.
Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.
jslog(). This is a client-side API that writes a message to the browser console.
The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:
gs.log(). This is a server-side API that writes a message to the system log.
Reference: Client-Side Scripting APIs, Debugging Client Scripts
D
Explanation:
https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/new_to_servicenow/app_store_learnv2_scripting_rome_debugging_client_scripts The following are debugging strategies for client-sidescripts, which run in the web browser and manipulate the user interface:
g_form.addInfoMessage(). This is a client-side API that displays an information message at the top of the form.
Field Watcher. This is a debugging tool that displays the current and previous values of one or more fields on a form.
jslog(). This is a client-side API that writes a message to the browser console.
The following is not a debugging strategy for client-side scripts, but for server-side scripts, which run on the ServiceNow platform and manipulate the database:
gs.log(). This is a server-side API that writes a message to the system log.
Reference: Client-Side Scripting APIs, Debugging Client Scripts
Question #5
Which Application Access configuration field(s) are NOT available if the Can read configuration field is NOT selected?
- A . All access to this table via web services
- B . Can create, Can update, and Can delete
- C . Can read does not affect the availability of other Application Access fields
- D . Allow configuration
Correct Answer: C
C
Explanation:
"You must first select read access to grant any other API record operation." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html
The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:
Can create. This field determines whether users can create records on the application tables.
Can update. This field determines whether users can update records on the application tables.
Can delete. This field determines whether users can delete records on the application tables.
These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.
The following Application Access configuration fields are available regardless of the Can read configuration field:
All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.
Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes.
Reference: Application Access, Certified Application Developer (CAD) Learning Path
C
Explanation:
"You must first select read access to grant any other API record operation." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html
The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:
Can create. This field determines whether users can create records on the application tables.
Can update. This field determines whether users can update records on the application tables.
Can delete. This field determines whether users can delete records on the application tables.
These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.
The following Application Access configuration fields are available regardless of the Can read configuration field:
All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.
Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes.
Reference: Application Access, Certified Application Developer (CAD) Learning Path
Question #6
Which of the following is NOT a trigger type in Flow Designer?
- A . Outbound Email
- B . Application
- C . Record
- D . Schedule
Correct Answer: A
A
Explanation:
See list of triggers on right hand side of this webpage: https://docs.servicenow.com/en-US/bundle/tokyo-application-development/page/administer/flow-designer/reference/flow-triggers.html
The trigger types in Flow Designer are Application, Record, Schedule, and Topic. Outbound Email is not a trigger type, but an action type that can be used in a flow to send an email message1.
Reference: Flow Designer Trigger Types
A
Explanation:
See list of triggers on right hand side of this webpage: https://docs.servicenow.com/en-US/bundle/tokyo-application-development/page/administer/flow-designer/reference/flow-triggers.html
The trigger types in Flow Designer are Application, Record, Schedule, and Topic. Outbound Email is not a trigger type, but an action type that can be used in a flow to send an email message1.
Reference: Flow Designer Trigger Types
Question #7
When creating new application files in a scoped application, cross scope access is turned on by default in which of the following?
- A . REST messages
- B . Table
- C . Script Include
- D . Workflow
Correct Answer: B
B
Explanation:
"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
B
Explanation:
"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
Question #8
In an Email Notification, which one of the following is NOT true for the Weight field?
- A . Only Notifications with the highest weight for the same record and recipients are sent
- B . A Weight value of zero means that no email should be sent
- C . The Weight value defaults to zero
- D . A Weight value of zero means the Notification is always sent when the Notification’s When to send criteria is met
Correct Answer: B
B
Explanation:
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.
Reference: Email Notification Weight
B
Explanation:
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.
Reference: Email Notification Weight
Question #9
Which of the following objects does a Display Business Rule NOT have access to?
- A . previous
- B . GlideSystem
- C . g_scratchpad
- D . current
Correct Answer: A
A
Explanation:
A Display Business Rule has access to the current, g_scratchpad, and GlideSystem objects, but not the previous object. The previous object is only available to Before Business Rules4.
Reference: Business
Rule API
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/business-rules/concept/c_BusinessRules.html
A
Explanation:
A Display Business Rule has access to the current, g_scratchpad, and GlideSystem objects, but not the previous object. The previous object is only available to Before Business Rules4.
Reference: Business
Rule API
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/business-rules/concept/c_BusinessRules.html
Question #10
Which of the following features are available to Global applications? (Choose two.)
- A . Automated Test Framework
- B . Source Control
- C . Delegated Development
- D . Flow Designer
Correct Answer: AD
AD
Explanation:
Global applications can use Automated Test Framework and Flow Designer features, but not Source Control and Delegated Development features. Source Control and Delegated Development features are only available to scoped applications.
Reference: [Global vs Scoped Applications], [Delegated Development]
AD
Explanation:
Global applications can use Automated Test Framework and Flow Designer features, but not Source Control and Delegated Development features. Source Control and Delegated Development features are only available to scoped applications.
Reference: [Global vs Scoped Applications], [Delegated Development]
Question #11
Which one of the following is NOT a UI Action type?
- A . List choice
- B . Form button
- C . List banner button
- D . Form choice
Correct Answer: D
D
Explanation:
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.
Reference: UI Actions, Field Types
Reference: https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/list- administration/task/t_EditingAUIAction.html
D
Explanation:
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.
Reference: UI Actions, Field Types
Reference: https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/list- administration/task/t_EditingAUIAction.html
Question #12
Which of the following is NOT supported by Flow Designer?
- A . Call a subflow from a flow
- B . Test a flow with rollback
- C . Use Delegated Developer
- D . Run a flow from a MetricBase Trigger
Correct Answer: B
B
Explanation:
Flow Designer is a graphical tool that allows users to automate processes in ServiceNow without coding. The following are supported by Flow Designer:
Call a subflow from a flow. This is a feature that allows users to invoke a subflow, which is a reusable unit of logic, from a flow. This can help simplify complex flows and avoid duplication of logic.
Use Delegated Developer. This is a feature that allows administrators to delegate the development and maintenance of flows and actions to users who are not administrators. This can help distribute the workload and empower non-admin users to create automations.
Run a flow from a MetricBase Trigger. This is a feature that allows users to trigger a flow based on a MetricBase query, which is a way of analyzing time-series data in ServiceNow. This can help automate actions based on data trends and patterns. The following is not supported by Flow Designer:
Test a flow with rollback. This is not a feature of Flow Designer, but of Automated Test Framework (ATF), which is a tool that allows users to create and run automated tests on ServiceNow applications and features. ATF supports testing flows with rollback, which means reverting any changes made by the flow during the test execution.
Reference: Flow Designer, Automated Test Framework
Reference: https://community.servicenow.com/community? id=community_QUESTION&sys_id=b4d26e44db13ab409540e15b8a9619c9
B
Explanation:
Flow Designer is a graphical tool that allows users to automate processes in ServiceNow without coding. The following are supported by Flow Designer:
Call a subflow from a flow. This is a feature that allows users to invoke a subflow, which is a reusable unit of logic, from a flow. This can help simplify complex flows and avoid duplication of logic.
Use Delegated Developer. This is a feature that allows administrators to delegate the development and maintenance of flows and actions to users who are not administrators. This can help distribute the workload and empower non-admin users to create automations.
Run a flow from a MetricBase Trigger. This is a feature that allows users to trigger a flow based on a MetricBase query, which is a way of analyzing time-series data in ServiceNow. This can help automate actions based on data trends and patterns. The following is not supported by Flow Designer:
Test a flow with rollback. This is not a feature of Flow Designer, but of Automated Test Framework (ATF), which is a tool that allows users to create and run automated tests on ServiceNow applications and features. ATF supports testing flows with rollback, which means reverting any changes made by the flow during the test execution.
Reference: Flow Designer, Automated Test Framework
Reference: https://community.servicenow.com/community? id=community_QUESTION&sys_id=b4d26e44db13ab409540e15b8a9619c9
Question #13
Which of the following are true for reports in ServiceNow? (Choose three.)
- A . Any user can see any report shared with them.
- B . Can be a graphical representation of data.
- C . All users can generate reports on any table.
- D . Can be run on demand by authorized users.
- E . Can be scheduled to be run and distributed by email.
Correct Answer: BDE
BDE
Explanation:
https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedule-report.html Generate and distribute scheduled reports via email.
A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:
Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients. The following are not true for reports in ServiceNow:
Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
All users can generate reports on any table. This is false because users can only generate reports on tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records.
Reference: Reports, Report Security
BDE
Explanation:
https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/reference-pages/task/schedule-report.html Generate and distribute scheduled reports via email.
A report is a graphical representation of data from one or more tables in ServiceNow. The following are true for reports in ServiceNow:
Can be a graphical representation of data. This is true because reports can use various chart types, such as pie, bar, line, or gauge, to visualize data in a meaningful way.
Can be run on demand by authorized users. This is true because reports can be accessed from the Reports menu or the Report Navigator and run by users who have the appropriate roles and permissions to view the data.
Can be scheduled to be run and distributed by email. This is true because reports can be configured to run at a specific time and frequency and send the results to one or more email recipients. The following are not true for reports in ServiceNow:
Any user can see any report shared with them. This is false because users can only see reports that are shared with them if they also have access to the data source of the report. For example, a user who does not have the itil role cannot see a report based on the incident table, even if the report is shared with them.
All users can generate reports on any table. This is false because users can only generate reports on tables that they have access to and that are enabled for reporting. For example, a user who does not have the admin role cannot generate reports on the sys_user table, which is the table for user records.
Reference: Reports, Report Security
Question #14
Modules must have a Link type.
Which one of the following is a list of Link types?
- A . List of Records, Separator, Catalog Type, Roles
- B . Assessment, List of Records, Separator, Timeline Page
- C . List of Records, Content Page, Order, URL (from arguments:)
- D . Assessment, List of Records, Content Page, Roles
Correct Answer: B
B
Explanation:
Reference: https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/administer/navigation_and_ui/reference/r_ModuleLinkTypes.html
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).
Reference: Modules, Create a Module
B
Explanation:
Reference: https://docs.servicenow.com/bundle/geneva-servicenow-platform/page/administer/navigation_and_ui/reference/r_ModuleLinkTypes.html
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).
Reference: Modules, Create a Module
Question #15
Which one of the following is true for a table with the “Allow configuration” Application Access option selected?
- A . Only the in scope application’s scripts can create Business Rules for the table
- B . Any user with the application’s user role can modify the application’s scripts
- C . Out of scope applications can create Business Rules for the table
- D . Out of scope applications can add new tables to the scoped application
Correct Answer: C
C
Explanation:
The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes.
The following is true for a table with the Allow configuration option selected:
Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.
The following are not true for a table with the Allow configuration option selected:
Only the in scope application’s scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.
Any user with the application’s user role can modify the application’s scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application’s user role. To modify the application scripts, users need to have the admin role or the application’s admin role.
Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application’s admin role and be in the application scope.
Reference: Application Access, Business Rules
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=1a721819dbfa23409a64e15b8a9619d2
C
Explanation:
The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes.
The following is true for a table with the Allow configuration option selected:
Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.
The following are not true for a table with the Allow configuration option selected:
Only the in scope application’s scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.
Any user with the application’s user role can modify the application’s scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application’s user role. To modify the application scripts, users need to have the admin role or the application’s admin role.
Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application’s admin role and be in the application scope.
Reference: Application Access, Business Rules
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=1a721819dbfa23409a64e15b8a9619d2
Question #16
When working in the Form Designer, configuring the label of a field in a child table changes the label on which table(s)?
- A . base table
- B . child table
- C . parent table
- D . all tables
Correct Answer: B
B
Explanation:
Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table.
Reference: [ServiceNow Docs – Table extension], [ServiceNow Community – How to change field label in child table]
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=7ddc4462dbe2b3840be6a345ca9619af
B
Explanation:
Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table.
Reference: [ServiceNow Docs – Table extension], [ServiceNow Community – How to change field label in child table]
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=7ddc4462dbe2b3840be6a345ca9619af
Question #17
Which one of the following is true?
- A . A UI Policy’s Actions execute before the UI Policy’s Scripts
- B . The execution order for a UI Policy’s Scripts and Actions is determined at runtime
- C . A UI Policy’s Scripts execute before the UI Policy’s Actions
- D . A UI Policy’s Actions and Scripts execute at the same time
Correct Answer: A
A
Explanation:
Created UI policy on incident form, action set’s cmdb_ci field as mandatory and script as not. result, field was not mandatory.
A UI Policy’s Actions execute before the UI Policy’s Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met.
Reference: [ServiceNow Docs – UI policy actions], [ServiceNow Docs – UI policy scripts]
A
Explanation:
Created UI policy on incident form, action set’s cmdb_ci field as mandatory and script as not. result, field was not mandatory.
A UI Policy’s Actions execute before the UI Policy’s Scripts. Actions are predefined operations that can be applied to fields or sections, such as making them mandatory, read-only, visible, or setting a default value. Scripts are custom JavaScript code that can be used to perform more complex logic or validations. Actions are executed first, and then Scripts are executed if the UI Policy conditions are met.
Reference: [ServiceNow Docs – UI policy actions], [ServiceNow Docs – UI policy scripts]
Question #18
Here is the Business Rule script template:
This type of JavaScript function is known as:
- A . Constructor
- B . Scoped
- C . Anonymous
- D . Self-invoking
Correct Answer: D
D
Explanation:
Self-invoking. Learn JavaScript!
This type of JavaScript function is known as self-invoking or immediately-invoked function expression (IIFE). It is a function that is defined and executed at the same time, without being assigned to a variable or being called by another function. It is often used to create a local scope for variables and avoid polluting the global namespace.
Reference: [W3Schools – JavaScript Function Definitions], [MDN Web Docs – Immediately-invoked function expressions]
D
Explanation:
Self-invoking. Learn JavaScript!
This type of JavaScript function is known as self-invoking or immediately-invoked function expression (IIFE). It is a function that is defined and executed at the same time, without being assigned to a variable or being called by another function. It is often used to create a local scope for variables and avoid polluting the global namespace.
Reference: [W3Schools – JavaScript Function Definitions], [MDN Web Docs – Immediately-invoked function expressions]
Question #19
Which method call returns true only if the currently logged in user has the catalog_admin role and in no other case?
- A . g_user.hasRole(‘catalog_admin’)
- B . g_user.hasRoleExactly(‘catalog_admin’)
- C . g_user.hasRoleOnly(‘catalog_admin’)
- D . g_user.hasRoleFromList(‘catalog_admin’)
Correct Answer: B
B
Explanation:
The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments.
Reference: [ServiceNow Docs – GlideUser API], [ServiceNow Community – Difference between hasRole() and hasRoleExactly()]
Reference: https://community.servicenow.com/community? id=community_QUESTIO N NO:&sys_id=dff705e6db7757c0d58ea345ca96196b
B
Explanation:
The method call that returns true only if the currently logged in user has the catalog_admin role and in no other case is g_user.hasRoleExactly(‘catalog_admin’). This method checks if the user has exactly one role, and returns true if it matches the argument. The other methods return true if the user has one or more roles, or if the user has any role from a list of arguments.
Reference: [ServiceNow Docs – GlideUser API], [ServiceNow Community – Difference between hasRole() and hasRoleExactly()]
Reference: https://community.servicenow.com/community? id=community_QUESTIO N NO:&sys_id=dff705e6db7757c0d58ea345ca96196b
Question #20
There is a basic strategy when creating a Utils Script Include. Identify the step that does not belong.
- A . Identify the table
- B . Script the function(s)
- C . Create a class
- D . Create a prototype object from the new class
Correct Answer: A
A
Explanation:
The step that does not belong when creating a Utils Script Include is identifying the table. A Script Include is a server-side script that can contain one or more classes or functions that can be reused by other scripts. It does not depend on a specific table, but can access any table through GlideRecord or other APIs. The other steps are part of creating a Script Include class and its prototype object.
Reference: [ServiceNow Docs – Script Includes], [ServiceNow Docs – GlideRecord API]
A
Explanation:
The step that does not belong when creating a Utils Script Include is identifying the table. A Script Include is a server-side script that can contain one or more classes or functions that can be reused by other scripts. It does not depend on a specific table, but can access any table through GlideRecord or other APIs. The other steps are part of creating a Script Include class and its prototype object.
Reference: [ServiceNow Docs – Script Includes], [ServiceNow Docs – GlideRecord API]
Question #21
Which roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control? (Choose two.)
- A . source_control
- B . source_control_admin
- C . admin
- D . git_admin
Correct Answer: AC
AC
Explanation:
The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:
source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.
admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.
The following roles do not grant access to source control repository operations:
source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.
git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration.
Reference: Source Control, Source Control Roles
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/ t_LinkAnApplicationToSourceControl.html
AC
Explanation:
The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:
source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.
admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.
The following roles do not grant access to source control repository operations:
source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.
git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration.
Reference: Source Control, Source Control Roles
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/ t_LinkAnApplicationToSourceControl.html
Question #22
When configuring the content of an Email Notification, which syntax should be used to reference the properties of an event triggering the Notification?
- A . ${event. <property name>}
- B . ${current. <property name>}
- C . ${property name>.getDisplayValue()}
- D . ${gs.<property name>}
Correct Answer: A
A
Explanation:
https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221
Reference: https://community.servicenow.com/community?id=community_Question:&sys_id=e017cbe5db1cdbc01dcaf3231f9619a3
When configuring the content of an Email Notification, the following syntax should be used to reference the properties of an event triggering the Notification: event.<propertyname>.Thisisthecorrectsyntaxtoaccessthepropertiesoftheeventrecordthattriggeredth eEmailNotification,suchasevent.name,event.parm1,orevent.parm2.Forexample,{event.parm1} will display the value of the first parameter of the event.
The following syntaxes are not correct for referencing the properties of an event triggering the
Notification:
current.<propertyname>.Thisisthesyntaxtoaccessthepropertiesofthecurrentrecordthatisassociatedwiththeevent,suchascurrent.number,current.shortdescription,orcurrent.state.Forexample,{current.shor t_description} will display the short description of the current record.
${property name>.getDisplayValue()}. This is the syntax to access the display value of a property of the current record, such as current.state.getDisplayValue(), current.assigned_to.getDisplayValue(), or current.category.getDisplayValue(). For example, current.state.getDisplayValue() will display the state of the current record in a human-readable format, such as New, In Progress, or Closed.
${gs.<property name>}. This is the syntax to access the properties of the GlideSystem (gs) object, which provides methods for performing system operations, such as gs.now(), gs.getUserID(), or gs.getProperty(). For example, gs.now() will display the current date and time of the system.
Reference: Email Notifications, Email Notification Variables
A
Explanation:
https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221
Reference: https://community.servicenow.com/community?id=community_Question:&sys_id=e017cbe5db1cdbc01dcaf3231f9619a3
When configuring the content of an Email Notification, the following syntax should be used to reference the properties of an event triggering the Notification: event.<propertyname>.Thisisthecorrectsyntaxtoaccessthepropertiesoftheeventrecordthattriggeredth eEmailNotification,suchasevent.name,event.parm1,orevent.parm2.Forexample,{event.parm1} will display the value of the first parameter of the event.
The following syntaxes are not correct for referencing the properties of an event triggering the
Notification:
current.<propertyname>.Thisisthesyntaxtoaccessthepropertiesofthecurrentrecordthatisassociatedwiththeevent,suchascurrent.number,current.shortdescription,orcurrent.state.Forexample,{current.shor t_description} will display the short description of the current record.
${property name>.getDisplayValue()}. This is the syntax to access the display value of a property of the current record, such as current.state.getDisplayValue(), current.assigned_to.getDisplayValue(), or current.category.getDisplayValue(). For example, current.state.getDisplayValue() will display the state of the current record in a human-readable format, such as New, In Progress, or Closed.
${gs.<property name>}. This is the syntax to access the properties of the GlideSystem (gs) object, which provides methods for performing system operations, such as gs.now(), gs.getUserID(), or gs.getProperty(). For example, gs.now() will display the current date and time of the system.
Reference: Email Notifications, Email Notification Variables
Question #23
Which one of the following is true for a Script Include with a Protection Policy value of Protected?
- A . Any user with the protected_edit role can see and edit the Script Include
- B . The Protection policy option can only be enabled by a user with the admin role
- C . The Protection Policy is applied only if the glide.app.apply_protection system property value is true
- D . The Protection Policy is applied only if the application is downloaded from the ServiceNow App Store
Correct Answer: D
D
Explanation:
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.
Reference: Script Includes, Protect Script Includes, Application Restricted Caller Access
D
Explanation:
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.
Reference: Script Includes, Protect Script Includes, Application Restricted Caller Access
Question #24
Which one of the following is true for GlideUser (g_user) methods?
- A . Can be used in Client Scripts and UI Policies only
- B . Can be used in Business Rules only
- C . Can be used in Client Scripts, UI Policies, and UI Actions
- D . Can be used in Business Rules, and Scripts Includes
Correct Answer: C
C
Explanation:
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.
Reference: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes
Reference: https://developer.servicenow.com/dev.do#!/reference/api/newyork/client/c_GlideUserAPI
C
Explanation:
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.
Reference: Client-Side Scripting APIs, GlideUser, Business Rules, Script Includes
Reference: https://developer.servicenow.com/dev.do#!/reference/api/newyork/client/c_GlideUserAPI
Question #25
When configuring a module, what does the Override application menu roles configuration option do?
- A . Users with the module role but without access to the application menu access the module
- B . Self-Service users can access the module even though they do not have roles
- C . Admin is given access to the module even if Access Controls would ordinarily prevent access
- D . Users with access to the application menu can see the module even if they don’t have the module role
Correct Answer: A
A
Explanation:
Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module."
The following is true for the Override application menu roles configuration option when configuring a module:
Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.
The following are not true for the Override application menu roles configuration option when configuring a module:
Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.
Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. Admin is a role
Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0716421
A
Explanation:
Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module."
The following is true for the Override application menu roles configuration option when configuring a module:
Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.
The following are not true for the Override application menu roles configuration option when configuring a module:
Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.
Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. Admin is a role
Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0716421
Question #26
Which platform feature can be used to determine the relationships between field in an Import Set table to field in an existing ServiceNow table?
- A . Business Service Management Map
- B . Data Sources
- C . Transform Map
- D . Cl Relationship Builder
Correct Answer: C
C
Explanation:
A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.
Reference: https://community.servicenow.com/community? id=community_Question:&sys_id=69fc8369db9cdbc01dcaf3231f961935
The following platform feature can be used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Transform Map. This is a feature that defines the mapping between the fields of an Import Set table and the fields of a target table, such as incident, problem, or user. A transform map also specifies the logic and rules for transforming the imported data, such as coalescing, scripting, or applying data policies.
The following platform features are not used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Business Service Management Map. This is a feature that provides a graphical representation of the configuration items (CIs) and their relationships in the Configuration Management Database (CMDB). A Business Service Management Map can be used to visualize the impact of incidents, changes, or problems on the CIs and the services they support.
Data Sources. This is a feature that defines the connection and authentication information for an external data source, such as a file, a JDBC database, or a web service. A data source is used to import data from the external source into an Import Set table.
CI Relationship Builder. This is a feature that creates relationships between CIs in the CMDB based on predefined or custom rules. A CI Relationship Builder can be used to populate the CMDB with the dependencies and connections between the CIs.
Reference: Transform Maps, Business Service Management Map, Data Sources, CI Relationship Builder
C
Explanation:
A transform map determines the relationships between fields displaying in an Import Set table and fields in an existing ServiceNow table, such as the Incidents or Users table.
Reference: https://community.servicenow.com/community? id=community_Question:&sys_id=69fc8369db9cdbc01dcaf3231f961935
The following platform feature can be used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Transform Map. This is a feature that defines the mapping between the fields of an Import Set table and the fields of a target table, such as incident, problem, or user. A transform map also specifies the logic and rules for transforming the imported data, such as coalescing, scripting, or applying data policies.
The following platform features are not used to determine the relationships between fields in an Import Set table to fields in an existing ServiceNow table:
Business Service Management Map. This is a feature that provides a graphical representation of the configuration items (CIs) and their relationships in the Configuration Management Database (CMDB). A Business Service Management Map can be used to visualize the impact of incidents, changes, or problems on the CIs and the services they support.
Data Sources. This is a feature that defines the connection and authentication information for an external data source, such as a file, a JDBC database, or a web service. A data source is used to import data from the external source into an Import Set table.
CI Relationship Builder. This is a feature that creates relationships between CIs in the CMDB based on predefined or custom rules. A CI Relationship Builder can be used to populate the CMDB with the dependencies and connections between the CIs.
Reference: Transform Maps, Business Service Management Map, Data Sources, CI Relationship Builder
Question #27
When configuring a REST Message, the Endpoint is:
- A . The commands to the REST script to stop execution
- B . The URI of the data to be accessed, queried, or modified
- C . Information about the format of the returned data
- D . The response from the provider indicating there is no data to send back
Correct Answer: B
B
Explanation:
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.
Reference: REST Messages, Scripted REST APIs
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/integrate/outbound-rest/reference/r_RESTMessageElements.html
B
Explanation:
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.
Reference: REST Messages, Scripted REST APIs
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/integrate/outbound-rest/reference/r_RESTMessageElements.html
Question #28
When evaluating Access Controls, ServiceNow searches and evaluates:
- A . Only for matches on the current table
- B . Only for matches on the current field
- C . From the most specific match to the most generic match
- D . From the most generic match to the most specific match
Correct Answer: C
C
Explanation:
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.
Reference: 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_evaluatio n_order
C
Explanation:
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.
Reference: 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_evaluatio n_order
Question #29
In a Business Rule, which one of the following returns true if the currently logged in user has the admin role?
- A . g_form.hasRoleExactly(‘admin’)
- B . gs.hasRole(‘admin’)
- C . g_form.hasRole(‘admin’)
- D . gs.hasRoleExactly(‘admin’)
Correct Answer: B
B
Explanation:
Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn’t exist
In a Business Rule, the following returns true if the currently logged in user has the admin role: gs.hasRole(‘admin’). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole(‘admin’) will return true if the current user has the admin role, and false otherwise.
The following do not return true if the currently logged in user has the admin role in a Business Rule: g_form.hasRoleExactly(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly(‘admin’) will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.
g_form.hasRole(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole(‘admin’) will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.
gs.hasRoleExactly(‘admin’). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object. There is no method that checks if the current user has exactly the specified role and no other roles in the gs object.
Reference: Business Rules, GlideSystem, GlideForm
B
Explanation:
Business Rule is server-side, so it uses GlideSystem API. gs.hasRoleExactly doesn’t exist
In a Business Rule, the following returns true if the currently logged in user has the admin role: gs.hasRole(‘admin’). This is the correct answer because gs is the GlideSystem object, which provides methods for performing system operations, and hasRole is a method that checks if the current user has the specified role. For example, gs.hasRole(‘admin’) will return true if the current user has the admin role, and false otherwise.
The following do not return true if the currently logged in user has the admin role in a Business Rule: g_form.hasRoleExactly(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRoleExactly is a method that checks if the current user has exactly the specified role and no other roles. For example, g_form.hasRoleExactly(‘admin’) will return true if the current user has only the admin role, and false if the current user has the admin role and any other role.
g_form.hasRole(‘admin’). This is not correct because g_form is the GlideForm object, which provides methods for manipulating forms, and hasRole is a method that checks if the current user has the specified role or any role that contains the specified role. For example, g_form.hasRole(‘admin’) will return true if the current user has the admin role or any role that contains the admin role, such as admin_ui or admin_script.
gs.hasRoleExactly(‘admin’). This is not correct because gs is the GlideSystem object, which provides methods for performing system operations, and hasRoleExactly is not a valid method of the gs object. There is no method that checks if the current user has exactly the specified role and no other roles in the gs object.
Reference: Business Rules, GlideSystem, GlideForm
Question #30
From the list below, identify one reason an application might NOT be a good fit with ServiceNow.
The application:
- A . Needs workflow to manage processes
- B . Requires “as-is” use of low-level programming libraries
- C . Requires reporting capabilities
- D . Uses forms extensively to interact with data
Correct Answer: B
B
Explanation:
From the list below, the following is a reason an application might not be a good fit with ServiceNow: Requires “as-is” use of low-level programming libraries. This is the correct answer because ServiceNow is a high-level platform that abstracts away the low-level details of the underlying infrastructure and technology stack. ServiceNow provides a rich set of APIs, tools, and features that allow users to develop applications without coding or with minimal coding. However, ServiceNow does not support the direct
B
Explanation:
From the list below, the following is a reason an application might not be a good fit with ServiceNow: Requires “as-is” use of low-level programming libraries. This is the correct answer because ServiceNow is a high-level platform that abstracts away the low-level details of the underlying infrastructure and technology stack. ServiceNow provides a rich set of APIs, tools, and features that allow users to develop applications without coding or with minimal coding. However, ServiceNow does not support the direct
Question #31
Identify the incorrect statement about Delegated Development in ServiceNow.
- A . Administrators can grant non-admin users the ability to develop global applications.
- B . Administrators can specify which application file types the developer can access.
- C . Administrators can grant the developer access to script fields.
- D . Administrators can grant the developer access to security records.
Correct Answer: A
A
Explanation:
Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/ concept/c_DelegatedDevelopment.html
The incorrect statement about Delegated Development in ServiceNow is that administrators can grant non-admin users the ability to develop global applications. Delegated Development allows administrators to grant non-admin users the ability to develop scoped applications, not global applications. Global applications are accessible by all other applications and do not have a namespace prefix. Scoped applications are isolated from other applications and have a unique namespace identifier. Delegated Development provides more granular control over the developer permissions, application resources, and data access.
Reference: [Advantages of Scoped Applications in ServiceNow], [Product Documentation | ServiceNow]
A
Explanation:
Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/ concept/c_DelegatedDevelopment.html
The incorrect statement about Delegated Development in ServiceNow is that administrators can grant non-admin users the ability to develop global applications. Delegated Development allows administrators to grant non-admin users the ability to develop scoped applications, not global applications. Global applications are accessible by all other applications and do not have a namespace prefix. Scoped applications are isolated from other applications and have a unique namespace identifier. Delegated Development provides more granular control over the developer permissions, application resources, and data access.
Reference: [Advantages of Scoped Applications in ServiceNow], [Product Documentation | ServiceNow]
Question #32
What is the REST API Explorer used to do?
- A . Practice using REST to interact with public data providers
- B . Find resources on the web for learning about REST
- C . Convert SOAP Message functions to REST methods
- D . Create sample code for sending REST requests to ServiceNow
Correct Answer: D
D
Explanation:
One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more.
Reference: [Use the REST API Explorer – Product Documentation: Tokyo – ServiceNow], [Introduction to Scripted REST APIs – ServiceNow Developers]
Reference: https://developer.servicenow.com/dev.do#!/learn/courses/newyork/
app_store_learnv2_rest_newyork_rest_integrations/
app_store_learnv2_rest_newyork_inbound_rest_integrations/
app_store_learnv2_rest_newyork_introduction_to_the_rest_api_explorer
D
Explanation:
One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more.
Reference: [Use the REST API Explorer – Product Documentation: Tokyo – ServiceNow], [Introduction to Scripted REST APIs – ServiceNow Developers]
Reference: https://developer.servicenow.com/dev.do#!/learn/courses/newyork/
app_store_learnv2_rest_newyork_rest_integrations/
app_store_learnv2_rest_newyork_inbound_rest_integrations/
app_store_learnv2_rest_newyork_introduction_to_the_rest_api_explorer
Question #33
Which one of the following is true regarding Application Scope?
- A . All applications are automatically part of the Global scope
- B . Applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts
- C . Any developer can edit any application
- D . Developers can choose the prefix for a scope’s namespace
Correct Answer: B
B
Explanation:
https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html
The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application.
Reference: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow – YouTube]
B
Explanation:
https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ApplicationScope.html
The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application.
Reference: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow – YouTube]
Question #34
Which one of the following is the baseline behavior of a table in a privately-scoped application?
- A . The table and its data are not accessible using web services
- B . Any Business Rule can read, write, delete, and update from the table
- C . Only artifacts in the table’s application can read from the table
- D . All application scopes can read from the table
Correct Answer: D
D
Explanation:
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.
Reference: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]
D
Explanation:
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.
Reference: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]
Question #35
Which one of the following is NOT a purpose of application scoping?
- A . Provide a relationship between application artifacts
- B . Provide a way of tracking the user who developed an application
- C . Provide a namespace (prefix and scope name) to prevent cross application name collisions
- D . Provide controls for how scripts from another scope can alter tables in a scoped application
Correct Answer: B
B
Explanation:
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.
Reference: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]
B
Explanation:
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.
Reference: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]
Question #36
It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan.
What are some of the considerations to document as part of the business process?
- A . Business problem, data input/output, users/stakeholders, and process steps
- B . Business problem, data input/output, project schedule, and process steps
- C . Business problem, data input/output, users/stakeholders, and database capacity
- D . Business problem, users/stakeholders, available licenses, and database capacity
Correct Answer: A
A
Explanation:
It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan. The following are some of the considerations to document as part of the business process:
Business problem. This is the description of the problem or opportunity that the application is intended to address or exploit. It should include the background, context, scope, and objectives of the problem or opportunity.
Data input/output. This is the specification of the data that the application will need to collect, store, manipulate, and display. It should include the data sources, formats, validations, transformations, and integrations of the data.
Users/stakeholders. This is the identification of the users and stakeholders who will be involved in or affected by the application. It should include the roles, responsibilities, expectations, and needs of the users and stakeholders.
Process steps. This is the definition of the steps and activities that the application will perform or support. It should include the inputs, outputs, triggers, conditions, and outcomes of each step or activity.
The following are not some of the considerations to document as part of the business process: Project schedule. This is the estimation of the time and resources required to complete the application development project. It should include the milestones, deliverables, dependencies, and risks of the project. This is not part of the business process, but part of the project management plan. Database capacity. This is the measurement of the amount of data that the application will generate and store in the database. It should include the data volume, growth rate, retention policy, and backup strategy of the data. This is not part of the business process, but part of the technical design and architecture of the application.
Available licenses. This is the number and type of licenses that the application will consume or require from the ServiceNow platform. It should include the license model, cost, and allocation of the licenses. This is not part of the business process, but part of the financial and legal aspects of the application.
Reference: Application Development Process, Business Process Analysis
A
Explanation:
It is best practice to define the business requirements and the process(es) an application will manage as part of the application development plan. The following are some of the considerations to document as part of the business process:
Business problem. This is the description of the problem or opportunity that the application is intended to address or exploit. It should include the background, context, scope, and objectives of the problem or opportunity.
Data input/output. This is the specification of the data that the application will need to collect, store, manipulate, and display. It should include the data sources, formats, validations, transformations, and integrations of the data.
Users/stakeholders. This is the identification of the users and stakeholders who will be involved in or affected by the application. It should include the roles, responsibilities, expectations, and needs of the users and stakeholders.
Process steps. This is the definition of the steps and activities that the application will perform or support. It should include the inputs, outputs, triggers, conditions, and outcomes of each step or activity.
The following are not some of the considerations to document as part of the business process: Project schedule. This is the estimation of the time and resources required to complete the application development project. It should include the milestones, deliverables, dependencies, and risks of the project. This is not part of the business process, but part of the project management plan. Database capacity. This is the measurement of the amount of data that the application will generate and store in the database. It should include the data volume, growth rate, retention policy, and backup strategy of the data. This is not part of the business process, but part of the technical design and architecture of the application.
Available licenses. This is the number and type of licenses that the application will consume or require from the ServiceNow platform. It should include the license model, cost, and allocation of the licenses. This is not part of the business process, but part of the financial and legal aspects of the application.
Reference: Application Development Process, Business Process Analysis
Question #37
Which of the following statements does NOT apply when extending an existing table?
- A . The parent table’s Access Controls are evaluated when determining access to the new table’s records and fields
- B . The new table inherits the functionality built into the parent table
- C . The new table inherits all of the fields from the parent table
- D . You must script and configure all required behaviors
Correct Answer: D
D
Explanation:
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.
Reference: Table Extension, Access Control Rules
D
Explanation:
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.
Reference: Table Extension, Access Control Rules
Question #38
Which of the following CANNOT be debugged using the Field Watcher?
- A . Business Rules
- B . Script Includes
- C . Client Scripts
- D . Access Controls
Correct Answer: B
B
Explanation:
The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.
Reference: Field Watcher
Script Includes
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/debugging/concept/c_FieldWatcher.html
B
Explanation:
The Field Watcher is a debugging tool that allows you to monitor the values of fields on a form as they change due to scripts or other actions. It can be used to debug Business Rules, Client Scripts, and Access Controls, but not Script Includes. Script Includes are server-side scripts that define reusable functions and classes. They are not associated with any specific field or form, and therefore cannot be watched by the Field Watcher.
Reference: Field Watcher
Script Includes
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/debugging/concept/c_FieldWatcher.html
Question #39
Which objects can be used in Inbound Action scripts?
- A . current and previous
- B . current and email
- C . current and event
- D . current and producer
Correct Answer: B
B
Explanation:
Inbound Action scripts are server-side scripts that run when an email is received by the system. They can use the current object to access the record that is created or updated by the email, and the email object to access the properties and methods of the email message. The previous and event objects are not available in Inbound Action scripts. The producer object is only available in Record Producer scripts, which are used to create records from a service catalog item.
Reference: Inbound Action scripts
[Record Producer scripts]
B
Explanation:
Inbound Action scripts are server-side scripts that run when an email is received by the system. They can use the current object to access the record that is created or updated by the email, and the email object to access the properties and methods of the email message. The previous and event objects are not available in Inbound Action scripts. The producer object is only available in Record Producer scripts, which are used to create records from a service catalog item.
Reference: Inbound Action scripts
[Record Producer scripts]
Question #40
Which one of the following is part of the client-side scripting API?
- A . workflow.scratchpad
- B . GlideUser object (g_user)
- C . current and previous objects
- D . GlideSystem object (gs)
Correct Answer: B
B
Explanation:
https://developer.servicenow.com/dev.do#!/reference/api/rome/client
The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user’s preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user’s role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.
Reference: [GlideUser object (g_user)]
[Workflow scripts]
[Business Rules]
Script Includes
[GlideSystem object (gs)]
B
Explanation:
https://developer.servicenow.com/dev.do#!/reference/api/rome/client
The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user’s preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user’s role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.
Reference: [GlideUser object (g_user)]
[Workflow scripts]
[Business Rules]
Script Includes
[GlideSystem object (gs)]
Question #41
Application developers configure ServiceNow using industry standard JavaScript to…
- A . Enable the right-click to edit the context menus on applications in the navigator
- B . Extend and add functionality
- C . Customize the organization’s company logo and banner text
- D . Configure the outgoing email display name
Correct Answer: B
B
Explanation:
Application developers configure ServiceNow using industry standard JavaScript to extend and add functionality. JavaScript is a scripting language that enables developers to create dynamic and interactive web pages, as well as manipulate data and logic on the server-side. ServiceNow provides various APIs and frameworks for developers to use JavaScript to customize and enhance the functionality of their applications, such as client scripts, UI policies, business rules, script includes, UI actions, and more.
Reference: [ServiceNow Docs – JavaScript in ServiceNow], [ServiceNow Docs – Scripting in ServiceNow]
B
Explanation:
Application developers configure ServiceNow using industry standard JavaScript to extend and add functionality. JavaScript is a scripting language that enables developers to create dynamic and interactive web pages, as well as manipulate data and logic on the server-side. ServiceNow provides various APIs and frameworks for developers to use JavaScript to customize and enhance the functionality of their applications, such as client scripts, UI policies, business rules, script includes, UI actions, and more.
Reference: [ServiceNow Docs – JavaScript in ServiceNow], [ServiceNow Docs – Scripting in ServiceNow]
Question #42
How many applications menus can an application have?
- A . 3, one for an application’s user modules, one for an application’s administrator modules, and one
for the ServiceNow administrator’s modules - B . As many as the application design requires
- C . 2, one for an application’s user modules and one for an application’s administrator modules
- D . 1, which is used for all application modules
Correct Answer: B
B
Explanation:
Reference: https://docs.servicenow.com/bundle/orlando-platform-user-interface/page/administer/navigation- and-ui/task/t_CreateAnApplicationMenu.html An application can have as many application menus as the application design requires. An application menu is a container for application modules, which are links to features or functionalities within an application. Application menus are displayed in the application navigator, which is the left sidebar of the ServiceNow interface. Developers can create and configure application menus using Studio or the Application Menus module. Application menus can have different roles and visibility settings, depending on the intended audience and purpose of the application.
Reference: [ServiceNow Docs – Application menus], [ServiceNow Docs – Create an application menu]
B
Explanation:
Reference: https://docs.servicenow.com/bundle/orlando-platform-user-interface/page/administer/navigation- and-ui/task/t_CreateAnApplicationMenu.html An application can have as many application menus as the application design requires. An application menu is a container for application modules, which are links to features or functionalities within an application. Application menus are displayed in the application navigator, which is the left sidebar of the ServiceNow interface. Developers can create and configure application menus using Studio or the Application Menus module. Application menus can have different roles and visibility settings, depending on the intended audience and purpose of the application.
Reference: [ServiceNow Docs – Application menus], [ServiceNow Docs – Create an application menu]
Question #43
The source control operation used to store local changes on an instance for later application is called a(n) <blank>.
- A . Branch
- B . Tag
- C . Stash
- D . Update set
Correct Answer: C
C
Explanation:
The source control operation used to store local changes on an instance for later application is called
a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be pushed to a remote repository. Developers can use stashes to save their work in progress without committing it to the local repository or discarding it. Stashes can be applied later to restore the changes to the working directory, or dropped if they are no longer needed.
Reference: [ServiceNow Docs – Stash local changes], [ServiceNow Docs – Source control]
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_StashLocalChanges.html
C
Explanation:
The source control operation used to store local changes on an instance for later application is called
a stash. A stash is a temporary storage area for uncommitted changes that are not ready to be pushed to a remote repository. Developers can use stashes to save their work in progress without committing it to the local repository or discarding it. Stashes can be applied later to restore the changes to the working directory, or dropped if they are no longer needed.
Reference: [ServiceNow Docs – Stash local changes], [ServiceNow Docs – Source control]
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_StashLocalChanges.html
Question #44
What syntax is used in a Record Producer script to access values from Record Producer form fields?
- A . producer.field_name
- B . producer.variablename
- C . current.variable_name
- D . current.field_name
Correct Answer: B
B
Explanation:
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.
Reference: [ServiceNow Docs – Record producers], [ServiceNow Docs – Record producer script]
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=cc3803addb1cdbc01dcaf3231f9619b6
B
Explanation:
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.
Reference: [ServiceNow Docs – Record producers], [ServiceNow Docs – Record producer script]
Reference: https://community.servicenow.com/community?id=community_QUESTION&sys_id=cc3803addb1cdbc01dcaf3231f9619b6
Question #45
Which of the following methods prints a message on a blue background to the top of the current form by default?
- A . g_form.addInfoMsg()
- B . g_form.addInfoMessage()
- C . g_form.showFieldMessage()
- D . g_form.showFieldMsg()
Correct Answer: B
B
Explanation:
From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html
g_form.showFieldMsg("field_name", "Hello World", "error"); Puts "Hello World" in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook
The method that prints a message on a blue background to the top of the current form by default is g_form.addInfoMessage(). The g_form object is a global object that provides access to form fields and UI elements on a form. The addInfoMessage() method is a method of the g_form object that displays an informational message next to the form header. The message has a blue background color by default, unless it is overridden by a CSS style. The addInfoMessage() method takes one argument, which is the message text to display.
Reference: [ServiceNow Docs – GlideForm (g_form) API], [ServiceNow Docs – g_form.addInfoMessage()]
B
Explanation:
From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html
g_form.showFieldMsg("field_name", "Hello World", "error"); Puts "Hello World" in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook
The method that prints a message on a blue background to the top of the current form by default is g_form.addInfoMessage(). The g_form object is a global object that provides access to form fields and UI elements on a form. The addInfoMessage() method is a method of the g_form object that displays an informational message next to the form header. The message has a blue background color by default, unless it is overridden by a CSS style. The addInfoMessage() method takes one argument, which is the message text to display.
Reference: [ServiceNow Docs – GlideForm (g_form) API], [ServiceNow Docs – g_form.addInfoMessage()]
Question #46
A scoped application containing Flow Designer content dedicated to a particular application is called a(n):
- A . Spoke
- B . Bundle
- C . Action
- D . Flow
Correct Answer: A
A
Explanation:
https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.html
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.
Reference: https://community.servicenow.com/community?id=community_blog&sys_id=7b3af354db93ab80afc902d5ca9619bc
A
Explanation:
https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.html
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.
Reference: https://community.servicenow.com/community?id=community_blog&sys_id=7b3af354db93ab80afc902d5ca9619bc
Question #47
What is a Module?
- A . The functionality within an application menu such as opening a page in the content frame or a separate tab or window
- B . A group of menus, or pages, providing related information and functionality to end-users
- C . A way of helping users quickly access information and services by filtering the items in the Application Navigator
- D . A web-based way of providing software to end-users
Correct Answer: C
C
Explanation:
https://docs.servicenow.com/bundle/rome-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateAModule.html
A module is the functionality within an application menu such as opening a page in the content frame or a separate tab or window. For example, Open is a module under the Problem application menu that opens a list of problem records. Modules are the second level navigation options for applications.
Reference: Modules | ServiceNow Tutorials
C
Explanation:
https://docs.servicenow.com/bundle/rome-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateAModule.html
A module is the functionality within an application menu such as opening a page in the content frame or a separate tab or window. For example, Open is a module under the Problem application menu that opens a list of problem records. Modules are the second level navigation options for applications.
Reference: Modules | ServiceNow Tutorials
Question #48
Which source control operation is available from BOTH Studio and the Git Repository?
- A . Create Branch
- B . Apply Remote Changes
- C . Stash Local Changes
- D . Edit Repository Configurations
Correct Answer: A
A
Explanation:
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]
A
Explanation:
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]
Question #49
Which one of the following is NOT required to link a ServiceNow application to a Git repository?
- A . Password
- B . URL
- C . User name
- D . Application name
Correct Answer: D
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]
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_LinkAnApplicationToSourceControl.html
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]
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/t_LinkAnApplicationToSourceControl.html
Question #50
Which Report Type(s) can be created by right-clicking on a column header in a table’s list?
- A . Bar Chart, Pie Chart, Histogram, and Line
- B . Bar Chart
- C . Bar Chart, Pie Chart, and Histogram
- D . Bar Chart and Pie Chart
Correct Answer: D
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]
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]
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?
- A . gs.log()
- B . gs.error()
- C . gs.warn()
- D . gs.debug()
Correct Answer: A
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:&sys_id=bd71cb29db98dbc01dcaf3231f9619c6
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:&sys_id=bd71cb29db98dbc01dcaf3231f9619c6
Question #52
If the Create module field is selected when creating a table, what is the new module’s default behavior?
- A . Open an empty form so new records can be created
- B . Open a link to a wiki article with instructions on how to customize the behavior of the new module
- C . Display an empty homepage for the application
- D . Display a list of all records from the table
Correct Answer: D
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
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
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?
- A . 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
- B . Set the Accessible from field value to All application scopes and de-select the Can create option
- C . Set the Accessible from field value to This application scope only and de-select the Allow access to this table via web services option
- D . Set the Accessible from field value to This application scope only
Correct Answer: D
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
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
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 . a, b, c, and d
- B . a and b
- C . b and c
- D . a, b, and c
Correct Answer: D
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]
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]
Question #55
When configuring an Access Control which has no condition or script, which one of the following statements is NOT true?
- A . table.*will grant access to every field in a record
- B . table.None will grant access to every record on the table
- C . table.field will grant access to a specific field in a record
- D . table.id will grant access to a specific record on the table
Correct Answer: D
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]
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]
Question #56
Which of the following methods are useful in Access Control scripts?
- A . g_user.hasRole() and current.isNewRecord()
- B . gs.hasRole() and current.isNewRecord()
- C . g_user.hasRole() and current.isNew()
- D . gs.hasRole() and current.isNew()
Correct Answer: B
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]
Reference: http://servicenowmypath.blogspot.com/2017/
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]
Reference: http://servicenowmypath.blogspot.com/2017/
Question #57
Which one of the following client-side scripts apply to Record Producers?
- A . Catalog Client Scripts and Catalog UI Policies
- B . UI Scripts and UI Actions
- C . UI Scripts and Record Producer Scripts
- D . Client Scripts and UI Policies
Correct Answer: A
A
Explanation:
Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers.
Reference: Catalog client scripts, Catalog UI policies
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/client-scripts/concept/c_CatalogClientScriptCreation.html
A
Explanation:
Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers.
Reference: Catalog client scripts, Catalog UI policies
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/client-scripts/concept/c_CatalogClientScriptCreation.html
Question #58
When a ServiceNow instance requests information from a web service, ServiceNow is the web service:
- A . Publisher
- B . Specialist
- C . Provider
- D . Consumer
Correct Answer: D
D
Explanation:
When a ServiceNow instance requests information from a web service, ServiceNow is the web service consumer. A web service consumer is an application that sends requests to a web service provider and receives responses from it. A web service provider is an application that exposes its functionality as web services. A web service publisher is a person or organization that publishes web services for others to use. A web service specialist is a person who has expertise in developing or using web services.
Reference: Web services
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/integrate/web-services/reference/r_AvailableWebServices.html
D
Explanation:
When a ServiceNow instance requests information from a web service, ServiceNow is the web service consumer. A web service consumer is an application that sends requests to a web service provider and receives responses from it. A web service provider is an application that exposes its functionality as web services. A web service publisher is a person or organization that publishes web services for others to use. A web service specialist is a person who has expertise in developing or using web services.
Reference: Web services
Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/integrate/web-services/reference/r_AvailableWebServices.html
Question #59
Which one of the following is the fastest way to create and configure a Record Producer?
- A . Create a Catalog Category, open the category, and select the Add New Record Producer button
- B . Use the Record Producer module then add and configure all variables manually
- C . Open the table in the Table records and select the Add to Service Catalog Related Link
- D . Open the table’s form, right-click on the form header, and select the Create Record Producer menu item
Correct Answer: C
C
Explanation:
The fastest way to create and configure a Record Producer is to open the table in the Table records and select the Add to Service Catalog Related Link. This will automatically create a Record Producer with the same fields as the table and add it to the Service Catalog. You can then modify the Record Producer as needed. The other options require more steps and manual configuration.
Reference: Create a record producer
C
Explanation:
The fastest way to create and configure a Record Producer is to open the table in the Table records and select the Add to Service Catalog Related Link. This will automatically create a Record Producer with the same fields as the table and add it to the Service Catalog. You can then modify the Record Producer as needed. The other options require more steps and manual configuration.
Reference: Create a record producer
Question #60
Which objects can you use in a Scheduled Script Execution (Scheduled Job) script?
- A . GlideRecord and current
- B . GlideUser and GlideRecord
- C . GlideSystem and GlideRecord
- D . GlideSystem and current
Correct Answer: C
C
Explanation:
https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_s cript_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
C
Explanation:
https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_s cript_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
Question #61
Which of the following is true for the Application Picker and Application Scope?
- A . Selecting application from the Application Picker does not set the Application Scope.
- B . Selecting Global in the Application Picker sets the Application Scope to incident
- C . Global is a reserved application which does not appear in the Application Picker
- D . Selecting an application from the Application Picker sets the Application Scope
Correct Answer: D
D
Explanation:
"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
D
Explanation:
"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
Question #62
Which of the following is an available feature in Studio? Choose 2 answers
- A . Push to external source control
- B . Search branch
- C . Merge branches
- D . Push to update set
Correct Answer: A, B
A, B
Explanation:
Search branch and merge branches are available features in Studio. Search branch allows you to search for a specific branch name or ID in your Git repository. Merge branches allows you to merge changes from one branch to another, resolving any conflicts that may arise. Push to external source control and push to update set are not available features in Studio. Push to external source control is a feature of Source Control Integration, which is a separate application from Studio. Push to update set is a feature of Update Set Previewer, which is also a separate application from Studio.
Reference: Studio, Source Control Integration, Update Set Previewer
A, B
Explanation:
Search branch and merge branches are available features in Studio. Search branch allows you to search for a specific branch name or ID in your Git repository. Merge branches allows you to merge changes from one branch to another, resolving any conflicts that may arise. Push to external source control and push to update set are not available features in Studio. Push to external source control is a feature of Source Control Integration, which is a separate application from Studio. Push to update set is a feature of Update Set Previewer, which is also a separate application from Studio.
Reference: Studio, Source Control Integration, Update Set Previewer
Question #63
The task table is an example of which of the following?
Choose 2 answers
- A . Legacy class
- B . Child class
- C . Base class
- D . Parent class
Correct Answer: C, D
C, D
Explanation:
"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
C, D
Explanation:
"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
Question #64
Which of the following is true about deleting fields from a table?
- A . Any field on a table can be deleted
- B . User-defined non-inherited fields can be detected
- C . Inherited fields can be detected
- D . Table records are deleted when a field is detected
Correct Answer: B
B
Explanation:
User-defined non-inherited fields can be deleted from a table in ServiceNow. These are fields that are created by users on a specific table and are not inherited from a parent table. Inherited fields cannot be deleted from a table, as they are defined on a parent table and shared by all child tables. Any field on a table cannot be deleted, as some fields are system-defined and essential for the table functionality. Table records are not deleted when a field is deleted, as the field deletion only affects the table structure and not the data.
Reference: Delete fields
B
Explanation:
User-defined non-inherited fields can be deleted from a table in ServiceNow. These are fields that are created by users on a specific table and are not inherited from a parent table. Inherited fields cannot be deleted from a table, as they are defined on a parent table and shared by all child tables. Any field on a table cannot be deleted, as some fields are system-defined and essential for the table functionality. Table records are not deleted when a field is deleted, as the field deletion only affects the table structure and not the data.
Reference: Delete fields
Question #65
Which of the following statements is true about Guided Application Creator?
- A . The global scope option is turned on by default
- B . A scope application user role is automatically created
- C . Default access controls are automatically created
- D . The welcome screen appears every time a new application is created
Correct Answer: D
D
Explanation:
The welcome screen appears every time a new application is created through the Guided Application Creator. The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app.
Reference: Guided App Creator
D
Explanation:
The welcome screen appears every time a new application is created through the Guided Application Creator. The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app.
Reference: Guided App Creator
Question #66
When creating an application through the Guided Application Creator, which of the following is NOT an option for creating a table?
- A . Upload spreadsheet
- B . Create table from template
- C . Extend a table
- D . Create table from scratch
Correct Answer: B
B
Explanation:
Create table from template is not an option for creating a table through the Guided Application Creator. The other options are available for creating a table in the app. Upload spreadsheet allows you to import data from an Excel file and create a table based on the spreadsheet columns and rows. Extend a table allows you to create a child table that inherits fields and behaviors from a parent table. Create table from scratch allows you to define your own fields and data types for a new table.
Reference: Create tables
https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/gac-tables.html
B
Explanation:
Create table from template is not an option for creating a table through the Guided Application Creator. The other options are available for creating a table in the app. Upload spreadsheet allows you to import data from an Excel file and create a table based on the spreadsheet columns and rows. Extend a table allows you to create a child table that inherits fields and behaviors from a parent table. Create table from scratch allows you to define your own fields and data types for a new table.
Reference: Create tables
https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/gac-tables.html
Question #67
Why would you build a custom app?
- A . To fulfill is specific use case on internal processes.
- B . To avoid using a code repository like GiotHub or GitLab
- C . To create a custom integration for a 3rd party system
- D . To replace servieNow base tables
Correct Answer: A, C
A, C
Explanation:
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 C eBook
A, C
Explanation:
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 C eBook
Question #68
What are the ways to designate data tables when Guided Application Creator (GAC)? Choose 3 answers
- A . Upload an existing PDF
- B . Create a new table on the platform
- C . Use an existing table on the platform
- D . Upload an existing spreadsheet
- E . Upload an existing word processing document.
- F . Use a freeform database
Correct Answer: A, B, D
A, B, D
Explanation:
The Guided Application Creator (GAC) is a tool that helps you create applications on the ServiceNow platform by guiding you through the steps of defining the data model, user interface, and logic.
When using the GAC, you can designate data tables in three ways:
Upload an existing PDF: You can upload a PDF file that contains the table schema and sample data.
The GAC will parse the PDF and create the table and fields based on the file content.
Create a new table on the platform: You can create a new table on the platform by specifying the table name, label, and description. You can also add fields, indexes, and relationships to the table using the GAC.
Upload an existing spreadsheet: You can upload a spreadsheet file that contains the table schema and sample data. The GAC will parse the spreadsheet and create the table and fields based on the file content.
The other options are not valid ways to designate data tables when using the GAC. You cannot upload an existing word processing document or use a freeform database. You can use an existing table on the platform, but you cannot designate it as a data table. You can only use it as a reference table for lookup fields.
Reference: Guided Application Creator
Create a table from a PDF or spreadsheet
Create a table from scratch
A, B, D
Explanation:
The Guided Application Creator (GAC) is a tool that helps you create applications on the ServiceNow platform by guiding you through the steps of defining the data model, user interface, and logic.
When using the GAC, you can designate data tables in three ways:
Upload an existing PDF: You can upload a PDF file that contains the table schema and sample data.
The GAC will parse the PDF and create the table and fields based on the file content.
Create a new table on the platform: You can create a new table on the platform by specifying the table name, label, and description. You can also add fields, indexes, and relationships to the table using the GAC.
Upload an existing spreadsheet: You can upload a spreadsheet file that contains the table schema and sample data. The GAC will parse the spreadsheet and create the table and fields based on the file content.
The other options are not valid ways to designate data tables when using the GAC. You cannot upload an existing word processing document or use a freeform database. You can use an existing table on the platform, but you cannot designate it as a data table. You can only use it as a reference table for lookup fields.
Reference: Guided Application Creator
Create a table from a PDF or spreadsheet
Create a table from scratch
Question #69
When a selecting a data type for a field that will be displayed on a form, which of the following statements is NOT correct?
- A . Use the Choice data type to limit options in a field
- B . Use the Data data type to enter the date and time of day.
- C . Use the Phone Number data type to automate phone number data validation.
- D . Use the string data type for a free-form text field.
Correct Answer: C
C
Explanation:
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.
Reference: [Field types]
[Date/Time field type]
C
Explanation:
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.
Reference: [Field types]
[Date/Time field type]
Question #70
Which one of the following is NOT part of the Form Designer?
- A . Form layout
- B . Page header
- C . Schema map
- D . Field navigator
Correct Answer: C
C
Explanation:
https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer
The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform.
The Form Designer has four main components:
Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.
Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.
Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.
Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.
Reference: [Form Designer]
[Schema map]
C
Explanation:
https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer
The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform.
The Form Designer has four main components:
Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.
Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.
Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.
Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.
Reference: [Form Designer]
[Schema map]
Question #71
Which class is NOT part of the Client side scoped APIs?
- A . GuideDialogWindow
- B . GuideAjex
- C . GuideRecord
- D . GuideForm
Correct Answer: C
C
Explanation:
This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.
GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.
GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.
The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.
Reference: [Client side scoped APIs]
[Server side scoped APIs]
C
Explanation:
This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.
GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.
GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.
The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.
Reference: [Client side scoped APIs]
[Server side scoped APIs]
Question #72
When designing and creating a form, what do you create to organize fields on a form?
- A . Related lists
- B . Tabs
- C . Sections
- D . Buttons
Correct Answer: C
C
Explanation:
When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.
The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.
Reference: [Form sections]
[Related lists]
[Application menus and modules]
[Form buttons]
C
Explanation:
When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.
The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.
Reference: [Form sections]
[Related lists]
[Application menus and modules]
[Form buttons]
Question #73
Which of the following is a good practice for adding instructions to a form?
- A . Annotations
- B . Related links to wiki pages
- C . A context Menu UI Action
- D . A population read-only field
Correct Answer: A
A
Explanation:
"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
A
Explanation:
"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
Question #74
Which of the following GuideRecord methods run a query against a database table?
Choose 3 answers
- A . -query( )
- B . runQuery()
- C . query()
- D . -get()
- E . get(
Correct Answer: A, C, E
A, C, E
Explanation:
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideRecordScoped/concept/c_GlideRecordScopedAPI.html
A, C, E
Explanation:
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/GlideQuery/concept/GlideQueryGlobalAPI.html#GlideQueryAPI
https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideRecordScoped/concept/c_GlideRecordScopedAPI.html
Question #75
Client-side scripts manage what?
- A . Forms and Forms Fields
- B . Playbook access
- C . Database and backend
- D . User access
Correct Answer: C
C
Explanation:
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html
C
Explanation:
https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html