Free and Premium ServiceNow CSA Dumps Questions Answers

Column Context Menusin ServiceNow provide options for interacting with list columns in a table. These menus allow users to customize list views, generate quick reports, export data, and configure list settings.

When users right-click on acolumn headerin a list view, they see a context menu with several actions. The correct answer,Option A, correctly describes these capabilities.

Create Quick Reports

Users can generatebar charts, pie charts, or other visual reportsbased on column data.

Example: Right-clicking on the " State " column in anIncidentslist allows users to create a report showing the count of incidents per state.

Configure the List

Users can modify the list layout, display additional columns, or customize fields.

Options includePersonalize List, Show / Hide Columns, and Sortfeatures.

Export Data

Data can be exported in various formats, such asExcel, CSV, PDF, or XML.

Example: Exporting all incidents assigned to a particular group.

Key Features of Column Context Menus:

Why the Other Options Are Incorrect:B. It displays actions related to filtering options, assigning tags, and search (Incorrect)

Filtering options are part of theFilter Navigator and List Context Menu, not theColumn Context Menu.

Assigning tags and performing searches happen within the list view but are not primary functions of theColumn Context Menu.

C. It displays actions related to viewing and filtering the entire list (Incorrect)

While column menus allow sorting and filtering, filtering theentirelist is mainly done via theList Context Menu(right-clicking the entire list or using the filter option at the top).

D. It displays actions such as view form, view related task, and add relationship (Incorrect)

Viewing forms, related tasks, and adding relationships are functions available when interacting withrecord-levelactions (right-clicking a row), not a column.

These actions are available via theList Context MenuorRelated Lists, not theColumn Context Menu.

Navigate toIncident > All.

Right-click on thePrioritycolumn header.

A menu appears with options such as:

Sort (Ascending/Descending)

Group By This Field

Create Report

Export Data

Configure List Layout

Example of Using a Column Context Menu in ServiceNow:

AData Policyin ServiceNow is used to enforcemandatory and read-only field conditionsfor data that isentered manually through forms or imported into the system.

Data Policies apply to data coming from external sources, such asimports, web services (API), and integrations.

If a field is set asmandatoryin a Data Policy, recordscannot be imported unless that field contains a value.

This ensuresdata integrityby preventing incomplete or invalid data from entering the system.

If an administrator configures a Data Policy to make the " Caller " fieldmandatoryon theIncidenttable, any imported incidentswithout a Caller value will be rejected.

How Data Policies Enforce Mandatory Data on Import:Example Scenario:

Why " True " is the Correct Answer:Data Policies enforce mandatory fields for both UI entry and imports.

Why " False " is Incorrect:If Data Policies didnotenforce mandatory fields on imports, incomplete records could enter the system, leading to data integrity issues.

ServiceNow Documentation:Data Policies

CSA Exam Guide:CoversData Policy enforcement for UI forms and imports.

Reference from CSA Documentation:Thus, the correct answer is:

A. True

InServiceNow Knowledge Management,flagging an articleis a feature that allows users toreport errors or issueswithin a knowledge article. This helps maintain article accuracy and ensures that outdated or incorrect information is addressed by knowledge managers.

Error Reporting

Users can flag an article if they findincorrect, outdated, or misleading information.

Knowledge managers receive anotificationabout flagged articles and can review them for updates.

Article Quality Control

Helps improve knowledge base content by allowing users topoint out inaccuracies.

Ensures that knowledge articles remainrelevant and useful.

Notifying Knowledge Managers

Flagged articles appear in theKnowledge Base Administration module, allowing managers totrack and resolve flagged issues.

A. To mark an article to read later

Incorrect: There isnobuilt-in " read later " feature in ServiceNow Knowledge Management.

Instead, users canbookmarkan article for quick access.

B. Allow a user to submit feedback about an article

Incorrect:

Feedback is submitted through theFeedback feature, which allows users to rate articles and provide comments.

Flaggingis specifically forerror reporting, not general feedback.

Key Purposes of Flagging an Article:Why Other Options Are Incorrect?

Flagging Knowledge Articles

Flagging an Article for Review

Managing Flagged Articles

Knowledge Management Administration

References from ServiceNow CSA Documentation:

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

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.

InServiceNow, aRecordrepresents all thedata saved within a particular form. Each record corresponds to a single entry in atableand contains multiplefieldsstoring different pieces of information.

ARecordis asingle instanceof data stored in a ServiceNowtable.

When a user fills out and submits aform, arecord is createdor updated in the respective table.

Each record has a uniqueSys ID(a 32-character identifier).

Example:

AnIncidentrecord contains fields such asNumber,Caller,Short Description, andPriority.

AChange Requestrecord contains fields likeChange Number,Requested By, andAssignment Group.

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

AFormis auser interfaceto enter and display data, but it does not store data itself.

It is just a way tointeract with records.

D. Lists

AListdisplaysmultiple recordsfrom a table, but each row in a list represents asingle record.

Lists are used for filtering, sorting, and searching records but do not represent a single data entry.

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

AService Catalog workflowin ServiceNow is a structured sequence of automated activities designed to manage and fulfill catalog requests. These workflows are essential in handlingapprovals, tasks, notifications, and process automationfor requests submitted through theService Catalog.

Drives Complex Fulfillment Processes:

When a user submits a catalog request, the workflow determines how it should be processed.

It automates the required steps, such asapprovals, task assignments, and record updates.

Different items in the catalog may require different workflows based on the request type.

Sends Notifications to Defined Users or Groups:

Service Catalog workflows includeemail and in-platform notificationsto keep users informed.

Notifications can be triggered at different stages, such as request submission, approval, fulfillment, and closure.

Example:If an item requires managerial approval, the workflow sends an approval request notification to the designated approver.

Approval and Task Automation:

Workflows can createapproval stepsfor request items before they proceed to fulfillment.

They can also generatetasksfor fulfillment teams based on predefined conditions.

Integration with Flow Designer and Other Automation Tools:

In newer ServiceNow versions,Flow Designeris often used instead of traditional workflows, but the core purpose remains the same.

Workflows can integrate withSLA (Service Level Agreements), script actions, and record updates.

Key Functions of a Service Catalog Workflow:Why Option C is Correct? " Drives complex fulfillment processes " → Correct, as workflows automate and manage Service Catalog request fulfillment.

" Sends notifications to defined users or groups " → Correct, since notifications are an integral part of ServiceNow workflows.

Why Other Options Are Incorrect?Option A:Incorrect – While workflows include tasks and approvals, they do not " generate item variable types. " Variables are defined within catalog items, not workflows.

Option B:Incorrect – Workflowscan send notifications, making this statement false.

Option D:Incorrect – Similar to Option A, workflows do not generate " item variable types. " Instead, they focus on fulfillment processes and notifications.

ServiceNow Product Documentation – Service Catalog

ServiceNow Learning – Service Catalog and Workflow Automation

ServiceNow Developer Portal – Flow Designer & Workflow Automation

References from Certified System Administrator (CSA) Documentation:

In ServiceNow, ataskis a record that represents work that needs to be completed. It follows a lifecycle where it is:

Created– A task is generated, either manually or automatically (e.g., an incident, change request, or problem record).

Worked Upon– Users perform necessary actions, update statuses, and progress the task towards resolution.

Closed– Once completed, the task reaches a closed state, indicating that no further action is needed.

Tasks in ServiceNow are derived from theTask [task]table.

Common task-based records includeIncidents, Change Requests, Problems, and Service Requests.

Tasks follow a defined workflow and state transitions (e.g., New → Work in Progress → Resolved → Closed).

Key Features of a Task:

A. Report:

A report is a visualization of data and does not follow a lifecycle involving work or closure.

B. Workflow:

A workflow definesprocess automationand the movement of tasks, but it is not something that gets " worked upon " directly like a task.

C. Event:

Events are system-generated triggers that notify or automate actions, but they do not have a structured lifecycle like a task.

Why Other Options Are Incorrect:

ServiceNow Documentation:Task Management in ServiceNow

CSA Exam Guide:Coverstask recordsas fundamental entities that go through a lifecycle.

Reference from CSA Documentation:Thus, the correct answer isD. Task.

In ServiceNow,metricsare essential tools used to track and measure key performance indicators (KPIs) related to IT Service Management (ITSM) processes. They help organizations assess how effectively they are meeting their objectives by collecting data over time.

Definition of a Metric:

Ametricin ServiceNow refers to a method of measuring and evaluating the performance and effectiveness ofIT service management processesover time.

It allows organizations to track changes in records and measure how long specific conditions exist within a workflow.

Key Characteristics of a Metric:

It is used toassess process performanceandevaluate efficiencywithin IT services.

It providesquantifiable datato analyze trends and improvements in Service Management.

Common use cases include trackingincident resolution times,change request approvals, andSLA compliance.

Understanding ServiceNow Metrics:Why Answer " C " is Correct:✔️ " A metric is used to measure and evaluate the effectiveness of IT service management processes. "

This definition aligns precisely with how ServiceNow definesmetrics—theytrack, measure, and analyzethe efficiency of various ITSM processes over time.

Metrics help organizations understand service performance trends and make data-driven decisions.

Why the Other Answers Are Incorrect:A. " A metric is a report gauge used on homepages to display real-time data. "

Incorrectbecausegaugesare UI elements thatvisualizedata from reports or metrics but are not themselves metrics. Metricscollect and measuredata, whereasgaugesdisplay the information.

B. " A metric is a time measurement used to report the effectiveness of workflows and SLAs. "

Incorrectbecause whiletime-based metricsexist (e.g., tracking how long an incident stays in a particular state), metrics in ServiceNow arebroaderand not limited to time measurement alone.

D. " A metric is a comparative measurement used to report the effectiveness of workflows and SLAs. "

Incorrectbecause metrics are not necessarilycomparative; they areabsolute measuresof process effectiveness. Metrics provideraw performance data, which can later be compared or analyzed over time.

ServiceNow CSA Study Guide – Reporting & Performance Analytics

ServiceNow Docs: Metrics Definition & Configuration(ServiceNow Docs - Metrics)

ServiceNow Performance Analytics & Reporting Overview

References from the Certified System Administrator (CSA) Documentation:

ServiceNow follows asingle-instance, single-tenant architecture,nota multiple-tenant architecture. This means:

Single-Instance:

Each ServiceNow instance is aunique, independent environmentfor a customer.

All customers have their own dedicated instance with their owncustom configurations, data, workflows, and applications.

ServiceNow instances are hosted in amulti-instance cloud modelrather than a multi-tenant model.

Single-Tenant Model (Multi-Instance Architecture):

Unlikemulti-tenant architectures(where multiple customers share the same application and database), ServiceNow provideseach customer with a separate, isolated instance.

Thisensures data security, performance isolation, and customization flexibility.

Each instance has its owndata storage, configuration, and upgrade schedule, reducing risks associated with shared environments.

Why ServiceNow Uses Multi-Instance Instead of Multi-Tenant:

Security & Data Isolation:Since each customer has an independent instance, there isno risk of data leakagebetween tenants.

Customization & Flexibility:Customers cancustomizetheir instance freely without affecting others.

Performance & Scalability:Each instance can bescaled independently, ensuring optimal performance.

ServiceNow does NOT use a multiple-tenant architecture.

ServiceNow follows a single-instance, single-tenant (multi-instance) model.

Each customer has a dedicated instance with isolated resources and configurations.

A multi-tenant architecturemeans multiple customerssharethe same application/database with logical separation, which is NOT the case in ServiceNow.

ServiceNow instead provides separate instancesfor each customer, meaning it isnota true multi-tenant system.

ServiceNow Product Documentation – Multi-Instance Cloud

ServiceNow Community – Single-Tenant vs. Multi-Tenant Explained

ServiceNow Best Practices – Security & Instance Architecture

Why Option B (False) Is Correct?Why Option A (True) Is Incorrect?References from Certified System Administrator (CSA) Documentation:

TheHistory sectionin theApplication Navigatortracks recently visited records, lists, and forms within ServiceNow. This feature allows users to quickly navigate back to previously accessed content without searching manually.

What Appears in the History Section?The History sectionlogs user activityrelated to:

Records (Option A)– Recently viewed records from any table, such as incidents, requests, or tasks.

Lists (Option C)– Any list views a user has accessed, such asIncident ListorChange Request List.

Forms (Option D)– Any individual record viewed in form view, such as anincident formoruser form.

Why is Option B (UI Pages) Correct?UI Pages do NOT appear in the History section.

UI Pagesare special custom pages built with Jelly scripting and used forcustom interfaces, portals, and dashboards(e.g., Service Portal pages).

Since they do not represent individual records, lists, or forms,they are not included in the user’s History tracking.

Why Are the Other Options Incorrect?A. Records

Recordsare individual database entries (e.g., specific incidents, change requests, or users).

Since records are frequently accessed, theyare logged in History.

C. Lists

Listsdisplay multiple records from a table (e.g., all open incidents).

Since users navigate through lists frequently, theyare logged in History.

D. Forms

Formsare used to view or edit individual records (e.g., an incident form).

Since forms are commonly accessed, theyare logged in History.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Application Navigator & History

???? ServiceNow Application Navigator Documentation

" The History section of the Application Navigator displays a list of the records, lists, and forms that you have recently accessed. "

" Custom UI Pages are not included in History tracking. "

In computing and networking, aclientrefers to anapplication or system that accesses a remote service or another computer system (known as a server). The client-server model is a fundamental concept in computing, where:

A client sends requeststo a server.

The server processes the requestand sends back a response.

This architecture is widely used inweb applications, databases, and ServiceNowitself, whereclients interact with the ServiceNow platform (server) via a web browser or API requests.

In ServiceNow, theclienttypically refers toa user’s browser or an external system making requests via API calls.

Theserveris the ServiceNow instance, which processes requests and returns responses.

Client-side scripts(such asClient ScriptsorUI Policies) run on the user ' s browser, whileserver-side scripts(such as Business Rules and Script Includes) execute on the ServiceNow server.

How This Relates to ServiceNow:

A. Server→ A serverreceives requestsand processes them but is not the requesting entity.

C. Script→ A script is apiece of codethat executes certain actions but does not represent an entire system accessing a service.

D. Policies→ Policies definerules or behaviors(e.g., UI Policies, Data Policies) but do not access a remote service.

Why Other Options Are Incorrect:

ServiceNow Documentation:Client and Server in ServiceNow

CSA Exam Guide:CoversClient and Server architecturein ServiceNow.

Reference from CSA Documentation:

In ServiceNow,User Criteriadefine conditions that determinewhich userscancreate, read, write, and retireknowledge articles in aKnowledge Base (KB). User Criteria help enforceaccess controland ensure that only authorized users can interact with specific knowledge bases.

Control who canread, contribute, edit, or retireknowledge articles.

Based onroles, groups, departments, locations, or custom conditions.

Applied at theKnowledge Base level, affecting all articles within that KB.

Can be combined using " Must match all " or " Match any " logic.

Example 1: Restricting Read Access

A knowledge base for IT Support should be accessibleonly to IT employees.

User Criteria:Department = IT, OR Role = itil

Only IT employees or ITIL users can read articles in this KB.

Example 2: Controlling Who Can Contribute

OnlyHR staffshould be allowed to create or update HR-related knowledge articles.

User Criteria:Group = HR Team, OR Role = knowledge_manager

Only HR Team members and Knowledge Managers can contribute.

User Criteriais the official term in ServiceNow for defining access control conditions for knowledge articles.

It allows precise control over who canread, create, write, or retirearticles.

It is a feature within theKnowledge Management application.

A. User Conditions – Incorrect

No such concept exists in ServiceNow. User Criteria, not " User Conditions, " determine knowledge article access.

B. User Info – Incorrect

" User Info " refers to details stored in thesys_usertable (e.g., name, email) but does not define knowledge permissions.

D. User Permissions – Incorrect

While permissions exist in ServiceNow (via roles and ACLs),User Criteriaspecifically manageKnowledge Baseaccess.

ServiceNow Docs: User Criteria for Knowledge Management

ServiceNow CSA Study Guide – Knowledge Management Permissions

ServiceNow Product Documentation: Configuring Knowledge Base Access

Key Features of User Criteria:Examples of User Criteria:Why " C. User Criteria " is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

ARelated Listin ServiceNow is used to display records from other tables that are related to the current record. It helps users view and manage associated records without navigating away from the main record they are working on.

Related Lists appear at the bottom of a form view.

They display records from tables that have a relationship (via reference fields, many-to-many relationships, or database joins) with the current table.

Users can add, remove, or modify related records directly from the Related List, depending on their permissions.

Key Features of Related Lists:Why " D. To present related records " is the correct answer?Related Lists show records from another table that have a relationship with the current record. For example:

AnIncidentrecord may have a Related List showing allTasksassociated with it.

AUserrecord may have a Related List displayingGroup Memberships.

AChange Requestrecord may have a Related List displaying all relatedCI (Configuration Items).

Option A: " To create a one-to-many relationship " – Incorrect. While Related Lists often display one-to-many relationships, they do not create them. Relationships are defined throughreference fields,many-to-many tables, ordatabase joins.

Option B: " To dot-walk to a core table " – Incorrect. Dot-walking allows users to access related fields from referenced records, but it is not the purpose of a Related List.

Option C: " To present related fields " – Incorrect. Related Lists display related records, not just individual fields. Related fields can be accessed using dot-walking or reference fields but are not the same as Related Lists.

ServiceNow Product Documentation - Related Lists

ServiceNow CSA Study Guide - Configuring Forms and Lists

ServiceNow Docs: Relationships in Tables

Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

In ServiceNow,tablesare fundamental components of the platform ' s database structure. A table consists ofrecords (rows)andfields (columns)that store data.

Arecordis an individual entry in a table, similar to a row in a traditional database.

Each record represents a single entity (e.g., an incident, a user, a request).

Records are stored uniquely in the system and are identified by aSys ID(a globally unique identifier).

Afieldis an attribute of a record, like a column in a database.

Each field has a specificdata type(e.g., string, integer, date, reference).

Fields define what type of information can be stored in a record.

1. Records (Rows) – Correct Option2. Fields (Columns) – Correct OptionExample:TheIncident [incident]tableSys ID

Number

Short Description

Caller

State

123abc

INC001

System crash

John D

New

456def

INC002

Network issue

Jane S

Open

Records:INC001, INC002 (each row is a record).

Fields:Number, Short Description, Caller, State (each column is a field).

B. Lists – Incorrect

Listsare aviewof table data but are not a part of the table itself.

A list displays multiple records from a table but does not define the structure of a table.

C. Forms – Incorrect

Formsare user interfaces used to view or edit single records.

A form allows users to interact with the data stored in a table but is not part of the table structure itself.

ServiceNow Docs: Tables and Records

ServiceNow CSA Study Guide – Understanding Tables, Records, and Fields

ServiceNow Product Documentation: List and Form Views

Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

In ServiceNow, knowledge articles can bemarked for reviewusing the " Flag article " feature. This allows users toindicate issuessuch as outdated content, incorrect information, or necessary updates.

Users can flag an articleif they believe it needs review or corrections.

The flagged article appears in theKnowledge Management Dashboard, where knowledge managers can track flagged articles.

Knowledge managers or owners canreview flagged articlesand make necessary updates or retire them if needed.

How the " Flag Article " Feature Works:

B. Review→ No such option exists in ServiceNow for marking an article for review. However, knowledge managers can schedule article reviews manually.

C. Bookmark→ Used tosavefrequently accessed articles for personal reference but does not indicate that the article needs a review.

D. On Hold→ Applies to workflows or approvals but is not a method for marking an article for review.

Why Other Options Are Incorrect:

ServiceNow Documentation:Flagging a Knowledge Article

CSA Exam Guide:Covers theFlag Articlefunction as a key feature in Knowledge Management.

Reference from CSA Documentation:Thus, the correct answer is:

A. Flag article

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, knowledge articles within aKnowledge Base (KB)aregrouped by categoriesto help users easily find and navigate relevant information.

Hierarchical Structure:

Categories can haveparent-child relationships, allowing forsubcategories.

Example:

Key Features of Knowledge Article Categorization:nginx

CopyEdit

ITSupport

├── Hardware

│ ├── Laptops

│ ├── Printers

├── Software

│ ├── Windows

│ ├── MacOS

Improved Search & Filtering:

Users can filter knowledge articlesby categoryin the Service Portal, Knowledge Management homepage, or in the Global Search.

Permissions & Visibility Control:

Categories can havespecific user criteriato restrict access to certain articles based on roles or groups.

Article Organization & Management:

Knowledge managers canreassign articlesto different categories if needed.

Knowledge Base (KB) articlesare always assigned to acategoryfor structured organization.

Without categories, articles would be unstructured and difficult to locate.

Knowledge Management Overview

Knowledge Management in ServiceNow

Creating and Managing Knowledge Categories

Knowledge Base Categories

