Pass the ServiceNow Certified System Administrator CSA Questions and answers with ExamsMirror

In ServiceNow’sService 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 validvariable typesthat can be added to aService Catalog Itemare:

Multiple Choice:

This variable type presents users with multiple predefined options, but only allows them to selectoneanswer.

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 ofIT, HR, Finance, etc.

Checkbox:

A simpleTrue/Falsevariable 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').

Option A (True/False, Multiple Choice, and Ordered)

True/Falseis not a variable type in the Service Catalog. ServiceNow usesCheckboxfor Boolean (Yes/No) values instead.

Orderedisnot 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.

ServiceNow Docs: Service Catalog Variableshttps://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)

Why the other options are incorrect?References from Certified System Administrator (CSA) Documentation:

ADashboardin ServiceNow is an interface that allows users to display multiplePerformance Analytics (PA) widgets, reports, and other visual elementsin a single, consolidated view.

Provides asingle-screenview of critical data, improvingvisibilityinto key metrics.

Can includereports, Performance Analytics indicators, lists, and interactive filters.

Allows users tocustomize layoutsand adjust widgets based on roles and permissions.

Useful forexecutive summaries, ITSM performance tracking, and real-time operational monitoring.

A. Form–

A Form is used todisplay and input data for a single recordin a table (e.g., an incident, change request, or user record).

It does not provide a multi-widget interface.

B. List–

A List displaysmultiple records from a tablein a tabular format but does not support widgets or Performance Analytics.

D. Timeline–

The Timeline visualization is used for showingtime-based data, such as Change Requests over time, but does not provide multiple reporting widgets in a single interface.

ServiceNow Docs: Dashboards Overviewhttps://docs.servicenow.com/en-US/bundle/utah-performance-analytics-and-reporting/page/use/dashboards/concept/dashboard-overview.html

ServiceNow CSA Official Training Guide (Reporting & Dashboards)

Key Features of a ServiceNow Dashboard:Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:

InServiceNow, theService Catalogis a centralized portal where users can request IT services, hardware, software, and other business-related items. Within theService Catalog, the fundamental components are known asService Catalog Items.

Definition of Service Catalog Items:

AService Catalog Itemrepresents a specific service, product, or action that a user can request from theService Catalog.

It is thecore componentthat defines what users can request.

Examples include:

Requesting anew laptop

Submitting anaccess request

Ordering asoftware installation

Why They Are the "Building Blocks" of the Service Catalog:

All Service Catalog requests are based on catalog items—without them, the catalog has no offerings.

Each item has associated workflows, approvals, and fulfillment processesthat define how the request is handled.

They form the foundationof the Service Catalog because every service request must be tied to an item.

Understanding Service Catalog Items

Why Answer "B" is Correct:✔️"They are the building blocks."

Service Catalog Itemsserve as the fundamental componentsof the catalog.

They define what services and products are available for request.

Withoutcatalog items, the Service Catalog would not function as intended.

Why the Other Answers Are Incorrect:A. "They run behind the scenes."

Incorrectbecause Service Catalog Items arevisible to usersin the Service Catalog portal.

While workflows and fulfillment processes may operate in the background, the items themselves arenot hidden.

C. "They are optional."

Incorrectbecause Service Catalog Items aremandatoryfor a functioning Service Catalog.

Thecatalog is useless without catalog items, making them essential, not optional.

D. "They provide options."

Incorrectbecause while Service Catalog Items can havevariables(such as dropdown selections or checkboxes), their primary role isnot just to provide options but to define the services available.

ServiceNow CSA Study Guide – Service Catalog & Request Management

ServiceNow Docs: Service Catalog Overview(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_catalog, sc_cat_item, sc_request, sc_task)

References from the Certified System Administrator (CSA) Documentation:

ServiceNow supports multiple authentication methods to verify user identities before granting access to an instance. The three valid authentication methods from the given options are:

Local Database Authentication

This is the default authentication method used in ServiceNow.

User credentials (username and password) are stored in the ServiceNow database.

Authentication is handled directly by ServiceNow without relying on external identity providers.

