CSA ServiceNow Certified System Administrator Questions and Answers

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:

To add a field to a form in ServiceNow, you can use two primary methods:

How to access:Right-click on the form header → SelectConfigure > Form Layout

Functionality:

Provides a simple interface toadd, remove, or reorder fieldson a form.

Allows adding new fields directly from the available database fields.

Suitable for basic form modifications without needing a drag-and-drop UI.

How to access:Click on thecontext menu(three horizontal bars on the top-left of the form) → SelectConfigure > Form Designer

Functionality:

Adrag-and-dropinterface to add, remove, or rearrange fields easily.

Enables more advanced customization, such as addingsections and UI policies.

Provides a visual representation of the form’s structure.

1. Configure > Form Layout2. Configure > Form Designer

Incorrect Answer Choices Explanation:A. Select Fields and Columns module– No such module exists for direct form editing. Fields are defined at the table level but not directly added to forms here.

D. Select Field Class Manager module– This module does not exist; it is not used for adding fields to forms.

ServiceNow Documentation: Form ConfigurationConfigure a Form

ServiceNow Form Designer GuideForm Designer

Official CSA Documentation Reference:

Thethree-bar iconin theForm headerof ServiceNow is commonly referred to as theHamburger icon. It provides access toadditional form actionsthrough acontext menu.

Opens adrop-down menuwith options such as:

Configure Form Layout

Configure Form Design

Insert and Stay

View History

Export Options

Helps users accessquick actionswithout navigating away from the form.

The icon consists ofthree horizontal lines, resembling ahamburger(bun-patty-bun).

This naming convention is widely used in web and mobile UI design.

Functions of the Hamburger Icon in ServiceNow:Why is it Called a " Hamburger Icon " ?

Incorrect Answer Choices Explanation:A. Pancake Icon– No such term exists in ServiceNow UI terminology.

B. Additional Actions or Context Menu– While the icondoesprovide additional actions, " Context Menu " refers to right-click options or three-dot menus, not the three-bar menu.

D. Cake Icon– No such UI term exists in ServiceNow or general UI design.

Understanding the ServiceNow Form Header

ServiceNow UI Overview

Official CSA Documentation Reference:

InServiceNow, aTemplateis a tool used topre-fill commonly used fieldsin a form, saving time and ensuring consistency in data entry.

ATemplateis a predefined set offield valuesthat can be applied to a form toautomatically populate fields.

Users can create and apply templates tospeed up form completionandreduce errors.

Templates are especially useful forstandardized requests, such asincident logging, change requests, or task assignments.

Create a Template:

Navigate toSystem UI → Templates.

Define thefieldsand their default values.

Assign the template to aspecific table(e.g.,incident,change_request).

Apply a Template to a Form:

When filling out a form, users canselect a templatefrom theTemplate Bar.

The templateautomatically populatesthe pre-configured fields.

Example Use Case:

Scenario:A Service Desk agent frequently logs incidents forpassword resets.

Solution:A " Password Reset " template can be created with:

Short Description: " Password reset request "

Category: " Access "

Assignment Group: " IT Support "

When an agent applies this template, these fields areautomatically populated, saving time.

What is a Template in ServiceNow?How to Use a Template?

Why Option A (Template) is Correct?Templates are the official ServiceNow tool for pre-filling commonly used fields in a form.

Why Other Options Are Incorrect?B. Reference Qualifier→ Incorrect

Reference Qualifierscontrolwhich values appear in a reference field(e.g., filtering available users in theAssigned Tofield).

They donot populate fields automatically.

C. Formatter→ Incorrect

AFormatteris a UI component thatdisplays additional information(e.g., anActivity Formattershows an activity log).

It doesnot populate form fields.

D. Assignment Rule→ Incorrect

Assignment Rulesautomaticallyassign recordsto users or groups based on conditions.

They donot populate multiple fieldsin a form.

ServiceNow Docs – Creating and Using Templateshttps://docs.servicenow.com

ServiceNow Learning – Templates and Data Population

ServiceNow Best Practices – Using Templates for Efficiency

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.

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:

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:

Thecorrect answer is " Flows " , which refers toFlow Designerin ServiceNow.

Flow Designeris ano-code/low-code automation toolthat allows users to automatebusiness logicfor a specific application or process, such as:

Approvals

Task creation

Notifications

Record operations(such as updating or deleting records)

AFlowis a sequence of automated actions that are triggered by specific events.

It ispart of Flow Designer, which is themodern alternative to the legacy Workflow Engine.

It providestrigger-based execution, meaning it can run when a record is created, updated, or upon a specific condition.

B. Action Sequences(Incorrect)

No such term exists in ServiceNow.

C. Action Sets(Incorrect)

No such feature exists in ServiceNow.

D. Task Flows(Incorrect)

This is not a term used in ServiceNow automation.

E. Flow Diagrams(Incorrect)

While Flow Designervisually representsflows, there isno feature named " Flow Diagrams " in ServiceNow.

Flow Designer Overview:https://docs.servicenow.com/bundle/utah-automation/page/administer/flow-designer/concept/flow-designer.html

How to Create and Use Flows:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/task/t_CreateFlow.html

Why " Flows " is the Correct Answer: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:

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.

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.

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 Overview:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/concept/flow-designer.html

Building Flows in Flow Designer:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/task/t_CreateFlow.html

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

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.

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.

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.

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, tables are structured in a hierarchical format wheresome tables can extend others, inheriting fields and properties. However, there are specific tables thatdo not extend any other table but can be extended—these are known asBase Tables.

Base Tables:

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

It serves as afoundationfor creating new tables.

Example:

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

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

Core Tables:

Core Tablesare thestandard tablesprovided by ServiceNow.

Theycan be base tables or extended tablesdepending on their role.

Example:

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

Extended Tables:

Extended Tablesare tables thatinherit fields and functionalityfrom aparent table.

Example:

Incident (incident)extends fromTask (task).

Custom Tables:

Custom Tablesare tables thatdevelopers create for specific business needs.

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

Understanding Table Types in ServiceNow

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

These tablesdo not inherit fieldsfrom any other table.

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

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

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

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

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

C. " Extended Tables "

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

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

D. " Custom Tables "

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

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

ServiceNow CSA Study Guide – Data Schema & Tables

ServiceNow Docs: Table Hierarchy & Extensions(ServiceNow Documentation)

ServiceNow Data Model Overview (Base Tables & Extended Tables)

References from the Certified System Administrator (CSA) Documentation:

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:

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

Local Database Authentication

This is the default authentication method used in ServiceNow.

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

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

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

LDAP (Lightweight Directory Access Protocol)

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

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

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

SSO (Single Sign-On)

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

ServiceNow supports various SSO protocols, including:

SAML 2.0 (Security Assertion Markup Language)

OAuth 2.0

OpenID Connect

Kerberos

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

A. XML feed–

XML feeds are used for data exchange,not authentication.

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

E. FTP authentication–

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

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

ServiceNow CSA Official Training Guide (User Authentication & Security)

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

InPerformance Analytics (PA),long-term signalsarekey performance indicators (KPIs) that help organizations make data-driven decisions for sustained workflow stability. These KPIs providetrends over time, allowing businesses to analyze patterns, predict future performance, and optimize workflows for efficiency.

Track Trends Over Time→ Identify slow-moving changes and patterns.

Support Predictive Analysis→ Help in making data-driven strategic decisions.

Reduce Unplanned Changes→ Avoid reactive decisions by monitoringhistorical data.

Incident Backlog Over Time→ Measures incident accumulation to prevent delays.

Change Success Rate→ Analyzes how well changes are implemented without failures.

Mean Time to Resolution (MTTR)→ Tracks how long it takes to resolve incidents.

How Long-Term Signals Help in Workflow Stability:Example KPIs Used in Performance Analytics:

Why " A. Long-term signals " is Correct:Long-term signals provide historical trends that help organizations maintain stable workflows.

B. Non-signals→No such term exists in Performance Analytics.

C. Anti-signals→Not a recognized Performance Analytics term.

D. Stability signals→Misleading term; long-term signalsare what provide stability insights.

Why Other Options Are Incorrect:

ServiceNow Documentation:Performance Analytics Overview

CSA Exam Guide:Coverslong-term KPI tracking for workflow stability.

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

A. Long-term signals

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 Filtershttps://docs.servicenow.com

ServiceNow Learning – Query Builder and Conditions

ServiceNow Best Practices – Using Filters in Lists and Reports

References from Certified System Administrator (CSA) Documentation:

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

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

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

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

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

A. Form–

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

It does not provide a multi-widget interface.

B. List–

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

D. Timeline–

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

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

ServiceNow CSA Official Training Guide (Reporting & Dashboards)

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

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:

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:

In ServiceNow, every record in a table has a unique 32-character identifier calledsys_id. This ID uniquely identifies a record and is stored in thesys_id fieldfor every table.

sys_id is a globally unique identifierassigned to every record in ServiceNow.

It is a 32-character hexadecimal string, ensuring uniqueness across instances.

It remains constant for a record, even if other fields in the record are modified.

sys_id is used in API calls, reference fields, and update setsto track records across environments.

A. sn_rec_id:No such field in ServiceNow.

B. rec_id:Not a valid field in ServiceNow.

C. u_id:Not a standard ServiceNow field. Custom fields may use " u_ " prefix butu_id is not a system field.

E. sn_gu_id:No such field in ServiceNow.

F. sn_sys_id:No such standard field in ServiceNow.

G. id:Generic term, but not a standard field in ServiceNow.

ServiceNow Data Model and sys_id Explained: ServiceNow Docs

sys_id Best Practices for Data Management

Why is the Correct Answer " sys_id " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:Thesys_idis crucial for tracking and managing records efficiently in ServiceNow and plays a key role in integrations, workflows, and automation.

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, 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, 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 Overviewhttps://docs.servicenow.com

ServiceNow Learning – Self-Service & Service Catalog Best Practices

References from 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:

In ServiceNow,Pluginsare used to activate additional applications or functionalities within a development instance. A plugin is apackage of features, configurations, and applicationsthat extends the platform’s capabilities.

Plugins introduce new capabilities– They allow you to enable or disable specific functionalities, such as ITSM, CMDB, HR Service Delivery, and Performance Analytics.

Plugins can be installed or activatedfrom theSystem Definition > Pluginsmodule.

Some plugins are available by default, while others require activation by an administrator or ServiceNow support.

Plugins can depend on other plugins, meaning some functionality requires multiple plugins to be activated.

A. App Package:No such term in ServiceNow. Applications in ServiceNow are delivered viaPlugins or App Engine Studio, not " App Package. "

B. Updated Pack:Not a ServiceNow term. ServiceNow updates are delivered aspatches or application updates, not an " Updated Pack. "

C. Patch:Apatchis a minor update or bug fix released by ServiceNow but does not introduce new functionality.

E. App Updated Set:Update Setstrack changes in a development instance but are used formigrating configurationsbetween instances, not for activating functionality.

ServiceNow Plugins Documentation:ServiceNow Docs

Managing and Activating Plugins in ServiceNow(Admin Guide)

Why is the Correct Answer " Plugin " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:

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 ServiceNowhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/events/reference/r_Events.html

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.

AnUpdate SetinServiceNowis a mechanism for capturing and migratingcustomizations and configurationsfrom one instance to another (e.g.,Development → Test → Production).

What is Captured in an Update Set?Update Sets recordconfiguration changes, such as:

Tables & Database Schema Changes(e.g., new tables, modified fields)

Form Layout & UI Changes(e.g., changes in form views, UI policies)

Schedules(e.g., Scheduled Jobs, Business Rules with scheduled actions)

Client Scripts(e.g., JavaScript running on the client side)

Business Rules, UI Actions, UI Policies

Workflows, Script Includes, ACLs (Access Control Rules)

Email Notifications, Dictionary Entries, Application Menus

What is NOT Captured in an Update Set?Data Records (e.g., Incident, Change Request, CMDB data)

Group Memberships & User Data

System Properties (some properties may require manual migration)

Attachments & Scheduled Reports

B. Changes made to tables, forms, views, and fields(Incorrect)

Views and Fieldsare part of UI changes, butschedules and client scriptsare also included in Update Sets, makingOption A more complete.

C. Changes made to tables, forms, Business Rules, and data records(Incorrect)

Data records (actual table entries like incidents or change requests) are NOT captured in Update Sets.

D. Changes made to tables, forms, groups, and configuration items (CIs)(Incorrect)

Groups and CIs (CMDB data) are considered data and are NOT included in Update Sets.

Instead,CIs should be migrated using Import Sets or CMDB data export/import.

Why Other Options Are Incorrect?

Understanding Update Sets

Update Sets Overview

What Gets Captured in Update Sets?

Best Practices for Using Update Sets

References from ServiceNow CSA Documentation:

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:

UI Policies and UI Actionsare both part of theServiceNow user interface customizationbut serve different purposes.

Used todynamically change form field behaviorsbased on specific conditions.

Canmake fields read-only, mandatory, or hiddenwithout requiring scripts.

Runson the client-side (browser)to improve performance and responsiveness.

Example:

If theCategoryisHardware, theSerial Numberfield becomesmandatory.

Used tocreate buttons, links, and context menu actions.

Can executescriptsto perform specific actions when clicked.

Runs on theserver-side or client-sidedepending on configuration.

Example:

A " Save " buttonthat becomesvisible only to users with a specific role.

UI Policy(not UI Action) is responsible for making fieldsread-only, mandatory, or hidden.

UI Action(not UI Policy) is responsible for making aSave button visiblefor specific users.

ServiceNow Docs: UI Policy Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIPolicies.html

ServiceNow Docs: UI Action Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIActions.html

UI Policy:UI Action:Why Option A is Incorrect?References from Certified System Administrator (CSA) Documentation:

n ServiceNow, theList Editorallows users to edit field values directly within a list without opening the record in a form. This feature is particularly useful for making quick modifications to multiple records without the need to open each one individually.

Users navigate to a list view of records (e.g., an incident list).

If a field is editable via the List Editor, clicking on it will allow inline editing.

After making changes, users can pressEnteror click outside the field to save.

Inline Editing:Users can modify fields directly from the list.

Multi-Row Editing:Certain fields support bulk updates.

Security Controls:Admins can control which fields are editable via List Editor through dictionary settings.

Audit and History Tracking:Changes made via List Editor are logged for tracking purposes.

A. Data Editor:No such term as " Data Editor " exists in ServiceNow.

B. Edit Menu:This does not refer to inline editing; instead, it ' s a general menu for editing options.

D. Form Designer:Used for configuring form layouts, not for inline editing.

ServiceNow Product Documentation → Lists and List Editing

ServiceNow CSA Exam Guide → Covers List Editor as a core feature of instance configuration.

How List Editor Works:Key Features of List Editor:Why Other Options Are Incorrect:Reference from CSA Documentation:This verifies thatList Editoris the correct answer.

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.

When a new table is created inServiceNowby extending another table, it followstable inheritanceprinciples. This means the newly created table (child table) receives all the fields from its parent table. Additionally, the new table can includecustom fieldsthat are unique to itself.

Here’s how inheritance works in ServiceNow when a table is extended:

Fields Inheritance:

The child table automatically inherits all fields from its parent table.

These inherited fieldscannot be removedfrom the child table but can be modified or overridden.

The child table can also have additionalcustom fieldsthat do not exist in the parent table.

Business Rules, Client Scripts, and UI Policies:

Unlike fields, these components arenot automatically inherited.

However, they can still affect the child tableif they are defined on the parent table using conditions that include the child table.

To apply them specifically to the child table, they need to beexplicitly definedfor the new table.

Access Control Rules (ACLs):

ACLs are not automatically inherited.

Each table in ServiceNow has its own set ofAccess Control Rules, which must be explicitly configured for the child table if different permissions are required.

Database Structure:

The child table creates aone-to-one relationshipwith the parent table, meaningall fields in the parent are available in the child table.

The new table is stored as a separate entity but references the parent table’s structure.

The child tableinherits all fieldsfrom the parent table.

The child table can also have its owncustom fields.

Business Rules, Client Scripts, UI Policies, and ACLs arenot automatically inherited, meaning options B and D are incorrect.

The tabledoes not archivethe parent table (making option A incorrect).

ServiceNow Product Documentation – Table Inheritance:https://docs.servicenow.com

ServiceNow Fundamentals – Table Relationships

ServiceNow Developer Portal – Extending Tables

ServiceNow Best Practices – Access Controls & Security Rules

Why Option C is Correct?References from Certified System Administrator (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 Stateshttps://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/knowledge-management/concept/knowledge-article-states.html

ServiceNow CSA Official Training Guide (Knowledge Management Lifecycle & Publishing Workflow)

Why is " Published " the Correct Answer?Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that aknowledge article must be in the " Published " stateto be visible to users in the Knowledge Base.

AUI Actionin ServiceNow can be configured toprompt or notify users when an action is completed, such as submitting an Incident. UI Actions are used to createbuttons, links, or context menu itemsthat trigger specific actions.

AUI Action(e.g., a " Submit " button on the Incident form) can be configured with asuccess messageusing thegs.addInfoMessage()function.

This message is displayed after the form submission to inform the user that theirIncident has been successfully submitted.

How UI Actions Can Prompt a Success Message:Example of a UI Action Script:javascript

CopyEdit

gs.addInfoMessage( " The incident has been successfully submitted. " );

This will display aconfirmation messageat the top of the page when an Incident is submitted.

Why " True " is the Correct Answer:UI Actions can display confirmation messages usinggs.addInfoMessage()or similar methods.

Why " False " is Incorrect:UI Actionscanbe used to provide user feedback, including success messages for actions like submitting an incident.

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 Reportshttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/use/using-lists/concept/filtering-lists.html

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.

TheKnowledge Base (KB) Searchfunctionality in ServiceNow is designed to help users find the most relevant articles efficiently. ServiceNow provides various sorting options for search results to ensure that users can access the most useful information.

Sorting Options in Knowledge Base Search:When users search for articles within a Knowledge Base, the results can be sorted using three primary criteria:

Most Recent Update (Option A)

This sorting method ranks articles based on theirlast modified date.

Newer or recently updated articles appear higher in the search results.

This ensures users see the most current information first.

Popularity (Option B)

Popularity is determined byuser interactionssuch as article views, feedback ratings, and usage.

More frequently accessed or positively rated articles are ranked higher.

This helps prioritize articles that have been helpful to other users.

Relevancy (Option C)

The ServiceNow platform uses aninternal search algorithmto determine relevance based on keywords, titles, and content within the article.

More relevant articles appear at the top, ensuring users get the most appropriate answers to their queries.

D. Manager Assignment (Incorrect)

Knowledge articles are not sorted by manager assignment.

Manager assignment applies to workflows and approvals, not to search ranking.

E. Number of Views (Incorrect)

While article popularity is a ranking factor,ServiceNow does not provide a direct " Sort by Number of Views " option.

The " popularity " metric includes views but also considersother engagement factorslike helpfulness ratings.

Why Are the Other Options Incorrect?

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Knowledge Management: Search and Filtering

???? ServiceNow Knowledge Management Docs

" Knowledge articles can be sorted byrelevance, popularity, or most recent updateto ensure users find the most useful and up-to-date information. "

Conclusion:The correct answers are:

A. Most recent update(Sorts by last modified date)

B. Popularity(Sorts based on article usage and engagement)

C. Relevancy(Sorts based on keyword matching and importance)

???? Understanding Knowledge Base search sorting is essential for ServiceNow administratorsto help users find the right information efficiently.

InServiceNow,User Impersonationallows anadmin or a user with the appropriate roleto temporarily act as another userwithout needing their password. This is mainly used fortesting and visibility, helping administrators and developers verify user permissions, role-based access, and UI experiences.

Testing Permissions & Roles

Ensures thatusers have the correct access rights(e.g., verifying ITIL user permissions for incident management).

Helps testUI Policies, Business Rules, and ACLs (Access Control Rules)by viewing the system from the perspective of different roles.

Debugging & Troubleshooting

Identifies why a usercannot access certain records or modules.

Helps inresolving permission-related issueswithout affecting live users.

Experience Validation

Ensures userssee the correct menus, fields, and optionsbased on their assigned roles.

Useful when developingnew applications, workflows, or Service Catalog items.

Admins and authorized userscan impersonate by clicking on their name in the top-right corner and selectingImpersonate User.

Once impersonated, all actions are logged for security and compliance.

Primary Functions of User Impersonation:How to Use Impersonation:

(A) Testing and visibility – Correct

The primary function ofuser impersonationis totest and verify what different users can see and doin the system.

It helps withdebugging UI, role-based access, ACLs, and workflow execution.

(B) Activate verbose logging – Incorrect

Verbose loggingis used fordetailed debugging and performance monitoring, butimpersonation does not enable logging features.

(C) View custom perspectives – Incorrect

ServiceNow doesnotuse the term " custom perspectives " in the context of impersonation.

Impersonationshows what a specific user sees based on their roles, but it doesnot create custom perspectives.

(D) Unlock Application master list – Incorrect

There isno such featureas an " Application Master List " that requires impersonation to unlock.

Application access is controlled byroles and permissions, not impersonation.

Explanation of Each Option:

Never impersonate a user without permission, especially in production environments.

All impersonation actions are loggedin the system for security and auditing purposes.

Use impersonation in a sub-production (development or test) instancebefore making changes to production.

Admins should use impersonation instead of logging in with test user accountsto maintain security and accountability.

Additional Notes & Best Practices:

ServiceNow Docs: Impersonating Users

https://docs.servicenow.com

ServiceNow Community: Best Practices for User Impersonation

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

InServiceNow, aListis a visual representation ofmultiple records from a table. Lists allow users to view, filter, sort, and interact with records in a structured tabular format.

Displays multiple recordsfrom a table.

Columns represent fieldsof the table.

Users can personalize the list(e.g., adjust columns, apply filters, and sort).

Common Actions:

Inline editing

Searching

Exporting data

Grouping and filtering

A. View

AViewdefines how data is displayed, but it is not a list itself.

Example: Differentform viewscan be created for the same table.

B. Dashboard

ADashboardis a visual representation of reports and performance analytics.

It doesnot display raw table recordsdirectly.

C. Panel

No such term as " Panel " exists in ServiceNow for displaying records from a table.

Key Features of Lists:Why Other Options Are Incorrect?

Lists Overview

ServiceNow Lists Documentation

Personalizing Lists

List Personalization Guide

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

InServiceNow, aDictionary Overrideallows an administrator tocustomize the properties of a fieldin achild tablewithout modifying the field in the parent table.

This is particularly useful intable inheritance scenarios, where a child tableinherits fields from a parent tablebut needs different behavior for certain fields.

Modify field properties(e.g.,mandatory,read-only,default value) inextended tables.

Preserve inheritancewhile allowing exceptions for specific child tables.

Avoid modifying the original dictionary definitionof a field at the parent table level.

Key Functions of Dictionary Overrides:Example of Dictionary Override in Action:Consider theTask Table (task), which is aparent tablefor many modules likeIncident, Change, and Problem.

TheTask Tablehas apriorityfield.

If theIncident Table (incident)needs to override thepriorityfield tomake it mandatory, an administrator can create aDictionary Overridefor thepriorityfield in theincidenttable.

Thepriorityfield in other child tables (e.g.,change_request,problem) remainsunaffected.

(A) A Dictionary Override is an incoming customer update in an Update Set which applies to the same objects as a newer local customer update – Incorrect

This definition describesUpdate Set Collisions, not Dictionary Overrides.

Update Set Collisions occur whenan update set applies changes to an object that has been modified locally.

(B) A Dictionary Override is the addition, modification, or removal of anything that could have an effect on IT services – Incorrect

This describesChange Management in ITSM, which tracks changes to IT services.

Dictionary Overrides specificallymodify field propertiesin extended tables.

(C) A Dictionary Override is a task within a workflow that requests an action before the workflow can continue – Incorrect

This describesApproval Actions in Workflows, not Dictionary Overrides.

Workflow approvalspauseexecution until an action is completed, but Dictionary Overrides donotfunction this way.

(D) A Dictionary Override sets field properties in extended tables – Correct

This is the correct definition.

Dictionary Overrides allow admins tocustomize field behavior in child tableswhile maintaining inheritance from parent tables.

Explanation of Each Option:

Use Dictionary Overrides sparinglyto avoid unnecessary complexity.

Always test changes in a sub-production environmentbefore applying them in production.

Document overrides properlyto help future administrators understand why an override was applied.

Use the " Dictionary Entry " (sys_dictionary) tableto view and manage dictionary overrides.

Additional Notes & Best Practices:

ServiceNow Docs: Dictionary Overrides Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for Dictionary Overrides

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Eventsplay a crucial role in theevent-driven architecture, allowing the system to respond dynamically to actions such as record updates, system notifications, and integrations.

There aretwo key componentsinvolved in event handling:

Event Registry

A table thatstores event definitions(i.e., predefined event names).

Defines which events can be triggered in the system.

Events in the registry arenot actual occurrences, but ratherpossible eventsthat can be triggered.

Located in thesys_event_registrytable.

Event Log

A log ofactual generated eventsthat have occurred in the system.

Whenever an event is triggered (e.g., record update, scheduled job, or integration), it gets recorded in theEvent Log.

Helps administrators track and troubleshoot event execution.

Stored in thesys_eventtable.

Why is Option A Correct? " Event Log contains generated Events, the Event Registry is a table of Event definitions. "

Event Registry = Defines possible events that can be triggered.

Event Log = Records actual events that have been triggered.

Why Are the Other Options Incorrect?B. " Event Log is formatted in the Log style, the Event Registry displays different fields. "

Misleading: While the log and registry have different layouts, the key difference isevent occurrences vs. event definitions, not just formatting.

C. " Event Log lists Events that were triggered by integrations, the Event Registry lists the Events that were triggered during the day (24-hour period). "

Incorrect:The Event Log tracks all triggered events, not just integrations.

TheEvent Registry does not track daily events, it just defines them.

D. " Event Log is the same as the Event Registry. "

Completely incorrect:The Event Logrecords actual event occurrences, while the Event Registrydefines possible eventsin the system.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Events and Event Processing

???? ServiceNow Event Management Documentation

" TheEvent Registry (sys_event_registry)contains event definitions that specify when an event can be generated. TheEvent Log (sys_event)records events that have actually occurred. "

Conclusion:The correct answer isA. Event Log contains generated Events, the Event Registry is a table of Event definitions.

???? Understanding the difference between the Event Log and Event Registry is crucial for troubleshooting, automation, and event-driven processing in ServiceNow.

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:

InServiceNow, agroupis acollection of userswho share common responsibilities, such as handling incidents, approvals, or service requests.

Groups are stored in thesys_user_grouptable

Eachgroupis arecord in thesys_user_grouptable, which manages user access and permissions.

Example: The " Service Desk " group (sys_user_grouprecord) may contain multiple IT support users.

Groups are used for role assignments

Instead of assigning roles directly to users,roles are assigned to groupsfor easier access management.

Groups can be used for approvals and task assignments

Groups are often assigned to handleapproval workflows, incident resolution, and change management tasks.

A. A group is one record stored in the Group Type [sys_user_group_type] table(Incorrect)

Thesys_user_group_typetable is used for categorizing groups,not storing actual group records.

C. A group defines a set of users that share the same location(Incorrect)

Incorrect: Groups arenot location-based; they are used fortask assignments, approvals, and permissions.

D. A group defines a set of users that share the same job title(Incorrect)

Incorrect: Users with the same job titlemay belong to different groupsbased on their responsibilities.

Key Details About Groups in ServiceNow:Why Other Options Are Incorrect?

Groups in ServiceNow

Managing User Groups

User and Group Management

ServiceNow User and Group Administration

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow 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 Sets:https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/import-sets/concept/c_ImportDataUsingImportSets.html

Load Data Module in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/import-sets/task/t_LoadData.html

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

InServiceNow Reporting,Function Fieldsare used toperform calculations, manipulate text, and transform datain a report. These fields allow users to applyarithmetic operations, coalescing, concatenation, and length calculationson existing data.

Arithmetic Operations– Performaddition, subtraction, multiplication, and divisionon numeric fields.

Coalesce– Combine multiple fields into one (useful for handling NULL values).

Concatenation– Join multiple string fields together (e.g., combining first and last names).

Length Calculation– Measure the length of a text field (e.g., checking character count in a description field).

Function fields aredesigned specifically for calculations and data transformationsin reports.

They allowadvanced data processing without requiring scripting.

A. Sourcing Fields→Incorrect

" Sourcing Fields " isnot a valid termin ServiceNow reporting.

C. Computational Fields→Incorrect

While this term sounds relevant,ServiceNow does not use " Computational Fields " in reporting.

D. Calculation Fields→Incorrect

" Calculation Fields " is not an official ServiceNow reporting term.

Function fields handle calculations, not a separate category called " Calculation Fields. "

Key Functions of Function Fields:Why is " B. Function Fields " the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Function Fields in Reportinghttps://docs.servicenow.com/en-US/bundle/utah-performance-analytics-and-reporting/page/use/reporting/concept/c_FunctionField.html

References from Certified System Administrator (CSA) Documentation:This confirms that " Function Fields " is the correct answerfor performingarithmetic, coalescing, concatenation, and length calculationsin reporting.

In ServiceNow, when defining afilter condition, theelement being filteredis called aField.

Afieldis an individual piece of data within atable(e.g.,Caller,State,Priorityin theIncidenttable).

The available fields in a filter depend on:

The table being filtered

User access rights (roles and permissions)

The columns (fields) available on the table

Understanding Fields in Filter Conditions:Example of a Filter Condition:css

CopyEdit

[ State ][ is ] [ In Progress ]

State→ This is aFieldin the table.

is→ This is theOperatorused for filtering.

In Progress→ This is theValuebeing compared.

A. Attribute– Attributes aremetadataabout a field but do not define filter conditions.

B. Label– The label is thedisplay nameof a field but is not used in filtering.

D. Column– While fields arestored as columnsin a database, in filtering, they are referred to asFields.

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

ServiceNow Filtering and Conditions

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

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Toimport articles into a Knowledge Base (KB)in ServiceNow, a user must have the " sn_knowledge_import " role. This role grants permission tobulk import knowledge articlesfrom sources like spreadsheets, text files, or external databases.

sn_knowledge_import–Required toimportarticles into a KB.

sn_knowledge_contribute–Allows users towrite and edit articlesbutnot importthem.

sn_knowledge_admin– Grantsfull admin controlover KB settings.

A. Can contribute

" Can Contribute " grants permission towrite/editarticles butnot import them.

B. sn_knowledge_contribute

This role only allowscreating and modifyingarticles. It doesnotgrant import access.

D. Can import

No such role or permission exists in ServiceNow.

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:

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:

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

Recording Customizations:

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

Capturing Related Records:

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

Update Sets capture theWorkflow Versionand associatedWorkflow Activities.

Exporting and Importing:

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

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

Commit the Update Set:

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

B. Workflows are moved using Transform Maps

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

C. Workflows are moved using Application Sets

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

D. Workflows cannot be moved between instances

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

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

ServiceNow Product Documentation - Update Sets

Update Sets Overview

Moving Customizations Using Update Sets

ServiceNow Workflows

Workflow Management

References from ServiceNow CSA Documentation:

In ServiceNow,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.

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.

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

https://docs.servicenow.com

ServiceNow Community Best Practices for Service Catalog Variables

https://community.servicenow.com

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

In ServiceNow, theglobal search baris located in theBanner Frame, which is thetopmost sectionof the user interface. Theglobal search featureallows users to search across multiple tables and records within the platform.

Searches across multiple record types(Incidents, Knowledge Articles, Change Requests, etc.).

Auto-suggests resultsas you type.

Filters resultsbased on user roles and permissions.

Uses indexingto improve search speed and efficiency.

Key Features of the Global Search in the Banner Frame:

Why " B. Banner frame " is Correct:TheBanner Framecontains theglobal search bar, which enables users to search across all available records in ServiceNow.

A. Application Navigator→The Application Navigator is used forbrowsing modules and applications, not for performing a global search.

C. List pane→The List Pane only displaysrecords from a specific table, and its search is limited to that list view.

D. Content frame→The Content Frame displaysforms, lists, and dashboards, but does not provide a global search function.

Why Other Options Are Incorrect:

ServiceNow Documentation:Global Search in ServiceNow

CSA Exam Guide:CoversBanner Frame and its functions, including Global Search.

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

B. Banner frame

In ServiceNow,Priorityis achoice field, meaning it has predefined values (e.g., 1 - Critical, 2 - High, etc.). If a customer wants to change the values to displayP1, P2, P3, P4consistently across all tasks, you must modify thechoice list valuesfor the Priority field.

Right-click on the Priority fieldin the Incident form.

Select“Show Choices”from the context menu.

In theChoice List Entriestable, modify theLabelvalues to match the internal terminology (P1, P2, P3, P4).

Ensure that the changes applyto all Task-related tables(such as Incident, Change, and Problem).

The“Show Choices”option displays the choice list for that specific field, allowing modifications to the values displayed in the dropdown.

This ensures consistency across all records using thePriorityfield.

A. Configure Lists:Configures list views,not choice field values.

B. Show Options:Not a valid option in ServiceNow for modifying choice fields.

C. Configure Task:Configures the task table settings,not choice list values.

E. Show Choice List:Not a valid ServiceNow menu option.

F. Configure Options:Not a valid option in ServiceNow for modifying choice fields.

Modifying Choice Lists in ServiceNow:ServiceNow Docs

How to Customize Dropdown Fields in ServiceNow

Steps to Modify the Priority Field Choices:Why is the Correct Answer " Show Choices " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:Using“Show Choices”, administrators can updatechoice valueswhile preserving the existingbackend values, ensuring consistency in workflows and reports.

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

Why These Options Are Correct?A. Make sure the latest flows are activated.

ServiceNowflow designerallows admins to create and manageapproval flowsfor catalog items.

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

C. Impersonate the requester to ensure the form works.

Impersonationallows administrators totest the user experiencewithout logging in as different users manually.

This is essential to verify thatnon-admin userscan correctlysubmit the requestand trigger the approval process.

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

Themanager approval flowrelies on the requester ' sManagerfield in their user record.

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

Why the Other Options Are Incorrect?B. Use the instance Incognito setting to quickly toggle between requester and approver.

There isno " Incognito setting " in ServiceNow to toggle users.

Thecorrect methodis using theimpersonatefeature.

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

WhileUpdate Setstrack customizations, they arenot required for testinga catalog item’s approval workflow.

Update Sets are primarily used formigrating changesbetween instances (e.g., from Dev to Test).

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

Admin accountsoverride approval workflowsand do not provide an accurate test.

The correct method is toimpersonate the requester and approver roles separatelyto ensure the workflow works as expected.

ServiceNow Flow Designer - Approval Workflow Testing Best Practices

ServiceNow Impersonation Feature for User Testing

ServiceNow ITSM - Catalog Item Testing & Validation

References to Official Certified System Administrator (CSA) Documentation:

Virtual Agentis ServiceNow’sAI-powered chatbotthat provides assistance via amessaging interface. It helps users obtain information, make decisions, and complete common tasks without human intervention.

Conversational Interface→ Users interact through chat to get information and perform tasks.

Automated Responses→ Uses predefinedtopicsandnatural language understanding (NLU)to provide relevant answers.

Integration with ServiceNow Applications→ Can create incidents, reset passwords, check order statuses, etc.

Available on Multiple Channels→ Works with Microsoft Teams, Slack, and the ServiceNow portal.

A. Agent Workspace→ A unified interface for agents to manage cases, not an AI chatbot.

B. Chat bot→ A generic term; Virtual Agent is the official chatbot in ServiceNow.

D. Knowledge Chat→ No such feature exists; however, Virtual Agent can integrate with the Knowledge Base.

E. Now Support→ ServiceNow’s customer support portal, not an AI-driven assistant.

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) Overview:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-level-management/concept/c_ServiceLevelAgreements.html

How SLAs Work in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-level-management/concept/slas-how-work.html

Key Features of SLAs in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

ServiceNow allowsa single Catalog Itemto be published tomultiple service catalogs, avoiding duplication while ensuring accessibility for the right users.

Instead ofcreating duplicate catalog items(which would require managing two separate items with the same functionality), we createone Catalog Itemandpublish it in both catalogs (HR and Facilities).

This approach ensurescentralized managementwhile maintaining accessibility for both departments.

It simplifies updates—any changes to the form or workflow will apply toboth catalogs automatically.

Why is Option B Correct?

Why Are the Other Options Incorrect?A. Create one Catalog Item for HR Event Room Set Up and one for Facilities Event Room Set Up; then publish each to the appropriate Catalog.

Incorrectbecause it createsduplicate catalog itemswith thesame functionality, increasing maintenance effort.

C. Create one Catalog Item for Event Room Set Up; then publish to the Parent Catalog, which is accessible to both HR and Facilities.

Incorrectbecausethere is no " Parent Catalog " conceptin ServiceNow.

ServiceNow allowspublishing a single item to multiple catalogs, but there is no need for aparent catalog.

D. Create one Catalog Item for Event Room Set Up; then use ACLs to control access.

Incorrectbecause ACLsrestrict access at a field, table, or record level, but theydo not control where a Catalog Item appears.

Thecorrect approachis topublish the item to multiple catalogsrather than using ACLs.

ServiceNow Service Catalog Management - Publishing Items to Multiple Catalogs

ServiceNow ITSM - Best Practices for Catalog Item Reusability

ServiceNow CSA Guide - Managing Service Catalogs and Items

References to Official 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:

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:

TheServiceNow platformprovides variousinterfacesfor users to interact with the system based on their role and requirements. These interfaces cater to different use cases, such as web-based, mobile, and portal-based access.

Now Mobile Apps (A) –Correct

ServiceNow providesNow Mobile applicationsfor bothiOS and Android.

These apps allow users to access self-service options, request services, check approvals, and complete tasks from mobile devices.

Apps includeNow Mobile, Field Service Mobile, and Mobile Agent.

Service Portals (D) –Correct

Service Portalsprovide auser-friendly web interfacethat allows users tosubmit requests, search for knowledge, and interact with catalog itemsin a simplified way.

Service Portals are customizable and used forself-service and customer-facing interactions.

Now Platform® User Interfaces (E) –Correct

This includes the standardUI16 (Current Web Interface), UI Builder for custom interfaces, and theClassic UIfor legacy systems.

Users can access ServiceNow throughdesktop web browsers, mobile web interfaces, and UI frameworks.

B. Agent Control Center(Incorrect)

No such predefined interface exists in ServiceNow as " Agent Control Center. "

C. Back Office Dashboard(Incorrect)

This is not a standard ServiceNow interface but may be a custom-built dashboard.

F. Field Service Taskboard(Incorrect)

This is afeaturewithinField Service Management (FSM), not a platform-wide interface.

ServiceNow User Interfaces Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html

Now Mobile App:https://docs.servicenow.com/en-US/bundle/utah-now-mobile/page/administer/service-now-mobile/concept/now-mobile-overview.html

Types of Interfaces in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

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

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

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

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

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

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

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

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

ACLs do not manageworkflowsor directly control group assignments.

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

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

D. security_admin(Incorrect)

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

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

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

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

Importingspreadsheet datainto a ServiceNow table follows a structured process that ensures data is accurately mapped and transformed before being added to the target table. The correct process consists of three main steps:

Navigate toSystem Import Sets > Load Data.

Upload thespreadsheet (CSV, Excel, etc.)or connect to anexternal data source.

The system creates anImport Set Tableto temporarily store the imported data.

ATransform Mapis created to definehow fields from the Import Setmap to fields in thetarget table(e.g.,incident,cmdb_ci).

Field mappingscan be manually configured orauto-mappedif field names match.

Coalesce fieldsare defined toprevent duplicate recordsby identifying unique keys.

TheTransform Mapis executed, transferring data from the Import Set to thefinal target table.

Anytransformation scripts(such as data conversions) are applied during this process.

The imported data is now available in the production table.

1. Load Data (Import Set Creation)2. Create Transform Map (Mapping Fields to Target Table)3. Run Transform (Apply Data to the Target Table)

B. Select Import Set, Select Transform Map, Run Transform

You must first load data before selecting an Import Set.Import Sets are createdafter data is loadedinto the system.

C. Select Data Source, Schedule Transform

WhileData Sourcesdefine where data comes from, theydo not load data directly.Scheduling transformationsis optional, but it ' s not the primary step-by-step method for importing data.

D. Define Data Source, Select Transform Map, Run Transform

Defining a Data Source is part of setting up external integrations, but it isnot required for a basic spreadsheet import.

Why Other Answers Are Incorrect:

ServiceNow Data Import and Transform Maps

ServiceNow CSA Training Module: " Importing Data and Managing Import Sets "

References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Knowledge Management,User Criteriais used to controlwho can view, contribute, or editknowledge articles and knowledge bases.

Scenario Requirements Breakdown:TheHR Knowledge Baseis already restricted to HR department members.

Anew knowledge articleneeds to be published in theQuarterly Reviewcategory.

OnlyHR Managersshould be able to read this specific article.

Best Approach (Correct Answer: D)Torestrict access to the article itself(not the entire knowledge base or category), we:

Open the knowledge article

Go to the " Can Read " field

Add a User Criteria that includes the " HR Manager " group

Publish the article

This ensures thatonly HR Managers can read this specific articlewhile the rest of the HR departmentcannotsee it.

A. On the Knowledge Base, add User Criteria with a Manager Can Read script to the Can Read list, publish article to any category

This would restrictall articlesin the knowledge base, not just the single article.

B. Add User Criteria for HR Manager Group on the Category’s Can Read list

User criteria canonly be applied at the Knowledge Base or Article level, not at the category level.

C. On the Knowledge Article, add an Access Control for HR Manager Group on the Can Read list, then publish article to any category

ACLs (Access Controls)are not used forKnowledge Article permissions. User Criteria is the correct method.

Managing User Criteria in Knowledge Management

Restricting Article Access

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

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:

TheAutomated Test Framework (ATF)is thebuilt-in testing frameworkin ServiceNow used totest applications, including Server-side scripts and logic.

Enablesautomated testing of ServiceNow applicationswithout manual effort.

Can testserver-sidescripts (e.g., Business Rules, Script Includes, and Workflows).

SupportsUI testingfor forms, lists, and portals.

Reduces testing time and enhancesrelease reliability.

ServiceNow is alow-code/no-codeplatform, so ATF provides aplatform-specifictesting tool.

ATF allowstest creation without coding, making it easy for administrators and developers to use.

Integrates with Continuous Integration (CI/CD) pipelinesto ensuresmooth updates.

Key Features of ATF:Why ATF is Used for Testing ServiceNow Applications?

A. Selenium →Incorrect

Seleniumis used forweb UI automation, but it isnot built into ServiceNow.

ATF is thepreferredtesting framework for ServiceNow applications.

B. Test Driven Framework (TDF) →Incorrect

No such frameworkcalled " Test Driven Framework " in ServiceNow.

TDD (Test-Driven Development)is asoftware development methodology, not a testing tool.

C. JUnit →Incorrect

JUnit is a Java-based testing frameworkused for Java applications.

ServiceNow scripts useJavaScript, not Java.

Why Other Options Are Incorrect?

Automated Test Framework (ATF)

Official ServiceNow Documentation Reference:

Importing data into ServiceNow involves usingImport Sets, which act astemporary staging tablesbefore transferring data to the target table. The correct sequence of steps is as follows:

Load the Data

Upload data from an external source (CSV, Excel, XML, JDBC, or API).

The data is stored in anImport Set table(temporary staging table).

Create Transform Map

ATransform Mapdefineshowdata from the Import Set should be mapped to thetarget table(e.g.,incident,cmdb_ci).

Example:Mapping " Full Name " in Import Set → " User Name " in sys_user table.

Transform Data

Executes theTransform Map, moving data from the Import Set into the target table.

Anydata conversion rules or business logic(such as field mapping, script processing) are applied.

Clean Up Import Table

After a successful import, thetemporary Import Set tablecan be deleted to free up space.

A. Select source file; Run automap; Transform data; Clean up target table

Automapis optional and does not apply in every scenario.

Cleaning up the target tableis incorrect—the cleanup applies to theImport Set table, not the target table.

B. Set up LDAP; Test map; Create update set; Run import; Apply update set

LDAP is foruser authentication, not for importing data.

Update Sets are used formoving configurations, notdata imports.

C. Identify source; Import transform map; Run transformer; Verify import

" Run transformer " is incorrect—the correct step is " Transform Data " .

Importing does not require averification step; instead, data is reviewed usingTransform History.