Why the Answer is True?References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (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’sService Catalog, the display sequence of variables within aCatalog Itemis controlled by theOrder field in the Variable form. TheOrder fielddetermines the position in which the variables appear when a user fills out a catalog item. Lower values appear first, and higher values appear later.

(A) The Default Value field in the Catalog Item form – Incorrect

TheDefault Valuefield sets an initial value for a variable but doesnotcontrol the display sequence. It is used to pre-fill a value when the form loads.

(B) The Sequence field in the Catalog Item form – Incorrect

There isno such fieldcalled " Sequence " in the Catalog Item form. The field that determines the sequence of variables is theOrderfield in the Variable form.

(C) The Order field in the Variable form – Correct

Each variable in a catalog item has anOrder field.

Variables with a lower order number are displayedbeforethose with a higher order number.

If multiple variables have the same order value, ServiceNow orders them based oninternal system processing order.

(D) The Choice field in the Variable form – Incorrect

TheChoice fieldapplies only toMultiple Choice, Select Box, and Radio Buttonvariables, determining the selectable options for users. It doesnotcontrol the display sequence of variables in a catalog item form.

Explanation of Each Option:

It is a best practice to useincremental numbering (e.g., 100, 200, 300, etc.)for order values instead of consecutive numbers (e.g., 1, 2, 3). This makes it easier to insert new variables later without having to renumber existing ones.

The order values are respectedunless a layout configuration (e.g., multi-column form layout)changes the positioning.

ServiceNow Docs: Creating and Configuring Service Catalog Variables

ServiceNow Community Best Practices for Service Catalog Variables

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

ServiceNow uses a hierarchical structure to manageService Catalog requests:

REQ (Request Record)

TheRequest (REQ#)is theparent recordthat represents the entire service request submitted by a user.

It groups all requested items and their associated tasks.

Found in thesc_requesttable.

RITM (Requested Item Record)

TheRequested Item (RITM#)is the specificcatalog itemordered by the user within a request.

A singleREQcan have multipleRITMsif the user ordered multiple items in a single request.

Found in thesc_req_itemtable.

TASK (Catalog Task Record)

TheTask (TASK#)is the individual fulfillment action required to complete the requested item.

A singleRITMcan have multipletasks, each assigned to different fulfillment teams.

Found in thesc_tasktable.

Why Answer " C " is Correct:✔️REQ (Number) > RITM (Number) > TASK (Number)

This is thecorrect pathbecause it follows theServiceNow fulfillment structure:

REQ (Request)– Tracks the entire request.

RITM (Requested Item)– Tracks individual items within the request.

TASK (Catalog Task)– Tracks the specific tasks needed to complete the requested item.

This path allows an administrator to drill down from the overallRequest (REQ#)to individualRequested Items (RITM#)and finally to theTasks (TASK#)assigned to fulfill those items.

Why the Other Answers Are Incorrect:A. RITM (Number) > REQ (Number) > PROCUREMENT (Number)

Incorrectbecause theREQ# (Request) comes firstbefore the RITM# (Requested Item).

Also,PROCUREMENT#is not always part of the fulfillment flow unless the item requires procurement (e.g., purchasing hardware).

B. REQ (Number) > RITM (Number) > PROCUREMENT (Number)

Incorrectbecausenot all requests involve procurement.

The last step should beTASK (sc_task), notPROCUREMENTunless it ' s a procurement-related request.

D. FULFILLMENT (Number) > RITM (Number) > TASK (Number)

Incorrectbecause " FULFILLMENT " is not a standard record typein ServiceNow.

The correct hierarchy starts withREQ# (sc_request), not " FULFILLMENT. "

ServiceNow CSA Study Guide – Service Catalog & Request Fulfillment

ServiceNow Docs: Request Fulfillment Process(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_request, sc_req_item, sc_task)

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow,Table Access Control (ACL) rulesdefine the permissions for accessing records within a table. When a user attempts to access a record, ServiceNow processesACL rules in a specific orderto determine if the user has the necessary permissions.

Specific Table Name ACLs

ServiceNowfirst checks ACL rulesthat are defined for the exact table being accessed.

If there are multiple ACL rules for the same table, ServiceNow evaluates themfrom most specific to least specific(i.e., field-level ACLs before table-level ACLs).

Parent Table Name ACLs(If applicable)

If the table inherits from another table (e.g.,Incident inherits from Task), ServiceNownext checks ACL ruleson theparent table.

This ensures that inherited rules are properly applied.

Wildcard ACLs (*)(Any table)

If no explicit ACL rule is found for the table or its parent, ServiceNow checkswildcard ACL rules (*), which apply toall tables.

Wildcard ACLs act as alast resortwhen no table-specific rules exist.

Order of Processing ACL Rules:

(A) any table name (wildcard), parent table name, table name – Incorrect

Wildcard rules (*) areprocessed last, not first.

(B) table name, parent table name, any table name (wildcard) – Correct

This follows the correctprocessing order:

First:ACLs for the specific table

Second:ACLs for the parent table (if applicable)

Third:Wildcard ACLs (*)

(C) parent table name, table name, any table name (wildcard) – Incorrect

Parent table ACLs arechecked aftertable-specific ACLs, not before.

(D) any table name (wildcard), table name, parent table name – Incorrect

Wildcard ACLs (*) arealways processed last, so this order is incorrect.

Explanation of Each Option:

Field-level ACLs(column-specific) take precedence overtable-level ACLs.

If multiple ACL rules apply,all must evaluate totruefor access to be granted.

Explicit Deny:If an ACL rule explicitlydenies access, the user is denied, even if another ACL grants access.

Always Test ACLs:Use the " Security Debugging " feature (/sys_security_acl_list.do) to verify how ACLs are applied.

Additional Notes & Best Practices:

ServiceNow Docs: How Access Control Rules Work

ServiceNow Community: Understanding ACL Processing Order

References from Certified System Administrator (CSA) Documentation:

InServiceNow,UI Policiesallow administrators todynamically control form fieldsbased on conditions without using scripts. With UI Policies, you can change thebehaviorof a field by making it:

Read-only→ The user canviewthe field butcannot edit it.

Mandatory→ The field becomesrequired, and the usermustfill it out before submitting the form.

Hidden→ The field isremoved from visibilityon the form.

Explanation of Each Option:A. Read-only–Correct

A UI Policy can make a fieldread-only, meaning users canseethe field butcannot modifyits value.

Example: A field likeRequest Number (REQ0001)is typicallyread-onlyafter submission.

B. Write-only–Incorrect

ServiceNowdoes nothave a " write-only " field setting in UI Policies.

If a field iseditable, users canboth read and write; if it’s hidden or read-only, writing is not possible.

C. Necessary–Incorrect

There isno " Necessary " field state in ServiceNow UI Policies.

If the intent is to make a field required, the correct term is " Mandatory " .

D. Mandatory–Correct

UI Policies can make a fieldmandatory, requiring the user toenter a valuebefore submitting the form.

Example: AnIncident Descriptionfield might be mandatory before an incident is submitted.

E. Empty–Incorrect

UI Policiescannot directly enforce an " empty " state. However, adefault valuecould be cleared using aclient script, but this isnot a UI Policy feature.

F. Hidden–Correct

UI Policies canhide a field, making it invisible on the form.

Example: A " Manager Approval " field may be hiddenuntila certain condition (e.g., request cost > $1000) is met.

Final Answer:Read-only

Mandatory

Hidden

ServiceNow Docs – UI Policies and UI Policy

ServiceNow Learning – Form Configuration & UI Policies

ServiceNow Developer Portal – Controlling Form Behavior with UI Policies

References from Certified System Administrator (CSA) Documentation:

TheBasic Configuration UI 16 modulein ServiceNow allows administrators to make basic UI customizations without needing to modify code or system properties manually. These settings apply to theoverall look and feelof the instance.

Banner Image (Option A)

Allows admins to change theServiceNow banner logoat the top of the page.

This is useful for branding the instance with a company’s logo.

Browser Tab Title (Option C)

Changes thetitle displayed on the browser tabwhen accessing the ServiceNow instance.

Helps customize the instance’s branding for different user environments (e.g., " IT Service Portal " instead of " ServiceNow " ).

System Date Format (Option D)

Allows admins toset the date formatdisplayed across the instance.

Helps standardize date display based on organizational or regional preferences (e.g.,MM/DD/YYYY vs. DD/MM/YYYY).

Customizable Elements via Basic Configuration UI 16:

Why Are the Other Options Incorrect?B. Record Number Format

Incorrect:The format of record numbers (such asINC0010001 for incidents) is controlled viaSystem Definition → Number MaintenanceandNOTin Basic Configuration UI 16.

E. Form Header Size

Incorrect:The form header size isnot directly customizable through Basic Configuration UI 16.

Form layout and styling changes are managed throughUI Policies, Client Scripts, or custom CSS configurations.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Basic Configuration UI 16

???? ServiceNow UI Customization Documentation

" Basic Configuration UI 16 provides a simple way to modifybanner images, browser titles, and system-wide date formats. "

Conclusion:The correct answers are:

A. Banner Image(Customizes the instance’s logo)

C. Browser Tab Title(Changes the browser tab text)

D. System Date Format(Sets the instance-wide date format)

???? Understanding Basic Configuration UI 16 is important for ServiceNow administratorsto quickly apply branding and instance-wide display settings without modifying system properties manually.

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:

InServiceNow,Client Scriptsare used to execute JavaScript codeon the client-side (browser)to control form behavior, validate data, or enhance user interaction.

Types of Client Scripts in ServiceNow:There arefourtypes of Client Scripts supported in ServiceNow:

onLoad (Option D)

Runswhen a form loads.

Used to pre-fill fields, hide/show elements, or set default values.

Example: Automatically setting the " Priority " field toHighwhen a new incident is created.

onChange (Option F)

Runswhen a specific field value changes.

Used for dynamic form behavior, such as making fields mandatory based on another field ' s value.

Example: If " Category " is changed to " Hardware, " then show the " Hardware Type " field.

onSubmit (Option A)

Runswhen the form is submitted.

Used for final validation before allowing submission.

Example: Preventing submission if a mandatory field is left empty.

onCellEdit (Option C)

Runswhen a cell value is edited inline in a list view.

Used to trigger immediate validation or updates without opening the full form.

Example: Displaying an alert when a user directly changes an incident ' s priority from a list view.

Why Are the Other Options Incorrect?B. onUpdate

No " onUpdate " client script type exists in ServiceNow.

" onUpdate " is relevant inBusiness Rules, not Client Scripts.

E. onEdit

No " onEdit " client script type exists.

Similar functionality can be achieved with " onChange " or " onCellEdit " scripts.

G. onSave

No " onSave " client script type exists.

" onSubmit " handles validation before saving a record.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Client Scripts

???? ServiceNow Client Scripts Documentation

" Client Scripts can beonLoad, onChange, onSubmit, or onCellEditdepending on when they execute. "

Conclusion:The correct answers are:

A. onSubmit(Runs when submitting a form)

C. onCellEdit(Runs when editing a list cell)

D. onLoad(Runs when a form loads)

F. onChange(Runs when a field value changes)

In theServiceNow Service Catalog, aREQ numberrepresents aRequest (REQ) record, which functions as anorder numberfor a service request. When a user submits a request through the Service Catalog, the system generates aRequest (REQ) record, which tracks the overall order.

REQ (Request Record) – The Order Number

This is theparent recordthat represents the entire order/request submitted by the user.

It contains key details such as the requester, the total cost, approval status, and the overall request state.

Example:REQ0010023

RITM (Requested Item) – The Individual Catalog Item

Each item requested within a REQ has its ownRequested Item (RITM) record.

The RITM tracks the fulfillment of a specific item within the order.

Example:RITM0010456(a single laptop ordered in a request)

TASK (Catalog Task) – The Actions to Complete the Request

Catalog Tasks (TASK) are created under an RITM to handle specific fulfillment steps.

Multiple tasks can exist under a single RITM, assigned to different fulfillment teams.

Example:TASK0013456(a task assigned to IT Support to configure the laptop)

Breakdown of the Service Catalog Request Structure:

Why the Other Options Are Incorrect:B. The stage (Incorrect)

Thestageof a request is part of the request lifecycle (e.g., Approval, Fulfillment, Completed), but it is not represented by theREQ number.

C. The task to complete (Incorrect)

Atask to completeis represented by aCatalog Task (TASK), not theREQ number.

Tasks are specific actions assigned to fulfill an item request.

D. The individual item in the order (Incorrect)

Anindividual itemin a Service Catalog request is represented by aRequested Item (RITM), not theREQ number.

Example Scenario:A user submits a request for anew laptop and a software license:

REQ0012345→ Tracks the overall request (Order Number)

RITM0016789→ Laptop Request

TASK0018901→ IT configures the laptop

RITM0016790→ Software License Request

TASK0018902→ IT assigns the software license

In ServiceNow, every table has a uniqueplatform name(also known as thedatabase nameorsys_id). The table that stores user records in ServiceNow is called " sys_user " .

Table Name:sys_user

Purpose:Stores user records, including their roles, group memberships, and personal details.

Location in ServiceNow:You can access this table by navigating to:All → Users and Groups → Users

Key Fields in sys_user Table:

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

Name (name)– Full name of the user.

Email (email)– Email address of the user.

Roles (roles)– Defines user permissions in the system.

Active (active)– Indicates if the user is active in the system.

A. u_users– Incorrect. The prefixu_is typically used forcustom tablescreated by administrators. This is not a default system table.

B. sys_users– Incorrect. The correct name issys_user(singular), notsys_users. ServiceNow follows a singular naming convention for system tables.

C. x_users– Incorrect. The prefixx_is reserved forScoped Applicationscreated within an instance. The User table is a core system table, not a scoped one.

ServiceNow Product Documentation → User Administration → sys_user Table

ServiceNow Tables Reference → sys_user

ServiceNow CSA Study Guide → User and Data Administration

Understanding the sys_user Table:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

Service Catalog variables in ServiceNow are used to capture user input when they request catalog items, record producers, or order guides. These variables help customize user interactions and drive automation within Service Catalog workflows.

Key Characteristics of Service Catalog Variables:

Global by Default:

When a Service Catalog variable is created, it isglobal by default, meaning it can beused across multiple catalog itemsunless scoped to a specific item.

This helps inreusabilityof variables across different catalog items, reducing redundancy.

However, administrators candisable the " Global " checkboxif they want the variable to be specific to one catalog item.

Types of Service Catalog Variables:

Variables can besingle-line text, choice lists, reference fields, checkbox, multi-line text, and more.

They allow administrators to collect structured data from users during item requests.

Reusability Across Catalog Items:

Global variables can be used across multiple catalog itemswithout creating duplicate variables.

This is useful when multiple items require the same type of user input (e.g., location, department).

Visibility and Dependency:

ServiceNow allowsUI policiesandcatalog client scriptsto control the behavior of these variables dynamically.

Admins can configurevisibility, mandatory status, or dependenciesbased on user selections.

Explanation of Other Options (Why They Are Incorrect):

Option A (Service Catalog variables can only be used in Record Producers) – Incorrect

While Service Catalog variablescanbe used in Record Producers, they arenot limitedto them.

Variables can also be used inCatalog Items, Order Guides, and Requested Items (RITM).

Option B (Service Catalog variables can only be used in Order Guides) – Incorrect

Service Catalog variablescanbe used in Order Guides, but they arenot restrictedto them.

Order Guides allow multiple items to be ordered together, but variables can be used independently in Catalog Items and Record Producers as well.

Option C (Service Catalog variables cannot affect the order price) – Incorrect

Service Catalog variablescan affect pricingthroughVariable Price Mapping.

If configured, variables (like dropdowns or checkboxes) can be linked to aprice adjustment, impacting the total cost of the request.

For example, selecting " Additional Storage " in a cloud server request could add extra costs dynamically.

Official Reference from ServiceNow Certified System Administrator (CSA) Documentation:

ServiceNow Documentation – Service Catalog Variables: ServiceNow Variables Guide

ServiceNow CSA Exam Guide: Covers Service Catalog fundamentals, including variable behavior and reusability.

InServiceNow Flow Designer, aTriggeris used toinitiateaflow. Triggers define the conditions under which a flow starts and can be based on various system events, schedules, or user actions.

(A) A Trigger – Correct

Triggers are the starting point of a flowin Flow Designer.

A flow will not execute unless a trigger condition is met.

Types of triggers include:

Record-based triggers(e.g., when a record is created, updated, or deleted)

Scheduled triggers(e.g., run at a specific time or interval)

Application-specific triggers(e.g., Service Catalog request submission)

(B) Core Action – Incorrect

Core Actionsare predefined actions that execute tasks within a flow, such as:

Sending notifications

Updating records

Calling APIs

They aresteps within a flow,notwhat initiates it.

(C) A Spoke – Incorrect

A spokein Flow Designer is a collection of actions and subflows related to a specific application or integration (e.g., ServiceNow ITSM Spoke).

Spokescontain actionsbut donotinitiate flows.

(D) An Event – Incorrect

Eventsin ServiceNow trigger Business Rules, Notifications, and Script Actions, but they arenot directly used to initiate flowsin Flow Designer.

However, aflow can be triggered based on an event, but the event itself is not the trigger—the flow’s trigger is configured to listen for the event.

Explanation of Each Option:

Triggers should be well-definedto prevent unnecessary flow executions that might impact performance.

Use Scheduled Triggersfor time-based workflows (e.g., daily reports).

Record Triggersare commonly used for automation within ITSM processes.

Debugging Triggers: Use theFlow Execution Detailspage to troubleshoot trigger execution.

Additional Notes & Best Practices:

ServiceNow Docs: Flow Designer Triggers

ServiceNow Community: Best Practices for Flow Designer Triggers

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Rolesare used to control access toApplications and Moduleswithin the platform. ARoleis a set of permissions that define what actions a user can perform and which records they can access.

Grant Access to Applications and Modules:

If a userdoes not have the required role, theycannot see or accessan application/module.

Control Record-Level and Field-Level Access:

SomeAccess Control Rules (ACLs)depend on roles topermit or restrictdata visibility.

Assign Multiple Roles to a User:

A user can havemultiple rolesbased on job responsibilities.

Example Roles in ServiceNow:

admin– Full access to all system features.

itil– Can manage incidents, problems, and changes.

catalog_admin– Manages the Service Catalog.

asset– Manages assets and CI records.

Key Functions of Roles in Access Control:

Navigate to:All → Users and Groups → Users

Open a user record

Scroll to the Roles related list

Click Edit and add roles

How to Assign Roles to Users:

A. Access Control Rules– Incorrect.

Access Control Rules (ACLs)definerecord-level and field-levelsecurity, but they donot control access to applications and modulesdirectly.

B. UI Policies– Incorrect.

UI Policiescontrol the visibility and behavior of form fields,not module or application access.

D. Assignment Rules– Incorrect.

Assignment Rulesautomatically assigntasks(e.g., Incidents, Requests) to groups or users, but theydo not control access.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Roles and Permissions

ServiceNow CSA Study Guide → User and Role Management

ServiceNow Knowledge Base → Controlling Access to Applications and Modules

References from Certified System Administrator (CSA) Documentation:

When a user places an order for an item or service from theService Catalogin ServiceNow, the system generates aRequest (REQ). This is a core component ofRequest Managementwithin the IT Service Management (ITSM) module.

User Places an Order:

The user selects an item from theService Catalog(e.g., a laptop, software, or an access request).

The order may consist of multiple items, depending on the selection.

ServiceNow Generates a Request (REQ):

ThisRequest (REQ#)acts as the umbrella record that tracks the order as a whole.

It is stored in thesc_requesttable.

Creation of Requested Items (RITM#):

Each item within the request generates aRequested Item (RITM#), stored in thesc_req_itemtable.

For example, if the user orders a laptop and a software license, two RITM records are created under the same Request.

Tasks (SCTASK#) Are Created:

Each Requested Item (RITM) may trigger one or moreCatalog Tasks (SCTASK#)in thesc_tasktable.

These tasks define the steps required to fulfill the request (e.g., procurement, approval, and configuration).

A. A Change Request– Incorrect. AChange Request (CHG#)is created only if the requested item involves changes to the infrastructure, such as a server upgrade. Not all catalog items require a change request.

B. An Order Guide– Incorrect. AnOrder Guideis a tool within the Service Catalog that helps users order multiple related items at once. However, it does not get generated when an order is placed.

D. An SLA– Incorrect. AService Level Agreement (SLA)may be associated with the request or tasks, but it is not automatically generated when a request is placed.

ServiceNow Product Documentation → Service Catalog → Request Fulfillment

ServiceNow CSA Study Guide → Service Catalog and Request Management

ServiceNow Tables Reference → sc_request, sc_req_item, sc_task

Understanding the Request Process in ServiceNow:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

In ServiceNow, afilter conditionconsists of three primary components:

Field– The specific column (attribute) in a table that you want to filter by.

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

Example:is, is not, contains, starts with, greater than, less than

Value– The actual data that the filter is looking for.

Example:High (for Priority), New (for State), IT Support (for Category)

Example of a Filter Condition in ServiceNow:If you want to filter Incident records where theStateisNew, the filter condition would be:

Field:State

Operator:is

Value:New

A. Table–

A table is where data is stored, but it isnota component of a filter condition.

Filters are appliedona table but do not include the table itself in the condition.

ServiceNow Docs: Filtering Data in Lists and

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

Why the Other Option is Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatField, Operator, and Valueare the three core components of a filter condition.

InServiceNow, when working with forms (such as Incident, Change, or Task forms), users can perform different actions tosave records. The two key operations in this context areInsertandUpdate.

Creates a new record in the database.

Saves the record and exits the form(returns to the list view or the previous screen).

The form is cleared after inserting the record.

It doesnotmodify an existing record; instead, it generates anew record with a new unique sys_id.

Example:

A user creates a newIncident, fills in details, and clicksInsert.

The systemsaves the new Incident and exitsto the list view.

Saves changes to an existing record.

Remains on the form after saving.

It doesnot create a new record; itmodifies the existing recordin place.

Example:

A user opens an existing Incident, changes the Priority, and clicksUpdate.

The systemsaves the changes but keeps the user on the form.

1. Insert Operation (Correct Description in Option C)2. Update Operation (Correct Description in Option C)

Why the Other Options Are Incorrect:A. Insert creates a new record and Update saves changes, both remain on the form (Incorrect)

Insert does not remain on the form; it exits after creating a new record.

B. Insert creates a new record and Update saves changes, both exit the form (Incorrect)

Update does not exit the form; it remains on the form after saving.

D. Insert saves changes and remains on the form, Update saves changes and exits the form (Incorrect)

Insert exitsafter creating a new record.

Update remains on the form, not exits.

Insert and Stay: This is avariation of Insert, whichcreates a new record but keeps the form openfor additional edits.

Submit vs. Insert:

Submitis typically used when submitting a form for workflow processing (e.g., Service Catalog Requests).

Insertexplicitly saves a record as a new entry.

Additional Notes:

Example Scenario in Incident Management:Action

Result

Click " Insert "

Creates anewIncident andexitsthe form.

Click " Update "

Saves changes to theexistingrecord andstays on the form.

InServiceNow Knowledge Management, users can providefeedbackonpublished knowledge articlesby flagging them. This feedback helpsknowledge managers and authorsidentify errors, outdated information, or areas for improvement.

Toview feedback left on a published article, there are two primary pathways:

Pathway 1: Knowledge Base > My Knowledge > Flagged Articles

This option allowsknowledge managers and authorsto see all flagged articlesthey have authored or have access towithin a specificKnowledge Base.

Location:Knowledge Base → My Knowledge → Flagged Articles

Pathway 2: Knowledge > My Articles > Flagged

This option lets authorsview only their own articlesthat have been flagged.

Location:Knowledge → My Articles → Flagged

A. Knowledge > Articles > My Flagged

There isno direct " My Flagged " optionunderKnowledge > Articles.

D. Knowledge > Articles > Published

This showsall published articlesbut doesnot specifically show flagged (feedback) articles.

Navigate toKnowledge > My Articles > Flagged.

OR navigate toKnowledge Base > My Knowledge > Flagged Articles.

Open a flagged article to review thefeedback comments and reason for the flagging.

ServiceNow Docs: Managing Knowledge Feedback and Flagged

ServiceNow CSA Official Training Guide (Knowledge Management & Feedback Handling)

Why the Other Options Are Incorrect?How to View Feedback in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms that the correct pathways to view feedback on published articles are " Knowledge Base > My Knowledge > Flagged Articles " and " Knowledge > My Articles > Flagged " .

In ServiceNow,all tablesin the database are recorded in amaster tablecalled[sys_db_object]. This table stores metadata about each table in the system, including itsname, label, and other attributes.

Stores a record for every table in the ServiceNow instance.

Tracks essential table properties, such as thetable name, label, and whether it is an extension of another table.

Helps administratorsview, modify, or create new tablesin ServiceNow.

Used inTable Administration and Custom Table Development.

A. [sys_master_db]–

This tabledoes not existin ServiceNow.

C. [sys_master_object]–

There is no such table named " sys_master_object " in ServiceNow.

D. [sys_object_db]–

This tabledoes not existin ServiceNow.

The correct name issys_db_object.

Navigate toSystem Definition→Tables.

Search for the tablesys_db_object.

Open the table to see records representing all tables in the instance.

ServiceNow Docs: Understanding Tables and

ServiceNow CSA Official Training Guide (System Data and Tables Overview)

Key Functions of [sys_db_object]:Why the Other Options Are Incorrect?How to View the [sys_db_object] Table in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms that[sys_db_object]is themaster tablethat contains a record for every table in the ServiceNow database.

In ServiceNow,UI Actionsare used to add buttons, links, and context menu items to forms and lists, enabling users to perform specific actions easily. UI Actions are essential for customizing the user experience and streamlining workflow interactions.

UI Actions allow administrators to create interactive elements such as:

Buttons(e.g., " Save, " " Approve, " " Reject " )

Form Links(Clickable links that trigger actions on a record)

Context Menu Items(Right-click menu options for records in lists and forms)

They can executeclient-side (via JavaScript)orserver-side (via scripts or GlideRecord API calls).

UI Actions enhance usability by allowing quick execution of tasks without navigating through multiple screens.

Understanding UI Actions in ServiceNow:

Why is Option B (UI Action) Correct?Buttons, form links, and context menu items are all created and managed using UI Actions in ServiceNow.

UI Actions define what happens when a button or menu item is clicked, including executing scripts, navigating to a different page, or performing an operation on a record.

Why Are the Other Options Incorrect?A. Business Rule

Business Rules runautomatically on the server-sidewhen records are inserted, updated, deleted, or queried.

They do not createbuttons, links, or context menu itemson the UI.

C. Client Script

Client Scripts execute on theclient-side (browser)and are used forform validation, field changes, and UI behavior modifications.

They do not create UI elements like buttons or menu items.

D. UI Policy

UI Policies dynamically changeform field behavior(e.g., hiding, showing, making fields mandatory, or read-only).

Theydo not add buttons or context menu items.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – UI Actions Overview

???? ServiceNow UI Actions Documentation

" UI Actions add buttons, links, and context menu items on forms and lists to enhance user interaction with the ServiceNow platform. "

Update Setsin ServiceNow are used tocapture customizations and configurationsmade in an instance, allowing these changes to be moved between instances (e.g., from development to test or production). ServiceNow provides best practices to ensure smooth migration and avoid issues with missing or conflicting updates.

What is an Update Set?

AnUpdate Setis a collection of customizations (e.g., changes to forms, scripts, workflows, business rules) that can be moved from one instance to another.

Ittracks changesin a controlled way, preventing accidental loss of configurations.

Why Avoid Using the Default Update Set?

TheDefault Update Setis automatically used when no other update set is selected.

It captures changesbut should never be used for instance-to-instance migrationsbecause:

Itcannot be exported.

It contains system changes that arenot logically grouped.

It can causeinconsistencies and missing dependencieswhen moving updates.

Instead, administrators shouldcreate a named Update Setfor specific development work.

Understanding Update Sets in ServiceNow:

Why Answer " A " is Correct:✔️ " Avoid using the Default Update Set as an Update Set for moving customizations from instance to instance. "

This follows ServiceNow’sbest practicesfor managing Update Sets.

Using theDefault Update Setcan lead tomissing updates, conflicts, and untracked changes, making migrations unreliable.

Why the Other Answers Are Incorrect:B. " Before moving customizations from instance to instance with Update Sets, ensure that both instances are different versions. "

Incorrectbecause ServiceNowrecommends that instances be on the same versionbefore applying Update Sets.

If instances are ondifferent versions, the Update Set may includeincompatible changes, causing failures.

C. " Use the Baseline Update Set to store the contents of items after they are changed the first time. "

Incorrectbecause there is no such thing as a " Baseline Update Set " in ServiceNow.

ServiceNowdoes not automatically create a backup of original configurations—administrators should manually create an Update Set before making changes.

D. " Once an Update Set is closed as ' Complete, ' change it back to ' In Progress ' until it is applied to another instance. "

Incorrectbecausea completed Update Set should not be reopened.

Once markedComplete, an Update Set isready for export and migration. Reopening it can causedata integrity issuesand confusion in version control.

ServiceNow CSA Study Guide – Update Sets & Configuration Management

ServiceNow Docs: Best Practices for Update Sets(ServiceNow Documentation)

ServiceNow Docs: Moving Customizations with Update Sets

References from the Certified System Administrator (CSA) Documentation:

LDAP (Lightweight Directory Access Protocol) Integrationin ServiceNow enables organizations to connect theircorporate directory services (such as Microsoft Active Directory)with their ServiceNow instance. This integration helps manageuser authentication and data synchronizationefficiently.

There aretwo key aspectsof LDAP Integration in ServiceNow:

Authentication

LDAP is commonly used foruser authentication, allowing users to log in to ServiceNow using theircorporate credentials.

Instead of storing passwords in ServiceNow, authentication requests are sent to theLDAP serverto verify the user ' s identity.

This helps in maintainingcentralized identity managementacross the organization.

Data Population

LDAP can be used toimport user and group informationinto ServiceNow.

This process is known asdata synchronization, where attributes such asusernames, email addresses, department details, roles, and group membershipsare pulled from LDAP and stored in ServiceNow.

This ensures that user information in ServiceNow isalways up-to-datewith the organization ' s directory.

B. Data Formatting–

While ServiceNow does process data from LDAP, " Data Formatting " isnotan aspect of LDAP integration.

Formatting refers to structuring or modifying data but is not a core function of LDAP integration.

C. Authorization–

Authorizationdetermines what a user can doafter authentication, such as assigning roles and permissions.

While ServiceNow can use LDAPgroupsto assign roles, the integration itselffocuses on Authentication and Data Populationrather than defining permissions within ServiceNow.

ServiceNow Docs: LDAP Integration

ServiceNow CSA Official Training Guide (LDAP Integration & User Authentication)

Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that the two main aspects of LDAP Integration in ServiceNow areAuthentication and Data Population.

Abusiness rulein ServiceNow is a server-side script written inJavaScriptthat executes when a record is inserted, updated, deleted, or queried. Business rules allow for automation and enforcement of business logic without requiring manual intervention.

Business rules arenot tied to formsbut instead runon the server-sidewhen a database operation occurs. They can be configured to execute:

Beforea record is saved (Before Business Rule)

Aftera record is saved (After Business Rule)

Asynchronously(Async Business Rule)

Before a query is run on the database(Query Business Rule)

Explanation of the Correct Answer:B. A business rule can be a piece of JavaScript(Correct)

Business rules are written inJavaScript, allowing administrators to define custom logic that executes on the server.

These scripts can modify data, enforce rules, validate fields, or trigger other workflows.

Example JavaScript snippet for a business rule:

if(current.state== ' 3 ' & & current.priority!= ' 1 ' ) {

current.priority= ' 1 ' ;

gs.addInfoMessage( " Priority set to High because state is Resolved. " );

}

This rule ensures that if an incident ' s state is changed toResolved, its priority is automatically set to High.

Why the Other Options Are Incorrect:A. A business rule must run before a database action occurs (Incorrect)

Business rulescan run before a database action occurs, but they can also executeafterorasynchronously.

Business rules have four execution types:

Before– Runs before the record is inserted/updated in the database.

After– Runs after the record is committed to the database.

Async– Runs in the background after the transaction completes.

Query– Runs before data is returned to a user (modifies query results).

C. A business rule must not run before a database action occurs (Incorrect)

This is false because some business rulesdo run beforea database action (e.g., aBefore Business Rulecan validate data before saving).

D. A business rule monitors fields on a form (Incorrect)

Business rulesdo not monitor form fields directly. Instead, they execute based on database operations.

If real-time monitoring of form fields is needed,Client Scripts(not Business Rules) are used for this purpose.

Automaticallyassigning prioritybased on ticket severity.

Preventing updates to certain records if a condition is not met.

Sending email notifications when a record changes.

Modifying data before it is saved to enforce business policies.

Example Use Cases for Business Rules:

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:

InServiceNow, the best practice for managingusers, groups, and rolesis based onrole-based access control (RBAC).

Assign Roles to Groups (Correct)

Instead of assigning roles directly to users, it is abest practice to assign roles to groups.

This ensuresbetter role management, easier administration, and scalability.

Example:

The " IT Support " group has the " itil " role.

All users in this group automatically get theitilrole.

Add Users to Groups (Correct)

Users should be assigned togroupsrather thanroles directly.

Groups inherit roles, so when a user is added to a group, they automatically receivethe appropriate access.

Example:

A new Service Desk agent joins the " Service Desk " group and immediately gets the associated roles (itil,incident_manager, etc.).

A. You should never assign roles to groups(Incorrect)

Incorrect: Assigning roles to groups is therecommended best practice.

Managing roles at thegroup levelmakesaccess control more efficient and scalable.

B. You should assign roles to users(Incorrect)

Incorrect: Assigning roles directly to users isnot a best practicebecause it becomes difficult to manage as the organization grows.

Instead, users should beadded to groupsthat have the necessary roles.

Best Practices for Users, Groups, and Roles:Why Other Options Are Incorrect?

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

References from ServiceNow CSA Documentation:

InServiceNow,Dot-Walkingis a technique used to retrieve information fromreferenced fields across different tables. It allows users to access data stored inrelated records without writing complex scripts.

When a field references another table,dot notation (.)is used totraversethe relationship and retrieve additional information from the referenced table.

It works informs, lists, reports, workflows, business rules, and scripts.

How Dot-Walking Works:Example 1: Retrieving User Information from an Incident RecordLet ' s say we have anIncidenttable where thecaller_idfield references theUser (sys_user) table.

If we need to retrieve the caller’semail address, we use:

caller_id.email

Here’s how it works:

caller_id→ References thesys_usertable

email→ Retrieves theemail field from the sys_user record

Example 2: Retrieving Department Name of an Incident CallerTo get thedepartmentof the caller, we use:

caller_id.department.name

caller_id→ References theUser table

department→ References theDepartment table

name→ Retrieves thedepartment name

(A) Table-Walking – Incorrect

There isno such termas " Table-Walking " in ServiceNow.

The correct term for referencing related fields isDot-Walking.

(B) Sys_ID Pulling – Incorrect

Thesys_idis a unique identifier for each record in ServiceNow, butpulling sys_ids alone does not retrieve referenced field data.

Dot-Walking allows access to fields in related tables, not just the sys_id.

(C) Dot-Walking – Correct

Dot-Walking is the correct techniqueused in ServiceNow to access referenced fields across tables.

It is used in scripting, reporting, workflows, Business Rules, and UI Policies.

(D) Record-Hopping – Incorrect

There isno such featureas " Record-Hopping " in ServiceNow.

The correct method for referencing data in related tables isDot-Walking.

Explanation of Each Option:

Dot-Walking reduces the need for complex queriesand makes scripting easier.

Use it in filters, reports, and workflowsto dynamically retrieve related data.

Limit excessive Dot-Walking in large tablesto avoid performance issues.

Alternative for scripts: If Dot-Walking does not work in advanced scripts, use GlideRecord queries to retrieve referenced records manually.

Additional Notes & Best Practices:

ServiceNow Docs: Understanding Dot-Walking

ServiceNow Community: Best Practices for Dot-Walking

References from Certified System Administrator (CSA) Documentation:

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), their attributes, and relationships. It plays a crucial role in IT Service Management (ITSM), helping organizations track assets, dependencies, and service impacts.

Thefour correct concepts associated with the CMDBare:

The CMDB is structured usingtablesandfieldswithin the ServiceNow database.

Different tables store different types ofConfiguration Items (CIs)such as servers, applications, and network devices.

Example CMDB Tables:

cmdb_ci(Base CMDB Table)

cmdb_ci_server(Stores server-specific CIs)

cmdb_ci_database(Stores database-related CIs)

Each table hasfieldsthat store attributes (e.g.,Serial Number, IP Address, Location).

The CMDB is essentially adatabasethat holds detailed information about IT assets and their relationships.

It enables organizations to maintain an accurate inventory of IT infrastructure.

The database helps withincident management, change management, and asset tracking.

Dependency Viewprovides agraphical representationof how Configuration Items (CIs) are related.

This visualization helps IT teamsunderstand dependencies, impact analysis, and root cause analysis.

Example:

If adatabase servergoes down, theDependency Viewcan show which applications and services will be affected.

The CMDB supports variousIT Service Management (ITSM) processes, such as:

Incident Management(linking incidents to affected CIs)

Change Management(analyzing the impact of changes on CIs)

Problem Management(identifying root causes of recurring issues)

The CMDB ensures that these processes operate with accurate and updated asset data.

1. Tables and Fields (Correct)2. A Database (Correct)3. The Dependency View (Correct)4. Service Processes (Correct)

Why the Incorrect Option is Wrong:B. User Permissions (Incorrect)

Whileuser permissions(such as roles and access controls) exist in ServiceNow, they arenot a fundamental concept of the CMDB itself.

Permissions (likecmdb_readoradmin) controlwho can access and modify the CMDB, but they are notcore CMDB components.

AnIT administratorwants to checkwhich business services depend on a specific database serverbefore performing maintenance.

Using theCMDB Dependency View, they see that the database server is linked to anemail serviceand acustomer portal.

This insight helps them plan achange requestto notify impacted users before the server is taken offline.

Example Use Case:

InServiceNow, anImport Set Tableis atemporary staging areawhere raw data is storedbefore it is transformed and moved into a target table. It is primarily used indata import processesto ensure data integrity and allow transformation before committing data to production tables.

Stores incoming data from external sources(e.g., CSV files, Excel files, APIs, LDAP, etc.).

Acts as a temporary staging areabefore records are mapped and transformed into atarget table(e.g.,incident,cmdb_ci,problem).

Allows validation and error handlingbefore final data migration.

Uses Transform Mapsto determine how fields in the import set relate to fields in the target table.

Key Functions of an Import Set Table:

Data is importedinto anImport Set Tablefrom an external source.

TheImport Set Table temporarily stores the datawithout affecting existing records.

ATransform Mapis applied to move and modify the data before inserting it into the correct table.

Once transformation is complete, the data is transferred to thetarget table, and the Import Set Table can be cleared.

Example Workflow of an Import Set:

(A) A table where data will be placed, post-transformation – Incorrect

Thetarget table(e.g.,incident,cmdb_ci,problem) holds the dataaftertransformation.

TheImport Set Table is only a temporary staging areabefore transformation occurs.

(B) A table that determines relationships – Incorrect

Relationship tables(e.g.,cmdb_rel_ci) definedependencies between recordsbut are not used for data import.

Import Set Tables do not determine relationships between records.

(C) A staging area for imported records – Correct

Import Set Tables temporarily store incoming recordsbefore processing.

The data is transformed and mappedbefore being inserted into the final target table.

This ensuresdata integrity and consistency.

(D) A repository for Update Set information – Incorrect

Update Sets (sys_update_set) store changes to configurations, such as scripts, workflows, and UI policies.

Import Set Tables are used for data imports, not Update Sets.

Explanation of Each Option:

Always review data in the Import Set Table before applying transformationsto avoid incorrect data entry.

Use Transform Mapsto define field mappings between Import Set Tables and target tables.

Monitor Import Logs(sys_import_set_run) for errors or incomplete data.

Delete old Import Set dataperiodically to improve performance and avoid unnecessary storage usage.

Additional Notes & Best Practices:

ServiceNow Docs: Import Set Overview

ServiceNow Community: Best Practices for Import Set Management

References from Certified System Administrator (CSA) Documentation:

InServiceNow Import Sets,coalescingis the process ofmatching existing recordsto avoid duplicate entries when importing data.Conditional coalesceis the only method that allows using ascriptto determine if records should be updated or inserted.

Single-field Coalesce (Incorrect)

Usesone fieldto determine if a record exists.

If a match is found, the record isupdated; otherwise, a new record is created.

Example: Usingemailas a coalesce field when importing user data.

Multiple-field Coalesce (Incorrect)

Usesmultiple fieldsto find a match.

If all specified fields match, the record isupdated. Otherwise, a new record is created.

Example: MatchingFirst Name + Last Name + Email.

No Coalesce (Incorrect)

Every import creates anew record, regardless of whether a similar record exists.

Conditional Coalesce (Correct)

Allows using ascript to define custom logicfor identifying records to update.

This isthe only coalescing method that supports scripting.

Example:

A script can check if eitheremailoremployee IDexists, andif neither exist, create a new record.

Types of Coalescing in Import Sets:

Understanding Coalesce in Import Sets

Import Set Coalescing

Conditional Coalesce Scripting

Using Conditional Coalesce

References from ServiceNow CSA Documentation:

In ServiceNow,record numbers are automatically generated and incrementedby the system. Each record created in a table receives a unique identifier based on a predefinednumber format.

Each table that extends the " task " or other core tables has a default numbering format.

Numbering is automatic, meaning users donothave to manually increment numbers.

The numbering format follows aprefix + incremental number(e.g., INC0001001 for incidents, CHG0002001 for changes).

The system ensuresunique sequential numberingwithin each table.

How Record Numbering Works:Configuring Auto-Numbering:Admins can customize numbering formats by modifying the " Number Maintenance " module:

Navigate toSystem Definition → Number Maintenance.

Select a table and configure theprefix, length, and starting number.

Changes apply automatically to new records created in that table.

Record numbersdo not require manual updates; the system handles it automatically.

Users can changeformat settings, butcannot manually increment individual record numbers.

ServiceNow prevents duplicate numbers to maintain data integrity.

Why " False " is the Correct Answer:

Manual incrementing isnotrequired or possible for individual records.

The platform automatically assigns the next sequential number to each record.

Why " True " is Incorrect:

ServiceNow Documentation:Number Maintenance

CSA Exam Guide:Coversautomatic record numbering and Number Maintenance settings.

Reference from CSA Documentation:Thus, the correct answer is:

B. False

InServiceNow, theService Catalogis the primary module where users canorder services and productsoffered by various departments. The Service Catalog provides acentralized portalfor users to browse and requestIT, HR, Facilities, Finance, and other departmental servicesin a structured and automated way.

TheService Catalogis aself-service interfacewhere users can request predefined services, products, and resources.

It acts as adigital storefrontfor an organization ' s internal and external services.

Each service request follows aworkflowthat may includeapprovals, task assignments, and fulfillment processes.

Service Offerings:

Users can requesthardware (laptops, mobile devices, monitors), software, access permissions, or HR-related services (e.g., PTO requests, onboarding).

Structured Request Fulfillment:

Each request follows aworkflowwith assigned tasks to the appropriate fulfillment teams.

Example: A request for anew laptopis routed toIT Supportfor approval and processing.

Automation and Approvals:

Some catalog items requiremanagerial or departmental approvalsbefore fulfillment.

Example: Requesting access torestricted applicationsmight need approval from anIT admin.

Integration with Incident, Change, and Asset Management:

The Service Catalog can triggerchange requests, incidents, and asset updatesas part of the fulfillment process.

Access Through the Self-Service Portal:

Users can access theService Catalogvia theSelf-Service Portalfor quick and easy navigation.

What is the Service Catalog?Key Features of the Service Catalog:

Why Option A (Service Catalog) is Correct?TheService Catalogis the correct place toorder services and productsoffered by different departments in ServiceNow.

It provides astructured and automatedway to request, approve, and fulfill service requests.

Why Other Options Are Incorrect?B. Self-Service– TheSelf-Service Portalprovides access to the Service Catalog but is not where services are ordered directly.

C. Service Department– No such module exists in ServiceNow. Departments use theService Catalogto provide services.

D. Customer Service– TheCustomer Service Management (CSM)module is forexternal customers, not internal service requests.

ServiceNow Docs – Service Catalog

ServiceNow Learning – Self-Service & Service Catalog Best Practices

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Create Incident, Password Reset, and Report Outageare examples ofService Catalog itemsthat guide users through submitting requests. These services are commonly implemented usingRecord Producers.

What is a Record Producer?ARecord Produceris a special type ofcatalog itemthat:

Creates recordsin a table (e.g., Incident, Change, or Request).

Provides auser-friendly interfacein the Service Catalog.

Maps user input fields to corresponding fieldsin the target table.

For example:

" Create Incident " uses a Record Producer to create a record in theIncident [incident]table.

" Password Reset " can create a record in acustom password reset tableor trigger a workflow.

" Report Outage " may create a record in theProblem or Incident table.

Why is Option A Correct? " They direct the user to a record producer. "

These catalog servicesdo not create Service Requests (REQs) like normal catalog items.

Instead, theyuse Record Producers to generate records directly in specific tables (e.g., Incident, Change, Problem).

This allowscustom form fields, pre-filled values, and direct mappingto the target table.

Why Are the Other Options Incorrect?B. " They direct the user to a catalog property. "

Incorrect:Catalog properties aresystem settingsthat control Service Catalog behavior, not user-facing forms.

Example:Catalog properties controlcart behavior, request approval rules, etc.

C. " They direct the user to a catalog UI policy. "

Incorrect:UI Policies controlfield behavior (e.g., hiding, showing, making fields mandatory) on the formbut do not determine how the request is processed.

D. " They direct the user to a catalog client script. "

Incorrect:Catalog Client Scripts controlform logic (such as auto-filling fields) but do not create records directly.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Record Producers in the Service Catalog

???? ServiceNow Record Producers Documentation

" A Record Producer is acatalog itemthat lets users create records in a table instead of generating a standard request. "

Conclusion:The correct answer isA. They direct the user to a record producer.

???? Record Producers are widely used in ServiceNow ' s Service Catalog to simplify and streamline user requests, ensuring data is properly captured and processed.

ARecord ProducerinServiceNowis atype of Catalog Itemthat allows users to create records intables(such as Incidents, Change Requests, or HR Cases) from theService Catalog. It provides asimplified and user-friendly interfacefor users to submit structured data without needing direct access to the actual form or database tables.

Key Features of a Record Producer:✔Creates task-based recordsin the appropriate table (e.g.,incident,sc_task,problem).

✔Uses a simplified forminstead of the standard form view of a record.

✔Can trigger workflows and business ruleswhen submitted.

✔Maps user inputs to table fieldsviaVariable Mappings.

An employee wants toreport a broken laptopbut does not need to see the fullIncident form.

The IT team creates aRecord Producernamed " Report an IT Issue " in theService Catalog.

The Record Producercollects user input(e.g., issue description, urgency, contact information).

Upon submission, itcreates an Incident record (incidenttable)in ServiceNow.

Example Use Case:

Why the Correct Answer is D:D. A Record Producer is a type of a Catalog Item that allows users to create task-based records from the Service Catalog(Correct)

This is the most accurate description of aRecord Producer.

It allows users tocreate recordsin a specifiedtask table (Incident, Change, Request, etc.)through theService Catalog.

Why the Other Options Are Incorrect:A. A Record Producer is a type of Catalog Item that is used for Requests, not Services (Incorrect)

Record Producers are not limited to Requests.

They can create various types of records, including Incidents, Change Requests, and HR Cases.

B. A Record Producer creates user records (Incorrect)

A Record Producerdoes not create user records(users are managed in thesys_usertable).

Instead, itcreates task-based recordsin other tables likeincidentorsc_task.

C. A Record Producer is a type of Catalog Item that provides easy ordering by bundling requests (Incorrect)

Order Guides, not Record Producers, handlebundling multiple Catalog Items into a single request.

ARecord Producer creates a single recordin a defined table.

Comparison: Record Producer vs. Other Catalog ItemsFeature

Record Producer

Standard Catalog Item

Order Guide

Creates a record in a ServiceNow table

Yes

No

No

Used to order physical/digital goods

No

Yes

Yes

Can bundle multiple requests

No

No

Yes

Uses a form-based submission

Yes

Yes

Yes

Theconversational bot platforminServiceNowthat helps usersobtain information, make decisions, and perform common tasksis calledVirtual Agent.

What is Virtual Agent?Virtual Agent is achatbot frameworkin ServiceNow that allows users to interact with the system usingnatural language processing (NLP). It automates responses, guides users through processes, and integrates with ServiceNow workflows to resolve requests efficiently.

Conversational AI & Automation

Uses AI andNatural Language Understanding (NLU)to interpret user input and provide relevant responses.

Predefined Topics & Custom Topics

Comes with pre-built conversation topics (e.g., resetting passwords, requesting IT help) and allows organizations to create custom topics.

Multi-Channel Support

Works with platforms likeMicrosoft Teams, Slack, ServiceNow Chat, and web portals.

Self-Service Capabilities

Enables users to resolve issueswithoutcontacting the Service Desk, improving efficiency.

Integration with ServiceNow Workflows

Can trigger workflows tocreate incidents, update records, retrieve knowledge articles, or complete approvals.

A. Answer Agent

Incorrect: There is no feature named " Answer Agent " in ServiceNow.

B. Live Feed

Incorrect:Live Feedis a social collaboration tool in ServiceNow that allows users to post updates and interact with others, similar to a message board. It does not provide AI-based conversational assistance.

D. Connect Chat

Incorrect:Connect Chatis ServiceNow’s real-timecollaborative chat system, used for direct communication between users and support agents, but it isnot an AI-driven Virtual Agent.

Key Features of Virtual Agent:Why Other Options Are Incorrect?

ServiceNow Product Documentation - Virtual Agent

Virtual Agent Overview

Setting Up Virtual Agent

ServiceNow Conversational Interfaces

Virtual Agent vs. Connect Chat

References from ServiceNow CSA Documentation:

TheSystem Dictionaryin ServiceNow stores and maintains themetadataabout tables and fields in the platform. It containsdefinitions for each table and column, including field data types, default values, and attributes.

Storestable and field definitions, including:

Column names

Data types(e.g., String, Integer, Reference)

Attributes(e.g., unique, read-only, required)

Default values

Ensuresdata integrityby defining the structure of database tables.

Used by administrators tomodify or extend existing tables.

Allows the creation ofcustom fieldsin tables.

Key Features of the System Dictionary (sys_dictionaryTable):

Navigate to:System Definition → Dictionary

Search for a table or fieldto view its metadata.

Modify attributes(if needed) to customize table behavior.

How to Access the System Dictionary:

A. The human-readable labels and language settings– Incorrect.

Human-readable labelsare stored in thesys_documentationtable, not the System Dictionary.

C. The information on how tables relate to each other– Incorrect.

Table relationshipsare stored in theSchema Map, not the System Dictionary.

D. The language dictionary used for spell checking– Incorrect.

Spell checking and translationsare managed insystem localization settings, not the System Dictionary.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → System Dictionary (sys_dictionary)

ServiceNow CSA Study Guide → Understanding Tables and Fields

ServiceNow Developer Documentation → Dictionary and Table Structure

References from Certified System Administrator (CSA) Documentation:Would you like me to verify another question?????

Aformatterin ServiceNow is aUI elementthat is added to a form to display useful information that isnot stored as a field in the database record.

Itenhances the form UIby providing additional context or tools for users.

Formattersdo not store datain the underlying database table.

They aredrag-and-drop elementsthat can be added to forms using theForm Layout editor.

Activity Formatter– Displays the history of updates, comments, and work notes.

Process Flow Formatter– Shows a graphical representation of the record ' s workflow.

Parent Breadcrumb Formatter– Displays the hierarchy of parent-child relationships.

CI Relations Formatter– Shows Configuration Item (CI) relationships in CMDB.

User Approval Formatter– Displays approval status and history.

Key Characteristics of a Formatter:Common Examples of Formatters in ServiceNow:

Why is Option B Correct?A formatter is a form element used to display information that is not a field in the record.

It provides additionalvisual or functional elementson a form without altering stored data.

Why Are the Other Options Incorrect?A. " A formatter allows you to configure applications on your instance. "

Incorrect:Formattersdo not configure applications; they only modify the form layout for better user experience.

Correct Alternative:Application configuration is done viaSystem ApplicationsorApplication Navigator.

C. " A formatter allows you to populate fields automatically. "

Incorrect:Formattersdo not fill or modify fields.

Correct Alternative:Business Rules, Client Scripts, and UI Policieshandle field population.

D. " A formatter is a set of conditions applied to a table to help find and work with data. "

Incorrect:Thecorrect term for this is a Filter or Condition Builder, not a Formatter.

Correct Alternative:Filters are used inList Views, Reports, and Business Rules.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Form Layout and Formatters

???? ServiceNow Formatters Documentation

" A formatter is aform element that displays information that is not a field in the recordbut enhances the user experience. "

In ServiceNow,Record Producersallow users to create records in tables through a user-friendly interface in the Service Catalog. Since the goal is to enableonly first-line workersto order the T-shirt, we need to control access based on their role.

ARecord Producerin the Service Catalog is the best way to gather user input (size, color, etc.) and create a new order record in the system.

The " Available For " list allows administrators to restrict access to specificusers or roles.

TheFirst Line [sn_first_line]role is explicitly designed to includeonly first-line workerswhile excluding managers.

Why is Option A Correct?Why Are the Other Options Incorrect?B. Create Catalog Item and use the Not Available list to specify the Manager Group

Catalog Itemsare valid for this use case but using the " Not Available For " list is a less effective approach.

If newmanager rolesorgroupsare added in the future, this method won’t automatically exclude them.

It’s better toexplicitly definewho can access the item rather than relying on exclusions.

C. Create Catalog Item and use the Available For list to specify ITIL [itil] role

TheITIL roleis typically assigned to Service Desk personnel and IT staff,not first-line workers.

This approach would allowmany unintended usersto request the T-shirt.

D. Create Order Guide and use the User Criteria list to specify First Line [sn_first_line] role

Order Guidesare used to bundle multiple catalog items and guide users through a complex ordering process.

Since this scenario only involves asingle item (T-shirt request),using an Order Guide is unnecessary.

ServiceNow Service Catalog Management - Record Producers

ServiceNow User Criteria and Access Control Best Practices

ServiceNow CSA Guide - Managing Roles and Access Restrictions

References to Official Certified System Administrator (CSA) Documentation:

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.

InServiceNow,System Import Setsis the primary application used toimport and transform datafrom external sources into the platform. It provides a structured way toload data into tableswhile allowingdata transformation and mappingbefore final insertion.

Data Loading from External Sources:

Supports imports fromCSV, Excel, XML, JSON, and JDBC databases.

Allows data fromexternal systemsto be brought into ServiceNow.

Staging Area for Data Processing:

Imported data first enters atemporary staging table(Import Set Table).

Data can then betransformedbefore being committed to the target table.

Data Mapping and Transformation:

UsesTransform Mapsto map fields from theImport Set Tableto theTarget Table.

Supportsautomatic field mappingandscripted transformations.

Data Cleansing and Validation:

Duplicate records can bedetected and removed.

Invalid or missing data can becorrected before insertion.

Navigate to System Import Sets(All → System Import Sets → Load Data).

Upload the data file(CSV, XML, JSON, etc.).

Create a Transform Mapto define how data is mapped to the target table.

Run the transformationto move data from the Import Set Table to the final table.

Verify the datain the target table.

A company importsemployee recordsfrom an externalHR system (CSV file).

TheSystem Import Setsmodule loads this data into astaging table.

ATransform Mapmoves the data into theUser [sys_user]table.

Key Features of System Import Sets:Steps to Load Data Using Import Sets:Example Use Case:

Why Option C (System Import Sets) is Correct?System Import Sets is the primary tool for loading data into ServiceNow from external sources.

Why Other Options Are Incorrect?A. Service Level Management→ Incorrect

Service Level Management (SLM)is used to trackService Level Agreements (SLAs), not to import data.

B. Configuration→ Incorrect

Configuration Management (CMDB)helps trackconfiguration items (CIs)but does not handle data imports.

D. System Update Sets→ Incorrect

Update Setsare used tomove configurations and customizationsbetween instances,not to import data.

ServiceNow Docs – Importing Data with System Import

ServiceNow Learning – Data Import & Transformation Best Practices

ServiceNow Developer Portal – Using Import Sets Efficiently

References from Certified System Administrator (CSA) Documentation:

If a user reports that theycannot see certain modulesin theApplication Navigator, the best way to troubleshoot is toimpersonate the user. Impersonation allows an administrator to see exactly what the user seeswithout needing their password.

Click on your profile icon (top-right corner).

SelectImpersonate User.

Search for and select theuser’s name.

The instance will reload, and you will see the UI as the user experiences it.

Navigate to theApplication Navigatorand check for missing modules.

Once done, clickStop Impersonation.

Ensures security(no need to reset or look up passwords).

Speeds up troubleshootingby allowing admins to replicate user issues.

Helps verify role-based access permissions.

Steps to Impersonate a User in ServiceNow:Why is Impersonation Useful?

Incorrect Answer Choices Explanation:A. Look up their password, so you can login with their account

This is asecurity violationand not an acceptable practice.

B. Initiate a Connect Chat session

Chatting with the user can help gather information, but it does not allow you to see what they see.

C. Install the Bomgar plug-in

Bomgaris a remote support tool, but impersonation is thebuilt-inand recommended method for troubleshooting in ServiceNow.

E. Launch a NowChat window

NowChat is used forcustomer support and collaboration, not for verifying module visibility.

Impersonate Users in ServiceNow

User Roles and Permissions

Official CSA Documentation Reference:

When creating acustom table in ServiceNow, the platform automatically assigns a table name prefixed with " u_ " to differentiatecustomtables fromout-of-the-box (OOB) tables.

The default prefix " u_ " is applied to allcustom global tables.

The table name follows the format: " u_ " + [custom name].

Example:

If you create a table named " abc " , the system assigns it the table name:u_abc.

All custom tables created by usersautomatically receive the " u_ " prefix.

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

Naming Convention for Custom Tables:Why " C. u_abc " is Correct?

A. snc_abc – Incorrect

" snc_ " is not used for custom tables; it is reserved forinternal ServiceNow functionality.

B. abc – Incorrect

Custom tablesdo not use raw names; they always include a prefix (u_).

D. sys_abc – Incorrect

" sys_ " is reserved forsystem tables(e.g.,sys_user,sys_db_object).

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

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

Creating Business

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

In ServiceNow,Import Setsallow administrators toimport and transform datafrom external sources into ServiceNow tables. The platform supports multiple file formats for importing data, includingXML, CSV, and Excel.

XML (Extensible Markup Language)

Used for structured data exchange between systems.

ServiceNow canimport XML filescontaining records formatted according to its schema.

CSV (Comma-Separated Values)

One of the most common formats for bulk data imports.

ServiceNow can processCSV filesand map them to target tables.

Excel (XLS/XLSX)

ServiceNow allows direct imports fromMicrosoft Excel spreadsheets.

Users can upload Excel files via the Import Set UI.

Supported Data Formats for Import Sets:

Import Data:The user uploads a supported file (XML, CSV, or Excel) into an Import Set table.

Mapping:The imported data is mapped to target tables using aTransform Map.

Transformation & Processing:Data is transformed, validated, and inserted into the correct destination tables.

How Import Sets Work in ServiceNow:

A. CSS, SOAP, and Excel→CSS is a styling language, and SOAP is a protocol, not a data format.

C. SOAP, REST, and XML→SOAP and REST areweb service protocols, not file formats used for import sets. XML is valid but alone is insufficient.

D. XML, SOAP, and CSS→SOAP and CSS are incorrect as they are not standard import file formats.

Why Other Options Are Incorrect:

ServiceNow Documentation:Importing Data into ServiceNow

CSA Exam Guide:Coverssupported data formats for Import Sets (XML, CSV, and Excel).

ServiceNow provides multiplesecurity-related modulesthat aSystem Administratorfrequently uses to manage access, authentication, and overall system security.

Why These Options Are Correct?A. System Properties > Security

This module allowsadministrators to configure general security settings, including password policies, session timeout, and encryption settings.

It helps manage security parameters at a system-wide level.

E. System Security > Access Control (ACL)

Access Control Lists (ACLs)define what data users can access, modify, and delete within the instance.

ACLs operate at thetable, field, and record levels, ensuring proper role-based access control (RBAC).

This is one of themost commonly usedsecurity modules by admins.

G. System Security > High Security Settings

High Security Settings (previously known as Security Hardening)enforce strict security controls, such as requiring multi-factor authentication (MFA) and enforcing strict password policies.

It is often used for compliance withsecurity regulationslike HIPAA, GDPR, and ISO 27001.

Why the Other Options Are Incorrect?B. Utilities > Migrate Security

This optiondoes not existin ServiceNow. There is no " Migrate Security " under Utilities.

C. System Security > Security

There is no " System Security > Security " module in ServiceNow. The correct structure isSystem Security > Access ControlorSystem Properties > Security.

D. Self-Service > My Access

This is aself-service modulefor end users to request and review their access.

It isnota tool thatSystem Administratorsuse to manage security settings.

F. Password Management > Security Questions

This is used to configuresecurity questions for password recoverybut isnot a core security modulethat admins frequently use.

General Security Settings in ServiceNow

ServiceNow Access Control (ACL) Best Practices

ServiceNow System Security and Role Management

References to Official Certified System Administrator (CSA) Documentation:

In ServiceNow, the " Service Desk > My Groups Work " module is designed to display tasks assigned to a groupbut not yet assigned to an individual user.This means that even if an IT manager oversees theNetworkandHardwareassignment groups, they will not see any tasks in this listif all tasks have already been assigned to specific individualswithin the group.

Let’s break down whyoption Ais the correct answer and why the other options are incorrect:

The " My Groups Work " list only shows tasks that are assigned to thegroupbut have not been assigned to a specificindividualwithin the group.

If all tasks are assigned to specificteam members, then the manager will not see any tasks in this list.

The IT manager can verify this by navigating to theTask List(e.g., Incidents, Changes, or Requests) and filtering by theNetworkandHardwareassignment groups.

Explanation for Correct Answer (A):

Theitil roleallows users toview, create, update, and resolve incidents, changes, problems, and other ITSM tasks.

However, not having this role wouldrestrict accessto various ITSM functionalities, but itdoes notimpact whether tasks appear inMy Groups Work.

If the manager lacks theitilrole, they might have trouble accessing or modifying tasks, but this wouldn ' t explain why they don’t see anything in the list.

TheService Desk groupis a separate entity in ServiceNow, typically associated with incident handling and user support.

TheMy Groups Workmodule isnot restricted to the Service Desk group—it displays work assigned toany groupthe user belongs to.

Since the manager is responsible for theNetwork and Hardwaregroups, being part of theService Deskgroup is irrelevant.

If the manager wasnot a memberof these groups, they wouldn ' t seeany group-related tasksat all.

However, the question states that the manager isresponsible for these groups, so it’s reasonable to assume they are either a member or at least agroup managerwith visibility.

Even if they were just a manager and not an officialgroup member, they would still be able to see the tasks assigned to the groups.

TheAssignment Group managerfield is an informational field that indicates who manages a group.

This fielddoes not controlwhat is displayed in theMy Groups Workmodule.

Even if this field were empty, it wouldn’t prevent a manager (who is a group member) from seeing unassigned tasks.

Explanation for Incorrect Answers:(B) The manager does not have the itil role.(C) The manager is not a member of the Service Desk group.(D) The manager is not a member of the Network and Hardware groups.(E) The Assignment Group manager field is empty.

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

References to Official Certified System Administrator (CSA) Documentation:

In ServiceNow,Data Policiesare rules thatenforce data consistencyby ensuring that specific fields meet certain conditionsbefore being saved to the database. They apply toall data operations, including form submissions, web services, and data imports.

Work at the server-side level, ensuring data integrity before it is stored.

Canmake fields mandatoryorread-onlyacross different interfaces (e.g., forms, API calls, imports).

UnlikeUI Policies, which apply only toforms, Data Policies apply to alldata transactions, including integrations and imports.

Help maintaindata quality and consistencyacross the system.

Making a Field Mandatory:

Ensure that the " Short Description " field is always filled before saving anIncident.

Enforcing a Read-Only Field:

Prevent users from modifying the " Created Date " field.

Standardizing Data on Import:

When importing employee data, ensure that the " Department " field is always set and not left blank.

Data Policies ensuredata accuracy and integritybefore it is stored.

They apply toforms, web services, import sets, and background processes.

They help organizationsmaintain standardized and structured data.

A. Data Policies enforce security – Incorrect

Security is enforced usingAccess Control Lists (ACLs), not Data Policies.

B. Data Policies standardize data in Update Sets – Incorrect

Update Sets trackconfiguration changes, not data validation.

D. Data Policies apply to lists to standard data – Incorrect

Data Policies do not specifically target lists; they enforce rules at thedatabase level.

ServiceNow Docs: Data Policies Overview

ServiceNow CSA Study Guide – Data Policies vs. UI Policies

ServiceNow Product Documentation: Enforcing Data Consistency with Data Policies

Key Features of Data Policies:Example Use Cases of Data Policies:Why " C. Data Policies enforce data consistency " is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

When creating acustom table in ServiceNow, the platform automatically assigns a table name prefixed with " u_ " to differentiatecustomtables fromout-of-the-box (OOB) tables.

The default prefix " u_ " is applied to allcustom global tables.

The table name follows the format: " u_ " + [custom name].

Example:

If you create a table named " abc " , the system assigns it the table name:u_abc.

All custom tables created by usersautomatically receive the " u_ " prefix.

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

Naming Convention for Custom Tables:Why " C. u_abc " is Correct?

A. snc_abc – Incorrect

" snc_ " is not used for custom tables; it is reserved forinternal ServiceNow functionality.

B. abc – Incorrect

Custom tablesdo not use raw names; they always include a prefix (u_).

D. sys_abc – Incorrect

" sys_ " is reserved forsystem tables(e.g.,sys_user,sys_db_object).

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

InServiceNow IntegrationHub, third-party API integrations within aFlow Designerflow are known asspokes. Aspokeis a scoped application containingFlow Designer actions and subflowsthat allow the flow to interact with external systems or ServiceNow applications.

Spokes in IntegrationHub

Aspokeis a collection ofpredefinedandcustomactions, subflows, and data streamsused to integrate with external systems.

Spokes provide ano-code/low-codeapproach to integrating third-party applications.

Examples ofprebuilt spokesavailable in ServiceNow include:

Slack Spoke(for Slack API integrations)

Microsoft Teams Spoke(for Teams integration)

Jira Spoke(for integrating with Atlassian Jira)

How Spokes Work

When a flow needs to interact with an external system (e.g., sending data to Jira or retrieving information from Slack), itcalls an action from a spoke.

Each spoke containsmultiple predefined actionsthat execute API requests or perform tasks like creating records, updating data, or fetching information.

Comparison with Other Options

A. an action→ Incorrect

Actions are individual steps in a flow, not the complete integration package. Actions exist inside spokes.

C. a connection→ Incorrect

Aconnectionis a configuration that stores authentication details (e.g., API keys, OAuth tokens) used by a spoke.

D. an integration step→ Incorrect

No such term as “integration step” exists in ServiceNow IntegrationHub.

ServiceNow Docs - IntegrationHub

ServiceNow Docs - Spokes in Flow

Key Concepts Related to IntegrationHub and SpokesOfficial References from the Certified System Administrator (CSA) Documentation:

In ServiceNow, theEvent Registryis a module thatstores and defines all system eventsthat can be triggered within the platform. Events in ServiceNow are used to trigger business rules, notifications, workflows, and integrations based on specific system activities.

TheEvent Registry [sysevent_register]table containspredefined and custom event definitions.

It allowsdevelopers and administratorsto definenew custom events.

Events can betriggered manually (via scripts) or automaticallybased on system actions.

Events arenot tied to a specific timeframebut are available for use whenever triggered.

Triggering a Notification

When an incident is assigned, an event such as " incident.assigned " is triggered, which can send an email notification to the assigned user.

Initiating an Automated Workflow

When a new user is onboarded, an event like " user.onboarded " can trigger a workflow to create necessary accounts and permissions.

Logging Custom Events for Reporting

Custom events like " asset.verified " can be used to track when an asset verification process is completed.

Key Features of the Event Registry:Example Use Cases of the Event Registry:

TheEvent Registryisnot a log of completed eventsbut arepository of event definitionsthat can be triggered.

It defines bothdefault and custom eventsthat can be used across different system processes.

It is used forevent-driven automationin ServiceNow.

Why " C. The Event Registry is a module that provides Event definitions " is the Correct Answer?

A. The Event Registry lists all Events that have successfully completed within a 24-hour period – Incorrect

This describes theEvent Log [sysevent]table, not the Event Registry.

B. The Event Registry is a list of all Events that originate through an integration – Incorrect

TheEvent Registryis not specific to integrations; it applies to all events in the system.

D. The Event Registry is a list of all Events that have successfully completed after being Invoked by a script – Incorrect

Events triggered by scripts are logged in theEvent Log, not theEvent Registry.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding the Event Registry

ServiceNow CSA Study Guide – Event Management

ServiceNow Product Documentation: Creating and Managing Events

References from Certified System Administrator (CSA) Documentation:

In ServiceNow, aroleis arecord stored in the sys_user_role tablethat defines a set ofpermissionsfor users. Roles determine what users cansee and dowithin the platform by granting access to applications, modules, and specific functionalities.

Stored in thesys_user_roletable.

Assignpermissionsto users and groups.

Define access toapplications, modules, and records.

Can beinheritedby users throughgroup membership.

Used inAccess Control Rules (ACLs)to restrict or allow access to records.

Key Features of Roles in ServiceNow:Common Roles in ServiceNow:Role Name

Description

admin

Full system access, including configuration and security settings.

itil

Allows access to IT Service Management (ITSM) modules like Incident, Change, and Problem.

catalog_admin

Manages the Service Catalog.

knowledge_manager

Manages the Knowledge Base.

Roles arestored as recordsin thesys_user_roletable.

Each role grantsspecific permissionsto users.

Users can have multiple roles assigned to them.

B. A role is one record in the Role [user_sys_role] table – Incorrect

The correct table name issys_user_role, not " user_sys_role " .

C. A role is a persona used in Live Feed Chat – Incorrect

Live Feed is a collaboration tool, butroles are not personas for chat.

D. A role is a set of modules for a particular application – Incorrect

Rolesgrant accessto modules, but they arenotthe modules themselves.

ServiceNow Docs: User Roles & Permissions

ServiceNow CSA Study Guide – Role-Based Access Control

ServiceNow Product Documentation: sys_user_role Table

Why " A. A role is one record in the Role [sys_user_role] table " is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

Flow Designeris ano-code/low-codeautomation tool in ServiceNow that enables users toorchestrate business processes across different serviceswith minimal technical knowledge. It allowsnon-technical usersto build complex workflows using drag-and-drop functionality.

No-Code/Low-Code Automation

Users candesign, test, and managebusiness processeswithout coding skills.

Actions can be executedsequentially or conditionallybased on logic.

Integration with ServiceNow Applications

Flow Designer works withIntegrationHub, allowing ServiceNow to interact with external systems like Slack, Microsoft Teams, and Jira.

Trigger-Based Execution

Flows can be triggeredby conditions, schedules, or user actions.

Prebuilt Spokes & Actions

ServiceNow providesprebuilt " Spokes " with reusable actions that simplify workflow automation.

A. Flow Manager(Incorrect)

No such module called " Flow Manager " exists in ServiceNow.

C. Flow Editor(Incorrect)

The term " Flow Editor " is not used in ServiceNow; the correct name isFlow Designer.

D. Workflow Editor(Incorrect)

Workflow Editoris part of the olderLegacy Workflow Engine, which requires scripting and is not recommended for no-code automation.

E. Workflow Designer(Incorrect)

This is not an official ServiceNow tool; Flow Designer has replaced older workflow tools for modern automation needs.

Flow Designer

Building Flows in Flow

Key Features of Flow Designer:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

InServiceNow, afilter conditionis used to definesearch criteriafor records in a table. A filter consists ofthree primary components:

Field→ The database field to be evaluated (e.g.,priority,state,assigned_to).

Operator→ Specifies how the field should be compared to a value (e.g.,is,contains,greater than).

Value→ The expected data in the field (e.g.,High,Resolved,John Doe).

Filter Condition:PriorityisHigh

Field:Priority

Operator:is

Value:High

Another Example:Stateis notResolved

Field:State

Operator:is not

Value:Resolved

Example of a Filter Condition:Why Option A is Correct?Field, Operator, and Valueare the correct components used to create a filter condition.

Why Other Options Are Incorrect?B. Condition, Operator, and Value→ Incorrect because " Condition " is a result of aField + Operator + Value, not a separate component.

C. Field, Condition, and Value→ Incorrect because " Condition " is not a direct component.

D. Variable, Field, and Value→ Incorrect becausevariablesare used in forms, not in filter conditions.

ServiceNow Docs – Creating and Applying

ServiceNow Learning – Query Builder and Conditions

ServiceNow Best Practices – Using Filters in Lists and Reports

References from Certified System Administrator (CSA) Documentation:

In ServiceNow, theApplication Navigatorallows users to browse and accessApplications and Modules. Toexpand or collapsethe Application Navigator, users interact with theApplication Menu icon (☰), commonly known as the " Hamburger " menu.

Locate thethree-line " Hamburger " icon (☰)at the top-left of theApplication Navigator.

Double-clickorsingle-clickto expand/collapse the list of applications and modules.

A. Star(Incorrect)

TheStar icon (⭐)representsFavorites, allowing users to mark frequently used modules for quick access.

B. Clock(Incorrect)

TheClock icon (⏱️)is forRecently Viewed Items, showing the user ' s most recent navigations.

D. Funnel(Incorrect)

TheFunnel icon (???? )is afilterused to refine search results or application lists, not to expand/collapse the navigator.

Navigating the Application

How to Expand/Collapse Applications & Modules:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

When importing data into ServiceNow, thefirst stepin theImport Set processisloading the datainto a temporaryImport Set table. This is done using theLoad Datamodule.

Load Data (First Step)

This step imports raw data from a source file (e.g., CSV, Excel, XML) into anImport Set tablein ServiceNow.

No transformation occurs at this stage; it simply moves data into a temporary staging table.

Create Transform Map & Apply Transform

After loading, aTransform Mapis used to map fields from the Import Set table to the target table (e.g., Incident, CMDB, Users).

TheTransform Datastep converts and inserts data into the final table.

Coalesce to Avoid Duplicates

Coalescing is an optional step that determines whether existing records should be updated or if new records should be created.

A. Coalesce Data(Incorrect)

Coalescingis used during theTransform phaseto prevent duplicate records but is not the first step.

B. Transform Data(Incorrect)

Transforming data occursafter it has been loadedinto the Import Set table.

C. Import Data(Incorrect)

No such specific module exists as " Import Data " ; the process begins with " Load Data. "

Importing Data Using Import

Load Data Module in

Steps in Importing Data:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

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:

To create anew email notificationin ServiceNow for users affected bynetwork outages, you must navigate to theNotifications moduleunderSystem Notification.

Navigate to:System Notification > Email > Notifications

ClickNewto create a new notification.

Configure the notification with the following:

Name: " Network Outage Notification "

Table:Select the relevant table (e.g.,Incident, Task)

When to Send:Define the trigger (e.g., when anIncident is created or updatedwith a Network Outage category).

Who Will Receive:Specifyaffected users.

Message Content:Create the email subject and body usingdynamic fields(such as affected user’s site).

Save and test the notification.

Notifications are managed in System Notification.

TheNotifications moduleallows you to configureemail triggers, recipients, conditions, and templatesfor system alerts.

B. Administration > Notification Overview:No such module in ServiceNow.

C. System Properties > Email > Settings:This configuresemail server settings, not individual notifications.

D. User Preferences > Email > Notifications:User preferences onlyenable or disablepersonal notifications, not create new ones.

E. Click Gear > Notifications > New:The gear icondoes not provide accessto email notifications.

Creating and Managing Email Notifications in ServiceNow:ServiceNow Docs

ServiceNow Notification Configuration Guide

Steps to Create a New Notification:Why is the Correct Answer " System Notification > Email > Notifications " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingSystem Notification > Email > Notifications, administrators can create a targetedemail notificationto alert users ofnetwork outageseffectively.

TheApplication Integration and Plugin Delivery (A1PD) SpokeBatch Installplugin inServiceNowallows users to installmultiple applications, customizations, and pluginsat once.

Batch Installation

Enables administrators to install multiple applications or pluginssimultaneously, reducing manual effort.

Automated Delivery

Facilitatesautomated deploymentof related applications and customizations.

Improved Instance Management

Ensures consistent configurations across multiple instances (e.g.,Dev → Test → Prod).

B. Continuous Integration and Continuous Delivery (CICD) SpokeBatch Install

Incorrect: CICD is used forversion control and automated deployments, not plugin installation.

C. Multiple Integration and Process Delivery (MIPD) SpokeBatch Install

Incorrect: No such ServiceNow plugin exists.

D. Quick Integration and Multiple Delivery (QIMD) SpokeBatch Install

Incorrect: No such ServiceNow feature exists.

Key Features of A1PD SpokeBatch Install:Why Other Options Are Incorrect?

A1PD Plugin Overview

ServiceNow Plugin Installation

Application Integration Best Practices

Managing Installed Applications

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

InServiceNow, thepersonal_listrole allows users toadd or remove fields from a list viewwithout requiring full administrator privileges.

Modify List Layout (Columns & Fields)

Users canadd, remove, or rearrange columnsin list views.

Save Personal List Preferences

Customizations applyonly to the user, unless they have additional permissions to modify system-wide settings.

Does NOT Allow System-Wide Changes

Unlike theadminrole,personal_listonly affectspersonal viewsof lists, not global configurations.

A. personalize.control(Incorrect)

No such role exists in ServiceNow.

C. ui_page_admin(Incorrect)

This role allows users tomanage UI Pages, but it does not provide list customization permissions.

D. ui_action_admin(Incorrect)

This role is used tomanage UI Actions(buttons, links, and client-side scripts), not list view configurations.

Key Capabilities of thepersonal_listRole:Why Other Options Are Incorrect?

Role-Based List Customization

ServiceNow List Personalization

User Roles and Permissions

ServiceNow User Roles

References from ServiceNow CSA Documentation:

TheCommon Services Data Model (CSDM)is a standardized framework within ServiceNow that provides a shared set of service-related definitions across ServiceNow products and the platform. It ensures consistency inservice reporting, CMDB structure, and configuration strategies, enabling organizations to achieve awell-structured, scalable, and maintainable Configuration Management Database (CMDB).

Why is the Answer A. Common Services Data Model (CSDM)?The statements in the question directly align with the objectives of CSDM:

" A standard and shared set of service-related definitions across ServiceNow products and platform that will enable and support true service level reporting. "

CSDM provides a structured framework toalign services, applications, and infrastructurein a way that supports consistent reporting and governance.

It enablesaccurate service reportingby defining standardized relationships between services, applications, and technical components in the CMDB.

" A CMDB framework across our products and platform that will enable and support multiple configuration strategies. "

CSDM provides astructured CMDB frameworkthat definesbest practices for data organization and relationships within the CMDB.

It supports multiple configuration strategies, such asapplication-centric, service-centric, and infrastructure-centric approaches.

B. Information Technology Service Management (ITSM):

ITSM refers toprocesses for managing IT services, such as Incident, Problem, Change, and Service Request Management.

While ITSM benefits from CSDM, itdoes not define a structured CMDB frameworklike CSDM does.

C. Configuration Management Database (CMDB):

CMDB is a database that stores configuration items (CIs) and their relationships.

CSDMprovides structure and best practicesfor CMDB but is not the same as CMDB itself.

D. Information Technology Infrastructure Library (ITIL):

ITIL is aset of best practicesfor IT service management.

It provides general guidance onservice management and CMDB usage, butit is not a ServiceNow-specific frameworklike CSDM.

ServiceNow Common Services Data Model (CSDM) Overview:ServiceNow Documentation

CSDM and CMDB Best Practices Guide(ServiceNow Community and Knowledge Base)

CMDB and ServiceNow Data Model Best Practices

Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:CSDM is critical forensuring a structured and governed CMDB, enabling service visibility, and supporting ITSM and ITOM processes effectively.

AnUpdate Setin ServiceNow is a mechanism used tocapture configuration changes(such as UI policies, business rules, client scripts, and more) from one instance and move them to another. This ensures that customizations and modifications can be transferred across different ServiceNow instances efficiently.

The process ofretrieving an Update Setfrom another instance follows these key steps:

Verify Update Set is Complete

Before moving an Update Set, it must be marked asCompleteto ensure that all related changes are included.

Navigate toSystem Update Sets > Local Update Setsand confirm that the status is set toComplete.

If the status isIn Progress, the Update Set cannot be retrieved.

Retrieve Update Set

In thetarget instance, navigate toSystem Update Sets > Retrieved Update Sets.

Click " Retrieve Update Set " and provide the remote instance’s URL where the update set exists.

The system will fetch the Update Set from the source instance.

Preview Update Set

Before applying changes, ServiceNow provides apreview optionto check for potential errors or collisions with existing customizations.

Click " Preview Update Set " to initiate validation.

The preview will highlight any skipped records, collisions, or missing dependencies.

Commit Update Set

If the preview is successful (i.e., no critical errors), click " Commit Update Set " to apply the changes to the instance.

Once committed, the changes in the Update Set will be merged into the system ' s configuration.

" Commit " is the correct final step– after previewing, the Update Set must becommittedto take effect.

" Apply " is incorrect– ServiceNow does not use " Apply " in the Update Set process; instead, it uses " Commit. "

" Test Connection " is not part of the Update Set retrieval process– it is relevant forMID Server connectivitybut not for Update Sets.

Why the Correct Answer is " D. Verify Update Set is Complete, Retrieve, Preview, Commit " Thus, the correct sequence is:

✔Verify Update Set is Complete → Retrieve → Preview → Commit

ServiceNow CSA Official Documentation– Update Set Management

ServiceNow Docs - Update Sets(Search for " Update Set Lifecycle " )

ServiceNow Community Best Practices on Update Sets

ServiceNow Community(Search for " Best Practices for Update Sets " )

ServiceNow Learning Portal - Admin Fundamentals

Available via ServiceNow Now Learning Platform(Look under " Instance Configuration " and " Update Sets " )

References from Certified System Administrator (CSA) Documentation:

On theReports pagein ServiceNow, different sections allow users to seewhich reports are visibleto various audiences.

Why These Options Are Correct?C. My reports

Displaysreports created by the logged-in user.

These reports areprivateunless explicitly shared.

E. Dashboards

Dashboardsconsolidate multiple reports andmake them visible to specific audiences.

Users canshare dashboardswith groups or individuals.

F. Global

Global reportsare available toall users with reporting access.

These reports arenot restrictedto a specific user or group.

I. All

The " All " sectionlistsevery report the user has access to, including:

Personal reports

Shared reports

Global reports

Reports from dashboards

Why the Other Options Are Incorrect?A. Group

There isno " Group " sectionin the Reports page.

However, reports can beshared with groups, but there is no direct " Group " view.

B. Department

Departments do not determine report visibilityin the Reports page.

Report access is controlled byroles, users, and groups, not departments.

D. Team

Teams are not a standard report visibility categoryin ServiceNow.

Reports are shared atuser, role, and global levels, not by " Team. "

G. Admin

There isno " Admin " sectionin the Reports page.

However,Admins can access all reportsvia the " All " section.

H. Analytics

Analytics is a separate modulein ServiceNow, primarily used forPerformance Analytics (PA)anddashboards.

It is not a standardreport visibility section.

J. Company

There isno " Company " sectionin the Reports page.

Reports can beshared at a global level, but not specifically by " Company. "

ServiceNow Reports - Managing Visibility and Access

ServiceNow Reporting Guide - Sections of the Reports Page

ServiceNow Dashboards and Report Sharing Best Practices

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow,Number Maintenanceis the application used to manage and modify numbering schemes for different tables, including theIncidenttable. Since the default prefix forIncident numbersis " INC " , an administrator can modify it to a company-specific prefix (e.g., " IN " ) by following these steps:

Navigate to the Number Maintenance Application:

Go toAll → System Definition → Number Maintenance

Search for theIncident table (task.number record for Incident).

Modify the Prefix:

Open the existingIncident numbering record.

Change thePrefixfrom " INC " to " IN " .

Ensure theNext Numberfield is correctly set (e.g., " IN0001001 " ).

Save the Changes:

ClickUpdateto apply the new prefix.

All newly created incidents will now follow the new format (IN0001001).

Existing incidents are NOT affected—only newly created records will reflect the new prefix.

Steps to Change the Incident Number Prefix:Why Option A (Number Maintenance) is Correct?The Number Maintenance application is the correct place to modify prefixes for tables like Incident.

Why Other Options Are Incorrect?B. Create a Business Rule that modifies the prefix before the Insert operation→ Incorrect

Business Rulesdo not control number generation.

Number generation is managed byNumber Maintenanceat the system level.

C. The prefix of an incident cannot be changed because it is a built-in feature→ Incorrect

The prefixCAN be changedusing theNumber Maintenanceapplication.

Only existing records retain their original prefix; new records follow the updated format.

D. Submit a Change Request to ServiceNow Technical Support→ Incorrect

This isnot necessary, asadministratorscan make this change directly throughNumber Maintenance.

ServiceNow Docs – Number Maintenance

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow Developer Portal – Number Prefix Best Practices

References from Certified System Administrator (CSA) Documentation:

Importing data into ServiceNow from a spreadsheet involves a structured process to ensure data integrity and proper mapping. The three main steps in the process are:

The first step in importing data into ServiceNow is to load the spreadsheet into an Import Set table.

This can be done through theSystem Import Sets > Load Datamodule.

The system will create a temporary table (Import Set) where the data will be staged before being transformed into target tables.

ATransform Mapis required to map fields from the Import Set table to the target table in ServiceNow.

Transform Maps define how data from the source (Import Set table) will be transferred and transformed into the destination table (e.g., Incident, User, CMDB, etc.).

The Transform Map allows for additional transformations such ascoalescing records(to avoid duplicates) and scripting for data manipulation.

After configuring the Transform Map, the final step is toRun Transform, which applies the mappings and moves the data from the Import Set table to the target table.

This process ensures that the imported data is correctly integrated into the ServiceNow instance and adheres to the configured rules.

Option A: " Select Data Source, Schedule Transform " – Incorrect because selecting a data source is part of data import, but " scheduling " a transform is not a required step in the standard import process.

Option C: " Define Data Source, Select Transform Map, Run Transform " – Incorrect because " Define Data Source " is more relevant when setting up external data imports. The process must begin with " Load Data " rather than defining the data source.

Option D: " Select Import Set, Select Transform Map, Run Transform " – Incorrect because an Import Set must first be created by loading data before it can be selected.

ServiceNow Docs: Importing Data Overview

ServiceNow Docs: Creating a Transform Map

ServiceNow Docs: Running a Transform Map

Step 1: Load DataStep 2: Create Transform MapStep 3: Run TransformWhy Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:

In ServiceNow,UI Actionsare used toadd buttons, links, and context menu itemson forms and lists to enhance user interaction.

UI Actions provide interactive elementssuch asbuttons, links, and context menu optionson forms and lists.

UI Actions allow execution ofserver-side and client-side scripts, includingGlideAjax and GlideRecordcalls.

They can be configured to execute underspecific conditions, such asuser roles, field values, or record states.

Examples of UI Actions include:

Submit, Update, and Deletebuttons on forms.

Custom action buttonssuch as " Escalate Incident " or " Resolve Task " .

List context menu itemssuch as " Approve " or " Reject " for workflow items.

A. UI Policies:Used fordynamically showing, hiding, or making fields mandatory, butnot for adding buttons or links.

B. UI Settings:No such module in ServiceNow.

D. UI Config:Not a valid option; UI Actions, not " UI Config, " control buttons and menus.

UI Actions Overview:ServiceNow Docs

Configuring UI Actions for Forms and Lists

Why is the Correct Answer " UI Actions " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingUI Actions, developers canenhance the user experienceby providing interactivebuttons and menu optionsin ServiceNow.

In ServiceNow,UI PoliciesandData Policiesserve different but complementary purposes in controlling data behavior and enforcing business rules.

UI Policies are client-side rules that dynamically change form behavior based on user interactions.

They enable administrators to show/hide fields, make fields read-only, or set fields as mandatory dynamically.

UI Policies only apply when a user is interacting with a form through the ServiceNow UI (Client-side execution).

These policies do not enforce rules if data is added via an Import Set, API, or background script.

Data Policies enforce rulesserver-side, meaning they applyregardless of how data is entered(e.g., form submission, Import Sets, SOAP/REST API calls, or Business Rules).

They ensure data integrity by making fields mandatory, setting read-only properties, or applying other restrictions.

Data Policies can apply conditions globally, unlike UI Policies, which work only in the UI context.

UI Policies:Data Policies:Key Differences:Feature

UI Policy

Data Policy

Scope

Affects only forms (Client-side)

Affects all data entry points (Server-side)

Execution Location

Runs in the browser

Runs on the server

Triggers

User interaction on the form

Any data entry method (Forms, Import Sets, API, etc.)

Enforcement

Works only when using the UI

Applies even when data is added outside the UI

" Data Policies run regardless of how data is entered into ServiceNow " →Correct, because Data Policies enforce rules whether the data is entered via UI, API, Import Sets, or other means.

" UI Policies are used for form interactions " →Correct, because UI Policies apply only to client-side form behavior.

Option A: Incorrect. UI Policies are not set by web services; they are applied when interacting with forms.

Option B: Incorrect. While some Data Policies can be converted into UI Policies, the reverse is not true in all cases.

Option D: Incorrect. UI Policies and Data Policies operate independently, and Data Policies do not depend on UI Policies running first.

Why Option C is Correct:Why Other Options are Incorrect:

In ServiceNow, when applying filters, theFunnel iconopens the condition builder, allowing users to set criteria for displaying records.

Understanding the requirement:

The user wants to seeIncidents where the state is ClosedORIncidents where the Assignment Group is Network.

The key word here isOR, meaning records satisfyingeithercondition should be displayed.

Steps to apply this filter in ServiceNow:

Click theFunnel iconto open the condition builder.

Define thefirst condition→ SelectState = Closed.

Click theORbutton (since we want records meeting either condition).

Define thesecond condition→ SelectAssignment Group = Network.

PressEnterto apply the filter.

Since the user wantseither condition to be true,ORis the correct logical operator.

PressingEnterafter defining the second conditionexecutes the filter.

A. Define the first condition; click AND button; define second condition; click Run:Incorrect becauseANDwould requireboth conditions to be true simultaneously, which is not what the user wants.

B. Define the first condition; click AND button; define second condition; press enter:Same issue as option A—AND willnarrow the resultsinstead ofexpanding them.

D. Define the first condition; click > icon on breadcrumb, define second condition; click Run:Thebreadcrumb navigationis used to modify filtersafter applying them, not to create them initially.

E. Define the first condition; click > icon on breadcrumb, define second condition; press enter:Same issue as option D—breadcrumb navigation is for modifying, not for initial filter creation.

Using Filters and Condition Builder in ServiceNow:ServiceNow Docs

ServiceNow Querying and Filtering Best Practices

Why is the Correct Answer " C " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:UsingORensures both conditions are considered independently, displaying incidents that are eitherClosedor assigned toNetwork.

TheCMDB Builderis the primary tool used inServiceNow’s Configuration Management Database (CMDB)for creating and managingdependencies between Configuration Items(CIs). It provides agraphical interfacethat allows administrators and CMDB managers to visualize and define relationships between CIs efficiently.

Visual Representation of CI Dependencies:

CMDB Builder provides agraphical interfacethat allows users tocreate, modify, and deleterelationships between Configuration Items (CIs).

It helps in identifyingimpact analysisandservice dependenciesby mapping CIs and their relationships.

Supports Complex CI Relationships:

Allows definingparent-child,peer, anddependencyrelationships between CIs.

Helps in ensuring the accuracy ofservice mapsandIT asset relationships.

Drag-and-Drop Functionality:

Users candrag and dropCIs onto the builder canvas andconnect them using predefined relationships.

Integration with CMDB Relationship Rules:

CMDB Builder adheres toCMDB relationship rulesto ensure that onlyvalidrelationships are created.

Impact and Root Cause Analysis:

Helps introubleshooting IT incidentsby showing thedependencies between services.

Useful inchange managementto predict potentialimpactson downstream services before making changes.

Key Features of CMDB Builder:

A. CI Relationship Editor:

TheCI Relationship Editorallows users toview and edit relationshipsbetween CIs in atabular formatbutdoes not provide a graphical dependency visualizationlike CMDB Builder.

It is moremanual and less interactivecompared to CMDB Builder.

C. CI Service Manager:

CI Service Manageris used for managingCI service mappingsbut isnot primarily a tool for creating dependencies between CIs.

It is more focused ondefining service-level relationshipsrather thanbuilding CMDB dependency models.

D. CI Class Manager:

CI Class Manageris used formanaging CI classes, attributes, and extending CMDB class structures.

It is not used forcreating dependencies between configuration items.

Why Other Options Are Incorrect:

ServiceNow CMDB Guide:CMDB Builder Overview

ServiceNow Best Practices for CMDB:CMDB Relationship Management

ServiceNow Admin Documentation:Understanding CMDB Dependency Management

References from the Certified System Administrator (CSA) Documentation:

Final Answer:CMDB Builder (Option B) is the correct answer, as it is the primary tool used to create, manage, and visualize dependencies between CIs in ServiceNow ' s CMDB.

InServiceNow, anEventis a system-generatednotificationthatindicates an occurrence within the platform. Events are triggered automatically or manually whenspecific conditionsare met and can be used to initiatenotifications, business rules, workflows, or integrations.

Events Indicate That Something Has Happened

Example: When anIncident is assigned, an event like " incident.assigned " can be triggered.

These eventsdo not execute actions themselves, but theynotify other processesto take action.

Events Are Stored in the [sys_event] Table

TheEvent Log(System Policy > Events > Event Log) records all generated events.

Administrators can monitorwhat events were triggered, their sources, and timestamps.

Events Can Be Used for Notifications & Workflows

Example: An event " incident.closed " can be configured to send a " Thank You " emailto the requester.

Example: A custom event " task.overdue " can be used to trigger a workflow escalation.

Eventssignal that something has happened, allowing other processes (like email notifications or workflows) to react.

Theydo not execute actions themselvesbut notifyscripts, business rules, or workflows.

Key Characteristics of Events in ServiceNow:Why is " B. An Event is an indication to the ServiceNow processes that something has occurred " the Correct Answer?

A. " An Event is a trigger that has a direct response in the platform " →Incorrect

Events themselvesdo not trigger direct responses; they onlynotify the systemabout occurrences.

The system must beconfigured to respond to an event(e.g., via aBusiness Rule, Notification, or Script Action).

C. " An Event is an indicator that a Priority 1 (P1) Incident has been logged " →Incorrect

While ServiceNowcan generate an event when a P1 Incident is logged, events arenot limited to incidents.

Events apply toall ServiceNow processes(incidents, changes, tasks, etc.).

D. " An Event is a recognized, scheduled occurrence of a process " →Incorrect

Eventsare not scheduled; they aretriggered by system activities(e.g., record updates, conditions met).

Scheduled Jobs or Scheduled Scripts handletime-based automation, not events.

Why the Other Options Are Incorrect?

Navigate to:System Policy > Events > Event Log

Review the event records, including event names, sources, and timestamps.

Navigate to:System Policy > Events > Registryto see predefined event names.

UseEvent Registryto create new events that triggernotifications or workflows.

How to View and Use Events in ServiceNow?

ServiceNow Docs: Events in

ServiceNow CSA Official Training Guide (Event Management & Notifications)

References from Certified System Administrator (CSA) Documentation:This confirms that " An Event is an indication to the ServiceNow processes that something has occurred " is the correct answer.

AConfiguration Item (CI)is any component thatneeds to be managed to deliver IT services. In ServiceNow, CIs are stored in theConfiguration Management Database (CMDB)and can include servers, applications, databases, network devices, and more.

Tracking & Management: Helps organizations track IT assets and their relationships.

Service Impact Analysis: Identifies how an issue with one component can affect related services.

Change Management Support: Ensures changes to IT assets are controlled and well-documented.

Incident & Problem Resolution: Provides insights into troubleshooting and root cause analysis.

Hardware: Servers, network devices, storage systems.

Software: Applications, databases, operating systems.

Services: Business services, IT services.

Documentation: Policies, SLAs, knowledge articles.

Why Are Configuration Items Important?Examples of Configuration Items (CIs):

Incorrect Answer Choices Explanation:A. CSDM Items– TheCommon Service Data Model (CSDM)is a framework for structuring CMDB data, but individual components in the CMDB are calledConfiguration Items (CIs).

B. CMDB– TheCMDB (Configuration Management Database)is thedatabasethat stores Configuration Items, but it is not a CI itself.

D. Service Offerings– AService Offeringrepresents a set of capabilities available to customers but is not the same as a CI.

E. Asset– AnIT Assetrefers to aphysical or virtual resourceowned by the organization, butnot all assets are CIs(e.g., a computer mouse may be an asset but not a CI).

ServiceNow CMDB Overview

Configuration Items (CIs)

Official CSA Documentation Reference:

ATransform Mapin ServiceNow is a tool used to define relationships betweenfields in an import set tableandfields in a target table. It helps map incoming data to the appropriate fields within the ServiceNow database when importing data from external sources.

Data is loadedinto anImport Set Table.

ATransform Mapis created to define how fields from the import set correspond to fields in the target table.

TheTransformation Processis executed, applying the mapping rules.

The data is stored in theTarget Tablewith any specified transformations applied.

Supportsfield mapping,scripted transformations, andcoalesce fields(for avoiding duplicate records).

Allows fordata cleansing and standardizationduring the transformation process.

Can be reused for multiple data imports.

A. Transform Schema→ No such concept exists in ServiceNow.

B. Schema Map→ Provides a visual representation of table relationships but does not define field mappings for imports.

C. Dictionary Map→ Used for mapping between dictionary definitions, not for transforming import set data.

E. Field Transformer→ Not a ServiceNow tool.

F. Import Designer→ No such module in ServiceNow.

Access Control rules in ServiceNow define who cancreate, read, write, or deleterecords in a table or specific fields. These rules are applied at thetable or field leveland follow a specificnaming convention:

TableName.FieldName

Naming Convention for Access Control Rules:

If an Access Control rule applies to a specifictable, its format isTableName(e.g.,incident).

If it applies to a specificfield, it followsTableName.FieldName(e.g.,incident.major_incident).

Major Incident is a field in the Incident table:

Theincidenttable represents the ITSMIncident Management module.

Major Incidentis aspecific fieldwithin theincidenttable.

To apply anAccess Control Ruleto this field, the rule name must beincident.major_incident.

A. Incident.Major_Incident:Incorrect because ServiceNow Access Control rulesdo not use uppercase table or field names—they are alwayslowercase.

B. incident= > major_incident:Incorrect syntax—ServiceNow does not use= > in Access Control names.

C. incident < = > major_incident:Incorrect syntax—ServiceNow does not use < = > in rule naming conventions.

D. incident||major_incident:Incorrect syntax—ServiceNow does not use||(logical OR) in Access Control naming.

ServiceNow Access Control Rules Guide:ServiceNow Docs

How to Create and Manage Access Control Rules in ServiceNow

Why is the Correct Answer " incident.major_incident " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingincident.major_incident, we correctly definefield-level securityfor theMajor Incidentfield in theIncident table.

InServiceNow, theTask [task]table is acore tablethat provides aset of standard fieldsused by multiple tables that extend it, including:

Incident [incident]

Problem [problem]

Change Request [change_request]

Service Request [sc_request]

These tablesinherit fieldsfrom theTasktable, ensuring consistency inassignments, state management, and workflows.

Standard Fields:

Assigned To

Assignment Group

Priority

State

Created By / Updated By

Short Description / Description

Extensibility:

TheIncident, Problem, and Change tablesallextendthe Task table, inheriting its fields.

Developers canadd additional fieldswhile keeping core task properties intact.

TheTask table is the primary tablefor work-related records in ServiceNow.

Itstandardizes fieldsacross multiple ITSM modules.

B. Assignment [assignment]→Incorrect

There isno standard " Assignment " tablein ServiceNow.

Assignments are managed through theTask tablevia theAssigned To and Assignment Group fields.

C. Service [service]→Incorrect

There isno generic " Service " tablethat acts as a core table for ITSM processes.

Service-related items are stored in different tables, such ascmdb_ci_service(for service records).

D. Workflow [workflow]→Incorrect

TheWorkflow tableis used for managing automated workflows anddoes not store task-related records.

Key Features of the Task Table:Why is " A. Task [task] " the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Task Table

References from Certified System Administrator (CSA) Documentation:This confirms thatthe Task table is the core table that extends to Incident, Problem, and other related tables.

In ServiceNow, users can log into theService Portalusingcertificate-based authentication methods. The two commonly supported methods are:

ACACis a smart card issued by theU.S. Department of Defense (DoD).

It is used by military personnel, contractors, and government employees for secure authentication.

ServiceNow supportsCAC authenticationby integrating with external identity providers.

APIV cardis used byU.S. federal agenciesfor authentication.

It followsFederal Information Processing Standard (FIPS) 201for identity verification.

ServiceNow allows users to log in using PIV authentication, ensuringsecure accessto government and enterprise systems.

1. Common Access Card (CAC) – (Correct Answer)2. Personal Identity Verification (PIV) – (Correct Answer)

Both CAC and PIV are widely recognized certificate-based authentication methodsused in ServiceNow for secure user authentication.

They provide multi-factor authentication (MFA)and meet federal security standards.

Why " C. CAC " and " E. PIV " are the Correct Answers?

A. Extended Validation Access (EVA) – Incorrect

No such authentication method exists in ServiceNow.Extended Validation (EV) certificatesare used for website security, not user authentication.

B. Organization Verification Card (OVC) – Incorrect

Not a recognized ServiceNow authentication method.

D. Domain Authentication Card (DAC) – Incorrect

No such authentication method exists in ServiceNow.

Explanation of Incorrect Options:

ServiceNow Docs: Common Access Card (CAC) Authentication

ServiceNow Docs: Personal Identity Verification (PIV) Authentication

ServiceNow CSA Study Guide – Authentication Methods in ServiceNow

References from Certified System Administrator (CSA) Documentation:

AService Level Agreement (SLA)in ServiceNow is a tracking mechanism that ensures tasks are completed within a specified time frame. SLAs help inmonitoring and enforcing deadlinesfor various tasks, such as incidents, changes, or service requests.

Tracks Task Duration

SLAs calculate theelapsed timesince a task was created and determine if it meets or breaches the defined resolution targets.

Ensures Timely Completion

SLAs definestart, pause, and stop conditionsbased on specific criteria (e.g., an incident must be resolved within 8 hours).

Visual Indicators

SLAs includeprogress bars, warning alerts, and breach notificationsto help users track deadlines.

Works with Business Rules and Workflows

SLAs can triggerescalations, notifications, or automated actionsif a task is at risk of breaching the SLA.

A. Task Escalation Clock(Incorrect)

No such feature called " Task Escalation Clock " exists in ServiceNow. Escalations are handled usingSLA workflows and escalation rules.

C. Inactivity Monitor(Incorrect)

TheInactivity Monitoris used to detect when a task has not been updated for a specific period, but it does not enforce time-bound completion.

D. Response Time Clock(Incorrect)

No specific " Response Time Clock " exists in ServiceNow.Response SLAstrack thetime taken to acknowledge a task, but this is part of the broader SLA system.

E. Business Time Remaining(Incorrect)

This isnot a specific featurebut rather a calculated field within SLAs that shows the time remaining before an SLA breaches.

Service Level Agreements (SLA)

How SLAs Work in

Key Features of SLAs in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

Afilter conditionin ServiceNow consists of three essential components that define how data is filtered in lists, reports, and queries. These components determine which records meet specific criteria.

Column (D)– Represents thefieldin the table that is being filtered (e.g., " Priority " in theincidenttable).

Operator (A)– Defines the comparison method, such asis, contains, starts with, greater than, etc.

Value (C)– Specifies thecriteriaused for filtering (e.g., " High " for Priority).

Components of a Filter Condition:Example of a Filter Condition in an Incident Table:PriorityisHigh

Column:Priority

Operator:is

Value:High

B. Match Criteria→ Not a defined component; filtering is based on column, operator, and value.

E. Field→ While " Field " is a general term,ServiceNow officially uses " Column " in filter conditions.

InServiceNow Flow Designer, adata pillrepresentsvariables, record fields, or outputs from previous stepsthat can be used dynamically in the flow.

Data pillsallow flow designers to referencerecord datawithout manually specifying table fields.

Dragging a data pillonto a flow step ensures that the correct values areautomatically mappedfrom the referenced record.

This is the recommended method for using record datawithin a flow.

Why is Option D Correct?

Why Are the Other Options Incorrect?A. Drag the table icon onto the flow definition

IncorrectbecauseFlow Designer does not use table iconsfor referencing records.

Instead, it utilizesdata pills and actionsto retrieve and manipulate record data.

B. Use the condition builder to specify the desired values

Incorrectbecause thecondition builderis used fordecision logic(e.g., If-Else conditions), not for referencing record data.

C. Specify the source table on the data pill related list

Incorrectbecause youcannot manually specifya table in a data pill.

Data pills areautomatically createdwhen an action retrieves data from a record.

E. Add the table reference using the slush bucket

Incorrectbecauseslush bucketsare used in ServiceNow for selecting multiple items (e.g., roles, groups),not for referencing record data in a flow.

ServiceNow Flow Designer - Using Data Pills

ServiceNow Flow Designer - Best Practices for Record Referencing

ServiceNow ITSM - Automating Workflows with Flow Designer

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow,Visual Task Boards (VTBs)provide aKanban-style interfaceto manage and track work. There arethree main typesof Visual Task Boards, but " Feature " is notone of them.

Freeform Board (Valid Type)

Manually created boards wherecards can be moved freelywithout predefined conditions.

Users canadd and organize tasks as needed.

Example: Personal task management.

Guided Board (Valid Type)

Createdfrom a list viewandlinked to a ServiceNow table(e.g., Incident, Change, Task).

Cards on the boardautomatically updatebased on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (Valid Type)

Similar toGuided Boards, but allows users tomanually reordertasks within lanes.

Offers moreflexibilitywhile still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

" Feature " is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term " Feature " in Agile Development (for tracking high-level product functionalities), but it is not related to VTBs.

Types of Visual Task Boards in ServiceNow:Why is " Feature " Incorrect?

Why Other Options Are Correct?Guided, Flexible, and Freeformare thethree valid typesof Visual Task Boards in ServiceNow.

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

References from ServiceNow CSA Documentation:

InServiceNow Flow Designer, users can accessdetailed informationabout actions added to a flow via theHelp Panel. The Help Panel providescontextual guidanceand documentation about the available actions, conditions, and steps within the flow.

Displays Information About Actions:

When an action is selected in Flow Designer, theHelp Panelprovidesdescriptions and usage details.

Helps users understandwhat the action doesand how to configure it.

Accessing the Help Panel:

Inside Flow Designer, users can click theHelp icon ( ? )or expand the Help Panel from the side.

This providesinline documentationfor added actions.

Guidance for New Users:

The panel providesServiceNow documentation links and tipsto help users build flows effectively.

Key Features of the Help Panel:Why Option C (Help Panel) is Correct?TheHelp Panelprovides built-in documentation and details about actions added to the flow.

Why Other Options Are Incorrect?A. Virtual Agent Help→ Incorrect

Virtual Agent Help is related tochatbot and conversational assistance, not Flow Designer.

B. Local Action Help→ Incorrect

No such feature exists in ServiceNow; action details are found in theHelp Panel.

D. Flow Assistant→ Incorrect

Flow Assistanthelps withbuilding expressions and selecting data pillsbut does not provide action documentation.

ServiceNow Docs – Flow Designer Help

ServiceNow Learning – Flow Designer and Automation Best Practices

ServiceNow Developer Portal – Flow Designer Action Configuration

References from Certified System Administrator (CSA) Documentation:

InServiceNow, administrators canreuse the same notification contentacross multiple channels (such asemail, SMS, and push notifications) by usingCommon Notification Content.

Consistency Across Channels

Ensures that the same message format is used acrossemail, SMS, and push notifications.

Easier Maintenance

Instead ofcreating separate contentfor each channel, administrators can manage all notification content from one place.

Dynamic Content

Supports variables and dynamic placeholders to customize messages based on recipient data.

A. Configure Default notification content

Incorrect: There is no " default notification content " feature in ServiceNow.

B. Enable Actionable notification content

Incorrect: Actionable notifications allow users totake actions directly from the notification, but they do not manage common content.

D. Set up Related notification content

Incorrect: No such feature as " Related notification content " exists in ServiceNow.

Key Features of Common Notification Content:Why Other Options Are Incorrect?

Common Notification Content Overview

ServiceNow Notification Management

Setting Up Common Notification Content

Creating Reusable Notification Content

References from ServiceNow CSA Documentation:

InServiceNow Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.

Submission:

A user creates a knowledge article and submits it for approval.

Approval Process:

Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.

Publishing:

Once approved, the article ispublishedand made available in the Knowledge Base.

Updating & Versioning:

If edits are needed, the article enters adraft or reviewstate.

Retirement:

When an article is no longer needed, it follows the workflow toretire or archiveit.

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

ServiceNow does not use a separate " Approval Policy " for knowledge articles; approvals are managed within the workflow.

B. Approval Definitions(Incorrect)

There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.

C. Workflow Designer(Incorrect)

TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.

E. State Lifecycle(Incorrect)

While knowledge articleshave a lifecycle (Draft → Review → Published → Retired), this is controlledby workflows, not by an independent " State Lifecycle " feature.

Knowledge Workflows

ServiceNow Knowledge Management

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

Thekey differencebetweenReportingandPerformance Analytics (PA)is how they handle data over time.

Showsreal-time datafrom tables.

Runs queries on dataat the momentthe report is generated.

Cannot analyze historical trendsunless data is manually stored.

Used forstatic reports, lists, charts, or dashboards.

Capturessnapshotsof data at scheduled intervals (e.g., daily, weekly).

Tracks trends and KPIs (Key Performance Indicators)over time.

Helps organizationsforecast and analyze historical patterns.

Used forbusiness intelligence and proactive decision-making.

ReportingPerformance Analytics (PA)

Incorrect Answer Choices Explanation:B. Performance Analytics can show trends; Reports cannot.

Reporting can show trends usingaggregated data(e.g., grouped by date), butPA is specifically designedfor tracking trends over time.

C. Reports can be run on a scheduled basis; Performance Analytics cannot.

BothReports and PA can be scheduledto run at regular intervals.

D. Performance Analytics data can be published to Dashboards; Reports cannot.

Reportscanbe published todashboards, just like Performance Analytics.

E. Performance Analytics shows KPIs; Reporting does not.

Reports candisplay KPIsusing calculated metrics and aggregations, butPA is optimizedfor KPI tracking over time.

Performance Analytics vs. Reporting

ServiceNow Reporting Overview

Official CSA Documentation Reference:

AMany-to-Many (M2M) relationshipin ServiceNow allows two or more tables to be relatedbi-directionally, so that related records are visible in arelated liston both tables.

Unlike aOne-to-Many (1:M)relationship (where only one table references another), M2M relationshipslink records in both directions.

This is achieved through anintermediary table, known as aMany-to-Many table, which stores the relationships.

A Many-to-Many table contains:

Areference fieldfor each of the tables being linked.

The relationship records, which connect records between the two tables.

Suppose you want to relateIncidentstoProblemsand vice versa.

Instead of adding a reference field in each table, you create anm2m_incident_problemtable.

Now, an Incident can be linked tomultipleProblems, and each Problem can be linked tomultipleIncidents.

These relationships will be visible asrelated listsin both tables.

How Many-to-Many Relationships Work in ServiceNow:Example of a Many-to-Many Relationship:

Incorrect Answer Choices Explanation:A. Database View– Used tocombine data from multiple tablesfor reporting but does not establish abi-directional relationshipbetween tables.

C. One to Many (1:M)– Asinglerecord in one table relates tomultiplerecords in another, but the relationship isnot bi-directional.

D. Extended– Refers totable inheritance, where a table inherits fields from its parent table, not a Many-to-Many relationship.

Many-to-Many Relationships in ServiceNow

Understanding Table Relationships

Official CSA Documentation Reference:

InServiceNow (and databases in general), data is stored intables, which consist of:

Columns (Fields):Representindividual data attributes(e.g., Name, Email, Status).

Rows (Records):Representindividual entriesin the table (e.g., a specific Incident or User).

Key Concepts:Table

Columns (Fields)

Rows (Records)

Incident

Number, Caller, Priority, Description

Each unique incident entry

User

Name, Email, Role, Department

Each individual user record

A column represents a single field (data attribute), such as " Priority " or " Short Description. "

A row represents a record (entry in the table), such as an individual incident or user.

A. A column is a field in the database and a record is one user→Incorrect

Records are not limited to users; a record could be an Incident, Change, or any other entry.

C. A column is one field and a record is one column→Incorrect

Arecord is not a single column; a record consists of multiple fields (columns).

D. A column contains data from one user and a record is one set of fields→Incorrect

Columns contain data for all users/records, not just one user.

A record is one row, not just a set of fields.

Why is " B. A column is one field and a record is one row " the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Understanding Tables and

References from Certified System Administrator (CSA) Documentation:

When usingHigh Security Settingsin ServiceNow, administrators often gaintemporary elevated privileges. To revert to normal security levels, they mustlog out and back into refresh their session.

High Security Settingsprovide elevated security configurations and mayoverride standard role-based access controls.

Logging outclears any temporary security settingsand restores normal administrator privileges.

This is therecommended practiceafter making security changes.

Why is Option B Correct?

Why Are the Other Options Incorrect?A. Select Normal role

Incorrectbecausethere is no " Normal " rolein ServiceNow.

C. Use System Administration > Normal Security module

Incorrectbecausethere is no " Normal Security " modulein ServiceNow.

D. Select Global Update Set

Incorrectbecause Update Sets controlcustomizations and configurations,not security settings.

E. End Impersonation

Incorrectbecause ending impersonation onlyswitches back to the admin accountif you were impersonating a user.

Itdoes not resetsecurity settings from High Security Mode.

ServiceNow CSA Guide - High Security Settings

ServiceNow Best Practices - Managing Security Configurations

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow Service Catalog, theUser Criteriafeature is used to specify which users are eligible to access (view or order) aService Catalog Item. User Criteria allows administrators todefine rules that determine whether a user can see or request a catalog item based on attributes such as roles, groups, departments, and locations.

User Criteria is createdto define the conditions (e.g., users in the IT department can order a laptop).

It is thenapplied to Catalog Items, Categories, or Access Control Rules.

If a user meets the criteria, they can see and order the item. If not, it remains hidden.

A. Can Read Role→ Incorrect. There is no such feature named " Can Read Role " in ServiceNow Service Catalog.

B. Catalog User Role→ Incorrect.ServiceNow does not have a predefined " Catalog User Role. " However, thecatalog_adminrole can manage catalog items, but it does not control access for end users.

C. Can Order Tab→ Incorrect. This is not a valid ServiceNow feature. Ordering permissions are controlled throughUser Criteria.

TheForm Designerin 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.

ServiceNow Product Documentation – Form Designer

ServiceNow CSA Training Module: " Configuring Forms and Fields "

" ServiceNow System Administration Guide – Form Customization Best Practices "

References from Certified System Administrator (CSA) Official Documentation:Would you like me to verify and format more questions in the same manner?

Dot Walkingis a ServiceNow feature that allows you to access and includedata from related tableswhen creating reports, conditions, scripts, and business rules.

When working with records, each table has fields that may reference another table (e.g., anIncidentrecord has an " Opened by " field that references theUsertable).

Dot Walkingallows you to traverse these relationships by using adot (.) notationto pull in data from related tables.

Example: If you want toinclude the email address of the user who created an incident, you can reference it as:

How Dot Walking Works:CopyEdit

incident.opened_by.email

This is useful forreportingwhen you need to include data from multiple related tables without needing custom joins.

A. SQL→ Incorrect. ServiceNow does not use direct SQL queries for reports. It relies on GlideRecord and Dot Walking instead.

C. Outer Join→ Incorrect. ServiceNow does not provide traditional SQL joins for reports. Instead, it usesDot Walking and Database Views.

D. Joins→ Incorrect. While Database Views allow for joins,Dot Walking is the primary method used to include related table data in reports.

In ServiceNow, users canself-assigntasks directly from theList Viewwithout opening the record. This improves efficiency by allowing users toquickly take ownershipof unassigned tasks.

C. Select the record using the check box then select the Assign To Me UI action on the List Header

Users can selectone or multiple recordsusing thecheckboxand then click the " Assign to Me " action in the list header.

This is useful forbulk assignmentwhen multiple tasks need to be assigned at once.

D. Right-click on the Task number and select the Assign to me option in the menu

Right-clickingon theTask Numberopens acontext menuwith the " Assign to me " option.

This is a quick way to take ownership of a taskwithout opening the record.

A. Select the record using the check box, then select the Person icon

There isno " Person icon " in theList Viewfor task assignment.

B. Double-click on the Assigned to value, type the name of the user, and select the green check

Inline editing (double-clicking)on the Assigned to field only worksif the field is editable, but it’s not the preferred way to self-assign a task.

E. Select the Task number, and select the Assign to me UI action on the form

This requiresopening the record, while the question specifically asks forlist view actions.

In ServiceNow,impersonating a userallows administrators or authorized users to temporarily assume another user’s identity. This is useful fortroubleshooting, testing permissions, and verifying user experiences.

admin (A)

Users with theadminroleautomaticallyhave impersonation privileges.

Admin userscan impersonate any user in the system.

Example: A system admin impersonates aService Desk Agentto test access restrictions.

impersonator (E)

Theimpersonatorrole allows a user to impersonate otherswithout full admin privileges.

This role is useful forsupport teams or testerswho need to verify user permissions.

Example: A QA tester is given theimpersonatorrole to test different roles in the system.

B. sys_admin

No such role assys_adminin ServiceNow—this is likely amistyped version of " admin " .

C. security_admin

security_adminis used forelevating privilegesto modify high-security settings, not for impersonation.

D. sys_user

Thesys_usertablestores user recordsbut isnot a role.

Regular userscannotimpersonate others unless they have theimpersonatororadminrole.

When importing data into ServiceNow,data integrity and accuracyare critical. ServiceNow recommendscleaning and verifyingdatabefore importingit into the system.

Obsolete or inaccurate datacan cause duplicate or incorrect records.

Pre-cleaningensures onlyrelevant, high-quality datais loaded into ServiceNow.

Improves system performanceby preventing unnecessary data clutter.

Identify and remove obsolete records(e.g., inactive users, old assets).

Fix formatting issues(e.g., date formats, duplicate values).

Verify data mappingsto ensure correct field alignment.

Use a small test importbefore a full-scale import.

Best Practice: Clean Data Before ImportingRecommended Pre-Import Steps:

A. Adjust your Transform maps, after the data is loaded into the target table →Incorrect

Transform Mapsshould be setbefore importing, not after.

Adjusting them afterward may requirereloading data.

B. Use extremely large Import Sets, instead of multiple large Import Sets →Incorrect

Large imports can causeperformance issues.

Best practice: Useincremental importswith data validation.

C. Create a new Import Set table for each new data load →Incorrect

Reusing Import Set tablesis more efficient.

New tables are neededonly for major structural differences.

E. Monitor data quality and clean imported data, using the Data Scrub Workspace →Incorrect

No such featureas " Data Scrub Workspace " exists in ServiceNow.

Datashould be cleaned before importing, not after.

Why Other Options Are Incorrect?

Best Practices for Importing Data

Preparing Data for Import

In ServiceNow,wildcardsare used to filter lists effectively. To search for records whereShort Description contains " email " , use theasterisk (*) wildcard.

Click the List Magnifier (???? ) to enable column search.

In the " Short Description " column search box, type:

Steps to Filter a List for " email " in Short Description:CopyEdit

*email

Press Enterto apply the filter.

*email→ Finds any record where " email " appearsanywherein theShort Description.

email*→ Finds records where " email " is at thebeginningof theShort Description.

*email*→ Also works but is redundant, as*emailalready searches within the text.

A. Click List Magnifier, on Short Description, type “email”, click enter →Incorrect

Typing just " email " only searches for an exact match, not occurrenceswithinthe text.

C. Click List Magnifier, on Short Description, type email, click enter →Incorrect

Same issue as (A) – it doesnotuse a wildcard, so it only returns exact matches.

D. On Search box, select text, type email, click enter →Incorrect

Theglobal search barisnot column-specific, meaning it searches across multiple tables, not justShort Description.

Using List Filters and Wildcards

ServiceNow Search Wildcards

Why Wildcards Matter?Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

Access Control Rules (ACLs)in ServiceNow define security rules thatcontrol user permissionsforviewing, creating, updating, and deletingrecords in the system. These rules ensure that users can onlysee and interact with the data they are authorized to access.

D. Access Control Rules

ACLsdefine security restrictionsat thefield, table, and record level.

These rules useconditions, scripts, and role-based permissionsto enforce security.

Example: A user with theitilrole may view incidents, but only users with theadminrole can delete them.

A. Role Assignment Rules

ServiceNowassigns roles to users, butroles alone do not define security rules.

ACLs controlwhat users can do, whilerolesonly grant potential access.

B. CRUD Rules

CRUD (Create, Read, Update, Delete)definespermission types, butnot security rules.

ACLs enforce CRUD operations based on roles and conditions.

C. Scripted User Rules

No such term as " Scripted User Rules " in ServiceNow security.

Possibly confused withScripted ACLs, which are part of Access Control Rules.

E. User Authentication Rules

Authentication rules controluser login mechanisms(LDAP, SSO, OAuth) but donot define access to data.

ACLs managedata security, while authentication ensuresusers are who they claim to be.

Understanding Choice Fields in ServiceNow:

AChoice fieldprovides a drop-down list ofpredefined valuesthat users can select from.

These fields are useful whenstandardized inputsare required (e.g., Status: Open, In Progress, Closed).

Why " Choice " is the Correct Answer:

AChoice fieldstores predefined options that users can select from a dropdown.

It ensuresdata consistencyby limiting inputs to a set of defined values.

Administrators can configure Choice fields inSystem Definition → Tables & Columnsby adding choices to specific fields.

Why Other Answers Are Incorrect:

B. Picker→ ServiceNow does havereference pickers(e.g., User Picker, Date Picker), but these are not used for predefined choice selections.

C. Drop down→ While a Choice fieldappearsas a dropdown, " Drop down " is not an official ServiceNow field type.

D. Option→ " Option " is a general term and not a specific ServiceNow field type.

Best Practice Solution:

To create or modifyChoice fields, go toSystem Definition → Tables & Columns, select the desired table, and edit the field properties.

UseChoice Liststo manage predefined values efficiently.

In ServiceNow, theActivitysection on a task record provides areal-time log of all recent updates, including field changes, comments, and system-generated events.

Displays achronological historyof changes made to a record.

IncludesWork Notes,Additional Comments, andField Changes.

Showswho made the changeandwhen it occurred.

Can befilteredto show only specific types of updates (e.g., comments, field changes).

A. Timeline →Incorrect

There is no standard " Timeline " section on a task record.

Visual Task Boards (VTBs)have timelines, but task records useActivity.

B. Journal →Incorrect

ServiceNowdoes nothave a " Journal " section for task records.

Journal fields(e.g., " Additional Comments " and " Work Notes " ) store specific updates, butActivityprovides the full record history.

C. Audit Log →Incorrect

TheAudit Log (sys_audit table)tracks changes but is not displayed directly on task records.

Admins need tomanually querytheAudit Logfor historical changes.

Activity Stream Overview

Understanding Journal Fields

Key Features of the Activity Section:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

To customize thebanner image, text, and colorsof your instance in ServiceNow, you use theSystem Properties > Brandingmodule. This module allows administrators to control variousUIaspects, including thebrandingof the system.

Banner Image: Change the header image seen across the UI.

Text: Customize the text displayed in the header or other branding areas.

Colors: Modify the colors of various UI elements to match your company ' s branding.

Key Customizations Available in Branding:This is typically applied to bothUI16 (desktop)andUI11 (classic)interfaces, ensuring a consistent experience across the instance.

A. Homepage Admin > Pages > Branding– This is used forhomepagesrather than global instance branding.

C. System Properties > Basic Configuration UI16– This section allows configuration of theUI layout and elementsbut does not specifically manage branding elements like banner image and colors.

E. Service Portal > Portals > Branding– This is specific toService Portal branding, not for global instance customization.

ServiceNow Branding Configuration

ServiceNow CSA Training Module: " System Properties and Branding "

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

To filter records in alist view, users can:

Click on thefilter icon.

Applyconditionsto refine the displayed records.

In the ServiceNow Configuration Management Database (CMDB), a Dependency View is the dedicated feature used to visually represent Configuration Items (CIs) and the relationships between them.

1. Functionality of Dependency Views:

Dependency Views (formerly known as BSM Maps) dynamically generate a graphical map of your IT infrastructure. When viewing a specific CI (like a database server), the Dependency View draws a network of nodes showing what services depend on that server (upstream relationships) and what underlying hardware or software that server relies upon (downstream relationships). This visualization is critical for incident impact analysis and change management planning.

2. Why the other options are incorrect:

A (Transform Map): This is used to map data from an Import Set table to a target ServiceNow table. It does not visualize CI relationships.

B (Flow Design): Flow Designer is a user interface for automating business processes and building workflows, completely unrelated to CMDB visualization.

C (Schema Map): While a Schema Map is a visualization tool, it shows the relationships between database tables (like how the Incident table extends the Task table), not the relationships between individual data records (CIs) within those tables.

Scripts that run in thebrowser (client-side)help controlUI behavior, form validation, and field interactionsin real-time without needing a server request.

Types of Client-Side Scripts in ServiceNow:Client Scripts

Run directly in the user ' s browser.

Used for form validation, auto-populating fields, or UI interactions.

Example:

javascript

CopyEdit

functiononLoad() {

g_form.setValue( ' priority ' , ' 2 ' );

}

UI Policies

Controlfield visibility, mandatory status, and read-only statedynamically.

Example: Ifcategory = Hardware, makeSerial Number field mandatory.

B. Access Control Scripts →Incorrect

Access Control Lists (ACLs)runserver-side, not in the browser.

C. Script Includes →Incorrect

Script Includesrunserver-sideand are used for reusable functions and API logic.

D. Business Rules →Incorrect

Business Rulesalso run on theserver, not in the browser.

Why Other Options Are Incorrect?

Client Scripts Overview

UI Policies in ServiceNow

Official ServiceNow Documentation Reference:

Assignment Rulesin ServiceNow automaticallyassign tasks(such as incidents, service requests, or change requests) to theappropriate group or individualbased on predefined criteria.

Acritical, high-priority service requestis created.

TheAssignment Rulechecks conditions (e.g., priority, category, requester, etc.).

The systemassignsthe request to the correctassignment group or individual.

How Assignment Rules Work:Example Scenario:

If an incident isPriority 1 (P1)and the category isNetwork, an assignment rule canautomatically route it to the " Network Support " group.

A. User Policy

No such feature exists in ServiceNow for task assignments.

B. UI Policy

UI Policies controlform behavior (visibility, field conditions, etc.), not assignment logic.

C. Predictive Intelligence

Predictive Intelligence usesmachine learningto suggest assignments, butAssignment Rulesare the primary mechanism for automatic task allocation.

To allow a new employee to work ontasks assigned to the Network and Hardware groups, they must have:

A User Account(sys_user) created in ServiceNow.

Group Membershipin both theNetworkandHardwaregroups.

E. Create User Account

Every user needs anaccount in ServiceNowbefore they can be assigned work.

C. Add User Account to Network Group

Membership in theNetwork groupallows the user to be assignedNetwork-related tasks.

F. Add User Account to Hardware Group

Membership in theHardware groupallows the user to work onHardware-related tasks.

A. Add User Account to itil group

While theitilrole grants access to ITSM functions, itdoes not automatically provide assignment rightsto the Network and Hardware groups.

B. Add User Account to ACL

Access Control Lists (ACLs)definepermissions, butgroup membership is requiredto receive assignments.

D. Add User Account to IT Knowledgebase

The IT Knowledge Base only grantsknowledge article access, not task assignments.

In ServiceNow,Access Control Rules (ACLs)determine user permissions for accessing tables, records, and fields. The evaluation order follows a structured hierarchy to ensure security and proper access control enforcement.

Table-Level Access Control– The system first checks if the user has access to the table. If the user does not have access at the table level, field-level ACLs are not evaluated.

Field-Level Access Control– If table access is granted, the system evaluates field-level access. A user must pass both the table-level and field-level conditions to access specific fields.

Row-Level Access– If there are row-level ACLs (e.g., access based on record ownership), they are also evaluated.

A. Ensures user has access to the fields in a table, before considering their access to the table– Incorrect because table access is evaluated first, not field access.

B. Ensures user can get to work as quickly as possible– Access controls prioritize security over speed, so this is not the primary result of ACL order evaluation.

C. Ensures user has access to the application, before evaluating access to a module within the application– Application access is controlled separately from ACLs and does not follow the same hierarchy.

In ServiceNow,tablesfollow an inheritance model, where tables can be extended from other tables. The distinction betweenBase Class tablesandParent Class tablesis as follows:

Base Class Table:

ABase Class table is not extended from any other table.

It exists at the top level in the table hierarchy.

Example:Task [task],Configuration Item [cmdb_ci] are base tables.

Parent Class Table:

AParent Class table may be extended from another tablebut also has tables extending from it.

It acts as a bridge between the base table and other extended tables.

Example:Change Request [change_request]extends fromTask [task] , makingTaskthe base class andChange Requesta parent class to other change-related tables.

A. Base Class tables always have tables extended from them, Parent tables do not have tables extended from them.

Incorrect because not all base tables have extensions.

Parent tablesdohave extended tables.

C. Extended tables can be extended from Parent tables or Base tables, but they cannot be extended from both.

Incorrect because extended tables caninheritfrom other extended tables in a multi-level hierarchy.

D. Extended tables are always extended from Parent tables, Extended tables are usually extended from Base tables.

Incorrect becauseextended tables can come from either Base or Parent tables, not just Parent tables.

Table Inheritance in ServiceNow

Extending Tables

Definitions:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

ATransform Mapin ServiceNow is used to define howimported datafrom external sources (such as CSV files, Excel sheets, or third-party integrations) is mapped into thetarget tablewithin the platform.

They allowadministratorsto definefield mappingsbetween theimport set tableand thetarget table.

Can includefield transformations, such as converting data formats or merging values.

Supportscriptedtransformations usingonBefore and onAfter scripts.

A. Field Transform– No such module exists in ServiceNow. Transform Maps handle field transformations.

C. Schema Map– The Schema Mapvisualizestable relationships but doesnothandle data imports.

D. Import Map– This isnot a valid ServiceNow module. The correct term isTransform Map.

ServiceNow Transform Maps Documentation

ServiceNow CSA Training Module: " Importing Data and Transform Maps "

Key Features of Transform Maps:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

TheActivity Streamin ServiceNow records allupdates, comments, work notes, and system eventsrelated to a record.

Tofilter the Activity log to show only Work Notes, follow these steps:

Locate theActivity Streamsection on the form.

Click theFunnel (Filter) icon.

SelectWork Notesto display only the relevant updates.

This allows thesubject matter expertto focus only onwork notesleft by other users, ensuring quick access to important information.

A. Click Context menu > Work Notes View

There isno default " Work Notes View " optionin the context menu for filtering the Activity log.

B. Click Personalize icon and select Activity Stream

ThePersonalize iconis used forUI preferences, not for filtering work notes.

C. Right-click form header > Form Layout > Add Work Notes Section

Adding a " Work Notes " field to the formdoes not filterthe existing activity log.

E. Click Context menu > History

TheHistory optiontracks user navigation and doesnot filter Work Notesin the Activity log.

InServiceNow,Flows (Flow Designer)is the recommended way tomanage multi-level approvals and notificationsfor catalog items like ordering a new iPhone.

Why Flows?

✔Automates Approval Processes– Flows allowsequential and parallel approval stepsto ensure that the request goes through multiple levels of approval.

✔Built-in Notifications– Automatically sendsemail or system notificationsto requesters andapprovers at each step.

✔Low-Code Solution– Eliminates the need for complex scripting by using agraphical interfaceto configure approvals and actions.

A user submits a request for anew iPhonethrough theService Catalog.

TheFlow Designer workflowstarts and routes the request to thefirst-level approver.

If approved, it moves to thesecond-level approver.

Notificationsare sent to the requestor and approvers at each step.

A. Parent-Child Approvers

No such built-in feature exists in ServiceNow. Approvals are handled viaFlow DesignerorWorkflow Engine.

B. Approval Chains

Approval Chains are not an officialServiceNow feature. The correct term isFlow Designer Approval Actions.

D. Approval Criteria

ServiceNow usesconditionsto define approval requirements, butApproval Criteriais not a standalone feature.

E. Approver Delegates

Delegates allow users toassign approvals to others, but theydo not manage multi-level approvals.

InServiceNow, aUseris arecordstored in theUser [sys_user]table. This table contains details about every user in the system, including theirname, email, roles, department, and more.

Stores Core User Information

Each user inServiceNow is represented as a record in this table.

Standard fields include:

User ID

Name

Email

Roles

Department

Location

Supports Authentication and Permissions

Users areassigned roles and groups, which controlwhat they can accessin ServiceNow.

Authentication methods likeLDAP, SSO, OAuth, and Local Authenticationrely on this table.

Integrates with Other ServiceNow Modules

Users insys_userare referenced in various tables, such as:

sys_user_role(User Roles)

sys_user_group(User Groups)

sys_user_has_role(Mapping between Users and Roles)

Key Characteristics of the User [sys_user] Table:

A. A user is a record stored in the User Preference [sys_user_preference] tableIncorrect– Thesys_user_preferencetablestores user-specific preferences (e.g., UI settings, default views), not user records.

B. A User is a record stored in the Profile [sys_user_profile] tableIncorrect– There isno standard " sys_user_profile " tablein ServiceNow.

C. A user is a field in the LDAP integrationIncorrect– WhileLDAP can import users into ServiceNow,users themselves are stored in the sys_user table, not in an LDAP-specific field.

Incorrect Answer Choices Analysis:

ServiceNow Docs – User Administration???? Managing Users in ServiceNow

ServiceNow Docs – User Table (sys_user)???? sys_user Table Overview

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

D. A user is a record stored in the User [sys_user] table

Alluser records in ServiceNow are stored in the sys_user table, making it the central repository foruser management, authentication, and access control.

ServiceNow usesImport Setsto bring data from various sources (such as CSV files, Excel spreadsheets, or external databases) into ServiceNow tables. Import Sets provide a flexible way to map incoming data into ServiceNow’s database structure.

A. Import Set

Import Setsare atemporary staging tablewhere external data is first loaded.

ATransform Mapis then used to map and transfer data from the Import Set table into thetarget table(e.g., Incident, Change Request, CMDB, etc.).

Common use cases:

Importinguser recordsfrom an external HR system.

MigratingCI datainto the CMDB.

Loadinghistorical incident recordsinto ServiceNow.

B. Update Set

Update Setsare used formoving customizations(such as UI changes, workflows, or scripts) between instances,not for importing data.

C. Data Pack

No such standard featurein ServiceNow called " Data Pack. "

Possibly confused withData Sources, which define external data locations but do not perform imports themselves.

D. Transform Set

Incorrect terminology—ServiceNow usesTransform Maps, not " Transform Sets. "

Transform Mapsdefine how data in anImport Setis mapped to target tables, but the import process itself is handled byImport Sets.

When importing data into ServiceNow via anImport Set, the system determines whether to update existing records or create new ones based on theCoalescefield setting.

If noCoalesce Fieldis defined,ServiceNow treats every imported row as a new record.

The import process doesnotcheck for existing records, meaning no records in the target table are updated.

This can result induplicate entriesif the imported data includes records that already exist in the target table.

ACoalesce Fieldis used tomatchincoming data to existing records.

If a matching record is found, it is updated instead of inserting a new one.

If no matching record is found, a new record is created.

Behavior When No Coalesce Field is Specified:How Coalescing Works:Incorrect Answers Explanation:A.All rows are rejected from the import, as coalesce field is required

This is incorrect because the import does not require a coalesce field to proceed. The system will still import all rows.C.Duplicate rows are rejected from the import

Without a coalesce field, duplicates arenotrejected. Instead, every row is inserted as a new record, even if it already exists in the target table.D.All rows are treated as new records, but errors will be flagged in the import log

Errors are only flagged in cases ofdata mismatches, validation failures, or incorrect mappings, not just because coalescing is missing.

ServiceNow Documentation→ " Importing Data - Coalescing Best Practices "

ServiceNow Import Set Documentation→ " Understanding Import Set Behavior Without Coalescing "

References from Certified System Administrator (CSA) Documentation:

Detailed Explanation:

To assign a task to themselves, users in ServiceNow can:

Option A:Use the check box to select the record, then click the Person icon to assign it.

Option B:Select the Task number and use theAssign to meUI action available on the form. These methods provide quick ways for users to take ownership of tasks directly from the list view. (Reference: ServiceNow Documentation - Task Assignment and List Actions)

Detailed Explanation:

In ServiceNow, users with the Impersonate role can impersonate other users to troubleshoot and validate user permissions and experiences. However,System Administratoraccounts cannot be impersonated to maintain security and prevent unintended administrative access. This restriction ensures that sensitive administrative functions are secure and can only be accessed directly. (Reference: ServiceNow Documentation - User Impersonation and Security Restrictions)

=================

In ServiceNow, anUpdate Setis a mechanism used to package and transfer customizations from one instance to another. TheDefault Update Setis automatically created for every instance and captures all unassigned configuration changes. However, it is considered abest practice not to use the Default Update Set for moving customizations between instances.

Lack of Organization & Traceability

The Default Update Set collects all modifications automatically, making it difficult to track specific changes related to a particular project or feature.

If multiple administrators or developers work in an instance, their changes will all be mixed together in the Default Update Set, leading to confusion and conflicts.

Risk of Losing Changes

Default Update Sets are not automaticallycomplete. Since users can forget to mark their customizations explicitly for an update set, some changes might not get captured.

If a system admin forgets to move a customization into a named update set, those changes may not be included in the migration process.

Cannot Be Moved Between Instances

The Default Update Setcannot be retrieved or movedbetween instances because it is system-managed. This makes itimpossibleto use it for transferring customizations effectively.

Named Update Sets, on the other hand, allow developers to package only the required changes for controlled migration.

Best Practice: Use Named Update Sets

It is highly recommended to create anamed Update Set(e.g., " Incident_Enhancements_Q1_2025 " ) for each set of related changes.

This provides a structured way to track, test, and promote configurations fromdevelopment → test → production environmentsin a controlled manner.

A. Merge Default Update Sets before moving between instancesIncorrect – The Default Update Set cannot be moved between instances, so merging it would not serve any purpose.

B. Submit Default Update Set to Application RepositoryIncorrect – The Application Repository is used forScoped Applications, not for update sets. The Default Update Set is system-managed and should not be used for structured deployments.

D. Keep Default Update Set to a maximum of 20 records, for troubleshooting purposesIncorrect – While keeping the Default Update Set small might be useful for tracking small changes, there is no such best practice limit of " 20 records. " It is still not recommended for migrations.

ServiceNow Product Documentation – Update Sets Best Practices???? Update Set Best Practices

ServiceNow Community Best Practices – Managing Update Sets???? Managing Update Sets

Reasons Why You Should Not Use the Default Update Set for Moving Between Instances:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. You should not use the Default Update Set for moving between instances.The best practice is to always createnamed Update Setsto ensure controlled, traceable, and reliable migrations of customizations between ServiceNow instances.

In ServiceNow, when working with large lists of records, users canquickly filterrecords based on specific column values using built-in list functionalities.

A. On the list, locate and right-click on the value Hardware, select Show Matching

This is thefastestway to filter a list.

Steps:

Locate a record with theCategory = Hardwarevalue.

Right-clickon the word " Hardware. "

Select " Show Matching " from the context menu.

The list is now filtered to display only records withCategory = Hardware.

B. Click Funnel icon, type Hardware, and click enter

TheFunnel icon(Filter) is used to createadvanced filters, but youcannot directly type " Hardware " into it.

You would need to manually create a filter condition:

Category→is→Hardware

C. On the Category column header, right-click and select Show > Hardware

Incorrect terminology—There is no " Show > Hardware " option.

Instead, you would need to useShow Matching(Answer A).

D. Right-click on magnifier, type Hardware, and click enter

There is no " magnifier " (search icon) method that filters records this way.

E. On Breadcrumb, click > icon, type Hardware, and click enter

Breadcrumbsprovide a visual representation ofexisting filters, but you cannotdirectly type values into breadcrumbs.

ServiceNowNotificationsare used to inform users about events or activities occurring within the system. They can be triggered based on system events and can be delivered via multiple channels, such as email, SMS, and push notifications.

How Notifications Work:

Triggered by events (e.g., when an incident is assigned to a user).

Configurable throughSystem Notification > Email > Notifications.

Can be sent viaEmail, SMS, or Push Notifications.

B. Alerts– Alerts provide system messages but are not tied to the notification system.

C. Texts– Not a ServiceNow feature; SMS notifications are handled within the Notification system.

D. Events– Events trigger notifications but do not directly inform users.

E. Emails– Email is one of thedelivery methodsfor notifications, butNotificationsis the actual ServiceNow feature managing them.

In ServiceNow, user records are stored in thesys_usertable. This table contains all user-related information such as username, email, department, roles, and active status.

sys_user Table Structure:

Stores all user accounts in the system.

Contains fields likeuser_name,email,first_name,last_name, androles.

Administrators can manage users viaUser Administration > Usersin the ServiceNow navigation panel.

B. User [sn_user]– There is no such table namedsn_userin ServiceNow.

C. User [u_sys_user]– Theu_prefix indicates a custom table, which is not the default ServiceNow table.

D. User [s_user]– This table does not exist in ServiceNow.

UI Policiesin ServiceNow dynamically control form field behaviorswithout scripting. They help maintaindata consistencyand improve user experience.

B. Setting fields hidden

UI Policies canhideform fields based on conditions.

Example: Hide the " Resolution Notes " field unlessState = Resolved.

D. Setting fields read-only

UI Policies canmake fields read-onlyto prevent users from modifying certain data.

Example: Set " Requested For " fieldread-onlyafter submission.

E. Setting fields mandatory

UI Policies canenforce mandatory fieldsbased on conditions.

Example: Make the " Justification " field mandatory ifPriority = High.

A. Setting fields to accept the data with ‘n’ number of characters

Field length restrictions are set in theDictionary Definition, not UI Policies.

C. Setting fields to accept the data in an expected format

Data formatting (e.g., date, phone number) is controlled byField Types and Data Policies, not UI Policies.

In ServiceNow, a useronlysees modules and records they have permission for, based onroles and group memberships. If an IT user can only seeSelf-Service, it ' s likely because theylack the required rolesfor IT tasks.

B. His user account does not belong to any groups that contain the ITIL role

TheITIL roleis assigned viauser groups(e.g., " Service Desk, " " IT Support " ).

If the user is not in anITIL role group, theywill notsee IT-related modules.

D. His user account does not have the ITIL role

TheITIL role (itil)is required to accessIncidents, Changes, Tasks, and Service Catalog Management.

Without it, the useronlyseesSelf-Serviceoptions (e.g., requesting services, reporting issues).

A. His user account failed LDAP authentication

If LDAP authentication failed, the userwould not be able to log in at all.

The issue here isrole-based access, not authentication.

C. His user account was not approved by his manager

User approval may be required for account creation, butit does not affect role permissions.

E. His user account is not logged in properly

If the user was not logged in properly, theywould not see any homepage at all.

The issue here islimited access due to missing roles.

The Shared Responsibility Model in ServiceNow clearly delineates responsibilities between the cloud service provider (ServiceNow) and the customer. ServiceNow manages the infrastructure, including the physical data centers, networking, hardware, and media disposal and destruction, ensuring proper security of the underlying platform. Hence, Media disposal and destruction and Infrastructure management fall under the provider’s responsibility.

The customer is responsible for their data, including backup and restore, access management (authentication and authorization), and encryption configuration on their data. While ServiceNow provides encryption capabilities, the customer must configure and manage encryption keys and access controls.

This model is critical for maintaining security and compliance in cloud environments and is explicitly detailed in ServiceNow’s official documentation and cloud security best practices.

Tofilter a long list of recordsand find those whereShort Description contains " email " , the best practice is to use thecolumn searchfeature:

Click the List Magnifier (???? )to open thecolumn searchoptions.

In the " Short Description " column search box, type:

Steps to Filter a List by " email " in Short Description:email

Press Enterto apply the filter.

This methodautomatically applies a " contains " filter, meaning it will showany records where " email " appears anywhere in the Short Description field.

A. Click List Magnifier to expand column search, on Short Description, type %email, click enter →Incorrect

% (percent sign) is not a valid wildcardin ServiceNow ' s list filters.

C. On Search box, select text, type email, click enter →Incorrect

Theglobal search box searches across multiple tables, not just the Short Description field.

D. Click List Magnifier to expand column search, on Short Description type ' email, click enter →Incorrect

Single quotes ( ' email ' ) are not requiredin column searches.

Why Other Options Are Incorrect?

Using List Filters in ServiceNow

ServiceNow Search Operators

Official ServiceNow Documentation Reference:

✔Form Builderis used todesign and modify formsthat users interact with when entering and updating records.

Key Features of Form Builder:

Drag-and-drop interface toadd, remove, or rearrange fields.

Supportssections, tabs, and related lists.

Enables quick modification of forms without writing scripts.

Option A (Generate analytical reports)is incorrect because reports are created using theReport Designer, not Form Builder.

Option C (Create new tables)is incorrect because tables are created viaTable Builderor directly in the Table module.

Option D (Configure system settings and permissions)is incorrect because permissions are managed throughroles, ACLs, and system properties.

???? Reference:ServiceNow Platform UI – Form Builder Guide

The icon highlighted in the image is theReference Icon(iinside a circle). It is used forReference fieldsin ServiceNow forms.

AReference fieldlinks to a record in another table (e.g., theCallerfield in anIncidentform references thesys_usertable).

Clicking theReference Icon (i)opens apreviewof the referenced recordwithout navigating away from the form.

This feature is helpful forquickly viewing user details, CI information, or related records.

A. Drilldown– This term is not used for form field behavior in ServiceNow; " drilldowns " are usually associated with reports.

B. Lookup– While lookups are used to search for values, they do not display previews of referenced records.

C. Quickview– This is not a defined ServiceNow field type.

D. Preview– While the icon allows previewing, the correct term isReference field, not " Preview field. "

E. Snapshot– No such field type exists in ServiceNow.

ServiceNow Reference Fields & Preview

ServiceNow CSA Training Module: " Configuring Forms and Fields – Reference Fields and Their Behavior "

How Reference Fields Work:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

When a user places an order through theService Catalog, it generates aRequest [sc_request]record in ServiceNow.

How to View Service Catalog Requests:???? Navigation Path:

All > Service Catalog > Requests

This module displays:

All submitted service catalog requests

Theircurrent status(e.g., Pending Approval, Fulfilled)

AssociatedRequested Items (RITM) and Tasks (SCTASK)

A. All > Service Catalog > Open Records > Items →Incorrect

The " Items " module does not show submitted requests; it listsavailable catalog items.

B. In the Navigation Filter, type ' requests ' and press Enter →Incorrect

Typing " requests " might bring up multiple unrelated records, making it inefficient.

The correct approach is to navigate toService Catalog > Requests.

C. All > Tables and Columns > Taste →Incorrect

" Tables and Columns " is used fortable managementand is not related to service catalog requests.

Also, " Taste " is atypo(likely meant to be " Tasks " ).

Why Other Options Are Incorrect?

Service Catalog Requests Overview

Official ServiceNow Documentation Reference:

In ServiceNow Access Control Lists (ACLs), the wildcards used to define rules follow a specific syntax: table_name.field_name.

1. The Wildcard (*):

The asterisk * represents " all " or " the rest. "

incident.* : This is a field-level ACL. It applies to every field on the incident table that does not have a specific ACL defined for it. For example, if you have an ACL for incident.short_description and an ACL for incident.* , the .* rule covers everything else (Priority, State, Caller, etc.).

2. The Record Level (None):

incident.None (often displayed just as incident ): This is a record-level ACL. It grants access to the row (the record itself). A user needs access to the record ( incident.None ) and the field ( incident.* ) to view or edit data.

3. Why other options are incorrect:

A & B: These use invalid syntax ( < == > , .all ) that does not exist in the ServiceNow ACL definitions.

C: This appears to be a syntactical error or a distractor. The pipe symbols ( | ) are not used in ACL name definitions.

In ServiceNow,Core Tablesare foundational tables that are included by default in the platform. These tables store essential records used across various applications and modules.

???? Key Core Tables in ServiceNow:

Task (task)– A core table that serves as the parent for several other tables, such as Incident, Change, and Problem.

User (sys_user)– Stores all user records in the instance.

Incident (incident)– A child table oftask, used to track issues and requests reported by users.

???? Why Option C is Correct?

User (sys_user)– Essential for user management in ServiceNow.

Task (task)– A fundamental table that many other tables extend from.

Incident (incident)– A widely used table in IT Service Management (ITSM), which extends fromtask.

???? Incorrect Options Explained:

A. Configuration, Connect, Chat– Configuration is broad and does not refer to a single table, and Connect and Chat are part of ServiceNow’s communication framework but are notcoretables.

B. Team, Party, Awards– These tables do not exist in ServiceNow’s core platform.

D. Work, Caller, Timecard– WhileCallermay refer to users, andTimecardis a table used in time-tracking applications, these are not considered core tables.

???? Reference:

Creating Tables in ServiceNow

ServiceNow Task Table Documentation

Understanding Core Tables in ServiceNow

In Visualization Designer, used in the Performance Analytics and Reporting space of ServiceNow, the " Preview " button is used to execute the current visualization setup and show how the filters and conditions apply to your data. This allows the report builder to validate the design without finalizing or publishing it.

Try: Not an available action in Visualization Designer.

Execute: More related to scripting or automation contexts.

Run: Used in reports or scripts but not the specific action in Visualization Designer.