This is useful for small implementations or instances where external authentication is not required.

LDAP (Lightweight Directory Access Protocol)

LDAP allows ServiceNow to integrate withcorporate directory services, such as Microsoft Active Directory, to authenticate users.

Users authenticate using theircorporate credentials, reducing the need to maintain separate user accounts in ServiceNow.

ServiceNow connects to an LDAP server and verifies credentials without storing passwords in the ServiceNow database.

SSO (Single Sign-On)

Single Sign-On enables users to log into ServiceNow using an external identity provider (IdP).

ServiceNow supports various SSO protocols, including:

SAML 2.0 (Security Assertion Markup Language)

OAuth 2.0

OpenID Connect

Kerberos

This allows users to authenticate once and gain access to multiple applications, improving security and user experience.

A. XML feed–

XML feeds are used for data exchange,not authentication.

ServiceNow can consume XML feeds for integrations but does not use XML feeds to authenticate users.

E. FTP authentication–

FTP (File Transfer Protocol) is used for transferring files between systems and isnot a valid authentication methodin ServiceNow.

ServiceNow Docs: User Authentication Methodshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/security/concept/user-authentication-methods.html

ServiceNow CSA Official Training Guide (User Authentication & Security)

Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:These references confirm thatLocal Database, LDAP, and SSOare valid authentication methods in ServiceNow.

Workflows inServiceNoware typically moved between instances usingUpdate Sets. Update Sets serve as a mechanism for capturing customizations and migrating them across different environments, such asDevelopment (Dev) → Test → Production (Prod).

Recording Customizations:

When a workflow is modified or created, its changes are recorded in an Update Set if theUpdate Set is active.

Capturing Related Records:

Workflows consist of multiple components (e.g., activities, conditions, transitions).

Update Sets capture theWorkflow Versionand associatedWorkflow Activities.

Exporting and Importing:

The Update Set containing the workflow is exported from the source instance (e.g., Dev).

It is then imported into the target instance (e.g., Test or Prod).

Commit the Update Set:

After import, the Update Set must be reviewed and committed to apply the changes in the target instance.

B. Workflows are moved using Transform Maps

Incorrect: Transform Maps are used forimporting and mapping datafrom external sources into ServiceNow tables, not for migrating configurations like workflows.

C. Workflows are moved using Application Sets

Incorrect: There is no such thing as "Application Sets" in ServiceNow. However,Applications (Scoped Apps)can be moved usingApplication Repositories (App Repo)orUpdate Sets, but this is different from standard Workflow migration.

D. Workflows cannot be moved between instances

Incorrect: Workflowscanbe moved usingUpdate Sets, and in scoped applications, they can also be packaged with the application.

How Update Sets Work for Workflows?Why Other Options Are Incorrect?

ServiceNow Product Documentation - Update Sets

Update Sets Overview

Moving Customizations Using Update Sets

ServiceNow Workflows

Workflow Management

References from ServiceNow CSA Documentation:

In ServiceNow, user records are stored in theUser [sys_user]table. This table contains all user-related data, including usernames, email addresses, roles, department affiliations, and more.

User ID(user_name) – Unique identifier for the user.

First Name & Last Name(first_name,last_name) – User’s full name.

Email(email) – The user’s email address.

Department(department) – The department to which the user belongs.

Roles(roles) – List of assigned roles that determine access permissions.

Active(active) – Indicates whether the user account is active or inactive.

B. User [sys_user_group]– Incorrect. This table storesgroups, not individual users.

C. User [syst_user_profile]– Incorrect. This table does not exist in ServiceNow.

D. User [user_profile]– Incorrect. There is no such table in ServiceNow.

ServiceNow Docs: User Administration – sys_user Table

ServiceNow CSA Study Guide – User and Group Administration

Key Fields in thesys_userTable:Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Favoritesallow users to quickly accessapplication menus and modulesthat they frequently use. By marking an application menu or module as a favorite, it appears under theFavorites tab in the Application Navigator, making navigation faster and more efficient.

(A) Breadcrumb – Incorrect

Breadcrumbs in ServiceNow show thenavigation pathwithin a list view or form.

They help users filter data quickly but donotstore shortcuts for quick access.

(B) Favorite – Correct

TheFavorite featurein ServiceNow allows users to save frequently used menus and modules for quick access.

Users canadd, remove, and reorderfavorites for better personalization.

Located in theApplication Navigator, favorites appear at the top for easy access.

Favorites can include forms, records, reports, or dashboards.

(C) Tag – Incorrect

Tagsare used toorganize and categorize records(e.g., incidents, problems, change requests).

Tags help users group related records but donotcreate direct menu shortcuts.

(D) Bookmark – Incorrect

ServiceNow doesnotuse the term "Bookmark" for quick access to menus and modules.

While users can bookmark URLs in a web browser, this is different from ServiceNow’s built-inFavoritesfeature.

Explanation of Each Option:

Users cancustomize Favoritesby renaming them or selecting an icon for better visibility.

Admins canpre-configure favoritesfor users based on roles to improve productivity.

Favorites improveuser efficiencyby reducing the number of clicks needed to reach frequently used items.

ServiceNow Docs: Using Favorites in the Application Navigator

https://docs.servicenow.com

ServiceNow Community: Personalizing the Application Navigator with Favorites

https://community.servicenow.com

Additional Notes & Best Practices:References from Certified System Administrator (CSA) Documentation:

When importing data intoServiceNow, anImport Setis created, and aTransform Mapis used to map data from the Import Set table to a target table (such asincident,cmdb_ci, oruser).

ATransform Mapdefineshow data from an Import Set is transferred to the target table. One of its key characteristics is that it can beused multiple times on the same import setto reprocess data or correct mapping errors.

Import Set Table:

Temporary storage for incoming data.

Data remains in the Import Set table until transformed.

Transform Map:

Areusable mappingthat determines how fields in the Import Set correspond to fields in the target table.

Can be runmultiple timeson the same Import Set data.

Coalesce Fields:

Usedbefore transformationto determine whether toupdate existing records or create new ones.

Key Characteristics of Importing Data in ServiceNow:

You import a CSV file into anImport Set Table.

You apply aTransform Mapto map data to theUser (sys_user) table.

If an issue occurs, you canrerun the Transform Map on the same Import Setinstead of reimporting the file.

Example Scenario:

A. An existing Transform Map can be used one time on the same import set– Incorrect.

Transform Maps can be reusedmultiple times on the same Import Set data.

B. Coalesce fields are used only after running Transform– Incorrect.

Coalesce fields are used before transformationto determine if a record should be updated or inserted.

C. Any user can manage and set up import sets– Incorrect.

Onlyusers with the appropriate roles(such asimport_adminoradmin) can manage Import Sets.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Import Sets and Transform Maps

ServiceNow CSA Study Guide → Data Import and Management

ServiceNow Knowledge Base → Understanding Coalesce Fields in Import Sets

References from Certified System Administrator (CSA) Documentation:

InServiceNow, tables are structured in a hierarchical format wheresome tables can extend others, inheriting fields and properties. However, there are specific tables thatdo not extend any other table but can be extended—these are known asBase Tables.

Base Tables:

ABase Tableis a table thatdoes not extend another tablebutcan be extended by other tables.

It serves as afoundationfor creating new tables.

Example:

Task Table (task)– TheIncident, Problem, and Change tablesextend from the Task table.

Configuration Item Table (cmdb_ci)– Used as a base for various CI types.

Core Tables:

Core Tablesare thestandard tablesprovided by ServiceNow.

Theycan be base tables or extended tablesdepending on their role.

Example:

Task (task)andUser (sys_user)are core tables, but onlysome core tables are base tables.

Extended Tables:

Extended Tablesare tables thatinherit fields and functionalityfrom aparent table.

Example:

Incident (incident)extends fromTask (task).

Custom Tables:

Custom Tablesare tables thatdevelopers create for specific business needs.

They may or may not extend another table depending on their design.

Understanding Table Types in ServiceNow

Why Answer "A" is Correct:✔️"Base Tables" are tables that may be extended by other tables but do not extend another table.

These tablesdo not inherit fieldsfrom any other table.

They provide thefoundation for extensions, making them the top-level tables in ServiceNow’s data hierarchy.

Example: TheTask tableis a base table because it does not extend another table but serves as the foundation for many other tables (e.g., Incident, Problem, Change).

Why the Other Answers Are Incorrect:B. "Core Tables"

IncorrectbecauseCore Tables are standard ServiceNow tables, but theycan be either base or extended tables.

Not all core tables follow the definition of a base table.

C. "Extended Tables"

Incorrectbecause extended tablesinherit fields from parent tables, meaning theydo extend another table.

Example: TheIncident table extends from the Task table, making it anextended table.

D. "Custom Tables"

IncorrectbecauseCustom Tablescan beeither base or extended tablesdepending on how they are created.

If a developer chooses to extend an existing table, then it isnot a base table.

ServiceNow CSA Study Guide – Data Schema & Tables

ServiceNow Docs: Table Hierarchy & Extensions(ServiceNow Documentation)

ServiceNow Data Model Overview (Base Tables & Extended Tables)

References from the Certified System Administrator (CSA) Documentation:

AReference fieldin ServiceNow allows you tolook up values from another table, effectively creating a relationship between two tables. When a user selects a value in a reference field, they are selecting a record from the referenced table.

Stores asys_id(unique identifier) of a record from another table.

Displays a user-friendly label from the referenced record.

Allowsdot-walking, enabling access to related fields from the referenced table.

Incident Table (source table)→ Contains a " Caller " field that references theUser Table(sys_user).

TheCallerfield allows users to select a user from theUser Table.

B. Verity→ Not a valid field type in ServiceNow.

C. Options→ Options are typically used in choice lists, not for referencing another table.

D. Selections→ No such field type exists in ServiceNow.

E. Dot Walk→ Dot-walking is afeaturethat allows accessing related fields but is not a field type itself.

F. Lookup→ While " Lookup Select Box " exists, it functions differently by filtering choices rather than directly referencing another table.

TheFlow Designermodule in ServiceNow is used to create and manageautomationsthat involve business logic such asapprovals, tasks, notifications, and integrations. It provides ano-code/low-codeenvironment where users can define automated workflows without needing to write scripts.

Automates Processes– Handles approvals, notifications, and task assignments.

No-Code Interface– Users can build workflows using adrag-and-dropinterface.

Replaces Legacy Workflows– Flow Designer is themodernalternative to Workflow Editor.

Integrates with Spokes– Can connect to other systems usingIntegration Hub.

Triggers– Define when a flow starts (e.g., record changes, schedules, API calls).

Actions– Define what happens (e.g., create a task, send an email, update a record).

Conditions– Add logic to control execution paths.

B. Process Automation > Flow Administration→ Used formanaging existing flows, not creating new ones.

C. Process Automation > Workflow Editor→ This is thelegacyworkflow automation tool, replaced by Flow Designer.

D. Process Automation > Process Flow→ No such module exists in ServiceNow.

E. Process Automation > Active Flows→ Displaysalready running flows, but does not allow new flow creation.

When youimpersonatea user in ServiceNow for testing, you temporarily assume their permissions and role-based access. Toreturn to your own user session, thebestway is toEnd Impersonation.

Click on theUser Menu (top right corner).

Select " End Impersonation " .

You will immediately return to your original user session.

A. Turn your computer off and on again→ Unnecessary and does not affect session management.

B. Clear browser cache→ Cache clearing is not required; impersonation is session-based.

D. Log out and back in→ While this works, it isnot the bestmethod becauseEnd Impersonationis a faster and direct solution.

ABusiness Rulein ServiceNow is aserver-side scriptthat executes when records are inserted, updated, deleted, or queried in a specified table. Business Rules allow automation and customization of workflows by defining logic that runs under specific conditions.

Table (B) –Correct

ABusiness Rulemust be associated with aspecific tablewhere it will execute (e.g., Incident, Change, Task).

This determineswhich recordsthe rule applies to.

Script to Run (E) –Correct

A script must be provided when defining advanced logic in a Business Rule.

Business Rules useserver-side JavaScriptto perform various actions, such as setting field values, enforcing validation, or triggering workflows.

Timing (H) –Correct

The execution timing of a Business Rule determineswhenit runs relative to a database transaction.

Business Rules can run:

Before(before record is saved)

After(after record is saved)

Async(after the transaction completes)

Display(when a form loads)

Condition to Evaluate (I) –Correct

Conditions definewhen the Business Rule should executebased on specific criteria.

Example: A Business Rule might runonly when the priority is set to High.

A. UI Action(Incorrect)

UI Actions (buttons, links, context menus) are separate from Business Rules and are used for UI customization.

C. Fields to update(Incorrect)

While Business Rules can update fields,you do not specify " fields to update " as a required setting. Instead, updates are made via scripts within the rule.

D. Who can run(Incorrect)

Business Rulesalways run on the server-sideand do not require user-specific execution settings.

F. Application Scope(Incorrect)

Although Business Rules belong to an application scope, this isautomatically determinedbased on the current application.

G. Update Set(Incorrect)

Business Rules arecaptured in an Update Set, but this is not a configuration setting while creating the rule.

ServiceNow Business Rules Overview:https://docs.servicenow.com/bundle/utah-application-development/page/script/server-scripting/concept/business-rules.html

Creating Business Rules:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/script/server-scripting/task/t_CreateABusinessRule.html

Key Elements to Specify When Creating a Business Rule:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default.

Homepages (A) –Correct

Homepages are stored asuser-specific or global content, and they are not included in update sets by default.

To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable.

Data (B) –Correct

Update Setsdo not include actual data, such as incident records, user records, or CMDB data.

Onlyconfiguration changes(like fields, forms, and workflows) are captured.

Data migration must be handled separately usingData Export or Integration methods.

Published Workflows (C) –Correct

Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set.

To capture it, you mustmanually updatethe workflow before moving it in an Update Set.

Report Definitions (H) –Correct

Reports and their configurations are not automatically included in Update Sets.

You mustmanually include themby marking them as " Captured in Update Set. "

D. Business Rules(Captured in Update Sets)

E. Schedules(Captured in Update Sets)

F. Database changes(Captured in Update Sets)

G. Related Lists(Captured in Update Sets)

I. Scheduled Jobs(Captured in Update Sets)

J. Client Scripts(Captured in Update Sets)

K. Views(Captured in Update Sets)

ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/c_UpdateSets.html

ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/update-set-best-practices.html

Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default):Official References from Certified System Administrator (CSA) Documentation:

AnAccess Control rule (ACL)in ServiceNow defineswho can access dataandwhat actions they can performon that data. Each ACL consists of three primary components:

Object being secured– The specific table, field, or record that the rule applies to.

Operation– The type of action that is being secured (e.g., Read, Write, Create, Delete).

Permissions required– The conditions, roles, or scripts that determine whether access is granted.

ACLs evaluatewhether a user has permissionto access a specific table, field, or action.

Thesecurity rules are processed from most specific to least specific(e.g., field-level > table-level).

Permissions can be granted based onroles, conditions, or custom scriptsusing GlideSystem (gs).

A. Groups, Conditional Expressions, and Workflows(Incorrect)

ACLs do not manageworkflowsor directly control group assignments.

B. Table Schema, CRUD, and User Authentication(Incorrect)

CRUD (Create, Read, Update, Delete) permissions are controlled by ACLs, butUser Authenticationis managed separately through login policies (LDAP, SSO, etc.).

D. security_admin(Incorrect)

security_adminis aspecial elevated rolerequired to modify security settings, but it is not what an ACL specifies.

Access Control Rules Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-security/page/administer/security/concept/access-control-rules.html

Configuring ACLs in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-security/page/administer/security/task/t_CreateOrModifyAnAccessControl.html

How ACLs Work in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation: