Free ServiceNow CAD Practice Exam with Questions & Answers | Set: 3

In the Application Navigator, visibility is evaluated at both the application menu level and the module level. A module can specify roles in its Roles field, but when that module Roles field is empty, the module does not add additional role requirements by itself. Instead, the user must still be able to see the application menu that contains the module. That means the effective gate becomes the application menu’s access configuration (including any required roles on the application menu). As a result, the module is visible to users who already have access to the application menu, because the module is not restricting access further. This behavior supports clean navigation design: define broad access at the application menu level, and only add module-level roles when you need to hide specific modules within an otherwise visible application menu. Options like “snc_internal” or “users with no roles” are not universally correct because module visibility is not determined by those conditions alone. The key rule is: if module Roles is empty, application menu access controls whether users can see the module.

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

Business Rules

Client Scripts

UI Actions

Script Includes

Tables and Fields

Workflows

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

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

Options A, B, and D are incorrect:

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

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

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

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

In ServiceNow, a workflow context refers to a specific instance of a workflow execution. When a workflow is initiated—whether by inserting or updating a record, triggering an event, or through scripts—the system creates a workflow context. This context is derived from a particular version of the workflow and is responsible for executing the defined activities and following the specified transitions within that workflow.

Key points about workflow context:

Instance of Execution: Each time a workflow runs, a new context is created to manage that specific execution instance. This allows multiple instances of the same workflow to operate independently and simultaneously.

Execution of Activities: The context manages the progression through the workflow's activities, ensuring that each step is executed in the defined order and under the specified conditions.

Tracking and Management: Workflow contexts enable administrators to monitor the state and progress of workflow executions. They provide visibility into which activities have been completed, which are pending, and any transitions that have occurred.

For example, if a workflow is designed to handle approval processes, each time an approval is initiated, a new workflow context is created to manage that particular approval instance. This context will track the approval's progress, manage notifications, and handle any branching logic defined in the workflow.

"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

Application Access on a table defines cross-scope behavior at the table boundary. To ensure that no other application scope can create records on the application’s data tables, the table must be restricted so that only the owning scope can access it. Setting Accessible from to This application scope only enforces that boundary by preventing other scoped applications from accessing the table, including record creation. This is exactly what the requirement describes: blocking other private scopes from creating records on the table. The “All application scopes” option is the opposite of what you want because it opens cross-scope access, and then trying to selectively block “Can create” still leaves broader exposure and is not aligned with the stated goal. Creating ACLs to block other scopes is also not the correct approach for cross-scope isolation because ACLs primarily control user and role access, while cross-scope access is governed by Application Access and cross-scope rules. Disabling “Allow access to this table via web services” is about API/web service exposure, not about other application scopes creating records through normal platform access.

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. References: Source Control, Source Control Roles