Free and Premium ServiceNow CSA Dumps Questions Answers

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

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

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

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

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

Function fields aredesigned specifically for calculations and data transformationsin reports.

They allowadvanced data processing without requiring scripting.

A. Sourcing Fields→Incorrect

" Sourcing Fields " isnot a valid termin ServiceNow reporting.

C. Computational Fields→Incorrect

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

D. Calculation Fields→Incorrect

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

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

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

ServiceNow Docs: Function Fields in

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

Afilter conditionin ServiceNow consists of three essential components that define how data is filtered in lists, reports, and queries. These components determine which records meet specific criteria.

Column (D)– Represents thefieldin the table that is being filtered (e.g., " Priority " in theincidenttable).

Operator (A)– Defines the comparison method, such asis, contains, starts with, greater than, etc.

Value (C)– Specifies thecriteriaused for filtering (e.g., " High " for Priority).

Components of a Filter Condition:Example of a Filter Condition in an Incident Table:PriorityisHigh

Column:Priority

Operator:is

Value:High

B. Match Criteria→ Not a defined component; filtering is based on column, operator, and value.

E. Field→ While " Field " is a general term,ServiceNow officially uses " Column " in filter conditions.

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

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

Plugins can be installed or activatedfrom theSystem Definition > Pluginsmodule.

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

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

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

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

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

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

ServiceNow Plugins Documentation:ServiceNow Docs

Managing and Activating Plugins in ServiceNow(Admin Guide)

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

TheServiceNow Virtual Agentis an AI-powered chatbot that assists userswithin a messaging interface(such as Microsoft Teams, Slack, or Service Portal). It helpsautomate resolutions and guide usersthrough common IT and HR issues.

Incident Auto-ResolutionallowsVirtual Agenttoautomatically detect, intercept, and resolve incidentsbefore they reach a human agent.

It appliesmachine learning (ML) and predefined rulesto determine whether a ticketcan be resolved through automation.

If an issuematches a known solution, the Virtual Agentprovides the resolution stepsto the user.

If self-resolution fails, the ticket isescalated to an agent.

It is anofficial feature in ServiceNow Virtual Agent.

It allows the chatbot tointercept incidentsand attempt resolution before escalation.

B. Ticket Resolver→Incorrect

" Ticket Resolver " isnot an official ServiceNow feature.

C. Virtual Agent Helper→Incorrect

No feature called " Virtual Agent Helper " exists in ServiceNow.

D. Web Intelligence→Incorrect

Web Intelligenceisnot related to ServiceNow Virtual Agent.

What is Incident Auto-Resolution?Why is " A. Incident Auto-Resolution " the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Virtual Agent & Incident

References from Certified System Administrator (CSA) Documentation:This confirms that " Incident Auto-Resolution " is the correct answer, as it allowsVirtual Agent to intercept and resolve submitted incidents automatically.

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

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

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

Example:

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

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

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

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

A. snc_abc – Incorrect

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

B. abc – Incorrect

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

D. sys_abc – Incorrect

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

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

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

Homepages (A) –Correct

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

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

Data (B) –Correct

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

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

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

Published Workflows (C) –Correct

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

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

Report Definitions (H) –Correct

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

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

D. Business Rules(Captured in Update Sets)

E. Schedules(Captured in Update Sets)

F. Database changes(Captured in Update Sets)

G. Related Lists(Captured in Update Sets)

I. Scheduled Jobs(Captured in Update Sets)

J. Client Scripts(Captured in Update Sets)

K. Views(Captured in Update Sets)

ServiceNow Update Sets

ServiceNow Update Set Best

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

InServiceNow, administrators canreuse the same notification contentacross multiple channels (such asemail, SMS, and push notifications) by usingCommon Notification Content.

Consistency Across Channels

Ensures that the same message format is used acrossemail, SMS, and push notifications.

Easier Maintenance

Instead ofcreating separate contentfor each channel, administrators can manage all notification content from one place.

Dynamic Content

Supports variables and dynamic placeholders to customize messages based on recipient data.

A. Configure Default notification content

Incorrect: There is no " default notification content " feature in ServiceNow.

B. Enable Actionable notification content

Incorrect: Actionable notifications allow users totake actions directly from the notification, but they do not manage common content.

D. Set up Related notification content

Incorrect: No such feature as " Related notification content " exists in ServiceNow.

Key Features of Common Notification Content:Why Other Options Are Incorrect?

Common Notification Content Overview

ServiceNow Notification Management

Setting Up Common Notification Content

Creating Reusable Notification Content

References from ServiceNow CSA Documentation:

InServiceNow 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:

InServiceNow, theSubmit buttonappears whencreating a new record, but it is not visible when editing an existing record. Instead, when editing an existing record, theUpdate buttonis used.

Creating a New Record:

When a user opens a form to create anew record, theSubmit button appears.

ClickingSubmitsaves the record and closes the form.

Example: When creating anew Incident, Change Request, or User record, the Submit button is visible.

Editing an Existing Record:

When a useropens an existing record, theUpdate button replaces the Submit button.

ClickingUpdatesaves the changes but does not create a new record.

Example: Editing anexisting Incident recorddoes not show a Submit button, only Update.

Changing a Reference Field in an Existing Record:

Updating areference field(like Assigned To or Caller) in an existing record does not trigger aSubmitbutton—onlyUpdateis available.

Saving an Old Record:

TheSavebutton may be available when a user makes changes but does not want to exit the form.

When Does the Submit Button Appear?When Does the Submit Button NOT Appear?Why Option B (When Creating a New Record) is Correct?The Submit button appears only when a new record is being created.

Why Other Options Are Incorrect?A. When saving an old record→ Incorrect

TheSave buttonappears when modifying an existing record but does not replaceSubmit.

C. When changing the reference field in an existing record→ Incorrect

Editing a reference field doesnotmake the Submit button appear. OnlyUpdateis available.

D. When updating an existing record→ Incorrect

TheUpdate buttonappears instead ofSubmitwhen modifying an existing record.

ServiceNow Docs – Forms and Form

ServiceNow Learning – Creating and Editing Records

ServiceNow Developer Portal – Understanding Form Actions (Submit vs. Update)

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Number Maintenanceis the application used to manage and modify numbering schemes for different tables, including theIncidenttable. Since the default prefix forIncident numbersis " INC " , an administrator can modify it to a company-specific prefix (e.g., " IN " ) by following these steps:

Navigate to the Number Maintenance Application:

Go toAll → System Definition → Number Maintenance

Search for theIncident table (task.number record for Incident).

Modify the Prefix:

Open the existingIncident numbering record.

Change thePrefixfrom " INC " to " IN " .

Ensure theNext Numberfield is correctly set (e.g., " IN0001001 " ).

Save the Changes:

ClickUpdateto apply the new prefix.

All newly created incidents will now follow the new format (IN0001001).

Existing incidents are NOT affected—only newly created records will reflect the new prefix.

Steps to Change the Incident Number Prefix:Why Option A (Number Maintenance) is Correct?The Number Maintenance application is the correct place to modify prefixes for tables like Incident.

Why Other Options Are Incorrect?B. Create a Business Rule that modifies the prefix before the Insert operation→ Incorrect

Business Rulesdo not control number generation.

Number generation is managed byNumber Maintenanceat the system level.

C. The prefix of an incident cannot be changed because it is a built-in feature→ Incorrect

The prefixCAN be changedusing theNumber Maintenanceapplication.

Only existing records retain their original prefix; new records follow the updated format.

D. Submit a Change Request to ServiceNow Technical Support→ Incorrect

This isnot necessary, asadministratorscan make this change directly throughNumber Maintenance.

ServiceNow Docs – Number Maintenance

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow Developer Portal – Number Prefix Best Practices

References from Certified System Administrator (CSA) Documentation:

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

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

Displays a user-friendly label from the referenced record.

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

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

TheCallerfield allows users to select a user from theUser Table.

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

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

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

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

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

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:

Access Control rules in ServiceNow define who cancreate, read, write, or deleterecords in a table or specific fields. These rules are applied at thetable or field leveland follow a specificnaming convention:

TableName.FieldName

Naming Convention for Access Control Rules:

If an Access Control rule applies to a specifictable, its format isTableName(e.g.,incident).

If it applies to a specificfield, it followsTableName.FieldName(e.g.,incident.major_incident).

Major Incident is a field in the Incident table:

Theincidenttable represents the ITSMIncident Management module.

Major Incidentis aspecific fieldwithin theincidenttable.

To apply anAccess Control Ruleto this field, the rule name must beincident.major_incident.

A. Incident.Major_Incident:Incorrect because ServiceNow Access Control rulesdo not use uppercase table or field names—they are alwayslowercase.

B. incident= > major_incident:Incorrect syntax—ServiceNow does not use= > in Access Control names.

C. incident < = > major_incident:Incorrect syntax—ServiceNow does not use < = > in rule naming conventions.

D. incident||major_incident:Incorrect syntax—ServiceNow does not use||(logical OR) in Access Control naming.

ServiceNow Access Control Rules Guide:ServiceNow Docs

How to Create and Manage Access Control Rules in ServiceNow

Why is the Correct Answer " incident.major_incident " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingincident.major_incident, we correctly definefield-level securityfor theMajor Incidentfield in theIncident table.

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

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

SelectImpersonate User.

Search for and select theuser’s name.

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

Navigate to theApplication Navigatorand check for missing modules.

Once done, clickStop Impersonation.

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

Speeds up troubleshootingby allowing admins to replicate user issues.

Helps verify role-based access permissions.

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

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

This is asecurity violationand not an acceptable practice.

B. Initiate a Connect Chat session

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

C. Install the Bomgar plug-in

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

E. Launch a NowChat window

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

Impersonate Users in ServiceNow

User Roles and Permissions

Official CSA Documentation Reference:

InServiceNow, Favorites allow users to quickly access frequently usedmodules, records, lists, or reports. Favorites can be customized, including renaming them, changing their icons, or modifying their colors.

Changing the Label of a FavoriteTorename or edit a Favorite, you must use thePencil icon (✏️), which indicatesedit mode.

Navigate to theApplication Navigatoron the left-hand side.

Locate theFavoritessection.

Hover over the favorite item you want to rename.

Click on thePencil icon(✏️) to open the edit menu.

Update thelabel(name) and other properties like color or icon.

ClickSaveto apply changes.

A. Clock(Incorrect)

TheClock icontypically representsrecently accessed items, not Favorites.

B. Hamburger(Incorrect)

TheHamburger menu (☰)represents navigation menus but is not used to edit Favorites.

D. Three dots(Incorrect)

TheThree dots (⋮)often indicate a menu with additional options but do not specifically edit Favorites.

E. Triangle(Incorrect)

NoTriangle iconis used for renaming Favorites.

F. Star(Incorrect)

TheStar icon (⭐)is used toadd or removeFavorites, but not to rename them.

ServiceNow Favorites

Steps to Change the Label of a Favorite:Explanation of Incorrect Options:Official 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:

In ServiceNow, users can quickly generate a report from a list view without needing to navigate to the Reports module. The two main ways to do this are:

Steps:

Open any list view (e.g., Incident, Change, or any table-based list).

Click thethree-line (hamburger) context menuon the top-left of the list.

SelectCreate Reportto generate a basic report based on the current list view.

Modify report settings (e.g., visualization type, filters, groupings).

Save the report for future reference.

Steps:

Apply the necessary filters to refine the list view.

Right-click on acolumn header(e.g., Priority, State, Category).

SelectCreate Reportfrom the context menu.

Configure the report visualization and save it if needed.

1. Using the Context Menu (Option C)2. Right-click on a Column Header (Option E)

Incorrect Answer Choices Explanation:A. Click on filter breadcrumb, drag and drop on the Report > Create New module

There is no such drag-and-drop functionality for report creation in ServiceNow.

B. Click Funnel, define filter conditions, click Create Report

TheFunnel iconis used to filter list views but does not directly generate reports.

D. Apply filter, right-click on column header, select Bar Chart

There is no direct " Bar Chart " option available when right-clicking on a column header.

Creating Reports from List Views

ServiceNow KB Article: KB0014148

Official CSA Documentation Reference:

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:

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

Submission:

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

Approval Process:

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

Publishing:

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

Updating & Versioning:

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

Retirement:

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

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

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

B. Approval Definitions(Incorrect)

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

C. Workflow Designer(Incorrect)

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

E. State Lifecycle(Incorrect)

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

Knowledge Workflows

ServiceNow Knowledge Management

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

Thekey differencebetweenReportingandPerformance Analytics (PA)is how they handle data over time.

Showsreal-time datafrom tables.

Runs queries on dataat the momentthe report is generated.

Cannot analyze historical trendsunless data is manually stored.

Used forstatic reports, lists, charts, or dashboards.

Capturessnapshotsof data at scheduled intervals (e.g., daily, weekly).

Tracks trends and KPIs (Key Performance Indicators)over time.

Helps organizationsforecast and analyze historical patterns.

Used forbusiness intelligence and proactive decision-making.

ReportingPerformance Analytics (PA)

Incorrect Answer Choices Explanation:B. Performance Analytics can show trends; Reports cannot.

Reporting can show trends usingaggregated data(e.g., grouped by date), butPA is specifically designedfor tracking trends over time.

C. Reports can be run on a scheduled basis; Performance Analytics cannot.

BothReports and PA can be scheduledto run at regular intervals.

D. Performance Analytics data can be published to Dashboards; Reports cannot.

Reportscanbe published todashboards, just like Performance Analytics.

E. Performance Analytics shows KPIs; Reporting does not.

Reports candisplay KPIsusing calculated metrics and aggregations, butPA is optimizedfor KPI tracking over time.

Performance Analytics vs. Reporting

ServiceNow Reporting Overview

Official CSA Documentation Reference:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ServiceNow Service Catalog Management - Record Producers

ServiceNow User Criteria and Access Control Best Practices

ServiceNow CSA Guide - Managing Roles and Access Restrictions

References to Official Certified System Administrator (CSA) Documentation:

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

Data Loading from External Sources:

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

Allows data fromexternal systemsto be brought into ServiceNow.

Staging Area for Data Processing:

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

Data can then betransformedbefore being committed to the target table.

Data Mapping and Transformation:

UsesTransform Mapsto map fields from theImport Set Tableto theTarget Table.

Supportsautomatic field mappingandscripted transformations.

Data Cleansing and Validation:

Duplicate records can bedetected and removed.

Invalid or missing data can becorrected before insertion.

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

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

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

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

Verify the datain the target table.

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

TheSystem Import Setsmodule loads this data into astaging table.

ATransform Mapmoves the data into theUser [sys_user]table.

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

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

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

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

B. Configuration→ Incorrect

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

D. System Update Sets→ Incorrect

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

ServiceNow Docs – Importing Data with System Import

ServiceNow Learning – Data Import & Transformation Best Practices

ServiceNow Developer Portal – Using Import Sets Efficiently

References from Certified System Administrator (CSA) Documentation:

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:

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:

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

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

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

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

E. System Security > Access Control (ACL)

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

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

This is one of themost commonly usedsecurity modules by admins.

G. System Security > High Security Settings

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

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

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

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

C. System Security > Security

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

D. Self-Service > My Access

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

It isnota tool thatSystem Administratorsuse to manage security settings.

F. Password Management > Security Questions

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

General Security Settings in ServiceNow

ServiceNow Access Control (ACL) Best Practices

ServiceNow System Security and Role Management

References to Official Certified System Administrator (CSA) Documentation:

Update Setsare the standard way to capturecustomizationsand move them from one ServiceNow instance to another. These customizations include:

Business Rules

UI Policies

Script Includes

Fields and Tables

Workflows

Update Setstrack changes in an instance and allow them to beexportedandimportedinto other environments (e.g., fromDevelopmenttoTestand then toProduction).

They ensure thatconfiguration changesare preserved and applied consistently across instances.

Why is Option A Correct?Why Are the Other Options Incorrect?B. Code Sets

There is no concept ofCode Setsin ServiceNow.

C. Update Packs

Update Packsdo not exist in ServiceNow. The correct term isUpdate Sets.

D. Configuration Logs

Configuration Logsrecord system activity butdo not package customizationsfor migration.

E. Remote Sets

Remote Update Setsexist, but they are just a variation ofUpdate Setsused when moving changes betweenremote instances.

The broader term " Update Sets " is more accurate.

F. Local Sets

No such termexists in ServiceNow.

G. Code Packs

There is no " Code Pack " in ServiceNow.

ServiceNow CSA Guide - Update Sets and Customization Migration

ServiceNow Developer Documentation - Using Update Sets

ServiceNow Best Practices - Moving Configuration Between Instances

References to Official Certified System Administrator (CSA) Documentation:

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

Why These Options Are Correct?C. My reports

Displaysreports created by the logged-in user.

These reports areprivateunless explicitly shared.

E. Dashboards

Dashboardsconsolidate multiple reports andmake them visible to specific audiences.

Users canshare dashboardswith groups or individuals.

F. Global

Global reportsare available toall users with reporting access.

These reports arenot restrictedto a specific user or group.

I. All

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

Personal reports

Shared reports

Global reports

Reports from dashboards

Why the Other Options Are Incorrect?A. Group

There isno " Group " sectionin the Reports page.

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

B. Department

Departments do not determine report visibilityin the Reports page.

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

D. Team

Teams are not a standard report visibility categoryin ServiceNow.

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

G. Admin

There isno " Admin " sectionin the Reports page.

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

H. Analytics

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

It is not a standardreport visibility section.

J. Company

There isno " Company " sectionin the Reports page.

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

ServiceNow Reports - Managing Visibility and Access

ServiceNow Reporting Guide - Sections of the Reports Page

ServiceNow Dashboards and Report Sharing Best Practices

References to Official Certified System Administrator (CSA) Documentation:

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:

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:

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

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

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

Reduce Unplanned Changes→ Avoid reactive decisions by monitoringhistorical data.

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

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

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

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

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

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

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

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

Why Other Options Are Incorrect:

ServiceNow Documentation:Performance Analytics Overview

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

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

A. Long-term signals

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

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

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

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

Filter Condition:PriorityisHigh

Field:Priority

Operator:is

Value:High

Another Example:Stateis notResolved

Field:State

Operator:is not

Value:Resolved

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

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

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

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

ServiceNow Docs – Creating and Applying

ServiceNow Learning – Query Builder and Conditions

ServiceNow Best Practices – Using Filters in Lists and Reports

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

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:

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:

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:

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:

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

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

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

Example:

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

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

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

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

A. snc_abc – Incorrect

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

B. abc – Incorrect

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

D. sys_abc – Incorrect

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

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

InServiceNow, theTask [task]table is acore tablethat provides aset of standard fieldsused by multiple tables that extend it, including:

Incident [incident]

Problem [problem]

Change Request [change_request]

Service Request [sc_request]

These tablesinherit fieldsfrom theTasktable, ensuring consistency inassignments, state management, and workflows.

Standard Fields:

Assigned To

Assignment Group

Priority

State

Created By / Updated By

Short Description / Description

Extensibility:

TheIncident, Problem, and Change tablesallextendthe Task table, inheriting its fields.

Developers canadd additional fieldswhile keeping core task properties intact.

TheTask table is the primary tablefor work-related records in ServiceNow.

Itstandardizes fieldsacross multiple ITSM modules.

B. Assignment [assignment]→Incorrect

There isno standard " Assignment " tablein ServiceNow.

Assignments are managed through theTask tablevia theAssigned To and Assignment Group fields.

C. Service [service]→Incorrect

There isno generic " Service " tablethat acts as a core table for ITSM processes.

Service-related items are stored in different tables, such ascmdb_ci_service(for service records).

D. Workflow [workflow]→Incorrect

TheWorkflow tableis used for managing automated workflows anddoes not store task-related records.

Key Features of the Task Table:Why is " A. Task [task] " the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Task Table

References from Certified System Administrator (CSA) Documentation:This confirms thatthe Task table is the core table that extends to Incident, Problem, and other related tables.

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:

InServiceNow Flow Designer, users can accessdetailed informationabout actions added to a flow via theHelp Panel. The Help Panel providescontextual guidanceand documentation about the available actions, conditions, and steps within the flow.

Displays Information About Actions:

When an action is selected in Flow Designer, theHelp Panelprovidesdescriptions and usage details.

Helps users understandwhat the action doesand how to configure it.

Accessing the Help Panel:

Inside Flow Designer, users can click theHelp icon ( ? )or expand the Help Panel from the side.

This providesinline documentationfor added actions.

Guidance for New Users:

The panel providesServiceNow documentation links and tipsto help users build flows effectively.

Key Features of the Help Panel:Why Option C (Help Panel) is Correct?TheHelp Panelprovides built-in documentation and details about actions added to the flow.

Why Other Options Are Incorrect?A. Virtual Agent Help→ Incorrect

Virtual Agent Help is related tochatbot and conversational assistance, not Flow Designer.

B. Local Action Help→ Incorrect

No such feature exists in ServiceNow; action details are found in theHelp Panel.

D. Flow Assistant→ Incorrect

Flow Assistanthelps withbuilding expressions and selecting data pillsbut does not provide action documentation.

ServiceNow Docs – Flow Designer Help

ServiceNow Learning – Flow Designer and Automation Best Practices

ServiceNow Developer Portal – Flow Designer Action Configuration

References from Certified System Administrator (CSA) Documentation:

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.

TheApplication Navigatorin ServiceNow allows users to quickly filter and locateapplications, modules, and menusby typing keywords in thefilter field.

When you type " service " into the filter field,only modules containing the word " service " in theirname or pathwill be displayed.

Analysis of Each Option:Option

Contains " service " ?

Appears in Navigator?

A. Configuration > Business Services

" Business Services " contains " service "

Appears

B. Self-Service > Knowledge

" Self-Service " contains " service "

Appears

C. Service Portal > Widgets

" Service Portal " contains " service "

Appears

D. Incident > Assigned to me

Does NOT contain " service "

Does NOT appear

Since " Incident > Assigned to me " doesnotcontain the word " service " , itwould NOT appearin theApplication Navigatorwhen filtering by " service " .

Configuration > Business Services

The " Business Services " module underConfigurationincludes the word " service " .

Self-Service > Knowledge

The " Self-Service " application contains the word " service " , so this module appears.

Service Portal > Widgets

The " Service Portal " module contains the word " service " , making it visible.

Incident > Assigned to me

Thisdoes NOT contain " service " in its path, so it willnotappear.

Why the Other Options Appear in the Application Navigator?

ServiceNow Docs: Using the Application

References from Certified System Administrator (CSA) Documentation:This confirms that " Incident > Assigned to me " would NOT appearin the Application Navigator when filtering by " service " .

In ServiceNow,Business Rulesare server-side scripts that executeat specific timesrelative to database operations. The " When " settingdetermineswhenthe Business Rule runs in relation to a record action (Insert, Update, Delete, Query).

Why is Option A Correct?Before

Executesbeforea record is saved to the database.

Used tovalidate data, modify values, or prevent an action(e.g., stopping an invalid update).

After

Executesaftera record is inserted, updated, or deleted.

Commonly used fortriggering notificationsor creating related records.

Async (Asynchronous)

Runsaftera database operation but executes inthe background.

Ideal forlong-running or performance-heavy tasks(e.g., integrating with external systems).

Display

Executesbefore a form loads, allowing modifications to fieldsbefore they are displayedto the user.

Typically used forpre-filling form fieldsbased on user roles or conditions.

Why Are the Other Options Incorrect?B. Prior to, Synchronous, on Update

" Prior to " is not a valid Business Rule execution timing.

" Synchronous " is a general term but isnot a specific execution timing optionin Business Rules.

" on Update " is a database operation,not an execution timing.

C. Insert, Update, Delete, Query

These aredatabase operationsthat trigger Business Rules,not execution timings.

Execution timing determineswhen(before, after, etc.), while these determinewhat triggers it.

D. Before, Synchronous, Scheduled Job, View

" Synchronous " is not a Business Rule timing option.

" Scheduled Job " refers toScheduled Jobs(not Business Rules).

" View " is a UI-related concept,not a Business Rule execution timing.

ServiceNow Business Rules - How They Work

ServiceNow Best Practices - Business Rule Execution Timing

ServiceNow Developer Documentation - Before, After, Async, and Display Business Rules

References to Official Certified System Administrator (CSA) Documentation:

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

Groups are stored in thesys_user_grouptable

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

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

Groups are used for role assignments

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

Groups can be used for approvals and task assignments

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

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

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

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

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

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

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

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

Groups in ServiceNow

Managing User Groups

User and Group Management

ServiceNow User and Group Administration

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

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:

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

Load Data (First Step)

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

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

Create Transform Map & Apply Transform

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

TheTransform Datastep converts and inserts data into the final table.

Coalesce to Avoid Duplicates

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

A. Coalesce Data(Incorrect)

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

B. Transform Data(Incorrect)

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

C. Import Data(Incorrect)

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

Importing Data Using Import

Load Data Module in

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

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:

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.

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

InServiceNow Service Catalog, the best practice for handling accessory selections is to usevariables or variable setswithin asingle catalog itemrather than creating multiple separate catalog items.

A. Create a Catalog Item for the tablet and add a checkbox variable for each accessory option.Correct– Addingcheckbox variablesfor accessories allows users to select multiple options within a single request.

Example variables:

[✓] Carrying Case

[✓] Screen Cleaner

[✓] Tablet Stand

[✓] Screen Protector

This makes orderingsimpler and more user-friendly.

B. Create a Catalog Item for the tablet, and add a variable set to the form for accessory options.Correct– AVariable Setis a reusable collection of variables that can be applied to multiple catalog items.

This approach is beneficial if multipledevices (e.g., laptop, phone, tablet)sharethe same accessory options.

The Variable Set can includecheckboxesfor selecting accessories.

E. In Shopping Cart configuration, select the option to show the " Add Accessories " button.Correct– Enabling the " Add Accessories " button in theShopping Cartallows users to add related products as separate items in their order.

This works well when accessories areseparate items in the catalogbut need to be linked for convenience.

Best Practices for Configuring the Tablet and Accessories:

C. Create one Catalog Item for each: tablet, carrying case, screen cleaner, tablet stand, and screen protector.Incorrect – Thisforces users to order accessories separately, making the processless efficient.

Best practice is to keep accessorieswithin the same formunless they are standalone items.

D. Create a Record Producer, and on the form, add a checkbox variable for each accessory option.Incorrect –Record Producerscreate records intables (e.g., Incident, Request, HR Case)but arenot used for Service Catalog ordering.

Thecorrect approachis to use aCatalog Item with variablesinstead.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Creating and Managing Catalog Items???? Creating Service Catalog Items

ServiceNow Docs – Variable Sets???? Service Catalog Variable Sets

ServiceNow Docs – Shopping Cart Configuration???? Shopping Cart Configuration

Official ServiceNow Documentation References:

Conclusion:The correct answers are:

A. Create a Catalog item for the tablet and add checkbox variables for accessories.

B. Use a Variable Set for the accessory options.

E. Enable the " Add Accessories " button in Shopping Cart configuration.

This approachenhances user experience, ensures flexibility, and aligns with ServiceNow Service Catalog best practices.

TheDependency Viewgraphically representsConfiguration Items (CIs)and their relationships in ServiceNow’sConfiguration Management Database (CMDB). It provides an interactive visualization of dependencies and relationships between infrastructure components, helping administrators understand system architecture.

Displays CI relationships in an interactive graphical format.

Helps identifyupstream and downstream dependencies(e.g., how a failed server affects dependent applications).

Can be accessed via theConfiguration Item (CI) formunder theRelated Linkssection.

Used inImpact Analysisfor Change Management and Incident Management.

A. Schema Map– Used to visualizetable relationships, not CI dependencies.

C. Dependency Map– Not a ServiceNow term; the correct term isDependency View.

D. Database View– Used to createvirtual tablescombining data from multiple tables but does not display CI dependencies graphically.

Process Automation Designer (PAD)is a feature in ServiceNow that allows business process owners to createunified and digitized cross-enterprise processesusing atask board interface.

Organizes multiple flows into a single process

Uses a visual task board-style interfaceto manage process stages

Integrates with Flow Designerto create, manage, and execute automation tasks

Allows role-based task assignment and collaboration

Key Features of Process Automation Designer:Use Case Example:Imagine a company has aNew Employee Onboardingprocess that involves:

IT setting up hardware

HR completing paperwork

Security providing building access

Instead of managing this manually across multiple flows,Process Automation Designerbrings all these steps intoone unified process, making it easy to track and automate.

A. Flow Designer →Incorrect

Flow Designeris used to createindividual automated workflows, but it does not provide aunified digitized task board.

C. Process Workflow Designer →Incorrect

No feature called " Process Workflow Designer " exists in ServiceNow.

D. Workflow Editor →Incorrect

Workflow Editor(Legacy tool) is used to creategraphical workflows, but it does not supportcross-enterprise digitized task boards.

Why Other Options Are Incorrect?

Process Automation Designer Overview

Using Process Automation Designer

Official ServiceNow Documentation Reference:

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:

In ServiceNow,rolesdetermine what users can see and do within the platform.

The IT useronly sees the Self-Service homepageinstead of the full ServiceNow interface, including task records.

This suggests that their accountdoes not have the necessary role(s) to access task records.

Issue:Why the Correct Answers?D. Their user account does not have the itil role

Theitil roleis required to work with ITSM task records (e.g., Incidents, Problems, Changes).

Without this role, usersonly have access to the Self-Service portal.

E. Their user account does not belong to any groups, which contain the itil role

Even if a user is not directly assigned theitil role, they can inherit itthrough a group membership.

If theiruser account is not part of an ITSM-related groupthat has theitil role, they will not be able to access tasks.

A. Their user account failed LDAP authentication →Incorrect

If LDAP authentication failed, the userwould not be able to log in at all.

In this case, theyare logged in but only see Self-Service, meaning authentication is not the issue.

B. Their user account is not logged in properly →Incorrect

If the login was incorrect, they would belogged out or receive an error message.

The issue here isa lack of permissions, not a login failure.

C. Their user account was not approved by their manager →Incorrect

Manager approval is not required for standard ITSM roles and access.

Why Other Options Are Incorrect?

User Roles in ServiceNow

Assigning Roles and Group Memberships

Official ServiceNow Documentation Reference:

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

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

Example:Priority,State,Assigned To

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

2. OperatorDefines the comparison condition for the filter.

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

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

3. ValueSpecifies the criteria being matched against the column.

Example:High,Closed,John Doe

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

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

Operator

Value

Priority

is

High

State

is not

Resolved

This filter will returnrecords where:

ThePriorityfield is set toHigh

TheStatefield is NOTResolved

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

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

Incorrect Answer Choices Analysis:

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

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

Official ServiceNow Documentation References:

In ServiceNow, role-based access control (RBAC) determines what a user can see and do within the platform. If a user can see an application and its module but encounters a blank page when attempting to create a new record, the most likely reason is insufficient permissions.

Understanding the Issue:

The usercan see the application and module, which indicates they have at leastreadaccess.

The blank page appears when they attempt to create a new record, which suggests a lack ofwriteaccess.

Role-Based Access Control in ServiceNow:

Every table in ServiceNow can haveACLs (Access Control Rules)that define what users can do based on their roles.

If a user hasonly read accessto the Inventory table (x_inventory), they can view records butcannot create new ones.

AwriteorcreateACL is required to allow the user to insert new records into the table.

Why Other Answers Are Incorrect:

A. Create New module has a broken link→ If the module had a broken link, the user would likely get an error or a " Page not found " message rather than a blank page.

B. Known intermittent issue with U115→ No such known issue exists in official CSA documentation.

C. User should be using Chrome instead of Explorer for their browser→ While browser compatibility issues can exist, they do not typically result in a blank page specifically when trying to create a new record.

E. User session has timed out→ If the session had expired, the user would be redirected to the login page rather than seeing a blank page.

Best Practice Solution:

Verify the ACLson the Inventory table (x_inventory) to check if the user haswriteandcreatepermissions.

Check the roles assignedto the user underUser Administration → Usersand ensure they have the appropriate roles for Inventory management.

Review the Application Menu and Module settingsto confirm proper configuration.

Understanding Service Catalog Components:

In ServiceNow, theService Catalogprovides a structured way for users to request services.

ARecord Produceris a special type of catalog item that createsrecords in a specific table(e.g., creating anIncidentrecord when submitting a " Get Help " form).

Why " Create Record Producer " is the Correct Answer:

ARecord Producerallows users to submit requests using a form thatcreates recordsin a specified table (in this case, the Incident table).

The submitted formautomatically routesthe record to theService Deskbased on assignment rules.

Itimproves user experienceby simplifying the incident creation process.

Why Other Answers Are Incorrect:

B. Create Catalog Item→ Catalog Items are used for ordering products or services (e.g., laptop requests) but do not create Incident records.

C. Create Order Guide→ Order Guides are used for grouping multiple Catalog Items into asingle request, not for creating Incidents.

D. Create Content Item→ Content Items provide links or information, but they do not create records in ServiceNow.

Best Practice Solution:

Navigate toService Catalog → Record Producersand create a newRecord Producerfor theIncident table.

Set appropriate fields, workflow, and assignment rules to ensure proper routing to theService Desk.

Detailed Explanation:

In ServiceNow, when reporting data is required from multiple tables and dot-walking isn’t feasible, creating aDatabase Viewis often the best approach. A Database View allows joining multiple tables virtually without creating new records, making it highly efficient for reporting. This view can then be used as a data source for reports, pulling information across tables without physically combining data. According to ServiceNow documentation, this is especially useful for creating complex reports that rely on data relationships across tables without altering the underlying data structure. (Reference: ServiceNow Documentation - Database Views)

==

In ServiceNow’sConfiguration Management Database (CMDB), threekey tablesform the foundation for storing and managingConfiguration Items (CIs)and theirrelationships.

cmdb_ci (E) - CI Base Class Table

This is thebase classfor allConfiguration Items (CIs)in the CMDB.

Every CI (e.g., servers, applications, network devices) extends from this table.

Stores general attributes like name, serial number, and asset tag.

cmdb (G) - CMDB Parent Table

This is theparent tablefor all CMDB-related tables.

Itdoes not store CI records directlybut serves as a reference structure.

All CMDB tables, includingcmdb_ci, inherit from this table.

cmdb_rel_ci (C) - CMDB Relationship Table

This tablestores relationshipsbetween different CIs.

Example: Aserver hosts an application, or adatabase is dependent on a storage unit.

Helps withimpact analysis and dependency mapping.

A. sn_cmdt_bak

No such table in standard ServiceNow CMDB.

B. sh_emdb_ci

Typo or incorrect table name—not part of the ServiceNow CMDB model.

D. cmdb_bak

" bak " suggests abackup table, but there isno standard " cmdb_bak " in ServiceNow.

F. sh_eomdb

Not a recognized CMDB table in ServiceNow.

Detailed Explanation:

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

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

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

==

In ServiceNow, Roles are used to configure access to Applications and Modules. Roles are a core component of ServiceNow ' s role-based access control model and determine which application menus, modules, features, and administrative capabilities a user can access.

For an Application , access can be restricted by assigning one or more roles to the corresponding Application Menu record. Only users possessing the required role can normally see that application in the navigation interface. ServiceNow documentation states that application access can be configured through the application ' s User role or through the Roles field on the Application Menu.

Modules are controlled similarly. The Module record contains a Roles field within its Visibility configuration. ServiceNow specifies that access to modules in the navigation menu is controlled through roles; users must meet the applicable role requirements before the module is displayed.

Users and Groups can receive roles, but they are not the permission mechanism configured directly on Applications and Modules. Departments are organizational records and do not determine Application Navigator access.

Therefore, the permission mechanism used to configure Application and Module access is Roles .

Study Guide Reference/Topics: User Administration → Roles → Role-Based Access → Application Menus → Module Visibility → Assigning Roles to Users and Groups.

TheApplication Navigatoris the primary navigation panel in ServiceNow. It provides access to allapplications and modules, includingIncident Management, Change Management, Service Catalog, and more.

It is found on theleft-hand sideof the ServiceNow interface.

Users cansearch, expand, and collapseapplications for easy navigation.

Common applications includeIncident, Problem, Change, and CMDB.

A. Self-Service Module– This module is forend usersto submit requests but does not provide access to all applications.

C. Service Desk Homepage– This is adashboard, not a navigation tool.

D. Favorites– TheFavorites sectionstores frequently accessed modules but does not list all applications.

ServiceNow Navigation – Application Navigator

ServiceNow CSA Training Module: " Navigating the ServiceNow Platform "

Where is the Application Navigator Located?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

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

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

For example:

Theadminrole provides full system access.

Theitilrole allows access to Incident and Change Management.

Thecatalog_adminrole grants permissions to manage Service Catalog items.

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

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

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

InServiceNow, 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:

Tofilter a long list of recordsand find those whereShort Description contains " email " , the best practice is to use thecolumn searchfeature:

Click the List Magnifier ( ???? )to open thecolumn searchoptions.

In the " Short Description " column search box, type:

Steps to Filter a List by " email " in Short Description:email

Press Enterto apply the filter.

This methodautomatically applies a " contains " filter, meaning it will showany records where " email " appears anywhere in the Short Description field.

A. Click List Magnifier to expand column search, on Short Description, type %email, click enter →Incorrect

% (percent sign) is not a valid wildcardin ServiceNow ' s list filters.

C. On Search box, select text, type email, click enter →Incorrect

Theglobal search box searches across multiple tables, not just the Short Description field.

D. Click List Magnifier to expand column search, on Short Description type ' email, click enter →Incorrect

Single quotes ( ' email ' ) are not requiredin column searches.

Why Other Options Are Incorrect?

Using List Filters in ServiceNow

ServiceNow Search Operators

Official ServiceNow Documentation Reference:

✔Common Services Data Model (CSDM)is aServiceNow best-practice frameworkthatstandardizes how IT services, applications, and infrastructure are structured in the CMDB. It provides ablueprintfor aligning ServiceNow configurations with business and IT operations.

Why CSDM is Important:

Ensures consistency inIT service mapping and asset relationships.

Helps organizationsalign CMDB datawith ITSM, ITOM, and other ServiceNow applications.

Providesdata governance and best practicesto maintain data integrity.

Option B (CMDB)is incorrect because theCMDB is the database that stores configuration items (CIs), but CSDM defines the model for structuring it.

Option C (ITSM)is incorrect because ITSM includes processes like Incident, Problem, and Change Management, but does not provide adata modelblueprint.

Option D (ServiceNow Wiki)is incorrect because ServiceNow no longer uses a wiki for documentation (it has been replaced by theServiceNow Docs Portal).

???? Reference:ServiceNow Common Services Data Model (CSDM) Guide

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:

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

In ServiceNow,User Criteriais the mechanism used to control and determine user access toknowledge bases (KBs) and knowledge articles. User criteria define which users, groups, or roles canread, write, and contributeto a knowledge base or specific articles within it.

How User Criteria Works:User Criteria are applied at both theknowledge baselevel and theknowledge articlelevel to manage access. They can be configured with specific conditions to allow or restrict access based on:

Users(specific users can be added directly)

Groups(access can be granted to a specific user group)

Roles(users with specific roles can be given access)

Advanced conditions(such as department, company, location, etc.)

A knowledge base can havemultiple user criteria, and a single user criterion can apply to multiple knowledge bases.

Read User Criteria– Determines who can view the knowledge base or an article.

Write User Criteria– Determines who can create, edit, or contribute knowledge articles.

Exclusions– You can exclude users or groups from accessing specific knowledge bases or articles even if they meet other conditions.

A. sn_kb_read, sn_article_read:

These are not standard ServiceNow permissions for controlling knowledge access.

In ServiceNow, permissions are managed through roles and user criteria, not direct ACL names like these.

B. Privacy Settings:

ServiceNow does not use " Privacy Settings " as an access control mechanism for knowledge bases.

Privacy settings might be relevant in other contexts, such asuser profiles or system preferences, but not for knowledge access control.

C. Read Access Flag:

There is no " Read Access Flag " in ServiceNow ' s knowledge management module.

Access is controlled viaUser Criteria, Roles, and Knowledge Base Settings.

Key Features of User Criteria in Knowledge Management:Why Other Options Are Incorrect?Official ServiceNow Documentation References:For more details, refer to the official ServiceNow documentation:

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Knowledge Management User Criteria

In the ServiceNow user interface, the Pencil icon is associated with editing or customizing an existing Favorite. In the traditional Application Navigator experience, selecting the edit option represented by the pencil allows a user to modify properties of saved Favorites, including the label/name, icon, and color . Therefore, when the requirement is specifically to change the label displayed for a Favorite, the Pencil icon is the appropriate selection.

The Star icon serves a different purpose: it is primarily used to add an application, module, or page to Favorites or to access Favorites. It does not represent the editing function requested in the question. The Triangle and Clock icons are not used for changing Favorite labels.

ServiceNow ' s current Next Experience documentation describes the equivalent workflow through Favorites > Edit your favorites , where a Favorite can be selected and its Name field changed. ServiceNow also confirms that Favorites can be customized by editing their names, icons, colors, and organization. ServiceNow

Study Guide Reference/Topics: User Interface and Navigation → Application Navigator → Favorites → Editing and Customizing Favorites → Favorite Labels and Icons.

In ServiceNow, lists allow users to view, filter, and group records dynamically. If you want to group records based on a particular column (e.g.,Category), you can use the " Group By " functionality.

A. On list Context Menu, select Group By > Category

TheList Context Menu(right-clicking anywhere in the list header) provides an option to group records by a specific column.

Selecting " Group By > Category " organizes records into expandable sections based on the selected field.

This is one of the quickest ways to group records in a list.

E. On the Category column title, click Context menu > Group By Category

Each column header in a list has its ownColumn Context Menu(accessible by clicking the three-line menu or right-clicking the column title).

Clicking“Group By Category”on theCategory columnwill instantly rearrange the list based on the values in that column.

B. On the Filter Menu, select Group By > Category

TheFilter Menuis used for setting up filters and conditions, but it doesnotprovide a " Group By " option.

It allows users to filter records but does not change the list structure.

C. Click Group On icon, select Category

There isno " Group On " icon in ServiceNow lists.

Grouping is done through context menus, not a dedicated " Group On " button.

D. On Navigator Filter, type tablename.group.category and press enter

TheApplication Navigator Filteris used for searching applications, modules, and tables—not for modifying list views.

Entering something likeincident.group.categorywill not perform a grouping action on a list.

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

Safe Testing Environment

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

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

Allows Hands-On Experience Without Risk

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

Any issues encountered willnot disrupt business operations.

Best Practice for ServiceNow Development

ServiceNowrecommends testing all new featuresin asandbox or development instancebefore enabling them in a production environment.

Why is " Activate the application plugin on your personal dev instance " the Correct Answer?

A. Check the latest release notes at docs.servicenow.com.Incorrect– While the release notes providevaluable information, theydo not provide hands-on experiencewith the application.

C. Search the wiki for the sales demo request form.Incorrect– ServiceNow hasmoved away from using wikis. Also, requesting asales demois not the best way totest an application yourself.

D. Activate the application plugin on your company ' s production instance.Incorrect–Never test a new application directly in production. This can causeunexpected issuesandimpact live operations.

Incorrect Answer Choices Analysis:

ServiceNow Developer Program – Personal Developer Instances (PDI)???? ServiceNow Developer Instances

ServiceNow Docs – Managing Plugins???? How to Activate Plugins

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. Activate the application plugin on your personal dev instance.

This methodallows safe testing and evaluationbefore considering implementation in a production environment.

ServiceNow uses JavaScriptas its primary scripting language for automation, business rules, UI actions, and server-side scripts.

Key Areas Where JavaScript Is Used in ServiceNow:

✔Client-side Scripting:UI Policies, Client Scripts

✔Server-side Scripting:Business Rules, Script Includes, Scheduled Jobs

✔Workflow & Flow Designer:Custom scripts for approvals, conditions, and notifications

✔Integration Scripts:REST API, SOAP API calls

B. C++

C++ is acompiled languageprimarily used for system software,not for ServiceNow scripting.

C. PHP

PHP is used forweb development, butnot supported in ServiceNow.

D. Python

Python isnot usedin ServiceNow for scripting. JavaScript is the standard for bothclient-side and server-side scripting.

Flow Designeris a modern, low-code automation tool in ServiceNow that allows users to build workflows efficiently. Here’s why the correct answers are:

Reduces technical debt (C)

Flow Designer enables reusability of workflows, reducing the need for custom scripting and minimizing long-term maintenance efforts.

Reducing technical debt means fewer dependencies on custom scripts, which can become difficult to manage over time.

Less manual scripting (D)

Flow Designer uses a visual drag-and-drop interface, allowing non-technical users to build workflows without deep scripting knowledge.

This helps in creating automated processes without writing complex business rules or scripts.

Smooth integration with 3rd party systems (E)

Flow Designer supports IntegrationHub, which provides pre-built connectors (Spokes) for various third-party applications such as Slack, Microsoft Teams, and Azure.

This makes it easier to create automated integrations with external services.

A. Supports advanced developers– Flow Designer is primarily designed for low-code/no-code automation, not specifically for advanced developers.

B. Enables complicated scripting– While Flow Designer allows some scripting via Script Actions, it is not meant for creating " complicated " scripts. Instead, it focuses on simplifying automation.

AnUpdate Setin ServiceNow is a container thatcaptures configuration changes(such as form modifications, business rules, or UI policies) made in an instance. These changes can then bemigrated from a development (Dev) environment to a test or production environment.

Key Features of Update Sets:✔Capturesform modifications, ACLs, scripts, and configurations.

✔Helps inmigratingchanges between instances (Dev → Test → Prod).

✔Ensuresconsistency across environments.

B. Transform maps

Used for mapping data fieldsduring an import, not for migrating configuration changes.

C. System dictionaries

Defines table and field attributesbut does not store configuration changes for migration.

D. Import sets

Used for importing external datainto ServiceNow, not for transferring configuration changes.

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

???? Key Core Tables in ServiceNow:

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

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

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

???? Why Option C is Correct?

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

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

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

???? Incorrect Options Explained:

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

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

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

???? Reference:

Creating Tables in ServiceNow

ServiceNow Task Table Documentation

Understanding Core Tables in ServiceNow

In ServiceNow,scripts that run in the browser (client-side)includeUI PoliciesandClient Scripts. These scripts execute on theuser’s web browser, allowing real-time interaction with forms and fields without requiring a server request.

Executed in the user’s browserwhen a form is loaded, saved, changed, or submitted.

Used forreal-time form validation, auto-population, and dynamic UI changes.

Written inJavaScriptand runs on the client side.

Applyrulesto make fieldsmandatory, visible, or read-onlydynamically.

Moreefficientthan Client Scripts because theydon’t require scriptingin most cases.

A. Script Include Scripts– Theserun on the server, not in the browser. They are reusable functions that can be called from different scripts.

B. Business Rule Scripts– Business Rulesexecute on the server-side, triggered by database operations (Insert, Update, Delete).

C. Access Control Scripts– These areserver-side security rules(ACLs) that restrict user access to records and fields.

ServiceNow Client Scripts and UI Policies

ServiceNow CSA Training Module: " Client-Side Scripting in ServiceNow "

1. Client Scripts:2. UI Policies:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

In ServiceNow,UI Actionsare customizable elements that enhance user interaction withforms,lists, and other UI components. When applied to forms, UI Actions allow users to trigger workflows, scripts, or system operations efficiently.

A. Form Context Menu

TheForm Context Menu(accessible by right-clicking on a form header or field) contains UI Actions such as:

Save,Insert,Insert and Stay,Configure Form Layout, etc.

Admins can customize this menu to include additional actions.

C. Form Buttons

Buttonsappear at the top or bottom of a form, allowing users to take specific actions.

Examples include:

Submit,Update,Resolve,Approve,Reject

These actions can be customized using UI Action scripting.

D. Form Links

Form Linksappear as clickable links at the bottom of a form.

Example:

“Show Related Incidents”link on an incident form.

These links allow users to navigate quickly between related records.

B. Form View

Form Viewis a layout configuration that determines how fields appear but isnota UI Action.

UI Actionstriggeractions, while Form Viewsdefine appearance.

E. Form Columns

Form Columnsrefer to the arrangement of fields within a form.

Columns help withform designbut do not serve as UI Actions.

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

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

???? Configure > Table

This willopen the Table Configuration Page, where you can:

View and edittable properties.

Managefields, relationships, and indexing.

Configuresecurity settings (ACLs)for the table.

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

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

Select " Configure " from the dropdown.

Click " Table " to access theTable Configuration Page.

Step-by-Step Navigation:

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

Allows modification of table-level settings

Best practice method for modifying table properties

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

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

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

Incorrect Answer Choices Analysis:

ServiceNow Docs – Configuring Tables???? Table Administration

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

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. The Form Context menu > Configure > Table

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

TheSystem Properties > Basic Configuration UI16page in ServiceNowallows administrators to customize the UI appearancefor end users. It providesbasic branding and theming optionsfor the ServiceNow instance.

Browser tab title→(A)You can modify the browser tab title that appears when users open ServiceNow.

Module text color→(B)This setting allows you to change the text color of the left navigation menu items.

Base theme→(D)You can select a base theme for the platform UI, impacting overall styling.

Header background color→(G)This setting changes the background color of the header in UI16.

Banner Image→(H)Allows uploading a custom banner/logo to replace the default ServiceNow logo.

C. Preferred browser→ Incorrect. ServiceNow does not allow setting a preferred browser from System Properties. Users must configure this on their own.

E. Font style→ Incorrect. UI16 Basic Configuration does not provide font customization options. Fonts are controlled through system themes and CSS.

F. Animation style→ Incorrect. ServiceNow UI16 does not provide options to change animation styles from Basic Configuration.

InServiceNow, theDependency Viewis agraphical representationthat allows Service Desk agents and IT teams totrace relationships between Configuration Items (CIs)and identify whichCIs are experiencing issues that may be affecting a business service.

Visualizes Relationships Between CIs and Services

Dependency View displaysCIs and their dependenciesin aninteractive map.

Service Desk agents can quicklysee which CIs are impactedandhow they affect the business service.

Identifies Impacted Configuration Items (CIs)

If aserver, database, or network component is down, Dependency Viewhelps tracewhich business service is affected.

This is useful forincident management, root cause analysis, and change impact assessment.

Integrated with CMDB (Configuration Management Database)

Dependency Views pull data from theCMDBtomap CI relationships.

This helps Service Desk agentsidentify problems quicklywithout needing deep technical knowledge.

Why is " Dependency View " the Correct Answer?

A. AI Service DashboardIncorrect– There is no standard " AI Service Dashboard " in ServiceNow.

B. CI Health DashboardIncorrect– TheCI Health Dashboardfocuses on theoverall health of CIs (e.g., compliance, correctness, completeness)but doesnot provide a dependency mapfor tracing service issues.

D. Event Management HomepageIncorrect–Event Management (ITOM)is used formonitoring events and alerts, butit does not provide an interactive dependency viewfortracing service issues.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Dependency Views???? Understanding Dependency Views

ServiceNow Docs – CMDB Relationship Visualization???? Using CMDB Relationships

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

C. Dependency View

Dependency Viewallows Service Desk agents totrace service issues back to the affected CIs, making it an essential tool forincident management and root cause analysis.

In the ServiceNow Service Catalog , the mechanism used to capture user input and options on a form is called a Variable . 11

1. Service Catalog Variables:

When a user accesses a Catalog Item (like " New Desktop Computer " ), they are presented with questions to specify what they need. These questions are not standard columns in a database table; they are Variables. Variables allow the Service Catalog to be dynamic and flexible without requiring schema changes (adding columns) to the underlying request tables for every new item.

2. Types of Variables:

To achieve the requirements listed in the question, a developer would use specific Variable types:

Select Box / Multiple Choice: Used for " Color " (Black/Silver) and " Keyboard " (Standard/Ergonomic).

In ServiceNow, when viewing alist view, you can easily filter out specific values byright-clicking on the field value and selecting " Filter Out " . This action dynamically updates the filter to exclude records with that value.

Navigate to theIncident List.

Locate a record withState = Resolved.

Right-clickon the " Resolved " value in theStatecolumn.

Select " Filter Out " from the context menu.

The list automatically refreshes, showing only incidentsexcluding " Resolved " .

A. On the list of records, locate the right-click on the Resolved value, select Exclude.

" Exclude " isnot an optionin the ServiceNow list filter menu. The correct option is " Filter Out " .

B. Click Funnel icon, click AND, Select Resolved, is Not State click Run.

Thefunnel iconopens the filter panel, but this answer is unnecessarily complex.Right-clicking and filtering out is faster.

C. On state column title, right-click, select Filter Out > Resolved.

Youcannot right-click the column titleto filter out a specific value; you must right-click on aspecific field value.

D. On Search, select State, type not Resolved, press enter.

The correct syntax in the filter bar is " State != Resolved " , butright-clicking is a more user-friendly method.

ServiceNow Filtering and List Views

ServiceNow CSA Training Module: " Working with Lists and Filters "

Steps to Exclude Incidents with the State " Resolved " :Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow, impersonation allows administrators toact as another userto troubleshoot, test permissions, or verify user experiences.

Tolog impersonation eventsin theSystem Log, the system property:

CopyEdit

glide.sys.log_impersonation

must beaddedand set totrue(true).

Key Features ofglide.sys.log_impersonation:Logswho impersonated whomin theSystem Log.

Capturestimestamp, user details, and session activity.

Helps withauditing and security compliance.

Navigate toSystem Definition > System Properties.

Search forglide.sys.log_impersonation.

If it doesn’t exist, create it:

Name:glide.sys.log_impersonation

Type:True/False

Value:true

Save the property and test impersonation.

How to Enable Impersonation Logging:

A. glide.user_setting →Incorrect

Not related to impersonation logging.

Deals withuser preferences and settings.

B. glide.sys.all_impersonation →Incorrect

No such property exists in ServiceNow.

D. glide.impersonation_setting →Incorrect

Incorrect property name; does not exist.

E. glide.sys.admin_login →Incorrect

Logsadmin logins, not impersonation events.

Why Other Options Are Incorrect?

Impersonating Users in ServiceNow

System Logs & Impersonation Tracking

Official ServiceNow Documentation Reference:

InServiceNow, when acustom tableis created, the systemautomatically generates four Access Control Rules (ACLs)to control the basic operations on that table. These rules define who cancreate, read, update, and delete recordsin the table.

Read (ACL: table_name.*.read)Allows users to view (read) recordsin the table.

Without this ACL, userscannot see any recordsin the table.

Create (ACL: table_name.*.create)Allows users to insert new recordsinto the table.

Without this ACL, userscannot add new records.

Update (ACL: table_name.*.update)Allows users to modify (edit) existing recordsin the table.

Userscannot edit recordsif this ACL is missing.

Delete (ACL: table_name.*.delete)Allows users to remove (delete) recordsfrom the table.

Userscannot delete recordswithout this ACL.

Default Access Control Rules Created for a New Table:

C. executeIncorrect– Theexecutepermission applies toScripts or UI Actions, not table records.

NoexecuteACL is automatically created for tables.

F. writeIncorrect– " Write " is NOT an ACL permission in ServiceNow.

Instead, " update " is the correct term for editing records.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Rules (ACLs)???? Access Control Best Practices

ServiceNow Docs – Creating Custom Tables???? Custom Tables and Security

Official ServiceNow Documentation References:

InServiceNow Table Inheritance, tables can be categorized asBase, Parent, or Childdepending on how they relate to other tables.

Task Table:

Base Table:Since it isnot extended from any other table, it serves as the foundation for other tables.

Parent Table:Because theIncident tableextends from Task, Task acts as aParenttable.

Incident Table:

Parent Table:BecauseSuper Incident extends from Incident, it becomes aParentto Super Incident.

Child Table:Since it extends fromTask, it is aChildtable to Task.

Super Incident Table:

Child Table:Because it extends fromIncident, it is aChildtable.

Not a Parent or Base Tablebecause no other table extends from it.

Understanding Table Relationships in the Given Scenario:Final Table Classification:Table

Base Table?

Parent Table?

Child Table?

Task

Yes

Yes

No

Incident

No

Yes

Yes

Super Incident

No

No

Yes

A. Incident table is a Base table →Incorrect

TheTask tableis the Base table, not Incident.

E. Super Incident table is a Parent table →Incorrect

No table extends from Super Incident, so itcannot be a Parent table.

F. Super Incident table is a Base table →Incorrect

It is extended fromIncident, meaning itis not a Base table.

I. Task table is a Child table →Incorrect

Sinceno other table extends to Task, it isnot a Child table.

Table Inheritance in ServiceNow

Extending Tables

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow,data policiesenforce rules to ensure data consistency and integrity across the platform. They can be applied at both theserver-sideandclient-side, even outside the standard UI (such as data imports and APIs).

Incident numbers should be read-only on all lists and forms, for all users.

Data policies can enforce field read-only rules globally.

TheIncident number (Number field) is typically auto-generatedand should not be editable by users. A data policy can ensure it remains read-only across all interfaces.

Short Description field should be mandatory, on all records, across all applications, on insert.

Data policies can make a field mandatory across the system, not just on specific forms.

UnlikeUI policies(which work only in forms), adata policy ensures this rule applies even during imports and API updates.

B. Dictionary Design Policy– No such policy exists in ServiceNow.

C. Data Quality Policy– This isnot a defined policy typein ServiceNow.

D. Field Criteria Policy– Not a recognized policy type in ServiceNow.

ServiceNow Data Policies Overview

ServiceNow CSA Training Module: " Data Policies vs. UI Policies – When to Use Each "

How Data Policies Apply to This Scenario:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Natural Language Query (NLQ)in ServiceNow allows users tofilter a list by typing a natural language phrase, making it easier to search and retrieve data without manually building filters.

For example, users can type:

➡️ " Show me all open incidents assigned to John Doe "

➡️ " Incidents created this week "

The platforminterprets the phraseand automaticallyapplies the correct filterto the list.

A. Automatically select a filter, based on keywords–NLQ does not automatically select filters based on keywords; instead, itprocesses full phrasesinto a filter.

C. Predict the filter desired by the user–NLQ does not predict filters but rather converts typed queries into list filters.

D. Speak to the condition builder–NLQ does not interact with the condition builder directly; it translates text queries into filters.

E. Set list filter, using audible commands–NLQ does not supportvoicecommands, onlytypedqueries.

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

Navigate toSystem Import Sets > Load Data.

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

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

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

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

Coalesce fieldsare defined toprevent duplicate recordsby identifying unique keys.

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

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

The imported data is now available in the production table.

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

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

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

C. Select Data Source, Schedule Transform

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

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

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

Why Other Answers Are Incorrect:

ServiceNow Data Import and Transform Maps

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

References from Certified System Administrator (CSA) Official Documentation:

In ServiceNow Knowledge Management, the ability to create, edit, or import articles into a specific Knowledge Base is governed by User Criteria , specifically the Can Contribute criteria.

1. User Criteria vs. Roles:

While ServiceNow heavily utilizes Roles (like itil or admin) for general platform security, Knowledge Bases use a more granular, criteria-based approach. On a Knowledge Base definition record, administrators define who can interact with it using two primary related lists:

Can Read: Who is allowed to see the articles.

Can Contribute: Who is allowed to author, edit, and import articles.

2. The Import Process:

ServiceNow allows users to import Word documents directly into a Knowledge Base to automatically generate HTML articles. To utilize this feature for a given KB, the user must meet the conditions defined in that KB ' s " Can Contribute " User Criteria (which could be based on their department, group, role, or individual user record).

3. Why the other options are incorrect:

A & B: sn_knowledge_contribute and sn_knowledge_import are not standard out-of-the-box base platform roles dedicated specifically to the single action of importing.

C: There is no distinct " Can import " User Criteria related list. The right to import is bundled into the general right to author/contribute.

In ServiceNow, when a user wants topersonalize the layout of the columnsin arelated list, they need to click theGear icon (⚙️).

Navigate to a record that contains arelated list.

Look at the top-right corner of the related list for theGear icon.

Click theGear iconto open the " Personalize List Columns " interface.

From there, the user canadd, remove, or rearrange columnsin the related list.

A. Magnifier– A magnifying glass is typically used forsearch functionsbut not for column customization.

B. Context Menu– The context menu (right-click) providesother actionsbut does not allow column layout changes.

C. Pencil– A pencil icon typically representseditingbut not column layout customization.

ServiceNow Personalizing List Views

ServiceNow CSA Training Module: " Personalizing Lists and Forms "

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

In ServiceNow, aRecord Produceris used to create atask-based record(such as anIncident, Change, or Request) from theService Catalog.

Record Producersprovide acustomized formthat allows users to submit data to create a record in a specific table (e.g., Incident, Change, Request, or a custom table).

They aredifferent from catalog items, which typically create aRequested Item (sc_req_item)instead of directly creating a task record.

They allowsimplified user inputwhileautomating record creationin a structured way.

A user submits aNew Hire Requestvia the Service Catalog.

ARecord Produceris triggered, creating atask-based record(such as a request or a custom HR case).

B. UI Builder– Used for designing UI pages,not for creating task-based records.

C. Assignment Rule– Determineswho a task is assigned to, butdoes not create records.

D. Flow Designer– Automates workflowsafter a record is created, but doesnot create task records from the Service Catalog.

E. UI Actions– Custom buttons and links for UI interaction, butnot used for record creation from the Service Catalog.

ServiceNow Record Producers

ServiceNow CSA Training Module: " Service Catalog and Record Producers "

Why Record Producers Are the Correct Choice?Example Use Case:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Theknowledge_adminrole in ServiceNow provides the ability to manage multiple knowledge bases. This includescreating, editing, publishing, retiring, and configuring settingsfor knowledge bases and articles.

???? Whyknowledge_admin?

Manages all knowledge basesin the instance.

Has permissions tocreate, edit, and deleteknowledge bases.

Can assignknowledge base-specific rolessuch asknowledge_managerorknowledge_editorto users.

Controlsworkflows, article approvals, and permissionsfor knowledge management.

???? Incorrect Options Explained:

A. knowledge_base_admin– This is not a valid ServiceNow role.

B. kb_admin– This is not an officially recognized role in ServiceNow.

C. sn_kb_admin– This role does not exist in thedefaultServiceNow configuration. The correct role isknowledge_admin.

???? Reference:

Knowledge Management Roles – ServiceNow Docs

Managing Knowledge Bases in ServiceNow

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:

Themain UI components of the ServiceNow platformare designed to provide a structured and user-friendly experience for interacting with the system. These core UI elements include:

Banner Frame– Displays key information such as the logo, user profile, settings, and global search.

Application Navigator– Provides access to different modules and applications within ServiceNow.

Content Frame– Displays the main content area where users interact with forms, lists, and dashboards.

A. Banner Navigator– Incorrect terminology; the correct term isBanner Frame.

C. Application Frame– No such UI component exists in ServiceNow.

E. Content Menu– This is not a primary UI component; the correct term isContent Frame.

Why Other Options Are Incorrect:

ServiceNow Documentation:User Interface Overview

CSA Exam Guide:CoversBanner Frame, Application Navigator, and Content Frameas the three primary UI components.

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

B. Banner Frame, D. Application Navigator, F. Content Frame

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

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

There aretwo key aspectsof LDAP Integration in ServiceNow:

Authentication

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

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

This helps in maintainingcentralized identity managementacross the organization.

Data Population

LDAP can be used toimport user and group informationinto ServiceNow.

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

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

B. Data Formatting–

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

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

C. Authorization–

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

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

ServiceNow Docs: LDAP Integration

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

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

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

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

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

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

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

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

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

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

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

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

ServiceNow Docs: User Administration – sys_user Table

ServiceNow CSA Study Guide – User and Group Administration

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

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

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

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

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

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

Multi-Row Editing:Certain fields support bulk updates.

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

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

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

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

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

ServiceNow Product Documentation → Lists and List Editing

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

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

InServiceNow 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, theNumber Maintenanceapplication is used toconfigure and modify numbering formats for specific tables. This application allows administrators to control how records are numbered across different modules.

Customization of Number Formats

Administrators can defineprefixes, number sequences, and suffixesfor records in different tables.

Example:INC0001001forIncidents,REQ0002001forRequests.

Resetting or Adjusting Number Sequences

You can manually adjust the numbering sequence if needed.

Example: Resetting incident numbering to start from a specific value.

Supports Multiple Tables

Works for standard tables likeIncidents, Problems, Requests, Change Requests, etc.

Can also be configured forcustom tables.

Application Navigation

Path:

Go toAll → System Definition → Number Maintenance

Locate the table and modify its numbering settings.

Key Features of Number Maintenance:Why Option A (Number Maintenance) is Correct? " Number Maintenance " is the official ServiceNow application for managing number formats per table.

Why Other Options Are Incorrect?B. System Maintenance– Incorrect; no such module in ServiceNow manages numbering formats.

C. Table Maintenance– Incorrect; this does not exist as an application in ServiceNow.

D. Record Maintenance– Incorrect; not a valid ServiceNow feature for modifying number formats.

ServiceNow Docs – Number Maintenance

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow System Definition – Number Format Best Practices

References from Certified System Administrator (CSA) Documentation:

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

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

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

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

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

caller_id.email

Here’s how it works:

caller_id→ References thesys_usertable

email→ Retrieves theemail field from the sys_user record

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

caller_id.department.name

caller_id→ References theUser table

department→ References theDepartment table

name→ Retrieves thedepartment name

(A) Table-Walking – Incorrect

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

The correct term for referencing related fields isDot-Walking.

(B) Sys_ID Pulling – Incorrect

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

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

(C) Dot-Walking – Correct

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

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

(D) Record-Hopping – Incorrect

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

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

Explanation of Each Option:

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

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

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

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

Additional Notes & Best Practices:

ServiceNow Docs: Understanding Dot-Walking

ServiceNow Community: Best Practices for Dot-Walking

References from Certified System Administrator (CSA) Documentation:

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

Displaysall fields (columns)within a selected table.

Showsdata types, attributes, and configurationsof each field.

Allows admins toadd, modify, or removefields.

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

Navigate to:System Definition > Tables & Columns

Select a table to view itsfield settings.

B. Access Control – Incorrect

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

C. Columns and Fields – Incorrect

No such module exists in ServiceNow.

D. Tables and Fields – Incorrect

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

ServiceNow Docs: System Definition – Tables & Columns

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Managing Fields in a Table

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

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.

In ServiceNow, afilter conditionconsists of three primary components:

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

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

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

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

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

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

Field:State

Operator:is

Value:New

A. Table–

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

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

ServiceNow Docs: Filtering Data in Lists and

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

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

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,Access Control rules (ACLs)are used torestrict or grant accessto data. Each Access Control rule consists of:

Table-level (Row-Level) ACLs– Control access to the entire record (row).

Field-level ACLs– Control access to specific fields within a record.

Access Control rules are evaluated in a specific orderto determine whether a user has the necessary permissions to perform an action (Read, Write, Create, Delete, etc.).

If both a row-level and a field-level ACL exist for the same table, BOTH must evaluate to " true " before access is granted.

The system checks conditions, scripts, and roles defined in the ACLsto decide whether the user meets the access requirements.

Access Control Rule Evaluation Process:Why is Option C Correct?If both a row-level rule and a field-level rule exist, both must evaluate to " true " for a user to perform an action.

Row-Level ACLscheck if a user can access the record itself.

Field-Level ACLscheck if a user can access specific fields within that record.

If a user failseitherACL check, access is denied.

Why Are the Other Options Incorrect?A. " Rules are evaluated using roles. The role with the most permissions evaluates the rules first. "

Access Control rulesare not evaluated based on roles with the most permissions.

Roles are just one factorin ACL evaluation, along with conditions and scripts.

B. " If more than one rule applies to a row, the older rule is evaluated first. "

ServiceNow does not prioritize ACL rules based on their creation date.

Instead, ACLs follow a structured evaluation order (general-to-specific).

D. " Rules are evaluated from the general to the specific, so a table rule must be active to continue. "

This is partially true but misleading.

ServiceNow evaluates ACLs fromspecific to general(Field → Table).

However,a table-level rule does NOT need to be activefor a field-level ACL to be evaluated.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Access Control Rules (ACLs) Evaluation

???? ServiceNow ACL Evaluation Documentation

" If a field-level rule and a row-level rule exist,both must evaluate to truefor the operation to be allowed. "

Conclusion:The correct answer isC. If a row-level rule and a field-level rule exist, both rules must be true before an operation is allowed.

???? Understanding ACL rule evaluation is critical for managing security in ServiceNow, ensuring that users have the appropriate access while maintaining data integrity.

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

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, the best practice for managingusers, groups, and rolesis based onrole-based access control (RBAC).

Assign Roles to Groups (Correct)

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

This ensuresbetter role management, easier administration, and scalability.

Example:

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

All users in this group automatically get theitilrole.

Add Users to Groups (Correct)

Users should be assigned togroupsrather thanroles directly.

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

Example:

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

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

Incorrect: Assigning roles to groups is therecommended best practice.

Managing roles at thegroup levelmakesaccess control more efficient and scalable.

B. You should assign roles to users(Incorrect)

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

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

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

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

References from ServiceNow CSA Documentation:

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

Drives Complex Fulfillment Processes:

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

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

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

Sends Notifications to Defined Users or Groups:

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

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

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

Approval and Task Automation:

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

They can also generatetasksfor fulfillment teams based on predefined conditions.

Integration with Flow Designer and Other Automation Tools:

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

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

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

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

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

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

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

ServiceNow Product Documentation – Service Catalog

ServiceNow Learning – Service Catalog and Workflow Automation

ServiceNow Developer Portal – Flow Designer & Workflow Automation

References from Certified System Administrator (CSA) Documentation:

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

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

When creating filters inServiceNow, the elements should be specified in the following order:

Field– The database field (column) that is being filtered.

Operator– The comparison method, such as " is " , " contains " , " greater than " , etc.

Value– The specific data that the filter should match.

Example of a Properly Structured Filter:Imagine filtering a list ofIncidentswhere the priority is high. The filter would be structured as:

Field:Priority

Operator:is

Value:High

is– Matches an exact value

is not– Excludes a specific value

contains– Looks for a partial match

greater than– Finds records with a value greater than the specified one

less than– Finds records with a value less than the specified one

B. Field, Operator, then Condition– Incorrect.

" Condition " is not an individual filter element in ServiceNow; theoperatoralready defines the condition (e.g., " is " , " contains " ).

C. Operator, Condition, then Value– Incorrect.

The field must comefirstto define what data is being filtered. The operator follows next.

D. Value, Operator, then Field– Incorrect.

This is completely reversed; you must specifywhat fieldyou are filtering first before applying conditions.

ServiceNow Product Documentation → Filters and Condition Builder

ServiceNow CSA Study Guide → Data Management and List Filters

ServiceNow List Views → Using Filters and Operators

Common Operators in ServiceNow Filters:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

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

Storestable and field definitions, including:

Column names

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

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

Default values

Ensuresdata integrityby defining the structure of database tables.

Used by administrators tomodify or extend existing tables.

Allows the creation ofcustom fieldsin tables.

Key Features of the System Dictionary (sys_dictionaryTable):

Navigate to:System Definition → Dictionary

Search for a table or fieldto view its metadata.

Modify attributes(if needed) to customize table behavior.

How to Access the System Dictionary:

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

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

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

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

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

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

Explanation of Incorrect Answers:

ServiceNow Product Documentation → System Dictionary (sys_dictionary)

ServiceNow CSA Study Guide → Understanding Tables and Fields

ServiceNow Developer Documentation → Dictionary and Table Structure

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

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

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

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

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

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

Assigning access roles to multiple users at once.

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

Managing security and permissions in ServiceNow.

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

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

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

ServiceNow Docs: User Administration – sys_user_group Table

ServiceNow CSA Study Guide – Managing Users and Groups

Key Fields in thesys_user_groupTable:Common Use Cases for Groups:Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

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

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

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

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

How the " Flag Article " Feature Works:

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

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

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

Why Other Options Are Incorrect:

ServiceNow Documentation:Flagging a Knowledge Article

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

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

A. Flag article

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:

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

Related Lists appear at the bottom of a form view.

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

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

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

AnIncidentrecord may have a Related List showing allTasksassociated with it.

AUserrecord may have a Related List displayingGroup Memberships.

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

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

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

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

ServiceNow Product Documentation - Related Lists

ServiceNow CSA Study Guide - Configuring Forms and Lists

ServiceNow Docs: Relationships in Tables

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

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

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

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:

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

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

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

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

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

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

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

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

Number

Short Description

Caller

State

123abc

INC001

System crash

John D

New

456def

INC002

Network issue

Jane S

Open

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

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

B. Lists – Incorrect

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

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

C. Forms – Incorrect

Formsare user interfaces used to view or edit single records.

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

ServiceNow Docs: Tables and Records

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

ServiceNow Product Documentation: List and Form Views

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

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:

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

Grant Access to Applications and Modules:

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

Control Record-Level and Field-Level Access:

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

Assign Multiple Roles to a User:

A user can havemultiple rolesbased on job responsibilities.

Example Roles in ServiceNow:

admin– Full access to all system features.

itil– Can manage incidents, problems, and changes.

catalog_admin– Manages the Service Catalog.

asset– Manages assets and CI records.

Key Functions of Roles in Access Control:

Navigate to:All → Users and Groups → Users

Open a user record

Scroll to the Roles related list

Click Edit and add roles

How to Assign Roles to Users:

A. Access Control Rules– Incorrect.

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

B. UI Policies– Incorrect.

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

D. Assignment Rules– Incorrect.

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

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Roles and Permissions

ServiceNow CSA Study Guide → User and Role Management

ServiceNow Knowledge Base → Controlling Access to Applications and Modules

References from Certified System Administrator (CSA) Documentation:

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

Thefour correct concepts associated with the CMDBare:

The CMDB is structured usingtablesandfieldswithin the ServiceNow database.

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

Example CMDB Tables:

cmdb_ci(Base CMDB Table)

cmdb_ci_server(Stores server-specific CIs)

cmdb_ci_database(Stores database-related CIs)

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

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

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

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

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

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

Example:

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

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

Incident Management(linking incidents to affected CIs)

Change Management(analyzing the impact of changes on CIs)

Problem Management(identifying root causes of recurring issues)

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

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

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

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

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

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

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

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

Example Use Case:

InServiceNow, knowledge articles within aKnowledge Base (KB)aregrouped by categoriesto help users easily find and navigate relevant information.

Hierarchical Structure:

Categories can haveparent-child relationships, allowing forsubcategories.

Example:

Key Features of Knowledge Article Categorization:nginx

CopyEdit

ITSupport

├── Hardware

│ ├── Laptops

│ ├── Printers

├── Software

│ ├── Windows

│ ├── MacOS

Improved Search & Filtering:

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

Permissions & Visibility Control:

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

Article Organization & Management:

Knowledge managers canreassign articlesto different categories if needed.

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

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

Knowledge Management Overview

Knowledge Management in ServiceNow

Creating and Managing Knowledge Categories

Knowledge Base Categories

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

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:

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.

In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.

Definition of a Role:

Aroleis a collection ofpermissionsthat grant access to different parts of the system.

Example:Theadminrole grants full access, while theitilrole allows incident management access.

sys_user_role Table:

This tablestores role recordsand their associated metadata.

Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).

Users are linked to roles through thesys_user_has_roletable.

How Roles Work in ServiceNow:

A user assigned a role gainsall the permissionsassociated with that role.

Roles can behierarchical(one role can inherit permissions from another).

Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.

Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.

B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.

C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.

ServiceNow Docs – Roles and Role

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

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:

AnUpdate Setin ServiceNow is a mechanism thattracks and packages customizations and configuration changesso they can be transferred between instances (e.g., fromDevelopmenttoTestorProduction).

It is primarily used ininstance migrationandchange management, ensuring that changes made in one environment can beapplied consistentlyin another.

Tracks Customizations– Records changes to system configurations, such as Business Rules, Client Scripts, UI Policies, and Workflows.

Facilitates Deployment– Enables controlled migration of changes from one ServiceNow instance to another.

Reduces Manual Effort– Instead of manually reconfiguring settings in different environments, administrators can package updates into asingle unit.

Version Control– Ensures that onlyintended changesare moved between instances.

Key Features of Update Sets:

Why the Correct Answer is A:A. An Update Set allows administrators to group a series of changes into a named set and then move this set as a unit to other systems(Correct)

This accurately describes the primary function of anUpdate Set.

Administratorsgroupmultiple changes into anUpdate Set, export it, and apply it to another instance.

Example Workflow:

Admin makes configuration changes(e.g., modifies a Business Rule, updates a Workflow).

Update Set captures those changesin a structured format.

The Update Set is exportedfrom the Development instance.

The Update Set is importedinto the Testing/Production instance and applied.

Why the Other Options Are Incorrect:B. By default, an Update Set includes customizations, Business Rules, and homepages(Incorrect)

Update Setsdo include customizations and Business Rules, but theydo notinclude homepages by default.

Dashboards and homepagesrequire a separate process usingsys_portal_page and sys_ui_page tables.

C. An Update Set is a group of customizations that is moved from Production to Development(Incorrect)

Update Sets are typically movedfrom Development to Test/Production, not the other way around.

Best practice is to make changes inDevelopment, test them inTest/UAT, and then deploy them toProduction.

D. By default, the changes included in an Update Set are visible only in the instance to which they are applied(Incorrect)

This is misleading becausean Update Set can be exported and applied to multiple instances.

Once an Update Set isimported and committed, its changes become active in that instance.

Best Practices for Using Update Sets:✔Always preview an Update Set before committing itto ensure it contains the correct changes.

✔Use Named Update Sets, not the default " Default Update Set, " to track changes effectively.

✔Ensure all related changes are included(e.g., dependencies such as script includes and tables).

✔Test Update Sets in a sub-production instancebefore applying them inProduction.

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

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

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

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

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

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

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

ServiceNow Product Documentation - Service Catalog Overview

ServiceNow CSA Study Guide - Service Catalog Fundamentals

ServiceNow Docs: Service Catalog Components

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

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 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, theLoad Data and Transform Mapprocess is used toimport data from external sources(e.g., CSV, Excel, XML) into the ServiceNow platform. TheMapping Assisttool is a feature within this process that helps administrators visually map fields between thesource data(imported file) and thetarget tablein ServiceNow.

Load Data:

Data is imported from an external source (e.g., CSV file, Excel spreadsheet, XML data).

The imported data is temporarily stored in astaging table(Import Set Table).

Transform Map:

ATransform Mapdefines how fields in the import set should be mapped to the target table in ServiceNow.

It allows datatransformation, filtering, and scriptingduring the import process.

Mapping Assist:

Mapping Assistis avisual toolthat helps administrators easily map fields between the import set and the target table.

It provides adrag-and-drop interfaceto connect fields.

Helps preventerrors in field mapping, ensuring data integrity.

Understanding the Load Data and Transform Map Process

Why Answer " D " is Correct:✔️ " Mapping fields using a Field Map. "

TheField Mapis created in theTransform Mapto define how fields from the import set match fields in the target table.

Mapping Assistis used tovisually linkthese fields, making it easier to set up the transformation process.

Why the Other Answers Are Incorrect:A. " Mapping fields using the Import Log. "

Incorrectbecause theImport Logtracks the progress of an import job but does not provide field mapping.

The Import Log is used fortroubleshooting errors, not for mapping fields.

B. " Mapping fields using Transform History. "

IncorrectbecauseTransform Historytracks past transformations and changes made during imports, but it isnot used for mapping fields.

It is used forauditing and debugging transformations, not field mapping.

C. " Mapping fields using an SLA. "

IncorrectbecauseSLAs (Service Level Agreements)are used for tracking and enforcing deadlines on tasks,not for data mapping.

SLAs have no role in theLoad Data and Transform Mapprocess.

ServiceNow CSA Study Guide – Import Sets & Data Transformation

ServiceNow Docs: Transform Maps & Field Mapping(ServiceNow Documentation)

ServiceNow Docs: Mapping Assist Feature

References from the 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, ataskis a record that represents work that needs to be completed. It follows a lifecycle where it is:

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

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

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

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

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

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

Key Features of a Task:

A. Report:

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

B. Workflow:

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

C. Event:

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

Why Other Options Are Incorrect:

ServiceNow Documentation:Task Management in ServiceNow

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

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

ASchema Mapin ServiceNow is a graphical representation of tables and their relationships within the database. It helpsadministrators and developersunderstand how data is structured and interconnected.

Visual Representation:Showsparent-child relationships,reference fields, andextensionsbetween tables.

Database Schema Navigation:Enablesquick accessto table structures and fields.

Impact Analysis:Helps inassessing changesbefore modifying fields, tables, or relationships.

Enhances Development Efficiency:Aids in customizing the system by understanding data dependencies.

Navigate to:System Definition → Schema Map

Select a Table:Enter a table name (e.g.,incident,task)

View Relationships:The map will display related tables (e.g., extended, referenced, and referencing tables).

Key Features of a Schema Map:How to Access Schema Maps:

A. A schema map enables administrators to define records from specific tables as trouble sources for Configuration Items– Incorrect.

Schema mapsdo not define trouble sources; they are used to visualizetable relationships.

B. A schema map graphically organizes the visual task boards for the CMDB– Incorrect.

Visual Task Boardsare separate from schema maps and are used for task management, not database visualization.

C. A schema map graphically displays the Configuration Items that support a business service– Incorrect.

This describes aDependency View, which is part of theCMDB, not the Schema Map feature.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Schema Maps

ServiceNow CSA Study Guide → Data Schema & Table Relationships

ServiceNow Developer Documentation → Understanding Tables & Relationships

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

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

(A) A Trigger – Correct

Triggers are the starting point of a flowin Flow Designer.

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

Types of triggers include:

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

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

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

(B) Core Action – Incorrect

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

Sending notifications

Updating records

Calling APIs

They aresteps within a flow,notwhat initiates it.

(C) A Spoke – Incorrect

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

Spokescontain actionsbut donotinitiate flows.

(D) An Event – Incorrect

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

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

Explanation of Each Option:

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

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

Record Triggersare commonly used for automation within ITSM processes.

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

Additional Notes & Best Practices:

ServiceNow Docs: Flow Designer Triggers

ServiceNow Community: Best Practices for Flow Designer Triggers

References from Certified System Administrator (CSA) Documentation:

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.

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: