ServiceNow CAD Certified Application Developer - ServiceNow Exam Practice Test

Web services are software systems that use standardized protocols and formats, such as XML and HTTP, to exchange data and messages between different applications or systems over the Internet or other networks12. Web services enable interoperability and integration among diverse software components, regardless of their programming languages, platforms, or architectures34.

References = 1: What are Web Services? - GeeksforGeeks 2: Web service - Wikipedia 3: What are Web Services? - Online Tutorials Library 4: What is a Web Service? | Webopedia

The data type of a field determines the format, validation, and display of the field value on a form. When selecting a data type for a field, you should consider the purpose and function of the field. The statements A, C, and D are correct for selecting a data type for a field. For example:

• Use the Choice data type to limit options in a field: The Choice data type allows you to create a field that has a predefined set of options for the user to select from. The options can be displayed as a drop-down list, radio buttons, or checkboxes. For example, you can use the Choice data type for a field that indicates the priority of a task.
• Use the Phone Number data type to automate phone number data validation: The Phone Number data type allows you to create a field that accepts and validates phone numbers. The field will automatically format the phone number according to the user’s locale and country code. For example, you can use the Phone Number data type for a field that stores the contact number of a user.
• Use the string data type for a free-form text field: The string data type allows you to create a field that accepts any text input from the user. The field can have a maximum length of 255 characters. For example, you can use the string data type for a field that captures the short description of an incident.

The statement B is not correct for selecting a data type for a field. There is no Data data type in ServiceNow. To enter the date and time of day, you should use the Date/Time data type. The Date/Time data type allows you to create a field that accepts and displays a date and time value. The field will use a calendar widget and a time picker to help the user enter the value. For example, you can use the Date/Time data type for a field that records the due date of a task.

References:

• [Field types]
• [Date/Time field type]

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

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]

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

"The sequence is ROLES first, then condition, then script." - Chuck Tomasi says so at this link: https://www.servicenow.com/community/grc-forum/order-of-execution-of-an-acl/m-p/1311962/highlight/true#M6538

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. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table]

There is no "copy" button on the application record (at least I couldn't see one). Also, see here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/reference/r_ManagingApplications.html

To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.

The following options are not the best ways to see what application artifacts will be in a published application:

• Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.
• Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.
• Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. References: Publish an Application, Application Files

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

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/dev_portal/API_reference/glideSystemScoped/concept/c_GlideSystemScopedAPI.html

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

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

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

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.

The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.

References:

• [Workflow overview]
• [Workflow context]

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

• Integer: A whole number that can be used in mathematical operations.
• Array: A collection of items that can be accessed by their index or iterated over using a For each action.
• String: Any kind of text, such as email addresses or the text contents of a file.

References:

• Define and Use Data Types in a Flow (Flow Designer)
• Variable data types - Power Automate | Microsoft Learn
• Product Documentation | ServiceNow

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. References: Reports, Report Security

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

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

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

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.

References:

• [Form sections]
• [Related lists]
• [Application menus and modules]
• [Form buttons]

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. References: [Use the REST API Explorer - Product Documentation: Tokyo - ServiceNow], [Introduction to Scripted REST APIs - ServiceNow Developers]

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

• Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option.
• Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option.
• Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option.
• Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option.

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

References:

• Application Access
• [GlideRecord methods]

A transform map determines the relationships between fields in an import set table and fields in an existing ServiceNow table. It also specifies how to transform the imported data before mapping it to the target table.

References:

• 1. What Exactly is an Import Set? - ServiceNow Developers
• Import set table - ServiceNow Application Development [Book]

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

The statement that is true for this script fragment is that the method returns true if the currently logged in user has the x_my_app_user role or the admin role. The g_user.hasRole() method is a client-side method that checks whether the current user has a specified role or set of roles. If no role is specified, it returns true if the user has any role. If one or more roles are specified, it returns true if the user has any one of the specified roles. However, this method always returns true if the user has the admin role, regardless of the role parameter. Therefore, in this case, the method returns true if the user has either the x_my_app_user role or the admin role. Reference: User Object Cheat Sheet, Checking user permissions

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

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

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

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

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

 Extending an existing table such as the Task table when creating a new application has several benefits, such as:

• You can repurpose existing fields by simply changing the label. For example, you can change the Short description field to Summary or Title for your new table.
• You can use existing fields with no modifications. For example, you can use the Assigned to, Priority, and State fields for your new table without changing anything.
• Existing logic from the parent table will be automatically applied to the new table. For example, you can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table.

The only option that is not true is d) All of the parent table records are copied to the new table. Extending a table does not copy any records from the parent table to the new table. It only creates a new table that inherits the fields and logic from the parent table.

References:

• [Extend a table]
• [Task table]

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

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

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. References: [ServiceNow Docs - GlideUser API], [ServiceNow Community - Difference between hasRole() and hasRoleExactly()]

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

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. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

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. References: Flow Designer Trigger Types

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. References: Application Access, Business Rules

It is possible to change an application’s scope in ServiceNow, either from global to private or from private to global. However, changing the scope of an application may affect its functionality and compatibility with other applications. Therefore, it is recommended to test the application thoroughly before and after changing its scope.

References:

• How To Change Application Scope In ServiceNow - YouTube
• How to move Custom Scoped Applications bettween instances - ServiceNow
• Steps to switch a scoped application from your company’s application repository to update sets - ServiceNow
• How to change the application (scope) of a SLA Definition without needing to recreate the SLA Definition - ServiceNow
• Advantages of Scoped Applications in ServiceNow - QualityClouds

The syntax used in a Record Producer script to access values from Record Producer form fields is producer.variable_name. A Record Producer is a type of catalog item that allows users to create records on any table from the service catalog. A Record Producer script is a server-side script that runs when a Record Producer is submitted, and can be used to set values or perform actions on the generated record. The producer object is a global object that represents the Record Producer form and its variables. The variable_name is the name of the variable defined in the Record Producer. References: [ServiceNow Docs - Record producers], [ServiceNow Docs - Record producer script]

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

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