[Q297-Q315] Use Real CSA – 100% Cover Real Exam Questions [May-2026]

In ServiceNow’s Service Catalog, variables are used to capture user input when they request catalog items. These variables allow for dynamic and customized data collection for different service requests.
Among the options provided, the three valid variable types that can be added to a Service Catalog Item are:
Multiple Choice:
This variable type presents users with multiple predefined options, but only allows them to select one answer.
Example: “What type of laptop do you need?” with options: MacBook, Windows Laptop, Chromebook.
Select Box:
Similar to Multiple Choice but presented in a drop-down format, making it useful when space needs to be conserved in a form.
Example: “Select your department” with a drop-down list of IT, HR, Finance, etc.
Checkbox:
A simple True/False variable that allows users to check a box to indicate a selection.
Example: “Do you need an external monitor?” (Checkbox can be checked for ‘Yes’ or left unchecked for ‘No’).
Why the other options are incorrect?
Option A (True/False, Multiple Choice, and Ordered)
True/False is not a variable type in the Service Catalog. ServiceNow uses Checkbox for Boolean (Yes/No) values instead.
Ordered is not a valid Service Catalog variable type.
Option B (True/False, Checkbox, and Number List)
True/False is incorrect (ServiceNow uses “Checkbox” instead).
Number List is not a valid Service Catalog variable type.
Option C (Number List, Single Line Text, and Reference)
Number List is not a valid variable type.
Single Line Text and Reference are valid variables but were not all correct in this case.
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs: Service Catalog Variables
https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogVariables.html ServiceNow CSA Official Training Guide (Service Catalog & Request Management)

In ServiceNow, access to applications is controlled byroles. Most applications, such asIncident, Change, and Facilities, require specific roles to access them. However, theSelf-Serviceapplication is available to all users, including those with the base”ess” (Employee Self-Service)role, which is assigned to every user by default.
Why “D. Self-Service” is the correct answer?TheSelf-Serviceapplication is designed for general users (end users, employees, customers) who do not have elevated permissions. It provides access to:
TheService Catalog(to request IT services, software, and hardware).
TheKnowledge Base(to search for articles and solutions).
Viewing and tracking submitted requests and incidents.
Submitting new incidents or requests.
Since it is meant forall users, it does not require any additional roles beyond the default ones given to employees or customers.
A: Change- Incorrect. TheChange Managementapplication is typically restricted toITIL users(users with theitilrole) and change managers. End users do not have access to this module.
B: Incident- Incorrect. While end users can create and view their own incidents viaSelf-Service, theIncident Managementmodule itself is restricted to IT support staff (users with theitilrole or higher).
C: Facilities- Incorrect. TheFacilitiesapplication, which includes asset tracking and work orders, is typically restricted to users managing physical assets or facility-related tasks. It is not available to all users by default.
ServiceNow Product Documentation – Self-Service Application Overview
ServiceNow CSA Study Guide – User Roles and Permissions
ServiceNow Docs: Access Control and Application Scope
Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

The activity formatter provides an easy way to track items not saved with a field in the record, such as journal fields like comments and work notes1.
ReferencesFormatters and Related Lists

In ServiceNow, users can quickly generate a report from a list view without needing to navigate to the Reports module. The two main ways to do this are:
Steps:
Open any list view (e.g., Incident, Change, or any table-based list).
Click thethree-line (hamburger) context menuon the top-left of the list.
SelectCreate Reportto generate a basic report based on the current list view.
Modify report settings (e.g., visualization type, filters, groupings).
Save the report for future reference.
Steps:
Apply the necessary filters to refine the list view.
Right-click on acolumn header(e.g., Priority, State, Category).
SelectCreate Reportfrom the context menu.
Configure the report visualization and save it if needed.
1. Using the Context Menu (Option C)2. Right-click on a Column Header (Option E) Incorrect Answer Choices Explanation:A. Click on filter breadcrumb, drag and drop on the Report > Create New module There is no such drag-and-drop functionality for report creation in ServiceNow.
B: Click Funnel, define filter conditions, click Create Report
TheFunnel iconis used to filter list views but does not directly generate reports.
D: Apply filter, right-click on column header, select Bar Chart
There is no direct “Bar Chart” option available when right-clicking on a column header.
Creating Reports from List Views
ServiceNow KB Article: KB0014148
Official CSA Documentation Reference: https://ut.service-now.com/sp?id=kb_article&number=KB0014148

Reference: https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/roles/concept
/c_Roles.html

In ServiceNow, the Task [task] table is a core table that provides a set of standard fields used by multiple tables that extend it, including:
Incident [incident]
Problem [problem]
Change Request [change_request]
Service Request [sc_request]
These tables inherit fields from the Task table, ensuring consistency in assignments, state management, and workflows.
Key Features of the Task Table:
Standard Fields:
Assigned To
Assignment Group
Priority
State
Created By / Updated By
Short Description / Description
Extensibility:
The Incident, Problem, and Change tables all extend the Task table, inheriting its fields.
Developers can add additional fields while keeping core task properties intact.
Why is “A. Task [task]” the Correct Answer?
The Task table is the primary table for work-related records in ServiceNow.
It standardizes fields across multiple ITSM modules.
Why the Other Options Are Incorrect?
B . Assignment [assignment] → ❌ Incorrect
There is no standard “Assignment” table in ServiceNow.
Assignments are managed through the Task table via the Assigned To and Assignment Group fields.
C . Service [service] → ❌ Incorrect
There is no generic “Service” table that acts as a core table for ITSM processes.
Service-related items are stored in different tables, such as cmdb_ci_service (for service records).
D . Workflow [workflow] → ❌ Incorrect
The Workflow table is used for managing automated workflows and does not store task-related records.
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Docs: Task Table Overview
https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/incident-management/concept/task-table.html This confirms that the Task table is the core table that extends to Incident, Problem, and other related tables.

The CI Dependency View in ServiceNow visualizes relationships between Configuration Items (CIs), allowing IT teams to trace dependencies between infrastructure components, such as servers, applications, and services.
Key Concept: CI Relationships
Relationships define dependencies between Configuration Items (CIs) in the Configuration Management Database (CMDB).
The CI Dependency View uses relationships to map infrastructure components and their service dependencies.
Example Scenario:
A Server (CI) hosts a Database (CI) → The database supports an Application (CI) → The application provides a Service (CI).
By viewing CI Relationships, you can trace failures upstream or downstream to understand the impact.
Why Other Options Are Incorrect?
A . Service Tracer → ❌ Incorrect
No such feature called “Service Tracer” exists in ServiceNow.
B . Automapping Utility → ❌ Incorrect
Auto-Discovery tools help populate the CMDB, but they do not enable tracing in the CI Dependency View.
D . Transform Map → ❌ Incorrect
Transform Maps are used in Import Sets to map data between tables, not for dependency mapping.
Official ServiceNow Documentation Reference:
CI Dependency Views
Understanding CMDB Relationships

In ServiceNow, the “Service Desk > My Groups Work” module is designed to display tasks assigned to a group but not yet assigned to an individual user. This means that even if an IT manager oversees the Network and Hardware assignment groups, they will not see any tasks in this list if all tasks have already been assigned to specific individuals within the group.
Let’s break down why option A is the correct answer and why the other options are incorrect:
✅ Explanation for Correct Answer (A):
The “My Groups Work” list only shows tasks that are assigned to the group but have not been assigned to a specific individual within the group.
If all tasks are assigned to specific team members, then the manager will not see any tasks in this list.
The IT manager can verify this by navigating to the Task List (e.g., Incidents, Changes, or Requests) and filtering by the Network and Hardware assignment groups.
❌ Explanation for Incorrect Answers:
(B) The manager does not have the itil role.
The itil role allows users to view, create, update, and resolve incidents, changes, problems, and other ITSM tasks.
However, not having this role would restrict access to various ITSM functionalities, but it does not impact whether tasks appear in My Groups Work.
If the manager lacks the itil role, they might have trouble accessing or modifying tasks, but this wouldn’t explain why they don’t see anything in the list.
(C) The manager is not a member of the Service Desk group.
The Service Desk group is a separate entity in ServiceNow, typically associated with incident handling and user support.
The My Groups Work module is not restricted to the Service Desk group-it displays work assigned to any group the user belongs to.
Since the manager is responsible for the Network and Hardware groups, being part of the Service Desk group is irrelevant.
(D) The manager is not a member of the Network and Hardware groups.
If the manager was not a member of these groups, they wouldn’t see any group-related tasks at all.
However, the question states that the manager is responsible for these groups, so it’s reasonable to assume they are either a member or at least a group manager with visibility.
Even if they were just a manager and not an official group member, they would still be able to see the tasks assigned to the groups.
(E) The Assignment Group manager field is empty.
The Assignment Group manager field is an informational field that indicates who manages a group.
This field does not control what is displayed in the My Groups Work module.
Even if this field were empty, it wouldn’t prevent a manager (who is a group member) from seeing unassigned tasks.
Reference to Official Certified System Administrator (CSA) Documentation:
ServiceNow CSA Guide – User Interface and Navigation
ServiceNow ITSM Fundamentals – Incident and Task Management
ServiceNow Role-Based Access Controls and Group Management
ServiceNow KB Articles – My Groups Work Module

These tables are available by default in a ServiceNow instance because they are part of the core platform and are used to store essential data for users, incidents, and tasks. The other tables are not available by default, but can be created or activated by installing plugins or applications.
References1: Tables & Dictionary – Frequently asked Questions (FAQ) – ServiceNow2: ServiceNow – The List of All Tables (sys_db_object)3: How To Set A Default Field Value in ServiceNow? – The Snowball

InServiceNow Knowledge Management, knowledge articles must be in a specificstatebefore they can be visible to end users. The correct state that allows users to view the article isPublished.
Understanding Knowledge Article StatesKnowledge articles in ServiceNow go through alifecyclethat includes the following states:
Draft- The article is being created or edited and isnot visibleto end users.
Review- The article is under internal review by approvers before publication. It remainshiddenfrom users.
Published- The article isapproved and publicly availableto users who have access to the Knowledge Base.
Retired- The article is no longer relevant or has been replaced. It isnot visibleto end users.
OnlyPublishedarticles appear in the Knowledge Base and can be accessed by users.
Articles inDraft, Review, or Retiredstates arenot visibleto the general audience.
B: Drafted- Articles inDraftare still being written or edited andcannot be accessed by users.
C: Retired- Retired articles are considered obsolete and areno longer displayedin the Knowledge Base.
D: Reviewed- Articles inRevieware under approval butare not yet visibleto users.
ServiceNow Docs: Knowledge Article Stateshttps://docs.servicenow.com/en-US/bundle/utah-servicenow- platform/page/product/knowledge-management/concept/knowledge-article-states.html ServiceNow CSA Official Training Guide (Knowledge Management Lifecycle & Publishing Workflow) Why is “Published” the Correct Answer?Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that aknowledge article must be in the
“Published” stateto be visible to users in the Knowledge Base.

In ServiceNow, the Service Catalog is a structured collection of IT and business services that users can request. It is designed to provide a self-service experience for end-users, streamlining service requests and automating fulfillment processes. The main components of a Service Catalog include:
Record Producers – These are simplified forms that allow users to create records in various tables without requiring direct access to those tables. They enable users to submit requests or incidents through the catalog in a user-friendly manner.
Order Guides – These facilitate the ordering of multiple related catalog items in a single request. For example, when a new employee is onboarded, an order guide can group multiple items such as a laptop, software access, and a phone.
Catalog Items – These are the individual items or services that users can request through the Service Catalog. Examples include hardware (like laptops and monitors), software access, and other business services.
Why the Other Options Are Incorrect:
Option A (Order Guides, Exchange Rates, Calendars) –
Exchange Rates and Calendars are not part of the Service Catalog framework in ServiceNow.
While Exchange Rates may be relevant in financial applications, they do not define the core components of the Service Catalog.
Calendars are used for scheduling, but they do not form part of the Service Catalog structure.
Option B (Order Guides, Catalog Items, and Interceptors) –
Interceptors are used to guide users through form-based submissions, but they are not a fundamental component of the Service Catalog.
Order Guides and Catalog Items are correct, but the presence of Interceptors makes this option incorrect.
Option C (Catalog Items, Asset Contracts, Task Surveys) –
Asset Contracts relate to IT Asset Management (ITAM) and are not core Service Catalog components.
Task Surveys are used for feedback collection but are not part of the core structure of a Service Catalog.
Reference:
ServiceNow CSA Documentation: Service Catalog Overview
ServiceNow CSA Learning Path: Service Catalog Fundamentals
ServiceNow Product Documentation: Order Guides & Record Producers