ServiceNow CSA Practice Exam Questions & Answers

UI Policies are the best way to implement dynamic form behavior such as making fields mandatory, hiding/showing fields, and setting values based on conditions.

Breaking Down the Requirements:

Making 'Resolution Code' mandatory when 'State' is changed to 'Resolved'

This requires a UI Policy that:

Condition: State = Resolved

Action: Set 'Resolution Code' field to Mandatory = True

Hiding the 'Major Incident' checkbox unless the logged-in user has the 'Major Incident Manager' role

This requires another UI Policy that:

Condition: User does NOT have the role major_incident_manager

Action: Hide the field

Why the Other Options Are Incorrect:

Option A (Dictionary Design)

The dictionary defines the structure of fields but does not control dynamic form behavior like field visibility or conditions.

Option B (Field Limiter)

There is no such feature called 'Field Limiter' in ServiceNow.

Option D (UI Design)

'UI Design' is not a recognized concept in ServiceNow. UI Policies are used for form behavior changes.

Option E (Form Constraint)

There is no 'Form Constraint' feature in ServiceNow; ACLs and UI Policies control field behavior instead.

ServiceNow features a built-in collaboration mechanism known as User Presence. This feature is designed to prevent collisions (two people overwriting each other's work) and promote real-time awareness when multiple users are on the same form.

1. User Presence Avatar (Option E):

When multiple users open the same record (like an Incident), a User Presence icon immediately appears in the form header (typically at the top right). This icon displays the avatar or initials of the other user(s) currently viewing the record. If you hover over the avatar, you can see their name.

2. Field-Level Indicators (Option C):

User Presence is not just about who is looking; it also shows what they are doing. If another user actively types into a field or changes a drop-down value, a small 'presence indicator' (a colored icon or dot) appears to the left of that specific field on your screen in real-time. This warns you that the field is being modified by someone else before you attempt to edit it yourself.

3. Why the other options are incorrect:

A: The Work Notes list is for logged journal entries, not real-time presence detection.

B & D: While ServiceNow has chat features (like Connect Chat or Sidebar), these do not automatically launch or force notification pop-ups merely because two people open the same record.

In ServiceNow, when defining a filter condition, the element being filtered is called a Field.

Understanding Fields in Filter Conditions:

A field is an individual piece of data within a table (e.g., Caller, State, Priority in the Incident table).

The available fields in a filter depend on:

The table being filtered

User access rights (roles and permissions)

The columns (fields) available on the table

Example of a Filter Condition:

css

CopyEdit

[ State ] [ is ] [ In Progress ]

State This is a Field in the table.

is This is the Operator used for filtering.

In Progress This is the Value being compared.

Why Other Answers Are Incorrect:

A . Attribute -- Attributes are metadata about a field but do not define filter conditions.

B . Label -- The label is the display name of a field but is not used in filtering.

D . Column -- While fields are stored as columns in a database, in filtering, they are referred to as Fields.

E . Data Element -- This is a general term, not specific to filter conditions.

Reference from Certified System Administrator (CSA) Official Documentation:

ServiceNow Filtering and Conditions

ServiceNow CSA Training Module: 'Using Filters and Queries in ServiceNow'

Process Automation Designer (PAD) is a feature in ServiceNow that allows business process owners to create unified and digitized cross-enterprise processes using a task board interface.

Key Features of Process Automation Designer:

Organizes multiple flows into a single process

Uses a visual task board-style interface to manage process stages

Integrates with Flow Designer to create, manage, and execute automation tasks

Allows role-based task assignment and collaboration

Use Case Example:

Imagine a company has a New Employee Onboarding process that involves:

IT setting up hardware

HR completing paperwork

Security providing building access

Instead of managing this manually across multiple flows, Process Automation Designer brings all these steps into one unified process, making it easy to track and automate.

Why Other Options Are Incorrect?

A . Flow Designer Incorrect

Flow Designer is used to create individual automated workflows, but it does not provide a unified digitized task board.

C . Process Workflow Designer Incorrect

No feature called 'Process Workflow Designer' exists in ServiceNow.

D . Workflow Editor Incorrect

Workflow Editor (Legacy tool) is used to create graphical workflows, but it does not support cross-enterprise digitized task boards.

Official ServiceNow Documentation Reference:

Process Automation Designer Overview

Using Process Automation Designer

The Data Visualization configuration panel in ServiceNow offers multiple options for presenting data, including:

• Chart visualizations - Display data in various chart formats (bar, pie, line, etc.) to visualize trends and comparisons
• Table/Grid view - Display data in a traditional tabular format with rows and columns

These two primary presentation options allow administrators to choose how data is most effectively displayed to end users based on their analytical needs.

When testing a catalog item with a manager approval flow, it's important to verify that the request submission, approval process, and workflow execution are working as expected. Following best practices ensures that the process functions correctly before deployment.

Why These Options Are Correct?

A. Make sure the latest flows are activated.

ServiceNow flow designer allows admins to create and manage approval flows for catalog items.

Before testing, it's crucial to verify that the latest version of the flow is activated, ensuring that the system runs the correct approval logic.

C. Impersonate the requester to ensure the form works.

Impersonation allows administrators to test the user experience without logging in as different users manually.

This is essential to verify that non-admin users can correctly submit the request and trigger the approval process.

D. Make sure the requester's user record has a manager specified.

The manager approval flow relies on the requester's Manager field in their user record.

If this field is empty, the approval request will not be sent to the correct manager, causing the workflow to fail.

Why the Other Options Are Incorrect?

B. Use the instance Incognito setting to quickly toggle between requester and approver.

There is no 'Incognito setting' in ServiceNow to toggle users.

The correct method is using the impersonate feature.

E. Create and select your Testing Update Set, before starting the test cases.

While Update Sets track customizations, they are not required for testing a catalog item's approval workflow.

Update Sets are primarily used for migrating changes between instances (e.g., from Dev to Test).

F. Use your Admin account, so you can approve the items quickly.

Admin accounts override approval workflows and do not provide an accurate test.

The correct method is to impersonate the requester and approver roles separately to ensure the workflow works as expected.

Reference to Official Certified System Administrator (CSA) Documentation:

ServiceNow Flow Designer - Approval Workflow Testing Best Practices

ServiceNow Impersonation Feature for User Testing

ServiceNow ITSM - Catalog Item Testing & Validation

The Form Designer in ServiceNow allows administrators to create, edit, and configure forms to control how records are displayed and interacted with in the system. It consists of three key components:

Page Header -- This section contains controls such as 'Save,' 'Undo,' and 'Redo.' It allows users to manage their changes while designing forms. The Page Header also displays the name of the form being edited.

Field Navigator -- This panel provides a categorized list of available fields that can be dragged and dropped onto the form layout. The fields are divided into different sections, such as 'Available Fields' and 'Existing Fields,' helping users to manage the form's data structure effectively.

Form Layout -- This is the central workspace where users design the form by arranging fields. Users can add new fields, move existing ones, and configure their properties. The layout determines how the form appears to end-users.

Reference from Certified System Administrator (CSA) Official Documentation:

ServiceNow Product Documentation -- Form Designer

ServiceNow CSA Training Module: 'Configuring Forms and Fields'

'ServiceNow System Administration Guide -- Form Customization Best Practices'

Would you like me to verify and format more questions in the same manner?