ServiceNow CSA ServiceNow Certified System Administrator Exam Practice Test

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

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

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

Hidden→ The field isremoved from visibilityon the form.

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

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

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

B. Write-only–Incorrect

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

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

C. Necessary–Incorrect

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

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

D. Mandatory–Correct

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

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

E. Empty–Incorrect

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

F. Hidden–Correct

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

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

Final Answer:Read-only

Mandatory

Hidden

ServiceNow Docs – UI Policies and UI Policy

ServiceNow Learning – Form Configuration & UI Policies

ServiceNow Developer Portal – Controlling Form Behavior with UI Policies

References from Certified System Administrator (CSA) Documentation:

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

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

onLoad (Option D)

Runswhen a form loads.

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

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

onChange (Option F)

Runswhen a specific field value changes.

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

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

onSubmit (Option A)

Runswhen the form is submitted.

Used for final validation before allowing submission.

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

onCellEdit (Option C)

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

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

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

Why Are the Other Options Incorrect?B. onUpdate

No "onUpdate" client script type exists in ServiceNow.

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

E. onEdit

No "onEdit" client script type exists.

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

G. onSave

No "onSave" client script type exists.

"onSubmit" handles validation before saving a record.

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

????ServiceNow Client Scripts Documentation

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

Conclusion:The correct answers are:

A. onSubmit(Runs when submitting a form)

C. onCellEdit(Runs when editing a list cell)

D. onLoad(Runs when a form loads)

F. onChange(Runs when a field value changes)

In 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 Service Catalog, anOrder Guideis a feature that allows users toorder multiple, related catalog items in a single request, simplifying the ordering process.

Helps usersrequest multiple items togetherinstead of submitting separate requests.

Ensures that related items are grouped logically (e.g., when onboarding a new employee, an Order Guide can include a laptop, software licenses, and access to required applications).

Usesvariables and rulesto pre-fill certain values and guide users through the ordering process.

Reduces the number of individual requests and makes fulfillment more efficient.

Purpose of an Order Guide:

(A) Order Guides restrict the number of items in an order to only one item per request – Incorrect

This isnot truebecause Order Guides allow users to requestmultiple itemsat once.

Asingle request (REQ#) is generatedthat contains multiple Requested Items (RITMs).

(B) Order Guides provide a list of guidelines for Administrators on how to set up item variables – Incorrect

Order Guides are forusers, not just administrators.

Theydo not provide setup guidelines; instead, they simplify ordering for end-users.

(C) Order Guides provide the ability to order multiple, related items as one request – Correct

This is theprimary functionof an Order Guide.

Instead of placing separate orders for different catalog items, a user can add allrelateditems to asingle request.

Example:Employee Onboarding Order Guide

Laptop

Email account

VPN access

Software (e.g., Microsoft Office, Adobe Suite)

(D) Order Guides take the user directly to the checkout without prompting for information – Incorrect

Order Guidescan include user prompts(variables, conditions) before checkout.

Users may be asked for specific detailsbeforesubmitting the request (e.g., laptop specifications, software preferences).

Explanation of Each Option:

Use dynamic variables: Order Guides can ask questions that determine which items should be included in the request.

Improve user experience: Order Guides streamline ordering, ensuring users request all necessary items without forgetting anything.

Enhance fulfillment efficiency: Since multiple items are grouped in one request, IT and fulfillment teams can process them together, reducing delays.

Example Use Cases:

New Hire Onboarding(laptop, software, security badge, phone)

Office Setup Request(desk, chair, monitor, accessories)

Additional Notes & Best Practices:

ServiceNow Docs: Order Guides Overview

ServiceNow Community: How to Configure an Order Guide

References from Certified System Administrator (CSA) Documentation:

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

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

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:

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:

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

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

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

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

Service Offerings:

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

Structured Request Fulfillment:

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

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

Automation and Approvals:

Some catalog items requiremanagerial or departmental approvalsbefore fulfillment.

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

Integration with Incident, Change, and Asset Management:

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

Access Through the Self-Service Portal:

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

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

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

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

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

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

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

ServiceNow Docs – Service Catalog

ServiceNow Learning – Self-Service & Service Catalog Best Practices

References from Certified System Administrator (CSA) Documentation:

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

What is an Update Set?

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

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

Why Avoid Using the Default Update Set?

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

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

Itcannot be exported.

It contains system changes that arenot logically grouped.

It can causeinconsistencies and missing dependencieswhen moving updates.

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

Understanding Update Sets in ServiceNow:

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

This follows ServiceNow’sbest practicesfor managing Update Sets.

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

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

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

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

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

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

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

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

Incorrectbecausea completed Update Set should not be reopened.

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

ServiceNow CSA Study Guide – Update Sets & Configuration Management

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

ServiceNow Docs: Moving Customizations with Update Sets

References from the Certified System Administrator (CSA) Documentation:

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.

ServiceNow uses a hierarchical structure to manageService Catalog requests:

REQ (Request Record)

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

It groups all requested items and their associated tasks.

Found in thesc_requesttable.

RITM (Requested Item Record)

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

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

Found in thesc_req_itemtable.

TASK (Catalog Task Record)

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

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

Found in thesc_tasktable.

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

This is thecorrect pathbecause it follows theServiceNow fulfillment structure:

REQ (Request)– Tracks the entire request.

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

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

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

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

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

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

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

Incorrectbecausenot all requests involve procurement.

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

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

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

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

ServiceNow CSA Study Guide – Service Catalog & Request Fulfillment

ServiceNow Docs: Request Fulfillment Process(ServiceNow Documentation)

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

References from the Certified System Administrator (CSA) Documentation:

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

ServiceNow Community: Best Practices for CMDB Data Accuracy

References from Certified System Administrator (CSA) Documentation:

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.

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

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

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

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

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

caller_id.email

Here’s how it works:

caller_id→ References thesys_usertable

email→ Retrieves theemail field from the sys_user record

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

caller_id.department.name

caller_id→ References theUser table

department→ References theDepartment table

name→ Retrieves thedepartment name

(A) Table-Walking – Incorrect

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

The correct term for referencing related fields isDot-Walking.

(B) Sys_ID Pulling – Incorrect

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

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

(C) Dot-Walking – Correct

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

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

(D) Record-Hopping – Incorrect

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

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

Explanation of Each Option:

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

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

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

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

Additional Notes & Best Practices:

ServiceNow Docs: Understanding Dot-Walking

ServiceNow Community: Best Practices for Dot-Walking

References from Certified System Administrator (CSA) Documentation:

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

Single-Instance:

Each ServiceNow instance is aunique, independent environmentfor a customer.

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

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

Single-Tenant Model (Multi-Instance Architecture):

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

Thisensures data security, performance isolation, and customization flexibility.

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

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

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

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

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

ServiceNow does NOT use a multiple-tenant architecture.

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

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

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

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

ServiceNow Product Documentation – Multi-Instance Cloud

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

ServiceNow Best Practices – Security & Instance Architecture

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

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.

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

Stores a record for every table in the ServiceNow instance.

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

Helps administratorsview, modify, or create new tablesin ServiceNow.

Used inTable Administration and Custom Table Development.

A. [sys_master_db]–

This tabledoes not existin ServiceNow.

C. [sys_master_object]–

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

D. [sys_object_db]–

This tabledoes not existin ServiceNow.

The correct name issys_db_object.

Navigate toSystem Definition→Tables.

Search for the tablesys_db_object.

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

ServiceNow Docs: Understanding Tables and

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

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

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:

In ServiceNow, eachKnowledge Base (KB)can have unique configurations, includinglifecycle workflows, user criteria, category structures, and management assignments. This flexibility allows organizations to manage knowledge articles according to different business needs, departments, or service functions.

Each knowledge base can have a customworkflowthat defines how articles are created, reviewed, published, and retired.

Examples of workflow stages:Draft → Review → Published → Retired.

Workflows ensure proper governance and content accuracy before publishing.

ServiceNow allows administrators to defineUser Criteriato controlwho can read, create, or contributeto a knowledge base.

Example:

IT Knowledge Base is only accessible to users with theITIL role.

HR Knowledge Base is only available toHR employees.

Each knowledge base can have a uniquecategory hierarchyto organize articles efficiently.

Example:

IT KB Categories:Hardware, Software, Network.

HR KB Categories:Benefits, Policies, Payroll.

Different knowledge bases can have different owners or managers.

Example:

IT KB is managed byIT Support Team.

HR KB is managed byHR Admins.

ServiceNow allows multiple knowledge bases with distinct configurations.

Each knowledge base can haveits ownworkflow, user criteria, categories, and managers.

This ensuresflexibility and proper governancein knowledge management.

ServiceNow Docs: Knowledge Management Overview

ServiceNow CSA Study Guide – Knowledge Base Administration

ServiceNow Product Documentation: Configuring Knowledge Bases

Key Aspects of Knowledge Base Customization:1. Unique Lifecycle Workflows2. User Criteria (Access Control)3. Category Structures4. Management AssignmentsWhy "A. True" is the Correct Answer?References from Certified System Administrator (CSA) Documentation:

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

Definition of a Metric:

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

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

Key Characteristics of a Metric:

It is used toassess process performanceandevaluate efficiencywithin IT services.

It providesquantifiable datato analyze trends and improvements in Service Management.

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

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

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

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

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

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

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

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

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

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

ServiceNow CSA Study Guide – Reporting & Performance Analytics

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

ServiceNow Performance Analytics & Reporting Overview

References from the Certified System Administrator (CSA) Documentation:

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:

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:

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.

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

Specific Table Name ACLs

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

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

Parent Table Name ACLs(If applicable)

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

This ensures that inherited rules are properly applied.

Wildcard ACLs (*)(Any table)

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

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

Order of Processing ACL Rules:

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

Wildcard rules (*) areprocessed last, not first.

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

This follows the correctprocessing order:

First:ACLs for the specific table

Second:ACLs for the parent table (if applicable)

Third:Wildcard ACLs (*)

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

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

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

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

Explanation of Each Option:

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

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

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

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

Additional Notes & Best Practices:

ServiceNow Docs: How Access Control Rules Work

ServiceNow Community: Understanding ACL Processing Order

References from Certified System Administrator (CSA) Documentation:

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

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.

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

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

Beforea record is saved (Before Business Rule)

Aftera record is saved (After Business Rule)

Asynchronously(Async Business Rule)

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

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

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

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

Example JavaScript snippet for a business rule:

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

current.priority='1';

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

}

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

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

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

Business rules have four execution types:

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

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

Async– Runs in the background after the transaction completes.

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

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

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

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

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

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

Automaticallyassigning prioritybased on ticket severity.

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

Sending email notifications when a record changes.

Modifying data before it is saved to enforce business policies.

Example Use Cases for Business Rules:

Coalescing is a crucial concept in ServiceNow's data import process. When a set of fields are marked as "coalesce" in aTransform Map, they act as unique identifiers to determine if an existing record should be updated rather than creating a new one.

If a match is found based on the coalesce field(s):

The system updates the existing record with the new data from the import.

If no match is found:

A new record is created.

How Coalescing Works in ServiceNow Imports:This means that coalescing helps maintain data integrity by preventing duplicate records while ensuring existing records receive updates when necessary.

When a record in the target table matches the value(s) in the coalesce field(s),ServiceNow updates that existing recordinstead of creating a new one.

This ensures that data is synchronized correctly rather than creating duplicate entries.

Option B (Incorrect):"If a match is not found using the coalesce fields, the system does not create a Transform Map."

The Transform Map isalways createdbefore the import process even starts. The presence or absence of a match has no impact on the Transform Map itself.

Option C (Incorrect):"If a match is found using the coalesce fields, the system creates a new record."

If a match is found, the existing record is updated,not replaced or duplicated.

Option D (Incorrect):"If a match is not found using the coalesce fields, the existing record is updated with the information being imported."

If a match isnotfound, anew recordis created, not an update to an existing one.

Why is Option A Correct?Why Are the Other Options Incorrect?

ServiceNow CSA Official Documentation on Data Import & Transform Maps:

ServiceNow Docs - Transform Maps

"If a field is coalesced, the system checks for matching records before inserting new ones. If a match is found, the existing record is updated; if no match is found, a new record is created."

Reference from Certified System Administrator (CSA) Documentation:

Conclusion:The correct answer isA. If a match is found using the coalesce fields, the existing record is updated with the information being imported.

????Understanding coalescingis vital for any ServiceNow administrator to ensure data integrity, avoid duplicates, and maintain system efficiency when handling data imports.

TheUser Menuin ServiceNow is accessible from the top-right corner of the interface by clicking on the user’s avatar or name. This menu provides various options that allow users to manage their sessions, roles, and impersonation settings.

The three correct actions a user can select from the User Menu are:

TheLog Outoption allows users to end their session and securely exit ServiceNow.

It is an essential feature for security and session management.

Location:User Menu > Log Out

Users with appropriate privileges (such as administrators) canelevate their rolesto gain temporary access to higher permissions.

This is primarily used when a user needs elevated access (e.g.,security_admin) to perform specific administrative actions.

Location:User Menu > Elevate Roles

Example:

A system administrator can elevate their role tosecurity_adminto access security-related configurations.

TheImpersonate Userfeature allows an administrator to act as another user without needing their credentials.

This is useful for troubleshooting, testing permissions, and verifying user-specific configurations.

Location:User Menu > Impersonate User

Example:

An admin impersonating a regular user can verify that the correct permissions and UI settings are applied.

1. Log Out ServiceNow (Correct)2. Elevate Roles (Correct, for Admin Users)3. Impersonate Users (Correct, for Admin Users)

Why the Other Options Are Incorrect:A. Send Notifications (Incorrect)

The User Menudoes notinclude an option to send notifications.

Notifications (emails, push notifications, SMS) are managed through:

System Notification > Email > Notifications

Outbound SMS or Messaging Settings

E. Order from Service Catalog (Incorrect)

Users can order items from theService Catalog, butthis action is not available from the User Menu.

Instead, users access the Service Catalog through:

Self-Service > Service Catalog

Requests and Catalog Items pages

F. Approve Records (Incorrect)

Users canapprove recordsif they have approval roles (e.g.,approver), but this action is not directly available from theUser Menu.

Approvals are managed through:

My Approvalsin Self-Service

The Approvals module in theServiceNow application navigator

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

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

Pathway 1: Knowledge Base > My Knowledge > Flagged Articles

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

Location:Knowledge Base → My Knowledge → Flagged Articles

Pathway 2: Knowledge > My Articles > Flagged

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

Location:Knowledge → My Articles → Flagged

A. Knowledge > Articles > My Flagged

There isno direct "My Flagged" optionunderKnowledge > Articles.

D. Knowledge > Articles > Published

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

Navigate toKnowledge > My Articles > Flagged.

OR navigate toKnowledge Base > My Knowledge > Flagged Articles.

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

ServiceNow Docs: Managing Knowledge Feedback and Flagged

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

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

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

Banner Image (Option A)

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

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

Browser Tab Title (Option C)

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

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

System Date Format (Option D)

Allows admins toset the date formatdisplayed across the instance.

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

Customizable Elements via Basic Configuration UI 16:

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

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

E. Form Header Size

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

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

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

????ServiceNow UI Customization Documentation

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

Conclusion:The correct answers are:

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

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

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

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

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

ServiceNow Docs: UI Action

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

TheApplication Navigator (App Navigator) search fieldin ServiceNow allows users to quickly findapplications, modules, and favoritesby typing relevant keywords. It helps in easy navigation by filtering available options as the user types.

Thefour correct answersdescribe what the App Navigator search field can return:

The search field can return bothapplicationsand their respectivemodulesin the left navigation panel.

Example: Searching for "Incident" will return:

Application:"Incident"

Modules:"All", "Open", "Resolved", "Create New"

Modulesare specific functionalities within an application.

Searching by a module name directly will display results that match the keyword.

Example: Searching for "Create New" will return modules like:

"Create New Incident"

"Create New Change Request"

The search field supports findingfull applicationsby their name.

Example: Typing "Change" will display theChange Managementapplication and its related modules.

If a user has marked specific modules or applications asFavorites, they will appear in search results.

This helps users quickly access commonly used features.

1. Names of Applications and Modules (Correct)2. Names of Modules (Correct)3. Names of Applications (Correct)4. Favorites (Correct)

Why the Other Options Are Incorrect:E. History Records (Incorrect)

TheHistory tabin the navigation panel showsrecently accessed records, but it isnot searchable through the App Navigator.

Instead, users can find history under:

History Module(System Settings > History)

Recent History Tabin the left navigation

F. Titles of Dashboard Gauges (Incorrect)

Dashboard Gaugesare visual elements onPerformance Analytics or Reporting Dashboardsand arenot searchablein the App Navigator.

Instead, dashboards and reports are found under:

Self-Service > Dashboards

Performance Analytics > Dashboards

A ServiceNow user wants toquickly access the "All Incidents" module.

They type "incident" into the App Navigator search.

The search results return:

Incident (Application)

All (Module)

Assigned to Me (Module)

Resolved (Module)

Example Use Case:This allows for quick navigation without manually expanding application menus.

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

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

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.

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

Connect Chatis the real-time messaging tool in ServiceNow that allows logged-in users to communicate instantly within the platform. It provideslive, interactive conversationsbetween users, which is particularly useful for collaboration in IT Service Management (ITSM), HR, and other ServiceNow modules.

Primary Functionality:

Enablesreal-time conversationswithin ServiceNow.

Allows communication betweenindividual users, groups, and support teams.

Can be integrated into variousServiceNow applications(e.g., Incident Management, HR Service Delivery).

Where to Access It:

Users can accessConnect Chatfrom theConnect Sidebar(a chat window on the right side of the screen).

Available under:All → Connect Chat.

Key Features:

Supportsone-on-one and group conversations.

Integrates withwork notes and commentson ServiceNow records.

Providesnotifications and presence indicatorsto show who is online.

Understanding Connect Chat:

B. Now Messenger– Incorrect.

No such tool calledNow Messengerexists in ServiceNow.

C. User Presence– Incorrect.

User Presenceallows users to seewho is onlinein the system but does not provide chat functionality.

D. Comments– Incorrect.

Commentsare used to provideasynchronous updateson records but do not enablereal-time communication.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Connect Chat

ServiceNow CSA Study Guide → Collaboration Tools in ServiceNow

ServiceNow Knowledge Base → Connect Chat vs. User Presence

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

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.

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

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

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

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

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

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

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

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

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

ServiceNow Documentation:Data Policies

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

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

A. True

InServiceNow,Access Control Rules (ACLs)define thepermissionsrequired for users to interact with records, fields, or UI actions. ACLs are enforced at thedatabase leveland are evaluatedbefore granting accessto a user.

Access Control rules can be configured usingthree primary permission requirements:

Rolesdefine aset of permissionsassigned to users.

Access Control rules canrequire users to have a specific role(e.g.,admin,itil,catalog_admin) to perform an action on a table, field, or record.

Example:

A rule might state:Only users with theitilrole can read theIncidenttable.

Conditional expressionsallow access based on a specified condition.

These conditions areevaluated at runtime, and access is granted if they are met.

Example:

A condition could be:"Allow access if the record's 'State' field is 'New'".

This would mean that users can only modify records if their state is "New".

Scriptsallow advanced, custom logic to determine access.

ACLs supportserver-side scripts(written in JavaScript) that use thegs.hasRole(),currentobject, or other logic to evaluate whether a user should have access.

Example:

1. Roles (Correct -)2. Conditional Expressions (Correct -)3. Scripts (Correct -)javascript

CopyEdit

// Allow access only if the user is the requester of the record

answer = current.requested_for== gs.getUserID();

Scripts provideflexibilityby allowing complex access conditions beyond simple roles or expressions.

C. Assignment Rules(Incorrect)

Assignment Rulesare used toautomatically assign recordsto users or groups based on conditions.

They do not defineaccess control permissions.

E. User Criteria(Incorrect)

User Criteriais used inService CatalogandKnowledge Base (KB)to control access to catalog items or knowledge articles.

It isnot usedfor ACLs at the table/field level.

F. Groups(Incorrect)

Groupsare collections of users but cannot be directly used in ACLs.

Instead,roles(which are often assigned to groups) are used to define ACL permissions.

Why Other Options Are Incorrect?

ServiceNow Product Documentation - Access Control Rules

Access Control Rules Overview

Defining Access Control Rules

ServiceNow Security Model

Role-Based Access

Scripted ACLs

References from ServiceNow CSA Documentation:

In ServiceNow, access to applications is controlled byroles. Most applications, such asIncident, Change, and Facilities, require specific roles to access them. However, theSelf-Serviceapplication is available to all users, including those with the base"ess" (Employee Self-Service)role, which is assigned to every user by default.

Why "D. Self-Service" is the correct answer?TheSelf-Serviceapplication is designed for general users (end users, employees, customers) who do not have elevated permissions. It provides access to:

TheService Catalog(to request IT services, software, and hardware).

TheKnowledge Base(to search for articles and solutions).

Viewing and tracking submitted requests and incidents.

Submitting new incidents or requests.

Since it is meant forall users, it does not require any additional roles beyond the default ones given to employees or customers.

A. Change– Incorrect. TheChange Managementapplication is typically restricted toITIL users(users with theitilrole) and change managers. End users do not have access to this module.

B. Incident– Incorrect. While end users can create and view their own incidents viaSelf-Service, theIncident Managementmodule itself is restricted to IT support staff (users with theitilrole or higher).

C. Facilities– Incorrect. TheFacilitiesapplication, which includes asset tracking and work orders, is typically restricted to users managing physical assets or facility-related tasks. It is not available to all users by default.

ServiceNow Product Documentation - Self-Service Application Overview

ServiceNow CSA Study Guide - User Roles and Permissions

ServiceNow Docs: Access Control and Application Scope

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

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

User Places an Order:

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

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

ServiceNow Generates a Request (REQ):

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

It is stored in thesc_requesttable.

Creation of Requested Items (RITM#):

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

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

Tasks (SCTASK#) Are Created:

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

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

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

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

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

ServiceNow Product Documentation → Service Catalog → Request Fulfillment

ServiceNow CSA Study Guide → Service Catalog and Request Management

ServiceNow Tables Reference → sc_request, sc_req_item, sc_task

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

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

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

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

REQ (Request Record) – The Order Number

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

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

Example:REQ0010023

RITM (Requested Item) – The Individual Catalog Item

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

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

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

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

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

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

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

Breakdown of the Service Catalog Request Structure:

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

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

C. The task to complete (Incorrect)

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

Tasks are specific actions assigned to fulfill an item request.

D. The individual item in the order (Incorrect)

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

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

REQ0012345→ Tracks the overall request (Order Number)

RITM0016789→ Laptop Request

TASK0018901→ IT configures the laptop

RITM0016790→ Software License Request

TASK0018902→ IT assigns the software license

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

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:

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

In ServiceNow’sService Catalog, the display sequence of variables within aCatalog Itemis controlled by theOrder field in the Variable form. TheOrder fielddetermines the position in which the variables appear when a user fills out a catalog item. Lower values appear first, and higher values appear later.

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

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

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

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

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

Each variable in a catalog item has anOrder field.

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

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

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

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

Explanation of Each Option:

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

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

ServiceNow Docs: Creating and Configuring Service Catalog Variables

ServiceNow Community Best Practices for Service Catalog Variables

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

InServiceNow, theStamp icon (????)in theForm Headeris used to accessForm Templates.Templatesallow users to quickly populate fields in a form withpredefined values, improving efficiency and consistency.

Open arecord form(e.g., Incident, Change, or Request form).

Click theStamp (????) iconin the form header.

Select atemplatefrom the list.

The form fields will bepre-filledwith the template’s values.

A. Paperclip

ThePaperclip iconis used toattach filesto a record, not access templates.

B. Pages

NoPages iconis used for templates in ServiceNow.

D. More Options{...}

TheMore Options menuprovides access to additionalrecord actions, but templates are accessed using theStamp icon.

InServiceNow,Access Control Rules (ACLs)are used togrant or restrict permissionsfor performing actions on a table or field.

To allow a user with theitilrole tocreate Incident records, the correctAccess Control Rulemust:

Apply to theincidenttable

Grant the "create" operation

Be restricted to users with the "itil" role

Breaking Down the Correct ACL Configuration:ACL Field

Correct Value

Name

incident.None(applies to the table-level, not a field)

Operation

create(allows creating new records)

Role

itil(only users with the itil role can create incidents)

incident.None→Applies to the entire table(for record creation).

incident.*→Applies to all fieldsin the table (not needed for create operations).

Why is "incident.None" used instead of "incident.*"?

A. Name:incident”; Permission: write; Role: itilIncorrect– The "write" permissionallows editing existing records, butdoes not allow creating new ones.

B. Name:incident Any, Operation: write, Permission: itilIncorrect– There is no such name format"incident Any"in ACLs. Also, "write" does not allow record creation.

C. Name:incident.*; Operation: write; Permission: itilIncorrect– "incident.*" appliesto all fields in the table, but doesnot apply to record creation.

D. Name:incident None, Permission: create: Role: itilIncorrect– The correct format uses"Operation: create", not "Permission: create".

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Rules????How ACLs Work

ServiceNow Docs – Configuring ACLs for Tables and Fields????Table-Level vs Field-Level ACLs

Official ServiceNow Documentation References:

Detailed Explanation:

TheServiceNow Storeis the primary marketplace for accessing pre-built integrations, known as spokes, for ServiceNow. These spokes enable rapid integration with third-party services, streamlining the development of automation and integration workflows. The store includes various applications and plugins tailored for ServiceNow workflows, facilitating the quick deployment of additional capabilities. (Reference: ServiceNow Documentation - ServiceNow Store and Integration Hub Spokes)

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

To filter records in alist view, users can:

Click on thefilter icon.

Applyconditionsto refine the displayed records.

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

Thesecurity_adminrole in ServiceNow is required to make changes toHigh Security Settings(now part ofSystem Security Settings).

Modify high-security settingsin ServiceNow.

Elevate privilegesto make changes to sensitive security configurations.

Manage Access Control Lists (ACLs)to define security rules.

Users with theadminrole alonecannot modify high-security settings.

Thesecurity_adminrole requireselevationvia the"Elevate Role" optionin the user menu.

This ensures thatonly authorized administratorscan modify security-related configurations.

B. sn_ad_admin– No such role exists in ServiceNow.

C. high_sec_admin– This is not a valid ServiceNow role.

D. admin– Theadmin role alonedoesnot grant access to high-security settingswithoutelevating to security_admin.

ServiceNow Security Admin Role and Elevated Privileges

ServiceNow CSA Training Module:"Managing Security Settings and Access Controls"

What Can the security_admin Role Do?Why Elevation is Required?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

The Customer Actions feature in the Security Center allows administrators to take targeted actions such as reviewing privileged user access and managing accounts that might pose a risk. It is specifically designed to enable organizations to identify and remediate risks associated with user privileges, such as excessive access rights or orphaned privileged accounts. This feature aggregates risk data and prompts action items, allowing administrators to review, approve, or revoke privileged access based on current organizational policies.

While Security Hardening focuses on platform configurations and the Security Posture Console provides an overview of security metrics and trends, Customer Actions is the practical tool for directly managing and reviewing privileged access to ensure least privilege principles are enforced.

InServiceNow, theActivity Streamsection on a task record displays themost recent updatesmade to that record. It logschanges in fields, comments, work notes, and system updatesin real time.

Displays a chronological history of changes

Showswho made the update, when it was made, and what changed.

Includescomments, work notes, system-generated updates, and field value changes.

Real-time updates for collaboration

If multiple users are working on the same record, they can seeupdates in real-time.

Useful for ITSM workflows (Incidents, Change Requests, Tasks).

Integrated with Comments and Work Notes

Users can addcomments (visible to users) or work notes (internal notes)directly in the Activity Stream.

Why is "Activity Stream" the Correct Answer?

Example View of Activity Stream in a Task Record:Timestamp

User

Action

10:15 AM

John Doe

Updated Priority from "Low" to "High"

10:20 AM

Jane Smith

Added a work note: "Waiting for user confirmation"

10:30 AM

System

State changed from "New" to "In Progress"

A. Related ListIncorrect– Related Lists showlinked records (e.g., affected CIs, approvals, attachments)butnot recent updates.

C. Audit LogIncorrect– TheAudit Log (sys_history_line table)tracksdatabase-level changesbut is not displayed as anActivity Streamon a task record.

D. TimelineIncorrect– No standard"Timeline"section exists inServiceNow task records.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Activity Streams????Understanding Activity Streams

ServiceNow Docs – Viewing Record History in Activity Stream????Using Activity Streams in Task Records

Official ServiceNow Documentation References:

TheSystem Administrator (admin)role is the most powerful and common role in ServiceNow, providing access to nearly all platform features, functions, and data. Users with this role have full control over system configurations, user management, security settings, application access, and more.

Full system accessto all applications, modules, tables, and records.

Ability toconfigure and customizethe platform.

Create, update, and deleterecords in any table.

Manage roles and users, including assigning roles to others.

Configure Access Control Rules (ACLs)to define security policies.

A. Security Admin [security_admin]→ Incorrect. Thesecurity_adminrole is primarily for managing security settings and access control rules. While powerful, it does not inherently provide access to all platform functions like theadminrole does.

B. Sys Admin [sys_admin]→ Incorrect. There isno such role as "sys_admin"in ServiceNow. The correct role isadmin.

C. Admin [sn_admin]→ Incorrect.sn_adminis not a standard ServiceNow role. The official role is simplyadmin.

E. Base Admin [base_admin]→ Incorrect. This is not a standard role in ServiceNow.

In ServiceNow,Core Tablesare foundational tables that are included by default in the platform. These tables store essential records used across various applications and modules.

????Key Core Tables in ServiceNow:

Task (task)– A core table that serves as the parent for several other tables, such as Incident, Change, and Problem.

User (sys_user)– Stores all user records in the instance.

Incident (incident)– A child table oftask, used to track issues and requests reported by users.

????Why Option C is Correct?

User (sys_user)– Essential for user management in ServiceNow.

Task (task)– A fundamental table that many other tables extend from.

Incident (incident)– A widely used table in IT Service Management (ITSM), which extends fromtask.

????Incorrect Options Explained:

A. Configuration, Connect, Chat– Configuration is broad and does not refer to a single table, and Connect and Chat are part of ServiceNow’s communication framework but are notcoretables.

B. Team, Party, Awards– These tables do not exist in ServiceNow’s core platform.

D. Work, Caller, Timecard– WhileCallermay refer to users, andTimecardis a table used in time-tracking applications, these are not considered core tables.

????Reference:

Creating Tables in ServiceNow

ServiceNow Task Table Documentation

Understanding Core Tables in ServiceNow

UI Actions related to Listsin ServiceNow provide ways to interact with and modify list data through differentUI elements.

A. List Links

Appear at thebottom of listsand provide actions such as"Create New"or"Save as Template."

B. List Control

Located in thelist title bar, allowing users to configure views, export data, and refresh lists.

C. List Buttons

Buttons added to a list form thattrigger specific actions, such as"Approve"or"Reject."

D. List Context Menu

Right-click menuon list records providing actions likeEdit, Delete, Assign, and Export.

E. List Override

No such feature called "List Override" exists in ServiceNow.

F. List Choices

This term is not a recognized UI Action for lists in ServiceNow.

InServiceNow Catalog Item Workflows, anapproval processoften includes aManager Approval step, which typically requires the requester'smanager(as defined in thesys_userrecord) to approve the request.

IfBob Smith's user record does not have a manager specified, the systemcannot determine who should approve the request, which may result in the approval step beingskipped.

A. There is a business rule, excluding Bob Smith from any approvals.

While business rules can affect approvals, it isunlikelythat a rule would exist specifically to exclude Bob Smith unless explicitly configured, which is uncommon.

B. Bob Smith does not have a delegate set up on his account.

Delegates areoptionaland only apply when a manager is unavailable. This does not affect whether the approval is skipped.

D. The manager does not have a delegate assigned.

A delegate only comes into play if an approveris out of officeor unavailable. This does not impact whether an approval isskipped entirely.

E. Bob Smith is a VIP.

Being marked as aVIPdoes not automatically bypass approval workflows. Approval processes follow defined rules in workflow configurations.

TheActivity Formatterin ServiceNow is a UI element that trackschanges and updatesmade to a record, including actionsnot saved directly within a field.

Displays atimeline of record updates, including comments, work notes, and field changes.

Capturessystem-generated events(such as status changes).

Allows users to viewhistorical activityon a record.

A. Sidebar– Thesidebarprovidesquick access to navigation menus, butdoes not track unsaved field changes.

B. List Editor– TheList Editorallowsinline editingof records but doesnot track changes separately.

D. Dictionary– TheDictionarydefines fields and tables but doesnot track changes made to records.

ServiceNow Activity Formatter

ServiceNow CSA Training Module:"Working with Activity Streams and Record History"

Key Features of the Activity Formatter:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

In ServiceNow, new tables can be created using theTables & Columnsmodule or theTablesmodule.

Navigation:System Definition > Tables & Columns

Allows admins tocreate and modify tables, including:

Adding columns (fields)

Setting relationships

Defining attributes

Navigation:System Definition > Tables

A simpler interface for creating tableswithout managing columns immediately.

B. Schema Map →Incorrect

Schema Mapvisualizestable relationships but does not allow table creation.

C. Dictionary →Incorrect

TheSystem Dictionary (sys_dictionary)is used tomanage fields and attributes, not create tables.

Creating Tables in ServiceNow

Understanding Tables & Columns

1. Tables & Columns Module(Correct Answer)2. Tables Module(Correct Answer)Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow, tasks (such as Incidents, Change Requests, and Service Requests) can be assigned toindividual usersorgroupsto manage workload distribution efficiently.

A. Groups

Groups in ServiceNow represent a collection of users with common roles or responsibilities.

Tasks are often assigned to groups first, allowing any member to take ownership.

Example:

IT Support Groupfor handling incident tickets.

Change Advisory Board (CAB)for approving changes.

B. Users

Individual users can receive task assignments directly.

Assigned users are responsible for completing or updating the task.

Example:

A specificService Desk Agentassigned to resolve an incident.

C. Departments

Departments in ServiceNow representorganizational divisions(e.g., HR, IT, Finance), but they donotreceive task assignments.

Assignments are made to groups or individuals within departments, not the department itself.

D. Teams

"Teams" is not a structured entity in ServiceNow for task assignments.

While some organizations may informally refer to groups as "teams," the platform recognizesGroupsandUsersas valid task recipients.

TheCI Dependency Viewin ServiceNowvisualizes relationships between Configuration Items (CIs), allowing IT teams totrace dependenciesbetween infrastructure components, such as servers, applications, and services.

Relationships define dependenciesbetweenConfiguration Items (CIs)in theConfiguration Management Database (CMDB).

TheCI Dependency Viewusesrelationshipstomap infrastructure componentsand theirservice dependencies.

AServer (CI)hosts aDatabase (CI)→ The database supports anApplication (CI)→ The application provides aService (CI).

By viewingCI Relationships, you cantrace failures upstream or downstreamto understand the impact.

Key Concept: CI RelationshipsExample Scenario:

A. Service Tracer →Incorrect

No such feature called"Service Tracer"exists in ServiceNow.

B. Automapping Utility →Incorrect

Auto-Discovery toolshelp populate theCMDB, but they do not enable tracing in theCI Dependency View.

D. Transform Map →Incorrect

Transform Mapsare used inImport Setsto map data between tables,not for dependency mapping.

Why Other Options Are Incorrect?

CI Dependency Views

Understanding CMDB Relationships

Official ServiceNow Documentation Reference:

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, theApprover [approver-user] roleis specifically designed for users who need toauthorize requestsbut should not have any other permissions or administrative access to the platform.

Canapprove or reject requests(e.g., Change Requests, Service Catalog Requests).

No additional platform permissions(cannot create, modify, or view records beyond approvals).

Assigned automatically tousers designated as approversin approval workflows.

AnIT Managerreceives an approval request for a new laptop.

Themanager logs in and sees only the approval request(no other system access).

Theyapprove/rejectthe request without modifying any records.

Key Features of the Approver Role:Example Use Case:

B. Authorize [authorize-user] →Incorrect

No such role exists in ServiceNow.

C. Reviewer [reviewer_user] →Incorrect

No such role exists in ServiceNow.

D. Approver Group [approval_group] →Incorrect

Approval groupsallow multiple users to approve a request collectively, but it is not a standalone role.

Theapprover-user roleis the correct answer for individual approvals.

E. Verification [verify_user] →Incorrect

No such role exists in ServiceNow.

Why Other Options Are Incorrect?

Approval Configuration

User Roles in ServiceNow

Official ServiceNow Documentation Reference:

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:

Detailed Explanation:

To edit the title of an application menu in ServiceNow:

Option C:Using the Navigator, selecting the application name, and clicking the pencil icon allows quick title adjustments.

Option D:Going toSystem Definitions > Application Menusand selecting the application provides comprehensive options for editing the application menu title and related settings. These approaches streamline menu customization and improve navigation. (Reference: ServiceNow Documentation - Application Menu Customization)

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

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:

InServiceNow Notification Configuration, dot-walking allows administrators to reference related records dynamically.

✔To send a notification to theCaller's Manager, you need to:

Open theNotification record.

Navigate to the‘Send to’ tab.

Add theCaller field.

Usedot-walkingto select theCaller's Manager field(e.g., caller_id.manager).

Option Ais incorrect because dot-walking is configured under the‘Send to’ tab, not the‘Who will receive’ tab.

Option Bis incorrect because while Flow Designer can trigger notifications, it does not specifically configure recipients based on dot-walking.

Option Cis incorrect because setting "Who will receive" toSubscribableis used for opt-in notifications, not direct notifications to the Caller's Manager.

????Reference:ServiceNow Administration – Notification Configuration & Dot-Walking

The Security Hardening feature in the ServiceNow Security Operations Security Center is specifically designed to help identify, resolve, and mitigate platform-related security issues and misconfigurations. Security hardening provides prescriptive guidance on improving your platform’s security posture by addressing vulnerabilities and ensuring compliance with security best practices. It includes automated checks and recommendations related to system configurations, access controls, and other settings that, if left unchecked, could expose the system to threats.

The Security Center’s Security Hardening dashboard aggregates these findings and allows administrators to track remediation progress effectively. Unlike the Security Scanner, which focuses more on vulnerability scanning of integrated systems, or Customer Actions, which involves manual customer intervention for specific issues, Security Hardening is the proactive tool ServiceNow provides to manage platform security risks internally.

InServiceNow,Client Scriptsrun on the client-side (browser) andmodify form behaviordynamically.

Tovalidate form data before submission, you must use anonSubmit()Client Script.

Executes Before Form Submission

TheonSubmit() Client Scriptrunsjust before the form is submitted, allowing validation checks.

If an issue is found, you canprevent form submissionusingreturn false;.

Best for Data Validation

Can check ifrequired fieldsare filled.

Can enforcebusiness rules on the client-side.

Example: Preventing submission if the"Short Description"field is empty.

Why is "onSubmit()" the Correct Answer?

ExampleonSubmit()Client Script:functiononSubmit() {

varshortDesc = g_form.getValue('short_description');

if(!shortDesc) {

alert('Short Description is required before submitting.');

returnfalse; // Stops the form from being submitted

}

returntrue;// Allows form submission

}

A. onSubmission()Incorrect–This is not a valid ServiceNow Client Script type.

C. onLoadIncorrect–Runs when the form loads, butdoes not validate form submission.

D. onUpdate()Incorrect–Runs when a record is updated, but doesnot control form submission.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Client Scripts Overview????Understanding Client Scripts

ServiceNow Docs – Using onSubmit() Client Scripts????Client Script Examples

Official ServiceNow Documentation References:

In ServiceNow,impersonating a userallows administrators or authorized users to temporarily assume another user’s identity. This is useful fortroubleshooting, testing permissions, and verifying user experiences.

admin (A)

Users with theadminroleautomaticallyhave impersonation privileges.

Admin userscan impersonate any user in the system.

Example: A system admin impersonates aService Desk Agentto test access restrictions.

impersonator (E)

Theimpersonatorrole allows a user to impersonate otherswithout full admin privileges.

This role is useful forsupport teams or testerswho need to verify user permissions.

Example: A QA tester is given theimpersonatorrole to test different roles in the system.

B. sys_admin

No such role assys_adminin ServiceNow—this is likely amistyped version of "admin".

C. security_admin

security_adminis used forelevating privilegesto modify high-security settings, not for impersonation.

D. sys_user

Thesys_usertablestores user recordsbut isnot a role.

Regular userscannotimpersonate others unless they have theimpersonatororadminrole.

AData PolicyinServiceNowensuresdata consistencyby enforcingmandatory fields and read-only field ruleswhendata is imported via Import Sets or Web Services.

Applies Business Rules to Imported Data

UnlikeUI Policies(which work only on forms),Data Policies enforce rules even when data is imported.

Ensures fields markedmandatory, read-only, or restrictedmaintain their constraints.

Ensures Data Integrity During Import Set Operations

Data coming fromexternal sources(e.g., API, CSV imports) mightlack required values.

Data Policiesprevent incomplete or incorrect recordsfrom being created.

Works Across Multiple Data Entry Methods

Data Policies apply to:

Forms(Optional)

Import Sets

Web Services (APIs)

Why is "Data Policy" the Correct Answer?

Example of a Data Policy in Action:Field

Condition

Action

State

If empty on import

Set to "New"

Priority

If not provided

Set to "Medium"

Short Description

If empty

Reject the record

A. Client ScriptIncorrect– Client Scripts only runon the user interface (browser-side), not on imports.

B. UI PolicyIncorrect– UI Policies only apply toform interactions, not to Import Sets or Web Services.

D. CSDM (Common Service Data Model)Incorrect– CSDM is aframework for organizing CMDB data, but it does not enforcedata integrity rulesduring imports.

E. Business RuleIncorrect– Business Rules can enforce logic, but theyrun after the record is inserted, meaning they donot prevent bad data from being imported.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Data Policies????Understanding Data Policies

ServiceNow Docs – Data Policies vs UI Policies????When to Use Data Policies

Official ServiceNow Documentation References:

InServiceNow,Flows (Flow Designer)is the recommended way tomanage multi-level approvals and notificationsfor catalog items like ordering a new iPhone.

Why Flows?

✔Automates Approval Processes– Flows allowsequential and parallel approval stepsto ensure that the request goes through multiple levels of approval.

✔Built-in Notifications– Automatically sendsemail or system notificationsto requesters andapprovers at each step.

✔Low-Code Solution– Eliminates the need for complex scripting by using agraphical interfaceto configure approvals and actions.

A user submits a request for anew iPhonethrough theService Catalog.

TheFlow Designer workflowstarts and routes the request to thefirst-level approver.

If approved, it moves to thesecond-level approver.

Notificationsare sent to the requestor and approvers at each step.

A. Parent-Child Approvers

No such built-in feature exists in ServiceNow. Approvals are handled viaFlow DesignerorWorkflow Engine.

B. Approval Chains

Approval Chains are not an officialServiceNow feature. The correct term isFlow Designer Approval Actions.

D. Approval Criteria

ServiceNow usesconditionsto define approval requirements, butApproval Criteriais not a standalone feature.

E. Approver Delegates

Delegates allow users toassign approvals to others, but theydo not manage multi-level approvals.

InServiceNow,Access Control Rules (ACLs)determine whether auser can access a specific record, table, or field.

When evaluatingtable ACLs, ServiceNow follows aspecific-to-generalapproach:

First, it checks the most specific ACL (Table ACL)

Example: If the table isincident, ServiceNow first checks ACLs forincident.

Then, it checks the Parent Table ACL(if the table is inherited)

Example: Sinceincidentextendstask, it will check ACLs fortask.

Finally, it checks the Wildcard ACL (*ACL)

If no specific or parent table ACL is matched, ServiceNow checks for awildcard ACL(*.read,*.write, etc.).

Specific Table ACL(e.g.,incident.read)

Parent Table ACL(e.g.,task.read)

Wildcard ACL(e.g.,*.read)

Order of ACL Evaluation:Thisensures granular access control, giving priority tomore specific rules before applying broader permissions.

*A. Specific to general: Table.Field ACL, Parent Table.Field ACL, .Field ACLIncorrect– Field ACLs are evaluatedaftertable ACLs. This option confuses table and field evaluation.

B. Bottom to top: Table ACL, Table.Field ACL, Parent Table.Field ACLIncorrect– The correct order isTable ACL → Parent Table ACL → Wildcard ACL, not Table.Field ACL order.

C. General to specific: Table ACL, Table.Field ACL, Parent Table, Field ACLIncorrect– ServiceNow appliesspecific ACLs first, not general ones.

D. Top to bottom: Wildcard Table ACL, Parent Table ACL, Table ACLIncorrect– Wildcard ACLs are evaluatedlast, not first.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Evaluation Order????Access Control Rules

ServiceNow Community – ACL Best Practices????Understanding ACL Processing

Official ServiceNow Documentation References:

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, to modify the available choices for a choice field like "Priority" on a form, an administrator must use the"Configure Choices"option. This can be accessed by:

Right-clicking the field label (e.g., Priority).

Selecting"Configure Choices"from the context menu.

Adding, editing, or removing available choice values for that field.

This method ensures that only the available choices are displayed to users.The "Priority" field in a Catalog Task is a choice field, so modifying its options requires "Configure Choices".

When using theData Pill Pickerin Flow Designer,dot-walkingis used to access fields inrelated tables.

The shortcut fordot-walkingin theData Pill Pickeris:????Ctrl

Dot-walkingallows users toaccess fields in referenced records.

For example, if you have anIncidentrecord with aCallerfield (which references thesys_usertable), you candot-walkto theCaller’s emailusing:

What is Dot-Walking?CopyEdit

incident.caller.email

This is useful whenbuilding conditions, flows, and reportsin ServiceNow.

A. Arrows– Arrow keys are used for navigation, but they do not support dot-walking.

B. Plus, Minus– These keys arenot used for dot-walkingin ServiceNow.

C. Ctrl C, Ctrl– These are copy-paste shortcuts, unrelated to dot-walking.

E. Shift F4, Shift F5– These do not have any function related to dot-walking.

ServiceNow Dot-Walking & Data Pill Picker

ServiceNow CSA Training Module:"Using Dot-Walking in Flow Designer and Reporting"

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

Detailed Explanation:

In ServiceNow, users with the Impersonate role can impersonate other users to troubleshoot and validate user permissions and experiences. However,System Administratoraccounts cannot be impersonated to maintain security and prevent unintended administrative access. This restriction ensures that sensitive administrative functions are secure and can only be accessed directly. (Reference: ServiceNow Documentation - User Impersonation and Security Restrictions)

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

InServiceNow, theActivitysection on theNotestab provides adetailed historyof all work documented on a record. It logs:

✔Updates & Field Changes(who changed what and when)

✔Comments & Work Notes

✔Approval History

✔Assignment Changes

TheActivity Streamis essential for tracking progress, ensuring transparency, and auditing record updates.

A. Journal

ServiceNow does not have a specific "Journal" tab for history tracking. However,journal fields(like work notes and comments) are logged in theActivitysection.

C. Diary

No such section called "Diary" exists in ServiceNow for tracking record history.

D. Audit Log

TheAudit Logtracks field-level changes in aseparate system logbut is not displayed in theNotes tab. It requires admin-level access to view detailed changes.

E. Timeline

"Timeline" is not a default section under the Notes tab. It is sometimes used incustom applications, but thecorrect answer is "Activity."

In ServiceNow, theDependency Viewprovides aninteractive graphical interfaceto visualizeConfiguration Items (CIs) and their relationships. It helps IT teams understand the dependencies between infrastructure components, applications, and services.

Graphical Representation of CI Relationships:

Displays Configuration Items (CIs) and their dependencies usinga dynamic, interactive visualization.

Useslines/arrowsto represent relationships such asdepends on, runs on, hosted by, etc.

Real-Time Impact Analysis:

Helps identifyhow an outage or change to one CI affects related components.

Useful forchange management, incident resolution, and troubleshooting.

Integration with CMDB (Configuration Management Database):

Dependency Views pull data from theCMDBand display it visually.

SupportsITSM (IT Service Management), ITOM (IT Operations Management), and IT Asset Management.

Supports Multiple Relationship Types:

Application-to-Application relationships

Infrastructure dependencies (e.g., servers, databases, cloud resources)

Business Services mapping to technical services

A. CSDM SchemaIncorrect – TheCommon Service Data Model (CSDM)is a framework for organizingCMDB data models, but it does not provide agraphical interfacefor visualizing dependencies.

B. Business Service MapIncorrect – Business Service Maps arepart of Service Mapping(ITOM feature), showinghigh-level business service dependencies, butDependency Viewprovides a more detailed, real-time interactive visualization ofCIs in CMDB.

D. CI Class MapIncorrect – The CI Class Map showsCMDB class structures, not live dependency relationships between CIs.

ServiceNow Docs – Dependency Views????Dependency Views Overview

ServiceNow Community – CMDB Best Practices????CMDB and Dependency Views

Key Features of Dependency View:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. Dependency Viewbecause it provides amodern interactive graphical interfaceto visualizeCIs and their relationshipsinCMDB.

To customize thebanner image, text, and colorsof your instance in ServiceNow, you use theSystem Properties > Brandingmodule. This module allows administrators to control variousUIaspects, including thebrandingof the system.

Banner Image: Change the header image seen across the UI.

Text: Customize the text displayed in the header or other branding areas.

Colors: Modify the colors of various UI elements to match your company's branding.

Key Customizations Available in Branding:This is typically applied to bothUI16 (desktop)andUI11 (classic)interfaces, ensuring a consistent experience across the instance.

A. Homepage Admin > Pages > Branding– This is used forhomepagesrather than global instance branding.

C. System Properties > Basic Configuration UI16– This section allows configuration of theUI layout and elementsbut does not specifically manage branding elements like banner image and colors.

E. Service Portal > Portals > Branding– This is specific toService Portal branding, not for global instance customization.

ServiceNow Branding Configuration

ServiceNow CSA Training Module:"System Properties and Branding"

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

In ServiceNow, aTaskis a fundamental record type that represents work that needs to be completed. Tasks can be assigned to users or groups, tracked through various states, and eventually marked asclosedwhen the work is completed.

Event (A)refers to a system-generated log of an occurrence (e.g., an email sent or a user action), but it is not a record that moves through states like a task.

Report (B)is used for analyzing and visualizing data but does not track work progress.

Flow (D)refers toFlow Designer flows, which automate processes but are not individual work items themselves.

Tasks are widely used across ServiceNow applications, such asIncident Management, Change Management, and Service Requests, to track and manage work.

????Reference:ServiceNow Platform Fundamentals – Task Management Concepts

Detailed Explanation:

Data Policiesin ServiceNow are designed to enforce data consistency across all entry points into the platform, including record forms (UI), Import Sets, and Web Services. Data Policies ensure that required fields, read-only fields, and other data integrity rules are maintained consistently. Unlike UI Policies, Data Policies apply universally to data imported or integrated, ensuring platform-wide data governance. (Reference: ServiceNow Documentation - Data Policies and Data Consistency)

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

When transferringlarge amounts of databetween ServiceNow instances, the mostefficient and recommended methodisExport to Data Package. This method allows for bulk data transfer, ensuring that relationships, dependencies, and data integrity are maintained.

Optimized for Large Data Transfers

Data Packages are designed toefficiently handle large datasetswithout performance degradation.

They maintain relationships between records, unlike simple XML exports.

Preserves Data Integrity

Ensures that allreferenced records(e.g., related tables) are included in the export.

Prevents data loss by preserving dependent records.

Faster and More Reliable than XML or Update Sets

XML exports areless efficientfor large datasets.

Update Setsdo nottransfer actual table records, only configurations (metadata).

Supports Complex Data Structures

Useful for movingentire tablesor a large subset of records while maintaining relationships.

Why "Export to Data Package" is the Best Choice?

B. Export to XMLIncorrect– XML exports arenot efficient for large data transfersbecause:

It does not manage relationships between records.

Importing large XML filescan cause performance issues.

More suitable for movingindividual recordsrather than large datasets.

C. Update SetsIncorrect–Update Sets do NOT transfer actual data, only configurations (e.g., fields, forms, workflows).

They aremeant for customization changes, not for moving large data records.

D. Export to ZipIncorrect– There is no"Export to Zip"option for large data transfers in ServiceNow.

This is likely adistractor option.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Data Export and Import Best Practices????Data Export and Import

ServiceNow Docs – Moving Data Between Instances????Exporting and Importing Data Packages

Official ServiceNow Documentation References:

Conclusion:The correct answer isA. Export to Data Packagebecause it is themost efficient and scalableway to transfer large amounts of data between ServiceNow instances whilemaintaining relationships and data integrity.

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:

InReport Designer, theDatasection is used to specifygrouping and calculationsto be performed on the report's dataset.

Youselect the tablefrom which the report will pull data.

You definefiltersto limit the dataset.

You specify"Group By" fieldsto categorize data.

You applyaggregations (SUM, COUNT, AVG, etc.)to perform calculations on fields.

A. Style– Controlsvisual appearance(colors, fonts, chart type, etc.) but doesnot handle data grouping or calculations.

B. Format– Used forformattingelements but doesnot control grouping or data calculations.

D. Configure– There is no "Configure" section inReport Designer; settings are managed under other sections.

E. Group By– While "Group By" is usedwithintheDatasection, it is not a separate section itself.

ServiceNow Report Designer – Data Configuration

ServiceNow CSA Training Module:"Creating and Configuring Reports"

What Happens in the "Data" Section?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InTable Builder, only users with appropriate permissions can modify form layouts.

✔Theadmin role(Option C) has full access to configure forms, tables, and relationships.

✔Thepersonalize_form role(Option A) allows users to configure form layouts, but not table structures.

Option B (app_engine_admin)is incorrect because this role is used for managing custom applications, not form layouts.

Option D (read_only_user)is incorrect because it does not grant any configuration permissions.

Option E (support_specialist)is incorrect because it is typically forsupport personnelwho handle incidents and cases, not form design.

????Reference:ServiceNow Platform Administration – Roles & Permissions

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.

On theReports pagein ServiceNow, different sections allow users to seewhich reports are visibleto various audiences.

Why These Options Are Correct?C. My reports

Displaysreports created by the logged-in user.

These reports areprivateunless explicitly shared.

E. Dashboards

Dashboardsconsolidate multiple reports andmake them visible to specific audiences.

Users canshare dashboardswith groups or individuals.

F. Global

Global reportsare available toall users with reporting access.

These reports arenot restrictedto a specific user or group.

I. All

The"All" sectionlistsevery report the user has access to, including:

Personal reports

Shared reports

Global reports

Reports from dashboards

Why the Other Options Are Incorrect?A. Group

There isno "Group" sectionin the Reports page.

However, reports can beshared with groups, but there is no direct"Group" view.

B. Department

Departments do not determine report visibilityin the Reports page.

Report access is controlled byroles, users, and groups, not departments.

D. Team

Teams are not a standard report visibility categoryin ServiceNow.

Reports are shared atuser, role, and global levels, not by "Team."

G. Admin

There isno "Admin" sectionin the Reports page.

However,Admins can access all reportsvia the"All" section.

H. Analytics

Analytics is a separate modulein ServiceNow, primarily used forPerformance Analytics (PA)anddashboards.

It is not a standardreport visibility section.

J. Company

There isno "Company" sectionin the Reports page.

Reports can beshared at a global level, but not specifically by "Company."

ServiceNow Reports - Managing Visibility and Access

ServiceNow Reporting Guide - Sections of the Reports Page

ServiceNow Dashboards and Report Sharing Best Practices

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow (and databases in general), data is stored intables, which consist of:

Columns (Fields):Representindividual data attributes(e.g., Name, Email, Status).

Rows (Records):Representindividual entriesin the table (e.g., a specific Incident or User).

Key Concepts:Table

Columns (Fields)

Rows (Records)

Incident

Number, Caller, Priority, Description

Each unique incident entry

User

Name, Email, Role, Department

Each individual user record

A column represents a single field (data attribute), such as "Priority" or "Short Description."

A row represents a record (entry in the table), such as an individual incident or user.

A. A column is a field in the database and a record is one user→Incorrect

Records are not limited to users; a record could be an Incident, Change, or any other entry.

C. A column is one field and a record is one column→Incorrect

Arecord is not a single column; a record consists of multiple fields (columns).

D. A column contains data from one user and a record is one set of fields→Incorrect

Columns contain data for all users/records, not just one user.

A record is one row, not just a set of fields.

Why is "B. A column is one field and a record is one row" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Understanding Tables and

References from Certified System Administrator (CSA) Documentation:

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:

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,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 usingHigh Security Settingsin ServiceNow, administrators often gaintemporary elevated privileges. To revert to normal security levels, they mustlog out and back into refresh their session.

High Security Settingsprovide elevated security configurations and mayoverride standard role-based access controls.

Logging outclears any temporary security settingsand restores normal administrator privileges.

This is therecommended practiceafter making security changes.

Why is Option B Correct?

Why Are the Other Options Incorrect?A. Select Normal role

Incorrectbecausethere is no "Normal" rolein ServiceNow.

C. Use System Administration > Normal Security module

Incorrectbecausethere is no "Normal Security" modulein ServiceNow.

D. Select Global Update Set

Incorrectbecause Update Sets controlcustomizations and configurations,not security settings.

E. End Impersonation

Incorrectbecause ending impersonation onlyswitches back to the admin accountif you were impersonating a user.

Itdoes not resetsecurity settings from High Security Mode.

ServiceNow CSA Guide - High Security Settings

ServiceNow Best Practices - Managing Security Configurations

References to Official Certified System Administrator (CSA) Documentation:

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:

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

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

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

A. Star(Incorrect)

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

B. Clock(Incorrect)

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

D. Funnel(Incorrect)

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

Navigating the Application

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

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

Spokes in IntegrationHub

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

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

Examples ofprebuilt spokesavailable in ServiceNow include:

Slack Spoke(for Slack API integrations)

Microsoft Teams Spoke(for Teams integration)

Jira Spoke(for integrating with Atlassian Jira)

How Spokes Work

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

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

Comparison with Other Options

A. an action→ Incorrect

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

C. a connection→ Incorrect

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

D. an integration step→ Incorrect

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

ServiceNow Docs - IntegrationHub

ServiceNow Docs - Spokes in Flow

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

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

Batch Installation

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

Automated Delivery

Facilitatesautomated deploymentof related applications and customizations.

Improved Instance Management

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

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

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

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

Incorrect: No such ServiceNow plugin exists.

D. Quick Integration and Multiple Delivery (QIMD) SpokeBatch Install

Incorrect: No such ServiceNow feature exists.

Key Features of A1PD SpokeBatch Install:Why Other Options Are Incorrect?

A1PD Plugin Overview

ServiceNow Plugin Installation

Application Integration Best Practices

Managing Installed Applications

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

InServiceNow, thepersonal_listrole allows users toadd or remove fields from a list viewwithout requiring full administrator privileges.

Modify List Layout (Columns & Fields)

Users canadd, remove, or rearrange columnsin list views.

Save Personal List Preferences

Customizations applyonly to the user, unless they have additional permissions to modify system-wide settings.

Does NOT Allow System-Wide Changes

Unlike theadminrole,personal_listonly affectspersonal viewsof lists, not global configurations.

A. personalize.control(Incorrect)

No such role exists in ServiceNow.

C. ui_page_admin(Incorrect)

This role allows users tomanage UI Pages, but it does not provide list customization permissions.

D. ui_action_admin(Incorrect)

This role is used tomanage UI Actions(buttons, links, and client-side scripts), not list view configurations.

Key Capabilities of thepersonal_listRole:Why Other Options Are Incorrect?

Role-Based List Customization

ServiceNow List Personalization

User Roles and Permissions

ServiceNow User Roles

References from ServiceNow CSA Documentation:

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.

In ServiceNow,UI PoliciesandData Policiesserve different but complementary purposes in controlling data behavior and enforcing business rules.

UI Policies are client-side rules that dynamically change form behavior based on user interactions.

They enable administrators to show/hide fields, make fields read-only, or set fields as mandatory dynamically.

UI Policies only apply when a user is interacting with a form through the ServiceNow UI (Client-side execution).

These policies do not enforce rules if data is added via an Import Set, API, or background script.

Data Policies enforce rulesserver-side, meaning they applyregardless of how data is entered(e.g., form submission, Import Sets, SOAP/REST API calls, or Business Rules).

They ensure data integrity by making fields mandatory, setting read-only properties, or applying other restrictions.

Data Policies can apply conditions globally, unlike UI Policies, which work only in the UI context.

UI Policies:Data Policies:Key Differences:Feature

UI Policy

Data Policy

Scope

Affects only forms (Client-side)

Affects all data entry points (Server-side)

Execution Location

Runs in the browser

Runs on the server

Triggers

User interaction on the form

Any data entry method (Forms, Import Sets, API, etc.)

Enforcement

Works only when using the UI

Applies even when data is added outside the UI

"Data Policies run regardless of how data is entered into ServiceNow"→Correct, because Data Policies enforce rules whether the data is entered via UI, API, Import Sets, or other means.

"UI Policies are used for form interactions"→Correct, because UI Policies apply only to client-side form behavior.

Option A: Incorrect. UI Policies are not set by web services; they are applied when interacting with forms.

Option B: Incorrect. While some Data Policies can be converted into UI Policies, the reverse is not true in all cases.

Option D: Incorrect. UI Policies and Data Policies operate independently, and Data Policies do not depend on UI Policies running first.

Why Option C is Correct:Why Other Options are Incorrect:

To translateService Catalog itemsinto multiple languages in ServiceNow, theTranslation Framework plugin (com.glide.translation_framework)must be activated. This plugin enablesautomatic translation of text fields, including:

Service Catalog items

Knowledge Base articles

Field labels

UI components

Providesmulti-language supportfor catalog items.

Usesmachine translation or manual translation mapping.

Works with theServiceNow Language Packsto provide localized experiences.

Key Features of the Translation Framework Plugin:

TheTranslation Framework plugin (com.glide.translation_framework)is specifically designed to supportmulti-language content translationfor the Service Catalog.

It allows translation of catalog item descriptions, labels, and options without custom scripting.

Why "B. Translation Framework Plugin" is the Correct Answer?

A. Localization Framework Plugin (com.glide.localization_framework) – Incorrect

This plugin helps withlocalization settingsbut is not specifically for catalog item translation.

C. Multiple Language Framework Plugin (com.glide.multiple.language_framework) – Incorrect

No such plugin exists in ServiceNow.

D. Language AI Framework Plugin (com.glide.language.ai_framework) – Incorrect

This is not a valid ServiceNow plugin.

Explanation of Incorrect Options:

ServiceNow Docs: Translation Framework Plugin

ServiceNow CSA Study Guide – Multi-language Support

ServiceNow Product Documentation: Translating Service Catalog Items

References from Certified System Administrator (CSA) Documentation:

InServiceNow,UI Actionsare used to addinteractive elementslikebuttons, links, and context menu itemsto forms and lists. They can triggerscripts, workflows, or other actionswhen clicked.

Form Buttons– Buttons that appear on a form (e.g.,Save, Update, Resolve Incident).

List Buttons– Buttons that appear in a list view and perform actions on multiple records.

Related Links– Links that appear in theRelated Linkssection of a form and provide quick navigation or actions.

Common Types of UI Actions:SinceForm Buttons, List Buttons, and Related Linksare alltypes of UI Actions, they arevalid UI Actions.

Search is a built-in system functionalitythat allows users to find records but doesnot involve UI Actions.

UI Actionsexecute predefined actions, whereasSearch simply retrieves and filters data.

ServiceNow search functions (Global Search, List Search, and Quick Search)arenot part of UI Actions.

B. Form Buttons→Valid UI Action

Appears on forms (e.g.,Submit, Save, Update).

C. List Buttons→Valid UI Action

Used in list views for bulk actions (e.g.,Close All, Approve Selected).

D. Related Links→Valid UI Action

Provides quick links in forms (e.g.,View CI Details, Reopen Ticket).

ServiceNow Docs: UI Actions

ServiceNow CSA Official Training Guide (UI Actions & User Interface Customization)

Why "Search" is NOT a UI Action?Why the Other Options Are UI Actions?References from Certified System Administrator (CSA) Documentation:

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

No-Code/Low-Code Automation

Users candesign, test, and managebusiness processeswithout coding skills.

Actions can be executedsequentially or conditionallybased on logic.

Integration with ServiceNow Applications

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

Trigger-Based Execution

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

Prebuilt Spokes & Actions

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

A. Flow Manager(Incorrect)

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

C. Flow Editor(Incorrect)

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

D. Workflow Editor(Incorrect)

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

E. Workflow Designer(Incorrect)

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

Flow Designer

Building Flows in Flow

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

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

Configuring ACLs in

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

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

Table (B) –Correct

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

This determineswhich recordsthe rule applies to.

Script to Run (E) –Correct

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

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

Timing (H) –Correct

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

Business Rules can run:

Before(before record is saved)

After(after record is saved)

Async(after the transaction completes)

Display(when a form loads)

Condition to Evaluate (I) –Correct

Conditions definewhen the Business Rule should executebased on specific criteria.

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

A. UI Action(Incorrect)

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

C. Fields to update(Incorrect)

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

D. Who can run(Incorrect)

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

F. Application Scope(Incorrect)

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

G. Update Set(Incorrect)

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

ServiceNow Business Rules

Creating Business

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

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:

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

Stored in thesys_user_roletable.

Assignpermissionsto users and groups.

Define access toapplications, modules, and records.

Can beinheritedby users throughgroup membership.

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

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

Description

admin

Full system access, including configuration and security settings.

itil

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

catalog_admin

Manages the Service Catalog.

knowledge_manager

Manages the Knowledge Base.

Roles arestored as recordsin thesys_user_roletable.

Each role grantsspecific permissionsto users.

Users can have multiple roles assigned to them.

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

The correct table name issys_user_role, not "user_sys_role".

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

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

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

Rolesgrant accessto modules, but they arenotthe modules themselves.

ServiceNow Docs: User Roles & Permissions

ServiceNow CSA Study Guide – Role-Based Access Control

ServiceNow Product Documentation: sys_user_role Table

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

Update Setsin ServiceNow are used tocapture configuration changesso they can be moved between instances (e.g., from development to production). However,new records, new groups, and modified Configuration Items (CIs) are not included in Update Setsby default because they are considereddata, not configuration changes.

New Records→ Data records (e.g., Incidents, Users, Groups) are not part of an Update Set.

New Groups→ Groups are data elements (stored in thesys_user_grouptable) and arenot includedin Update Sets.

Modified Configuration Items (CIs)→ CIs belong to theConfiguration Management Database (CMDB), and changes to CIs are considereddata, not configuration changes.

UI Policies, Business Rules, Client Scripts, Workflows, Forms, and Tables

Changes to system configuration (not transactional data)

Breakdown of Each Element:What is Captured in an Update Set?

Why "B. They are not captured in an Update Set" is Correct:New records, groups, and modified CIs are considered data, and Update Sets do not track data by default.

A. They are included in an Update Set→Incorrect because Update Setsdo not track data recordslike CIs, groups, or user records.

C. They are customizations→Customizations refer toconfiguration changes, but records and CIs are considereddata, not customizations.

D. They do not have anything in common→All three (new records, groups, and CIs) aredataelements, meaning they share the characteristic ofnot being included in Update Sets.

Why Other Options Are Incorrect:

ServiceNow Documentation:Update Sets and What They Capture

CSA Exam Guide:Coverswhat is and is not included in Update Sets.

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

B. They are not captured in an Update Set

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

How to Create and Use

Why "Flows" is the Correct Answer:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

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

ServiceNow Learning – Templates and Data Population

ServiceNow Best Practices – Using Templates for Efficiency

References from Certified System Administrator (CSA) Documentation:

InServiceNow Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.

Submission:

A user creates a knowledge article and submits it for approval.

Approval Process:

Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.

Publishing:

Once approved, the article ispublishedand made available in the Knowledge Base.

Updating & Versioning:

If edits are needed, the article enters adraft or reviewstate.

Retirement:

When an article is no longer needed, it follows the workflow toretire or archiveit.

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

ServiceNow does not use a separate "Approval Policy" for knowledge articles; approvals are managed within the workflow.

B. Approval Definitions(Incorrect)

There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.

C. Workflow Designer(Incorrect)

TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.

E. State Lifecycle(Incorrect)

While knowledge articleshave a lifecycle (Draft → Review → Published → Retired), this is controlledby workflows, not by an independent "State Lifecycle" feature.

Knowledge Workflows

ServiceNow Knowledge Management

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

AnUpdate Setin ServiceNow is a mechanism used tocapture configuration changes(such as UI policies, business rules, client scripts, and more) from one instance and move them to another. This ensures that customizations and modifications can be transferred across different ServiceNow instances efficiently.

The process ofretrieving an Update Setfrom another instance follows these key steps:

Verify Update Set is Complete

Before moving an Update Set, it must be marked asCompleteto ensure that all related changes are included.

Navigate toSystem Update Sets > Local Update Setsand confirm that the status is set toComplete.

If the status isIn Progress, the Update Set cannot be retrieved.

Retrieve Update Set

In thetarget instance, navigate toSystem Update Sets > Retrieved Update Sets.

Click"Retrieve Update Set"and provide the remote instance’s URL where the update set exists.

The system will fetch the Update Set from the source instance.

Preview Update Set

Before applying changes, ServiceNow provides apreview optionto check for potential errors or collisions with existing customizations.

Click"Preview Update Set"to initiate validation.

The preview will highlight any skipped records, collisions, or missing dependencies.

Commit Update Set

If the preview is successful (i.e., no critical errors), click"Commit Update Set"to apply the changes to the instance.

Once committed, the changes in the Update Set will be merged into the system's configuration.

"Commit" is the correct final step– after previewing, the Update Set must becommittedto take effect.

"Apply" is incorrect– ServiceNow does not use "Apply" in the Update Set process; instead, it uses "Commit."

"Test Connection" is not part of the Update Set retrieval process– it is relevant forMID Server connectivitybut not for Update Sets.

Why the Correct Answer is "D. Verify Update Set is Complete, Retrieve, Preview, Commit"Thus, the correct sequence is:

✔Verify Update Set is Complete → Retrieve → Preview → Commit

ServiceNow CSA Official Documentation– Update Set Management

ServiceNow Docs - Update Sets(Search for "Update Set Lifecycle")

ServiceNow Community Best Practices on Update Sets

ServiceNow Community(Search for "Best Practices for Update Sets")

ServiceNow Learning Portal - Admin Fundamentals

Available via ServiceNow Now Learning Platform(Look under "Instance Configuration" and "Update Sets")

References from Certified System Administrator (CSA) Documentation:

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:

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

Click on theUser Menu (top right corner).

Select"End Impersonation".

You will immediately return to your original user session.

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

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

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

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,UI Actionsare used toadd buttons, links, and context menu itemson forms and lists to enhance user interaction.

UI Actions provide interactive elementssuch asbuttons, links, and context menu optionson forms and lists.

UI Actions allow execution ofserver-side and client-side scripts, includingGlideAjax and GlideRecordcalls.

They can be configured to execute underspecific conditions, such asuser roles, field values, or record states.

Examples of UI Actions include:

Submit, Update, and Deletebuttons on forms.

Custom action buttonssuch as "Escalate Incident" or "Resolve Task".

List context menu itemssuch as "Approve" or "Reject" for workflow items.

A. UI Policies:Used fordynamically showing, hiding, or making fields mandatory, butnot for adding buttons or links.

B. UI Settings:No such module in ServiceNow.

D. UI Config:Not a valid option; UI Actions, not "UI Config," control buttons and menus.

UI Actions Overview:ServiceNow Docs

Configuring UI Actions for Forms and Lists

Why is the Correct Answer "UI Actions"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingUI Actions, developers canenhance the user experienceby providing interactivebuttons and menu optionsin ServiceNow.

In ServiceNow,Tagsare used tocategorize, flag, and quickly locate recordswithin the system. Tags help users organize records for easy retrieval and filtering.

User-created or system-defined tagsallow for custom categorization of records.

Tags can beapplied to any record, such asincidents, changes, knowledge articles, or tasks.

Users canfilter records based on tagsfor quick access.

Tags arepersonal(for individual users) orglobal(shared across users).

Incident Management:

A user can tag"High Priority"incidents for quick reference.

Knowledge Base Articles:

Articles related topassword resetcan be tagged as"Password Issues"for easier searchability.

Service Catalog Requests:

Users can tag frequently used catalog items as"Common Requests".

Key Features of Tags in ServiceNow:Example Use Cases of Tags:

Tags categorize and organize records, making them easy to find.

They act ascustom labelsthat help users filter and retrieve records efficiently.

They arebuilt-in featuresin ServiceNow and can be managed from theTag Management module.

Why "C. Tags" is the Correct Answer?

A. Search – Incorrect

TheSearch functionhelps users find records but does not categorize or flag them.

B. Favorites – Incorrect

Favoritesallow users tobookmark frequently accessed modules and reports, but they do not categorize records.

D. Bookmarks – Incorrect

Bookmarksare not a native ServiceNow feature for categorizing records;Favoritesserve this function instead.

Explanation of Incorrect Options:

ServiceNow Docs: Using Tags to Organize Records

ServiceNow CSA Study Guide – Navigating and Searching in ServiceNow

ServiceNow Product Documentation: Managing and Filtering Tagged Records

References from Certified System Administrator (CSA) Documentation:

TheCommon Services Data Model (CSDM)is a standardized framework within ServiceNow that provides a shared set of service-related definitions across ServiceNow products and the platform. It ensures consistency inservice reporting, CMDB structure, and configuration strategies, enabling organizations to achieve awell-structured, scalable, and maintainable Configuration Management Database (CMDB).

Why is the Answer A. Common Services Data Model (CSDM)?The statements in the question directly align with the objectives of CSDM:

"A standard and shared set of service-related definitions across ServiceNow products and platform that will enable and support true service level reporting."

CSDM provides a structured framework toalign services, applications, and infrastructurein a way that supports consistent reporting and governance.

It enablesaccurate service reportingby defining standardized relationships between services, applications, and technical components in the CMDB.

"A CMDB framework across our products and platform that will enable and support multiple configuration strategies."

CSDM provides astructured CMDB frameworkthat definesbest practices for data organization and relationships within the CMDB.

It supports multiple configuration strategies, such asapplication-centric, service-centric, and infrastructure-centric approaches.

B. Information Technology Service Management (ITSM):

ITSM refers toprocesses for managing IT services, such as Incident, Problem, Change, and Service Request Management.

While ITSM benefits from CSDM, itdoes not define a structured CMDB frameworklike CSDM does.

C. Configuration Management Database (CMDB):

CMDB is a database that stores configuration items (CIs) and their relationships.

CSDMprovides structure and best practicesfor CMDB but is not the same as CMDB itself.

D. Information Technology Infrastructure Library (ITIL):

ITIL is aset of best practicesfor IT service management.

It provides general guidance onservice management and CMDB usage, butit is not a ServiceNow-specific frameworklike CSDM.

ServiceNow Common Services Data Model (CSDM) Overview:ServiceNow Documentation

CSDM and CMDB Best Practices Guide(ServiceNow Community and Knowledge Base)

CMDB and ServiceNow Data Model Best Practices

Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:CSDM is critical forensuring a structured and governed CMDB, enabling service visibility, and supporting ITSM and ITOM processes effectively.

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

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

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

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

Help maintaindata quality and consistencyacross the system.

Making a Field Mandatory:

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

Enforcing a Read-Only Field:

Prevent users from modifying the"Created Date"field.

Standardizing Data on Import:

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

Data Policies ensuredata accuracy and integritybefore it is stored.

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

They help organizationsmaintain standardized and structured data.

A. Data Policies enforce security – Incorrect

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

B. Data Policies standardize data in Update Sets – Incorrect

Update Sets trackconfiguration changes, not data validation.

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

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

ServiceNow Docs: Data Policies Overview

ServiceNow CSA Study Guide – Data Policies vs. UI Policies

ServiceNow Product Documentation: Enforcing Data Consistency with Data Policies

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

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:

InServiceNow's System Import Sets, administrators canimport data from external sources(such as CSV, Excel, or databases) intoany tablewithin the platform usingTransform Maps.

ATransform Mapdefines how data from an Import Set table is mapped to fields in atarget table (destination table).

Administrators can select any tablein the system as the destination, including bothstandard and custom tables.

Thedestination table is not limitedto Task-related tables (Incident, Problem, Change, etc.).

Users can also applycoalesce rulesto determine if records should be updated or inserted during the transformation.

ServiceNowallows administrators to select any tableas the destination when setting up a Transform Map.

This includes standardITSM tables (Incident, Problem, Change, Task, Service Catalog)as well ascustom tablescreated by administrators.

There areno restrictionson which table can be a destination.

A. "The Task table is the only table that can be a destination"→Incorrect

TheTasktable is widely used, but it isnot the only tablethat can receive imported data.

B. "Only Incident, Problem, Change, Task, and Service Catalog tables can be destinations"→Incorrect

These are common ITSM tables, butany table in the systemcan be selected as a destination.

C. "Only the Incident, Problem, and Change tables can be destinations"→Incorrect

This istoo restrictivebecause other tables, including custom ones, can also be used.

Navigate to:System Import Sets > Create Transform Map

Select the Import Set Tableas thesource.

Choose any available tablein ServiceNow as thedestination.

Definefield mappingsbetween the source and target table.

Configurecoalesce rulesto update or insert records.

ServiceNow Docs: Creating and Using Transform

ServiceNow CSA Official Training Guide (Import Sets & Data Management)

Key Points About Transform Maps & Data Import:Why is "D. Any ServiceNow table" the Correct Answer?Why the Other Options Are Incorrect?How to Configure a Transform Map in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms thatany ServiceNow tablecan be adestination tablefor imported data when using Transform Maps inSystem Import Sets.

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.

InServiceNow Incident Management,work notesare used to capturetechnical and internal updatesfor an incident. These notes arestored in the Activity Logwhenever the incident is saved.

TheWork Notesfield is used forinternal communicationamong support teams.

When an incident is updated and saved,all work notesareappended to the Activity Log(a complete history of the incident).

The Activity Log provides achronological recordof all changes, includingwork notes, field updates, and system-generated messages.

Understanding Work Notes and the Activity Log:Why Option A is Correct?"All Work Notes field text is recorded in the Activity Log"– This is correct because every time an incident is saved, the Work Notesare appended to the Activity Log.

Why Other Options Are Incorrect?B. Work Notes field text is overwritten each time work is logged→ Incorrect becauseWork Notes are appended, not overwritten. Previous work notes remain visible in the Activity Log.

C. Impact is calculated by adding Priority and Urgency→ Incorrect becauseImpact, Urgency, and Priorityare independent fields, thoughPriorityis determined based onImpact + Urgencyvia business rules.

D. Additional Comments are cleared and recorded in Work Notes→ Incorrect becauseAdditional Comments(for customer-facing communication) andWork Notes(for internal teams) areseparate fields. Additional Comments are not cleared upon save.

ServiceNow Docs – Incident Management: Work Notes and Activity

ServiceNow Learning – Understanding the Incident Activity Stream

ServiceNow Best Practices – Internal vs. External Communication in Incidents

References from Certified System Administrator (CSA) Documentation:

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.

InServiceNow Flow Designer,local flow variablesare accessed in theData Panel as data pills.

Local Flow Variables:

These aretemporary variablesthat storedataduring the execution of a flow.

Can be used topass valuesbetween actions within the same flow.

Accessing Local Variables in the Data Panel:

TheData Panelcontainsdata pills, which representstored values.

Flow variables appear asblue data pillsthat can bedragged and droppedinto different actions.

Example: A variable storingUser IDcan be dragged into an"Assign Task"action to assign a task dynamically.

Why Data Pills?

Data pills act astokensrepresenting values that update dynamically during flow execution.

Ensuresreusabilityandautomationacross multiple actions.

How Flow Variables Work in Flow Designer:Why Option D (As data pills) is Correct?Flow variables appear as "data pills" in the Data Panel, which can be dragged into flow actions.

Why Other Options Are Incorrect?A. As newly generated icons→ Incorrect

No "icons" are generated; flow variables are represented asdata pills.

B. As scratchpad variables→ Incorrect

Scratchpad variablesexist inBusiness Rules, butnot in Flow Designer.

C. As new tabs→ Incorrect

Flow variables donot appear as tabs; they appear in theData Panel as data pills.

ServiceNow Docs – Flow Designer: Using Data

ServiceNow Learning – Working with Flow Variables and Data Panel

ServiceNow Developer Portal – Flow Designer Best Practices

References from Certified System Administrator (CSA) Documentation:

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

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

It allowsdevelopers and administratorsto definenew custom events.

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

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

Triggering a Notification

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

Initiating an Automated Workflow

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

Logging Custom Events for Reporting

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

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

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

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

It is used forevent-driven automationin ServiceNow.

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

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

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

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

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

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

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

Explanation of Incorrect Options:

ServiceNow Docs: Understanding the Event Registry

ServiceNow CSA Study Guide – Event Management

ServiceNow Product Documentation: Creating and Managing Events

References from Certified System Administrator (CSA) Documentation:

Access Control Rules (ACLs) are a fundamental security feature in ServiceNow that protect applications by identifying and restricting access to files and data. ACLs define which users or roles have permissions to create, read, write, or delete data within an application.

Understanding Access Control Rules (ACLs)ACLs in ServiceNow operate based on three key elements:

Object Type– Defines what is being secured (table-level or field-level access).

Operation– Specifies the type of access (Create, Read, Write, Delete, Execute, etc.).

Condition & Script– Determines when access is granted (role-based permissions or specific conditions).

Data Security:Ensures that only authorized users can access specific data.

Granular Access:Controls permissions at the table and field level.

Regulatory Compliance:Helps organizations maintain security standards and data protection laws.

ServiceNow applies ACLs from the most specific to the most general (Field-level → Table-level → Global-level).

If no ACL explicitly allows access, the system denies it by default (Deny by Default Policy).

ACLs can be role-based, condition-based, or script-based for advanced security configurations.

A. Application Configuration– This refers to application settings but does not control access to data.

B. Verbose Log– Logging helps in debugging but does not secure applications or restrict access.

D. Application Scope– Defines application boundaries but does not control data access permissions.

ServiceNow CSA Documentation: Access Control Rules (ACLs)

ServiceNow Security Best Practices: Security and Access Control

Why Access Control Rules are Important?How ACLs Work in ServiceNow?Incorrect Answer Choices Explanation: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:

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.

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:

In ServiceNow, users can log into theService Portalusingcertificate-based authentication methods. The two commonly supported methods are:

ACACis a smart card issued by theU.S. Department of Defense (DoD).

It is used by military personnel, contractors, and government employees for secure authentication.

ServiceNow supportsCAC authenticationby integrating with external identity providers.

APIV cardis used byU.S. federal agenciesfor authentication.

It followsFederal Information Processing Standard (FIPS) 201for identity verification.

ServiceNow allows users to log in using PIV authentication, ensuringsecure accessto government and enterprise systems.

1. Common Access Card (CAC) – (Correct Answer)2. Personal Identity Verification (PIV) – (Correct Answer)

Both CAC and PIV are widely recognized certificate-based authentication methodsused in ServiceNow for secure user authentication.

They provide multi-factor authentication (MFA)and meet federal security standards.

Why "C. CAC" and "E. PIV" are the Correct Answers?

A. Extended Validation Access (EVA) – Incorrect

No such authentication method exists in ServiceNow.Extended Validation (EV) certificatesare used for website security, not user authentication.

B. Organization Verification Card (OVC) – Incorrect

Not a recognized ServiceNow authentication method.

D. Domain Authentication Card (DAC) – Incorrect

No such authentication method exists in ServiceNow.

Explanation of Incorrect Options:

ServiceNow Docs: Common Access Card (CAC) Authentication

ServiceNow Docs: Personal Identity Verification (PIV) Authentication

ServiceNow CSA Study Guide – Authentication Methods in ServiceNow

References from Certified System Administrator (CSA) Documentation:

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

Now Mobile

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