When working with along list of records, users canfilter dataquickly using theShow Matchingfeature.

C. On the list, locate and right-click on the value Hardware, select Show Matching

Right-clickingon the " Hardware " value and selecting " Show Matching " filters the list toonly show records where the Category is Hardware.

This is thefastestway to apply aquick filter.

A. On Breadcrumb, click the > icon, type Hardware and click enter

Breadcrumbsdo not support direct text inputfor filtering.

Breadcrumbs showexisting filtersbut are not used to type new values.

B. On the Category column header, right-click and select Show > Hardware

Incorrect menu option—There is no " Show > Hardware " selection.

Instead, users would need to use " Show Matching " (Correct Answer C).

D. Right-click on magnifier, type Hardware, and click enter

There isno " magnifier " optionfor filtering in list view.

E. Click Funnel icon, type Hardware and click enter

TheFunnel (Filter) iconis used to createadvanced filters, but it doesnotsupport direct text input like this.

The correct way to use theFilterwould be:

Click theFunnel icon

SetCategory = Hardware

ClickRun

In ServiceNow,related listsdisplay records that have a relationship with the current record based onreference fieldsordatabase relationships. When adding a related list to a form, users select from aList Collector, which shows available related lists based on table relationships.

B. Catalog Task → Parent

Catalog Tasksare individual work items that belong to aRequest Item (RITM).

TheParentfield links a Catalog Task to its correspondingRITM.

This related list allows users to view all Catalog Tasks associated with a parent request.

C. HR Case → Parent

InHR Service Delivery (HRSD), HR Cases track employee requests.

TheParentfield links an HR Case to a parent HR Case or HR Service Request.

This related list allows HR agents to see all related sub-cases.

D. Problem → Parent

Problem Recordscan have aParent-Childrelationship where a child problem is linked to a larger problem.

TheParentfield is used to establish this hierarchy.

This related list helps track all sub-problems linked to a main problem.

A. Release Phase == Parent

" Release Phase " is not a standard related list in ServiceNow.

TheRelease Management moduleusesphases, but they do not typically function as aParentreference.

E. Outage → Task Number

WhileOutagescan be linked toTasks, they arenotcommonly referenced as a related list in standard implementations.

A more appropriate relationship would be " Affected CI " rather thanTask Number.

A record-based trigger is a component thatcauses a flow to run after a record has been created or updated in a specified table1. It allows users to define conditions and actions for the flow based on the record’s state and values1. For example, a record-based trigger can start a flow when a new incident is created or when an existing incident is updated with a certain priority1.

References

Flow trigger types - Product Documentation: San Diego - ServiceNow1

ASchema Mapin ServiceNow provides avisual representationof a table ' s relationships, including itsextensions, references, and dependencies. This is useful for administrators and developers to understandhow data is structuredwithin an instance.

Navigate to System Definition > Tables

Select the desired table(e.g.,incident,task,cmdb_ci, etc.)

Scroll to the " Related Links " sectionat the bottom of the form

Click " Show Schema Map "

How to Access the Schema Map for a Table:This will open agraphical representationof the table, showing:

Tables thatextend fromthe selected table

Tables thatreferencethe selected table

Fields that establish relationships

A. System Dictionary > Show Schema Map; Select Table

The Schema Map isnot accessed via the System Dictionary.

C. System Definition > Show Schema Map; Select Table

There is nodirect " Show Schema Map " menuunder System Definition; you must go throughTablesfirst.

D. System Definition > Dictionary: Select Table; Go to Related Links and click Show Schema Map

TheDictionarymodule does not provide a Schema Map option directly for tables.

Schema Maps Overview

Viewing Table Relationships with Schema Map

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

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:

Tomodify the order of fields on a formin ServiceNow, you have two main options:

Form Layout(A - Correct Answer)

Navigation:Context Menu > Configure > Form Layout

Allows you to rearrange fields using a simplelist-based interface.

You can add, remove, or reorder fields quickly.

Form Design(C - Correct Answer)

Navigation:Right-click on the form header > Configure > Form Design

Opens adrag-and-drop interfacefor modifying form layout.

Provides more advanced customization options, including sections, tabs, and field arrangements.

B. Context Menu > Form > Layout

No such menu option exists in ServiceNow.

D. Context Menu > Configure > Form Designer

There is no direct " Form Designer " option in the context menu; instead, it ' s accessed viaConfigure > Form Design.

E. Right-click on header > Configure > UX Dashboard

UX Dashboard is used forUI pages, dashboards, and workspace configurations, not form layout changes.

Configuring Forms in ServiceNow

Using Form Designer

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

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:

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 Fieldshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/metadata/concept/c_TablesAndFields.html

References from Certified System Administrator (CSA) Documentation:

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

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

Displays a user-friendly label from the referenced record.

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

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

TheCallerfield allows users to select a user from theUser Table.

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

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

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

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

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

In ServiceNow, asys_idis aunique 32-character identifier(UUID - Universally Unique Identifier) that is automatically assigned to every record in the system.

It isa unique 32-character alphanumeric string(e.g.,5137153cc611227c000bbd1bd8cd2005).

Every record in every table in ServiceNow has asys_idfield.

Thesys_id remains the same across instances if the record is transferred via an Update Set.

It helpsuniquely identifyrecords and is used in scripting, APIs, and database relationships.

In theIncident [incident]table, an incident record might have:

Number:INC0012345

sys_id:9d72f6141b122200d37a85e15b2d6fe6

Key Characteristics of sys_id:Example:

Thesys_id is always 32 characters long.

It is acritical part of the ServiceNow database structure.

Used forrelationships, APIs, scripting, and querying records.

Why " A. Unique 32-character identifier that is assigned to every record " is Correct?

B. A client-side Business Rule – Incorrect

Business Rulesdo not generate sys_ids; they control logic execution.

C. A server-side Business Rule – Incorrect

Business Rules are used for automation, but sys_id is a system-generated field.

D. Unique 64-character identifier that is assigned to every record – Incorrect

The correct length of sys_id is32 characters, not 64.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding sys_id

ServiceNow CSA Study Guide – Database Architecture

ServiceNow Product Documentation: Unique Identifiers in ServiceNow

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, you can add additional fields to a form using either:

Form Layout(for quick field additions)

Form Designer(for a drag-and-drop UI approach)

Context Menu > Configure > Form Layout (B)

This allows administrators toadd or remove fieldsin a simplelist-based interface.

Used when only minor modifications are needed.

Context Menu > Configure > Form Design (C)

Opens theForm Designer, adrag-and-drop UI editorfor configuring forms.

Allows users torearrange fields, sections, and tabseasily.

A. Context Menu > Form > Layout(Incorrect)

The correct path isConfigure > Form Layout, not " Form > Layout. "

D. Right-click on header > Add > Field(Incorrect)

Right-clicking the form headerdoes not provide an option to add fields directly.

E. Context Menu > Form > Designer(Incorrect)

The correct option isConfigure > Form Design, not " Form > Designer. "

F. Right-click on header > Configure > UX Dashboard(Incorrect)

UX Dashboards areused for analytics and reporting, not form configuration.

Form Layout in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/task/t_ConfigureFormLayout.html

Form Designer Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_FormDesigner.html

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

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 Overviewhttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/incident-management/concept/task-table.html

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

TheService Catalogis a core feature in ServiceNow that provides users with a structured interface to request services and products. Thebaseline Service Catalog homepageincludes links to key components that help users navigate and submit requests efficiently. These components are:

Record Producers– These are forms that allow users to create records in tables other than the Request table (e.g., submitting an incident or a change request).

Order Guides– These help users request multiple related items in a single submission, streamlining complex orders.

Catalog Items– These are the individual products or services users can request, such as software installations, hardware requests, or access requests.

Option B: " Order Guides, Item Variables, and Workflows " – Incorrect, becauseItem VariablesandWorkflowsare not direct links on the Service Catalog homepage. Item Variables are attributes of Catalog Items, and Workflows handle backend processing but are not listed as a navigational component.

Option C: " Order Guides, Catalog Items, and Workflows " – Incorrect, because Workflows are not directly linked from the homepage.

Option D: " Record Producers, Order Guides, and Item Variables " – Incorrect, because Item Variables are part of Catalog Items but not a distinct link on the homepage.

ServiceNow Product Documentation - Service Catalog Overview

ServiceNow CSA Study Guide - Service Catalog Fundamentals

ServiceNow Docs: Service Catalog Components

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

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

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.

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

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

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.

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

https://docs.servicenow.com

ServiceNow Community: Best Practices for Dot-Walking

https://community.servicenow.com

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,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 Setshttps://docs.servicenow.com

ServiceNow Learning – Data Import & Transformation Best Practices

ServiceNow Developer Portal – Using Import Sets Efficiently

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Tables & Columnsis the module that allows administrators to view and managefield settingsfor a table. This module provides a list of tables in the system along with details about theircolumns (fields), data types, and attributes.

Displaysall fields (columns)within a selected table.

Showsdata types, attributes, and configurationsof each field.

Allows admins toadd, modify, or removefields.

Provides details onrelationships between tables(e.g., reference fields, one-to-many relationships).

Navigate to:System Definition > Tables & Columns

Select a table to view itsfield settings.

B. Access Control – Incorrect

This module managessecurity rules (ACLs)for accessing records but does not display table field settings.

C. Columns and Fields – Incorrect

No such module exists in ServiceNow.

D. Tables and Fields – Incorrect

The correct module name is " Tables & Columns " , not " Tables and Fields " .

ServiceNow Docs: System Definition – Tables & Columns

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Managing Fields in a Table

Key Features of the " Tables & Columns " Module:How to Access Tables & Columns in ServiceNow:Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

In ServiceNow,groupsare stored in theGroup [sys_user_group]table. Groups are used to organize users with similar responsibilities, permissions, or functional roles.

Name(name) – The unique name of the group.

Manager(manager) – The user responsible for managing the group.

Roles(roles) – The roles assigned to the group, which are inherited by all group members.

Parent Group(parent) – If applicable, this establishes group hierarchy.

Assigning access roles to multiple users at once.

Routing tasks or approvals (e.g., Incident assignments to an IT Support group).

Managing security and permissions in ServiceNow.

A. Group [user group]– Incorrect. This is not a valid ServiceNow table.

B. Group [sys_user]– Incorrect. This is theUsertable, not the Group table.

D. Group [sys_user_group_profile]– Incorrect. This table does not exist in ServiceNow.

ServiceNow Docs: User Administration – sys_user_group Table

ServiceNow CSA Study Guide – Managing Users and Groups

Key Fields in thesys_user_groupTable:Common Use Cases for Groups: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

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

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 Modelhttps://docs.servicenow.com

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:

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 Articleshttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/knowledge-management/task/review-article-feedback.html

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, theService Catalogis a structured collection of IT and business services that users can request. It is designed to provide a self-service experience for end-users, streamlining service requests and automating fulfillment processes. The main components of a Service Catalog include:

Record Producers– These are simplified forms that allow users to create records in various tables without requiring direct access to those tables. They enable users to submit requests or incidents through the catalog in a user-friendly manner.

Order Guides– These facilitate the ordering of multiple related catalog items in a single request. For example, when a new employee is onboarded, an order guide can group multiple items such as a laptop, software access, and a phone.

Catalog Items– These are the individual items or services that users can request through the Service Catalog. Examples include hardware (like laptops and monitors), software access, and other business services.

Option A (Order Guides, Exchange Rates, Calendars)–

Exchange RatesandCalendarsare not part of the Service Catalog framework in ServiceNow.

While Exchange Rates may be relevant in financial applications, they do not define the core components of the Service Catalog.

Calendars are used for scheduling, but they do not form part of the Service Catalog structure.

Option B (Order Guides, Catalog Items, and Interceptors)–

Interceptorsare used to guide users through form-based submissions, but they are not a fundamental component of the Service Catalog.

Order Guides and Catalog Items are correct, but the presence of Interceptors makes this option incorrect.

Option C (Catalog Items, Asset Contracts, Task Surveys)–

Asset Contractsrelate to IT Asset Management (ITAM) and are not core Service Catalog components.

Task Surveysare used for feedback collection but are not part of the core structure of a Service Catalog.

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 Workflowshttps://docs.servicenow.com

ServiceNow Learning – Service Catalog and Workflow Automation

ServiceNow Developer Portal – Flow Designer & Workflow Automation

References from Certified System Administrator (CSA) Documentation:

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:

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

https://docs.servicenow.com

ServiceNow Community: Best Practices for Import Set Management

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

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

InServiceNow Role Management, aroleis a collection ofpermissionsthat control what users can see and do within the platform.

Role Hierarchy (Role Inheritance)

Rolescan contain other roles(known asnested roles).

When a user is assigned aparent role, theyinherit all child roleswithin it.

Example:

TheITIL roleincludesincident_managerandproblem_managerroles.

AssigningITILto a userautomatically grants them all the permissions of the included roles.

Roles Are Assigned by Administrators

Typically, roles are assigned by aSystem Administratoror an authorized user.

Role-Based Access Control (RBAC)

ServiceNow usesRBACto control access to applications, records, and actions.

B. Users can click on the Personalize Role feature to try different roles

Incorrectbecause userscannot manually switch rolesunless they have theimpersonation privilege.

C. A role is granted to a user by the System Administrator

Partially correct, butnot the best answerbecause rolescan also be assigned via groupsor automated processes, not just by a System Administrator.

D. Each user has a role in the ServiceNow platform

Incorrectbecause not all usersmust have a role.

Example:A self-service user can access the systemwithouthaving any specific role.

ServiceNow Docs: Role-Based Access Control (RBAC)https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/roles/reference/r_RBAC.html

ServiceNow CSA Official Training Guide (User & Role Management)

Key Characteristics of Role Assignment:Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatroles can contain other roles, and when a user is assigned a role, they inherit all roles within it.

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:

Thesix methods available for user authenticationin ServiceNow are:

Local Database– The user authenticates using a username and password stored in theinstance database.

Multifactor Authentication (MFA)– The user provides their username, password, and apasscode(e.g., from Google Authenticator).

LDAP (Lightweight Directory Access Protocol)– The user authenticates using credentials stored in a corporateLDAP directory.

SAML 2.0 (Security Assertion Markup Language)– The user is authenticated via an externalSAML Identity Provider (IdP).

OAuth 2.0– The user authenticates via anOAuth identity provider(such as Google, Microsoft, or Facebook).

Digest Token Authentication– The user authenticates using anencrypted tokenrather than directly submitting a password.

Thus, the correct answer is:

A, B, C, D, E, F

ServiceNow supports multiple authentication methods to provideflexibility, security, and integration capabilitieswith external identity providers.

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

This method is commonly used when no external authentication provider is configured.

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

Passcodefrom a registered device (such as Google Authenticator, Microsoft Authenticator).

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

Allows users toauthenticate against an external LDAP directory(such as Microsoft Active Directory).

The user must have amatching record in the ServiceNow user table ([sys_user]).

ServiceNowdoes not store passwordswhen using LDAP; it only validates credentials against the directory.

SAML 2.0 Authentication:

Users authenticate via aSAML Identity Provider (IdP)such asOkta, Microsoft Azure AD, or Ping Identity.

ServiceNow acts as aService Provider (SP)and does not store passwords.

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

Allows authentication viaOAuth providers(Google, Facebook, Microsoft, etc.).

Users do not need to store passwords in ServiceNow; instead, authentication is delegated to theOAuth identity provider.

Digest Token Authentication:

Uses anencrypted token(instead of a plaintext password) to authenticate users.

Often used forAPI-based authenticationor scenarios where passwords should not be transmitted over the network.

Each method aligns with ServiceNow ' s authentication mechanisms as per official documentation.

ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.

ServiceNow Docs – Authentication Methodshttps://docs.servicenow.com

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

Why These Are the Correct Methods?References from Certified System Administrator (CSA) Documentation:

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), which can includeboth tangible and intangible business assets.

Tangible assets: Physical devices like servers, network components, and workstations.

Intangible assets: Software, applications, cloud services, licenses, and business services.

Relationships and Dependencies: CMDB maintains the relationships between CIs to help with impact analysis, change management, and troubleshooting.

What is Stored in the CMDB?CMDB plays a crucial role inIT Service Management (ITSM), ensuring that organizations haveaccurate and up-to-dateasset data for better decision-making.

(A) The CMDB contains data about tangible and intangible business assets – Correct

TheCMDB tracks and manages both physical (tangible) and virtual (intangible) assets.

Examples oftangible assets: Servers, routers, desktops, mobile devices.

Examples ofintangible assets: Cloud services, software applications, business services.

(B) The CMDB contains the Business Rules that direct the intangible, configurable assets used by a company – Incorrect

Business Rules are not stored in the CMDB.

Business Rules in ServiceNow are part of the platform’s automation framework and control system behavior but donotdefine configuration items.

(C) The CMDB archives all Service Management PaaS equipment metadata and usage statistics – Incorrect

TheCMDB does not function as an archive; it maintains real-time, active data about CIs.

Usage statistics are stored in performance analytics and reporting tools, not in the CMDB.

(D) The CMDB contains ITIL process data pertaining to configuration items – Incorrect

While CMDBsupports ITIL processes, it doesnot store ITIL process datadirectly.

ITIL process data (e.g., incident, problem, change records) is stored inITSM modules, not in the CMDB itself.

CMDBdoes contain CI relationshipsthatsupportITIL processes likeIncident, Problem, and Change Management.

Explanation of Each Option:

CI Classes & Hierarchy: ServiceNow CMDB uses a hierarchical structure with variousCI Classes(e.g.,cmdb_ci,cmdb_ci_server,cmdb_ci_database).

CMDB Health Dashboard: Ensures data accuracy withcompleteness, compliance, and correctnessmetrics.

Relationship Management: CIs in the CMDB are linked to show dependencies, which iscrucial for impact analysisin change and incident management.

Discovery & Service Mapping: ServiceNow’sDiscovery and Service Mappingtools helpautomate CI data collection.

Additional Notes & Best Practices:

ServiceNow Docs: CMDB Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for CMDB Data Accuracy

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

The primary operations performed on tables inServiceNowfollow theCRUDmodel:

Create (C)– Adding a new record to a table.

Read (R)– Viewing or retrieving a record from a table.

Write (W)– Editing or updating an existing record.

Delete (D)– Removing a record from a table.

These operations are fundamental todatabase managementand align with ServiceNow’sAccess Control Rules (ACLs), which enforce security permissions for each operation.

A. Create, Rate, Update, DeleteIncorrect– " Rate " is not a standard database operation.

B. Create, Read, Upload, DeleteIncorrect– " Upload " is not a standard database operation.

D. Capture, Rate, Write, DevelopIncorrect– None of these terms (except " Write " ) relate to database operations.

Incorrect Answer Choices Analysis:

ServiceNow Docs – CRUD Operations in Tables???? Tables and CRUD Operations

ServiceNow Docs – Access Control Rules???? ServiceNow ACLs for CRUD

Official ServiceNow Documentation References:

InServiceNow Knowledge Management, articles are typicallyrestrictedto specific users or roles. However,if you want an article to be accessible without requiring login, you must enable thePublic setting.

Navigate toKnowledge Base Settings.

Enable thePubliccheckbox.

Save the changes.

The article is nowviewable by anyone, even without logging into ServiceNow.

A. The View All setting

No such setting exists for public access in ServiceNow.

B. The Allow role

" Allow roles " restricts accessto specific roles, but does not make the article public.

C. The ESS role

TheESS (Employee Self-Service) roleallows accessto logged-in users, not public users.

In ServiceNow,a role is a collection of permissionsthat control what actions a user can perform and what data they can access within the system.

Roles are used togrant access to applications, modules, and records, and they are assigned to users based on their job functions. Users can have multiple roles, which collectively define their permissions.

For example:

Theadminrole provides full system access.

Theitilrole allows access to Incident and Change Management.

Thecatalog_adminrole grants permissions to manage Service Catalog items.

B. A set of user access policies→ Incorrect, because user access policies are more granular security rules, whereas a role is a broader concept grouping multiple permissions.

C. A Persona in a workflow→ Incorrect, because a role is not the same as a persona in a workflow; personas are more conceptual.

D. A set of access control rules→ Incorrect, becauseroles do not define access control rules directly; they are usedwithin ACLs (Access Control Lists)to determine access permissions.

InServiceNow, thetable configuration pageallows administrators tomodify table settings, fields, relationships, and properties.

To access this page from aform view, you must use theForm Context Menu (☰in the top-left corner of the form)and navigate to:

???? Configure > Table

This willopen the Table Configuration Page, where you can:

View and edittable properties.

Managefields, relationships, and indexing.

Configuresecurity settings (ACLs)for the table.

Open a record in a form view(e.g., a Catalog Task form).

Click the Form Context menu(☰at the top-left).

Select " Configure " from the dropdown.

Click " Table " to access theTable Configuration Page.

Step-by-Step Navigation:

Why " Configure > Table " is the Correct Answer?Directly accesses the table ' s configuration page

Allows modification of table-level settings

Best practice method for modifying table properties

A. The Form Context menu > View > TableIncorrect– There is no " View > Table " option in the context menu.

C. The Form Context menu > Configure > DictionaryIncorrect– The " Dictionary " option allowsediting individual field propertiesbutnot the entire table configuration.

D. The Form Context menu > View > Show TableIncorrect– No such " Show Table " option exists in theForm Context Menu.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Configuring Tables???? Table Administration

ServiceNow Docs – Modifying Table Properties???? Configuring a Table

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. The Form Context menu > Configure > Table

This is the correctnavigation pathto access thetable configuration pagefrom a form in ServiceNow.

InServiceNow, afilter conditionis used toquery data from tables. It consists of three main components:

1. Column (Field)Represents the database column (or field) that is being filtered.

Example:Priority,State,Assigned To

In ServiceNow UI, this appears as thefirst dropdownin a filter condition.

2. OperatorDefines the comparison condition for the filter.

Examples:is,is not,greater than,contains,starts with

In ServiceNow UI, this appears as themiddle dropdownin a filter condition.

3. ValueSpecifies the criteria being matched against the column.

Example:High,Closed,John Doe

In ServiceNow UI, this is thethird input fieldin a filter condition.

Example of a Filter Condition in ServiceNow UI:Column (Field)

Operator

Value

Priority

is

High

State

is not

Resolved

This filter will returnrecords where:

ThePriorityfield is set toHigh

TheStatefield is NOTResolved

B. Match CriteriaIncorrect–No such term exists in ServiceNow filters.

C. FieldIncorrect– " Field " is another word for " Column " , but " Column " is the correct term in ServiceNow filter conditions.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Filtering Data???? How to Create Filters in ServiceNow

ServiceNow Docs – Query Builder and Operators???? Building Filter Queries

Official ServiceNow Documentation References:

InServiceNow, by default, the " Save " button is not displayedon the form header. Instead, users typically use the " Submit " or " Update " buttons.

To enable the " Save " buttonon the form header, you mustenable theglide.ui.advancedsystem property.

Enables the " Save " Button in the Form Header

Theglide.ui.advancedpropertyactivates additional UI options, including theSave button on forms.

Once enabled, users will see the " Save " button alongside " Submit " and " Update " in the form header.

Allows Partial Record Saves Without Submitting

Unlike " Submit " (which creates a new record) or " Update " (which modifies an existing record), " Save " allows users toretain changes without submitting the form.

Useful fordrafts or in-progress edits.

Controlled via System Properties

The " Save " buttonisnot a field or UI actionthat can be manually added through Form Design or Layout.

It is enabledat the system levelviaSystem Properties > UI Properties.

Why is " Turning onglide.ui.advanced " the Correct Answer?

Navigate toAll > System Properties > UI Properties

Find theglide.ui.advancedproperty

Set it to " true "

Save the changes

Refresh theIncident form→ The " Save " button will now appear

How to Enable the Save Button in ServiceNow?

B. Context Menu > Form Design > Add the " Save " buttonIncorrect– The " Save " button isnot a UI actionthat can be added via Form Design. It must beenabled through system properties.

C. All > System Properties > UI Properties > Turn on the " Save " buttonIncorrect– No suchspecific " Save " button settingexists in UI Properties. The correct setting isglide.ui.advanced.

D. Context Menu > Form Layout > Add the " Save " buttonIncorrect–Form Layout only controls fields, not form buttons. The " Save " button is controlled viaUI Properties.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Enabling the Save Button???? Configuring UI Properties

ServiceNow Docs – Using the glide.ui.advanced Property???? Understanding glide.ui.advanced

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

A. All > System Properties > UI Properties > Turn on theglide.ui.advancedproperty

Thisenables advanced UI options, including the " Save " button, allowing users tosave records without submitting them.

When setting up a notification in ServiceNow, you must define three critical elements:

What is the content of the notification?

This includesemail subject, body, variables, and templatesthat define how the notification will be displayed to the recipient.

Under what conditions is the notification sent?

Notifications are triggered based onconditionssuch as:

Record Insert/Update/Delete

Specific field value changes

Events generated by business rules

Who receives the notification?

The recipients can be configured using:

Specific users or groups

Scripted recipients

Users associated with the record (e.g., Caller, Assigned To)

B. The associated knowledge base– Notifications arenot tiedto knowledge bases; they are triggered by records and events.

E. Settings for handling inactive user accounts– While user preferences exist, this is not a required step in notification creation.

ServiceNow Notifications Guide

ServiceNow CSA Training Module: " Creating and Managing Notifications in ServiceNow "

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

A Business Rule is a server-side script designed to respond to database operations.

Triggers: The specific database operations that trigger a Business Rule are Insert , Update , Delete , and Query .

Timing: As established in Question 510, these rules can run Before the save completes or After the save completes (or Async).

Therefore, the most accurate description of the valid triggers provided in the options is " Before or after a record is saved to the database. "

Option B is incorrect because reporting does not trigger business rules (unless it ' s a " Query " rule, but " downloads a report " is not the definition). Option D refers to Authentication or Installation Exits, not standard Business Rules.

Detailed Explanation:

In ServiceNow,User Presencefeatures provide real-time visibility into record collaboration. This includes:

Option B:An icon that appears beside fields updated by other users, indicating recent changes.

Option E:A user presence icon showing initials of users currently viewing the record. These real-time indicators improve collaboration and prevent conflicts during data entry. (Reference: ServiceNow Documentation - Real-time Collaboration and User Presence)

=================

Detailed Explanation:

Business Rulesin ServiceNow are server-side scripts that execute in response to database operations, such as when a record is displayed, inserted, updated, deleted, or queried. They are critical for automating processes, ensuring data integrity, and performing backend operations without user intervention. Business Rules can be set to run at different times, such as before or after the database action, depending on the requirement. (Reference: ServiceNow Documentation - Business Rules and Server-side Scripting)

=================

Predictive Intelligence (PI)in ServiceNow is anAI-powered frameworkthat helpsautomate classificationanddecision-makingbased on historical data. It canautomatically populate values for fields like Priority and Categorybased on theShort Descriptionfield value.

D. Predictive Intelligence

Usesmachine learning modelsto analyze patterns in previous records.

Automaticallysuggests or assigns valuesfor fields likePriority, Category, and Assignment Group.

Example:

If a user submits anincident with " Email not working " in theShort Description, Predictive Intelligence can:

SetCategorytoEmail

SetPrioritytoMedium

Assign the ticket to the appropriateSupport Group

A. UI Policy

UI Policiescontrolform behavior(e.g., showing/hiding fields) butdo notdynamically assign values based on machine learning.

B. Assignment Rule

Assignment Rulesdeterminewho gets assigneda record based on conditions butdo not populate Priority or Category automatically.

C. Action

" Action " is not a framework—it refers toFlow Designer actions, which require manual configuration.

E. CSDM (Common Service Data Model)

CSDMis adata frameworkfor managing CIs and services, but it doesnot handle automatic field population.

In ServiceNow, Application Scope is a fundamental concept used to protect applications by identifying and restricting access to application artifacts (such as tables, scripts, and business rules). 3

1. The Concept of Scope:

Every application in ServiceNow has a scope.4

Global Scope: This is the default scope for the baseline ServiceNow instance. Legacy applications and general configurations usually live here.

Private/Scoped Applications: These are distinct namespaces (e.g., x_acme_book_mgmt ). 5

2. Why Option D is Correct (Availability and Protection):

The primary purpose of a private scope is to define boundaries. It acts as a protective layer that does two main things:

Protection: It prevents code in the Global scope or other Scoped applications from modifying your application ' s data or logic without explicit permission. 6

Availability (The Answer): It allows the developer to explicitly define which parts of the application are public. By default, artifacts in a private scope are hidden from other applications. 7 The developer must configure " Cross-scope privileges " or set specific " Access " settings (e.g., making a Script Include " Accessible from: All application scopes " ) to determine what is available for use by others. 8

3. Why the other options are incorrect:

A: Scope does the opposite; it restricts access by default, rather than granting " all access. "

B: Scope does not determine the functionality of core services; it acts as a container for custom or store-bought applications.

C: Scope prevents other applications from changing your tables, but it allows the application to change its own tables and logic. 9

In ServiceNow, users cancustomizetheir list views byrearranging, adding, or removing columns. This is done through theList Layout Configuration.

B. Right-click on any column header. Context Menu > Configure > List Layout

Thequickestway to modify columns in a list view.

Steps:

Right-click on any column headerin the list.

SelectConfigure > List Layoutfrom the context menu.

Add, remove, or rearrange columns as needed.

ClickSave.

A. Click Personalize List

Incorrect terminology—there is no " Personalize List " option for configuring list columns.

" Personalize " is used for settingpersonal preferences, not list layouts.

C. Click List Context Menu > Personalize List

TheList Context Menudoes not have a " Personalize List " option for column arrangement.

D. Click List Content Menu > Configure > List Layout

Typo in " List Content Menu " —the correct term is " List Context Menu " .

However,right-clicking on the column header(Answer B) is the recommended method.

To rename a field label in ServiceNow (such as changing " Priority " to " PValue " ), you must eitherupdate the dictionary definitionorchange the field label.

Right-click on the " Priority " field labelin the form.

Select " Configure Dictionary " .

Update the " Label " fieldto " PValue " .

Save the changes.

The new label will now be reflected across the system where applicable.

Right-click on the " Priority " field labelin the form.

Select " Configure Label " .

Update thelabel textto " PValue " .

Save the changes.

This methodonly changes the field labelfor display purposeswithout affecting the underlying database structure.

B. Right-click on Priority and select Configure Display Settings

There isno " Configure Display Settings " option when right-clicking on a field label in ServiceNow.

D. Right-click on Priority and select Configure Column

" Configure Column " is used forlist views, not for changing field labels on forms.

ServiceNow Field Labels and Dictionary

ServiceNow CSA Training Module: " Configuring Forms and Fields "

Option 1: Configure Dictionary (Recommended for Full Customization)Option 2: Configure Label (Quick Change for Display Purposes)Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

ServiceNow operates on an Advanced High Availability (AHA) architecture.

Responsibility: The management of this architecture, including data replication and disaster recovery, is the sole responsibility of ServiceNow .

The Process: In the event of a catastrophic failure at a primary data center, ServiceNow operations teams are responsible for executing the failover procedures to shift traffic to the paired secondary data center. This is a managed service; the customer does not have buttons or controls to switch data centers themselves.

Assigning work tasks to aGroupinstead of anindividualoffers flexibility, better workload management, and ensures tasks are handled efficiently.

Group members can choose their tasks from " My Groups Work "

The " My Groups Work " module in ServiceNow allows group members to see all unassigned tasks for their group and take ownership of available tasks.

This is particularly useful when multiple team members share responsibility for completing tasks.

Groups can assign tasks to users based on on-call schedules

ServiceNow’sOn-Call Schedulingfeature allows automatic assignment of tasks to available members based on a predefined schedule.

This ensures that work is distributed fairly among team members who are on shift.

Site support members can pick tasks, based on Location

Tasks can be assigned dynamically based on thelocation of the request.

This is particularly useful for IT support teams, field service teams, and facilities management teams, where physical presence is required to complete a task.

Groups can assign tasks to users based on skills

UsingSkill-Based Routing, ServiceNow can match tasks to users who have the right skills for the job.

For example, if a request requires expertise in " Windows Server Management, " the system will assign it to a group member with that skill.

E. Group members can avoid tasks that are nearing SLA breach

This is incorrect because ServiceNowprioritizes SLA breachesand usually escalates such tasks rather than allowing users to avoid them.

F. Groups can assign tasks to users based on availability

WhileOn-Call Schedulingcan assign tasks based on availability, ServiceNow doesnotautomatically assign tasks dynamically based on real-time availability. Availability tracking isnota standard assignment mechanism in ServiceNow unless customized.

ServiceNow Product Documentation→ " Assigning Tasks to Groups "

ServiceNow Product Documentation→ " On-Call Scheduling "

ServiceNow Product Documentation→ " Skill-Based Routing "

Benefits of Assigning Tasks to a Group:Incorrect Answers Explanation:References from Certified System Administrator (CSA) Documentation:

In ServiceNow,tagsare used to categorize and organize records for quick access. When managing tags, users can control theirvisibilityby settingwho can see them.

B. Everyone

The tag ispublicand visible to all users in the instance.

Example: AService Desk teamcreates a " High Priority " tag that everyone can use.

C. Groups and Users

Tags can be restricted to specificgroupsorindividual users.

Example: ASecurity Teamcreates a tag only visible toIT Security staff.

E. Me

Tags can beprivate, meaning only the creator (you) can see them.

Example: A user creates a " Follow-up " tag for theirownpersonal tracking.

A. Admins

Incorrect—Admins can manage tags, but " Admins " isnota visibility setting.

Instead, visibility is set toEveryone, Groups, or Me.

D. Roles and Permissions

Incorrect terminology—ServiceNowdoes notprovide a tag visibility setting based on " Roles and Permissions. "

Tags are assigned based onspecific users or groups, not roles.

By default, ServiceNow encrypts data in transit using industry-standard Transport Layer Security (TLS) protocols. This ensures that any data transmitted between the client and the ServiceNow platform, or between ServiceNow and integrated systems, is encrypted and protected from interception or tampering.

While ServiceNow also offers options for data at rest encryption and customer-managed encryption keys, these features often require additional configuration or subscription services. Encryption of data in use (while data is being processed in memory) is a more advanced concept and not provided by default.

Thus, encryption of data in transit is the baseline encryption feature included automatically in all ServiceNow instances.

When selecting aTarget Tablefor anImport Set, you must choose a table that exists within the ServiceNow system and falls within your scope of permissions. The following types of tables are eligible as target tables:

Tables within the Global Scope(A - Correct Answer)

If the table exists within theglobal application scope, it is accessible from all applications.

Example:Task [task],User [sys_user] ,Configuration Item [cmdb_ci]

Tables within the Existing Application Scope(B - Correct Answer)

Tables belonging to the same application scope as the import set can be selected.

Example: If you are working in a scoped application likeHR Service Delivery, you can import data intoHR-related tables.

Related Tables Using Dot Walk(E - Correct Answer)

You can select related tables usingdot-walkingto reference data from linked tables.

Example: If importing intoIncident [incident], you can reference data fromCaller (sys_user)via dot-walking.

C. Tables outside of ServiceNow

ServiceNowcannotdirectly import data into external databases or non-ServiceNow tables.

Instead, you can export data to an external system after processing.

D. Tables which allow write access to other applications

ServiceNow enforcesscope protection, so you cannot write to tables in a different application scope unless explicitly allowed.

You needcross-scope privilegesto modify tables in another application.

Importing Data into ServiceNow

Understanding Application Scope

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow,Tagsallow users tocategorize and grouprecords in a list. Tagged records arevisible to othersif set to public or shared with specific users or groups.

A. Tags

Tags help usersorganize and quickly locaterecords.

Tags can beprivate (Me)orshared (Everyone, Groups, or Specific Users).

Example:

A support team might tagcritical incidentswith " Urgent " for easy tracking.

B. History

TheHistorymodule showsrecently accessed recordsbut does not categorize or share records.

C. Favorites

Favoritesallow users tobookmark specific records or listsfor quick access, but they areprivateand not shared with others.

D. Activity Formatter

TheActivity Formattertrackschanges and updatesin a record (e.g., who modified the record, comments added), but it does notcategorize or sharerecords.

InFlow Designer, aFlow Executionis initiated by atrigger. A trigger determineswhen and under what conditions a flow starts.

Record-Based Trigger

Executes the flow when a record iscreated, updated, or deletedin a specific table.

Example: A flow runs when anIncident is createdwith a specific priority.

Schedule-Based Trigger

Executes the flow at aspecific time or on a recurring schedule.

Example: A flow runsevery Monday at 8 AMto check overdue tasks.

Application-Based Trigger (Inbound Actions, API Calls, or Events)

Executes the flow when a specificevent occursin ServiceNow.

Example: A flow runswhen an email is receivedin ServiceNow.

Types of Triggers in Flow Designer:

B. An existing subflow

Subflowsare reusable flows that can be calledwithin a parent flow.

A subflow doesnot initiate executionon its own; it must be triggeredby a flow or script.

C. Allow logic

No such term exists inFlow Designer; logic applieswithina flow but doesnot initiate execution.

D. An execution data pill

Data pillsrepresent stored datawithina flow butdo not trigger execution.

Why Other Answers Are Incorrect:

ServiceNow Flow Designer – Triggers

ServiceNow CSA Training Module: " Building Flows with Flow Designer "

References from Certified System Administrator (CSA) Official Documentation:

InServiceNow List Views, users cancustomize and personalizethe displayed columns to fit their needs.

Open anylist view(e.g., Incidents, Requests).

Click theGear icon (⚙)in the top-right corner of the list.

ThePersonalize List Columnswindow appears.

Select or remove columns as needed.

ClickSaveto apply changes.

Steps to Personalize List Layout (Columns):This customization isuser-specific, meaning it only affects the logged-in user’s view.

B. Select the column to be personalized > Click Edit icon (Penal) > Choose options to personalize

NoEdit icon (Pencil) for column customizationexists in List Views.

C. Context Menu > View > Personalize

TheContext Menu (right-click menu)allows you to filter or sort data but doesnot customize columns.

D. Select the column to be personalized and right-click the header > Choose options to personalize

Right-clicking the column header providessorting and grouping options, not full column customization.

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.

InServiceNow,Business Rulesareserver-side scriptsthat execute when a record is created, updated, deleted, or queried. The " When " setting in a Business Rule determineswhen the rule runs in relation to database operations.

BeforeExecutes before a record is inserted, updated, or deleted.

Used forvalidations, data modifications, and setting field valuesbefore saving.

AfterExecutes after a record has been committed to the database.

Used fortriggering notifications, writing logs, or updating related records.

Async(Asynchronous)Executes after a short delay, allowing the main transaction to complete first.

Used forlong-running processes like API calls, email sending, or external system updates.

DisplayExecutes before the record is sent to the client (UI).

Used topopulateg_scratchpadfor client-side scripts.

The Four Timing Options for Business Rules:

Example Use Cases for Business Rule Timings:Business Rule Timing

When It Runs

Use Case

Before

Before saving to the database

Validate data, auto-populate fields

After

After saving to the database

Send notifications, update related records

Async

Shortly after the transaction completes

Call an external API, send an email

Display

Before the form loads

Pass server data to client-side scripts (g_scratchpad)

A. Insert, Update, Delete, QueryIncorrect– These aredatabase operations, not the execution timing options for Business Rules.

C. Prior to, Synchronous, on UpdateIncorrect– These termsdo not matchthe standard ServiceNowBusiness Rule timing settings.

D. Before, Synchronous, Scheduled Job, ViewIncorrect– " Scheduled Job " isnota Business Rule timing option (it is part ofScheduled Script Executions).

Incorrect Answer Choices Analysis:

ServiceNow Docs – Business Rules Overview???? Understanding Business Rules

ServiceNow Docs – Best Practices for Business Rules???? Best Practices for Business Rules

Official ServiceNow Documentation References:

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.

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.

The fundamental difference between a Client Script and a Business Rule in ServiceNow lies in where they execute and when. A Client Script runs on the client side — that is, in the user ' s browser — and is primarily used to control UI behavior, validate data before submission, and enhance user interaction with forms. Client Scripts can run at different stages (onLoad, onChange, onSubmit), but they always execute within the browser environment.

A Business Rule, on the other hand, runs on the server side and executes when records are inserted, updated, deleted, or queried in the database. Business Rules are used for enforcing data integrity, automating server-side logic, and integrating with other systems. They can be set to run before or after a database action (before insert, after update, etc.).

Therefore, the correct statement is that Client Scripts execute on the client and Business Rules execute on the server.

InServiceNow Knowledge Management, several features help supportcontinuous improvementof knowledge articles by allowing users to providefeedback, ratings, and flag issues. These features ensure that knowledge remainsaccurate, relevant, and usefulover time.

B. Add Comments

Allows users to provide feedback directly on knowledge articles.

Comments help knowledge managers refine content based on user suggestions.

D. Tag as Helpful

Users can mark an article as helpful, indicating that it provided useful information.

Helps knowledge managers assess the article’s effectiveness.

E. Flag Article

Users can flag an article if they find inaccuracies or outdated content.

Flags alert knowledge managers to review and update the content.

F. Rate with Stars

Users can rate an article using astar-based rating system(e.g., 1 to 5 stars).

This helps knowledge managers understand which articles arehigh-quality vs. low-quality.

A. Submit KB Errata

No such built-in feature exists in ServiceNow Knowledge Management.

C. CC Click Frowning Icon

No such feature exists. ServiceNow provides a " Helpful " or " Flag " option instead.

ThePropertiessection in theReport Designeris used to:

Specify the report name

Select the table or data sourcefor the report

Allows renaming the reportfor better identification.

Defines the primary data source(table) for the report.

Sets report-level settingssuch as visibility, sharing options, and description.

B. Data →Incorrect

TheData sectionis used tofilter and refine the databut not to set the table or name the report.

C. Configure →Incorrect

No such section named " Configure " exists in the Report Designer.

D. Type →Incorrect

TheType sectionis used toselect the type of report(e.g., Pie Chart, Bar Chart, List, etc.).

E. Sources →Incorrect

No " Sources " section exists in the Report Designer.

Key Features of the Properties Section:Why Other Options Are Incorrect?

Report Designer Overview

Official ServiceNow Documentation Reference:

When testing anew ServiceNow application, the best practice is tofirst try it in a safe, non-production environmentto avoid any unintended impact on your company’s live instance.

Safe Testing Environment

Apersonal developer instance (PDI)is provided by ServiceNow for testing and development.

Activating a plugin in a PDIdoes not affect the company’s production system.

Allows Hands-On Experience Without Risk

You canexplore, configure, and test the new applicationin a personal dev instance.

Any issues encountered willnot disrupt business operations.

Best Practice for ServiceNow Development

ServiceNowrecommends testing all new featuresin asandbox or development instancebefore enabling them in a production environment.

Why is " Activate the application plugin on your personal dev instance " the Correct Answer?

A. Check the latest release notes at docs.servicenow.com.Incorrect– While the release notes providevaluable information, theydo not provide hands-on experiencewith the application.

C. Search the wiki for the sales demo request form.Incorrect– ServiceNow hasmoved away from using wikis. Also, requesting asales demois not the best way totest an application yourself.

D. Activate the application plugin on your company ' s production instance.Incorrect–Never test a new application directly in production. This can causeunexpected issuesandimpact live operations.

Incorrect Answer Choices Analysis:

ServiceNow Developer Program – Personal Developer Instances (PDI) ???? ServiceNow Developer Instances

ServiceNow Docs – Managing Plugins???? How to Activate Plugins

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. Activate the application plugin on your personal dev instance.

This methodallows safe testing and evaluationbefore considering implementation in a production environment.

✔Visual Task Boards (VTB)provide aKanban-style interfacefor tracking and managing tasks visually. Users can:

Create personal or team boardsto manage tasks.

Drag and drop task cardsbetween different lanes (e.g., " To Do, " " In Progress, " " Completed " ).

Filter and categorize workdynamically.

Types of Visual Task Boards:

Freeform Boards– Simple personal boards for organizing work.

Guided Boards– Based on ServiceNow lists and automatically updated.

Flexible Boards– A mix of Freeform and Guided boards.

Option B (Service Desk)is incorrect because it refers to theService Desk applicationfor handling incidents and tickets.

Option C (Virtual Agent Homepage)is incorrect because it is used forchatbot interactions, not task management.

Option D (Personal Task Tracker)is incorrect because there is no such feature in ServiceNow.

???? Reference:ServiceNow Visual Task Boards (VTB) Documentation