CSA ServiceNow Certified System Administrator Question and Answers

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 Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/integrate/authentication/concept/c_LDAPIntegration.html

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.

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

Used todynamically change form field behaviorsbased on specific conditions.

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

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

Example:

If theCategoryisHardware, theSerial Numberfield becomesmandatory.

Used tocreate buttons, links, and context menu actions.

Can executescriptsto perform specific actions when clicked.

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

Example:

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

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

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

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

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

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

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

Testing Permissions & Roles

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

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

Debugging & Troubleshooting

Identifies why a usercannot access certain records or modules.

Helps inresolving permission-related issueswithout affecting live users.

Experience Validation

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

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

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

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

Primary Functions of User Impersonation:How to Use Impersonation:

(A) Testing and visibility – Correct

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

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

(B) Activate verbose logging – Incorrect

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

(C) View custom perspectives – Incorrect

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

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

(D) Unlock Application master list – Incorrect

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

Application access is controlled byroles and permissions, not impersonation.

Explanation of Each Option:

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

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

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

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

Additional Notes & Best Practices:

ServiceNow Docs: Impersonating Users

https://docs.servicenow.com

ServiceNow Community: Best Practices for User Impersonation

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

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

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

Conversational AI & Automation

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

Predefined Topics & Custom Topics

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

Multi-Channel Support

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

Self-Service Capabilities

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

Integration with ServiceNow Workflows

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

A. Answer Agent

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

B. Live Feed

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

D. Connect Chat

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

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

ServiceNow Product Documentation - Virtual Agent

Virtual Agent Overview

Setting Up Virtual Agent

ServiceNow Conversational Interfaces

Virtual Agent vs. Connect Chat

References from ServiceNow CSA Documentation:

ServiceNow uses a hierarchical structure to manageService Catalog requests:

REQ (Request Record)

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

It groups all requested items and their associated tasks.

Found in thesc_requesttable.

RITM (Requested Item Record)

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

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

Found in thesc_req_itemtable.

TASK (Catalog Task Record)

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

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

Found in thesc_tasktable.

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

This is thecorrect pathbecause it follows theServiceNow fulfillment structure:

REQ (Request)– Tracks the entire request.

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

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

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

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

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

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

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

Incorrectbecausenot all requests involve procurement.

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

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

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

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

ServiceNow CSA Study Guide – Service Catalog & Request Fulfillment

ServiceNow Docs: Request Fulfillment Process(ServiceNow Documentation)

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

References from the Certified System Administrator (CSA) Documentation:

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

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

Fields Inheritance:

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

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

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

Business Rules, Client Scripts, and UI Policies:

Unlike fields, these components arenot automatically inherited.

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

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

Access Control Rules (ACLs):

ACLs are not automatically inherited.

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

Database Structure:

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

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

The child tableinherits all fieldsfrom the parent table.

The child table can also have its owncustom fields.

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

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

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

ServiceNow Fundamentals – Table Relationships

ServiceNow Developer Portal – Extending Tables

ServiceNow Best Practices – Access Controls & Security Rules

Why Option C is Correct?References from Certified System Administrator (CSA) Documentation:

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

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

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

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

Example: Searching for " Incident " will return:

Application: " Incident "

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

Modulesare specific functionalities within an application.

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

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

" Create New Incident "

" Create New Change Request "

The search field supports findingfull applicationsby their name.

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

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

This helps users quickly access commonly used features.

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

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

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

Instead, users can find history under:

History Module(System Settings > History)

Recent History Tabin the left navigation

F. Titles of Dashboard Gauges (Incorrect)

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

Instead, dashboards and reports are found under:

Self-Service > Dashboards

Performance Analytics > Dashboards

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

They type " incident " into the App Navigator search.

The search results return:

Incident (Application)

All (Module)

Assigned to Me (Module)

Resolved (Module)

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

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

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

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

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

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

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

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

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

Why Are the Other Options Incorrect?A. Records

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

Since records are frequently accessed, theyare logged in History.

C. Lists

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

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

D. Forms

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

Since forms are commonly accessed, theyare logged in History.

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

🔗 ServiceNow Application Navigator Documentation

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

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

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

A client sends requeststo a server.

The server processes the requestand sends back a response.

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

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

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

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

How This Relates to ServiceNow:

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

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

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

Why Other Options Are Incorrect:

ServiceNow Documentation:Client and Server in ServiceNow

CSA Exam Guide:CoversClient and Server architecturein ServiceNow.

Reference from CSA Documentation:

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

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 Knowledge Management,flagging an articleis a feature that allows users toreport errors or issueswithin a knowledge article. This helps maintain article accuracy and ensures that outdated or incorrect information is addressed by knowledge managers.

Error Reporting

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

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

Article Quality Control

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

Ensures that knowledge articles remainrelevant and useful.

Notifying Knowledge Managers

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

A. To mark an article to read later

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

Instead, users canbookmarkan article for quick access.

B. Allow a user to submit feedback about an article

Incorrect:

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

Flaggingis specifically forerror reporting, not general feedback.

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

Flagging Knowledge Articles

Flagging an Article for Review

Managing Flagged Articles

Knowledge Management Administration

References from ServiceNow CSA Documentation:

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

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

Pathway 1: Knowledge Base > My Knowledge > Flagged Articles

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

Location:Knowledge Base → My Knowledge → Flagged Articles

Pathway 2: Knowledge > My Articles > Flagged

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

Location:Knowledge → My Articles → Flagged

A. Knowledge > Articles > My Flagged

There isno direct " My Flagged " optionunderKnowledge > Articles.

D. Knowledge > Articles > Published

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

Navigate toKnowledge > My Articles > Flagged.

OR navigate toKnowledge Base > My Knowledge > Flagged Articles.

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

ServiceNow Docs: Managing Knowledge Feedback and Flagged Articleshttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/knowledge-management/task/review-article-feedback.html

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

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

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

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

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

If no match is found:

A new record is created.

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

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

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

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

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

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

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

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

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

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

ServiceNow CSA Official Documentation on Data Import & Transform Maps:

ServiceNow Docs - Transform Maps

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

Reference from Certified System Administrator (CSA) Documentation:

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

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

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

Recording Customizations:

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

Capturing Related Records:

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

Update Sets capture theWorkflow Versionand associatedWorkflow Activities.

Exporting and Importing:

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

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

Commit the Update Set:

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

B. Workflows are moved using Transform Maps

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

C. Workflows are moved using Application Sets

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

D. Workflows cannot be moved between instances

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

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

ServiceNow Product Documentation - Update Sets

Update Sets Overview

Moving Customizations Using Update Sets

ServiceNow Workflows

Workflow Management

References from ServiceNow CSA Documentation:

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

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?🚀

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

Base Tables:

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

It serves as afoundationfor creating new tables.

Example:

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

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

Core Tables:

Core Tablesare thestandard tablesprovided by ServiceNow.

Theycan be base tables or extended tablesdepending on their role.

Example:

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

Extended Tables:

Extended Tablesare tables thatinherit fields and functionalityfrom aparent table.

Example:

Incident (incident)extends fromTask (task).

Custom Tables:

Custom Tablesare tables thatdevelopers create for specific business needs.

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

Understanding Table Types in ServiceNow

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

These tablesdo not inherit fieldsfrom any other table.

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

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

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

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

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

C. " Extended Tables "

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

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

D. " Custom Tables "

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

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

ServiceNow CSA Study Guide – Data Schema & Tables

ServiceNow Docs: Table Hierarchy & Extensions(ServiceNow Documentation)

ServiceNow Data Model Overview (Base Tables & Extended Tables)

References from the Certified System Administrator (CSA) Documentation:

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

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow System Definition – Number Format Best Practices

References from Certified System Administrator (CSA) Documentation:

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:

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:

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

Thesix methods available for user authenticationin ServiceNow are:

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

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

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

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

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

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

Thus, the correct answer is:

A, B, C, D, E, F

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

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

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

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

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

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

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

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

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

SAML 2.0 Authentication:

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

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

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

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

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

Digest Token Authentication:

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

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

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

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

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

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

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

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), 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,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 Actionshttps://docs.servicenow.com

ServiceNow Learning – Form Configuration & UI Policies

ServiceNow Developer Portal – Controlling Form Behavior with UI Policies

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.

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:

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

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

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

✔Can trigger workflows and business ruleswhen submitted.

✔Maps user inputs to table fieldsviaVariable Mappings.

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

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

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

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

Example Use Case:

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

This is the most accurate description of aRecord Producer.

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

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

Record Producers are not limited to Requests.

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

B. A Record Producer creates user records (Incorrect)

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

Instead, itcreates task-based recordsin other tables likeincidentorsc_task.

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

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

ARecord Producer creates a single recordin a defined table.

Comparison: Record Producer vs. Other Catalog ItemsFeature

Record Producer

Standard Catalog Item

Order Guide

Creates a record in a ServiceNow table

Yes

No

No

Used to order physical/digital goods

No

Yes

Yes

Can bundle multiple requests

No

No

Yes

Uses a form-based submission

Yes

Yes

Yes

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

Creates a new record in the database.

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

The form is cleared after inserting the record.

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

Example:

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

The systemsaves the new Incident and exitsto the list view.

Saves changes to an existing record.

Remains on the form after saving.

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

Example:

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

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

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

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

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

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

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

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

Insert exitsafter creating a new record.

Update remains on the form, not exits.

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

Submit vs. Insert:

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

Insertexplicitly saves a record as a new entry.

Additional Notes:

Example Scenario in Incident Management:Action

Result

Click " Insert "

Creates anewIncident andexitsthe form.

Click " Update "

Saves changes to theexistingrecord andstays on the form.

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:

When setting adata policyin ServiceNow, it applies to all data entered into the platform, regardless of whether the data comes from:

UI Forms

Import Sets

Web Services (APIs, integrations, etc.)

Where Does the Data Policy Run?Data Policies Run on the Server-Side

Data policies enforcedata consistency and validationat theserver level.

Theyapply uniformly across all data entry points, ensuring that validation rules are enforced before storing data in the database.

A. Client →Incorrect

Data Policies donotrun on the client-side (browser).

Client ScriptsandUI Policieshandle client-side validation.

C. Browser →Incorrect

Data Policies donotoperate within the browser; theywork at the database levelon the server.

D. Network →Incorrect

ServiceNowdoes not enforce policies at the network layer; all validations occur on theapplication server (Server-Side Processing).

Why Other Options Are Incorrect?Key Differences Between Data Policies and Other Validation Methods:Validation Type

Runs On

Applies To

Purpose

Data Policy

Server

UI, Import Sets, Web Services

Enforces rules across all data sources

UI Policy

Client (Browser)

UI Forms

Dynamically changes form behavior

Client Script

Client (Browser)

UI Forms

Runs JavaScript in the user ' s browser

Business Rule

Server

Database Transactions

Executes logic when records are inserted, updated, or deleted

Data Policies Overview

Difference Between UI Policies and Data Policies

Official ServiceNow Documentation Reference:

ServiceNow providesfive primary rolesthat define access and permissions within the platform. These roles help structure user responsibilities and ensure that users only have access to the necessary functions.

Thehighest level of accessin ServiceNow.

Can manage all platform features, applications, data, and configurations.

Has control overusers, security settings, system properties, and scripting capabilities.

Example: A ServiceNow admin configuring new workflows, modifying tables, or setting up instance-wide settings.

Manages specific applications or functionalities within ServiceNow.

Includes roles such as:

knowledge_admin(Manages Knowledge Base)

report_admin(Manages Reports)

catalog_admin(Manages Service Catalog)

Example: A Knowledge Base Administrator controlling access to articles and updating knowledge categories.

Users with theITIL rolewho perform IT Service Management (ITSM) tasks.

Cancreate, update, and resolve recordssuch as incidents, problems, changes, and requests.

Example: A service desk agent handling incidents and requests.

Users with theApprover rolecanapprove or reject requests, such as change requests or access requests.

Can view or modify approval records directed to them but cannot fulfill other ITIL tasks.

Example: A manager approving a new software installation request.

Basic userswith no assigned roles.

Cansubmit requests, view their own tickets, and access public pages(e.g., Knowledge Base, Catalog).

Example: An employee submitting a request for laptop repair via the ServiceNow portal.

1. System Administrator (admin)2. Specialized Administrator3. Fulfiller (ITIL Role)4. Approver5. Requester (Employee Self-Service - ESS)

These roles form thefoundation of role-based access control (RBAC)in ServiceNow.

They ensure that usersonly access the data and functions relevant to their job responsibilities.

Additional roles can be assigned based on business needs, but these five cover the core platform functionalities.

Why These Are the Provided Roles in ServiceNow:

ServiceNow Documentation:User Roles in ServiceNow

CSA Exam Guide:CoversSystem Administrator, Specialized Administrator, Fulfiller, Approver, and Requesteras the standard user roles.

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

A. System Administrator, B. Specialized Administrator, C. Fulfiller, D. Approver, E. Requester

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

Local Database Authentication

This is the default authentication method used in ServiceNow.

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

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

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

LDAP (Lightweight Directory Access Protocol)

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

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

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

SSO (Single Sign-On)

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

ServiceNow supports various SSO protocols, including:

SAML 2.0 (Security Assertion Markup Language)

OAuth 2.0

OpenID Connect

Kerberos

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

A. XML feed–

XML feeds are used for data exchange,not authentication.

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

E. FTP authentication–

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

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

ServiceNow CSA Official Training Guide (User Authentication & Security)

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

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

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

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

Workflows ensure proper governance and content accuracy before publishing.

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

Example:

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

HR Knowledge Base is only available toHR employees.

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

Example:

IT KB Categories:Hardware, Software, Network.

HR KB Categories:Benefits, Policies, Payroll.

Different knowledge bases can have different owners or managers.

Example:

IT KB is managed byIT Support Team.

HR KB is managed byHR Admins.

ServiceNow allows multiple knowledge bases with distinct configurations.

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

This ensuresflexibility and proper governancein knowledge management.

ServiceNow Docs: Knowledge Management Overview

ServiceNow CSA Study Guide – Knowledge Base Administration

ServiceNow Product Documentation: Configuring Knowledge Bases

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

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

Displays multiple recordsfrom a table.

Columns represent fieldsof the table.

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

Common Actions:

Inline editing

Searching

Exporting data

Grouping and filtering

A. View

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

Example: Differentform viewscan be created for the same table.

B. Dashboard

ADashboardis a visual representation of reports and performance analytics.

It doesnot display raw table recordsdirectly.

C. Panel

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

Key Features of Lists:Why Other Options Are Incorrect?

Lists Overview

ServiceNow Lists Documentation

Personalizing Lists

List Personalization Guide

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

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

Single-Instance:

Each ServiceNow instance is aunique, independent environmentfor a customer.

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

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

Single-Tenant Model (Multi-Instance Architecture):

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

Thisensures data security, performance isolation, and customization flexibility.

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

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

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

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

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

ServiceNow does NOT use a multiple-tenant architecture.

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

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

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

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

ServiceNow Product Documentation – Multi-Instance Cloud Modelhttps://docs.servicenow.com

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

ServiceNow Best Practices – Security & Instance Architecture

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

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

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

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

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

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

A. Form–

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

It does not provide a multi-widget interface.

B. List–

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

D. Timeline–

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

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

ServiceNow CSA Official Training Guide (Reporting & Dashboards)

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

In ServiceNow’sService Catalog, variables are used to capture user input when they request catalog items. These variables allow for dynamic and customized data collection for different service requests.

Among the options provided, the three validvariable typesthat can be added to aService Catalog Itemare:

Multiple Choice:

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

Example: " What type of laptop do you need? " with options:MacBook, Windows Laptop, Chromebook.

Select Box:

Similar to Multiple Choice but presented in a drop-down format, making it useful when space needs to be conserved in a form.

Example: " Select your department " with a drop-down list ofIT, HR, Finance, etc.

Checkbox:

A simpleTrue/Falsevariable that allows users to check a box to indicate a selection.

Example: " Do you need an external monitor? " (Checkbox can be checked for ' Yes ' or left unchecked for ' No ' ).

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

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

Orderedisnot a valid Service Catalog variable type.

Option B (True/False, Checkbox, and Number List)

True/False is incorrect(ServiceNow uses " Checkbox " instead).

Number List is not a valid Service Catalog variable type.

Option C (Number List, Single Line Text, and Reference)

Number List is not a valid variable type.

Single Line Text and Reference are valid variables but were not all correct in this case.

ServiceNow Docs: Service Catalog Variableshttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogVariables.html

ServiceNow CSA Official Training Guide (Service Catalog & Request Management)

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

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

Access Control rules can be configured usingthree primary permission requirements:

Rolesdefine aset of permissionsassigned to users.

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

Example:

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

Conditional expressionsallow access based on a specified condition.

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

Example:

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

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

Scriptsallow advanced, custom logic to determine access.

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

Example:

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

CopyEdit

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

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

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

C. Assignment Rules(Incorrect)

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

They do not defineaccess control permissions.

E. User Criteria(Incorrect)

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

It isnot usedfor ACLs at the table/field level.

F. Groups(Incorrect)

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

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

Why Other Options Are Incorrect?

ServiceNow Product Documentation - Access Control Rules

Access Control Rules Overview

Defining Access Control Rules

ServiceNow Security Model

Role-Based Access

Scripted ACLs

References from ServiceNow CSA Documentation:

In ServiceNow, theService Catalogapplication allows administrators to create, configure, and manage catalog items that users can request. To create a new catalog item, administrators must access the correct module within theService Catalogapplication.

Maintain Categories (Option A)

This module is used to create and managecategorieswithin the Service Catalog.

Categories are used to organize catalog items into logical groups but do not allow the creation of actual catalog items.

Maintain Items (Option B)(Correct Answer)

This module is used tocreate, edit, and manage catalog itemsin the Service Catalog.

It provides options to define the item name, description, fields, workflows, and pricing details.

Administrators use this module when they want tobegin creating a new catalog item.

Content Items (Option C)

This module is related toContent Management System (CMS) and Knowledge Basebut is not used for creating standard Service Catalog items.

It allows administrators to create links to external content rather than actual requestable catalog items.

Items (Option D)

TheItemsmodule displays catalog items but does not allow an administrator to create new ones.

It is primarily forviewingitems rather than maintaining them.

Explanation of the Available Options:

The " Maintain Items " module is theonlymodule where administrators can create, edit, and manage catalog items in ServiceNow.

Other options either relate to categories, content management, or viewing existing items, making them incorrect choices.

Why is " B. Maintain Items " the Correct Answer?

ServiceNow Product Documentation - Service Catalog Administration🔗 https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/service-catalog-management/concept/service-catalog-management.html

ServiceNow CSA Exam Guide - Service Catalog & Request Fulfillment

ServiceNow Fundamentals Training - Creating and Managing Catalog Items

References from Official CSA Documentation:

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

ARecordis asingle instanceof data stored in a ServiceNowtable.

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

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

Example:

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

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

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

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

It is just a way tointeract with records.

D. Lists

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

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

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

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

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

There aretwo key componentsinvolved in event handling:

Event Registry

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

Defines which events can be triggered in the system.

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

Located in thesys_event_registrytable.

Event Log

A log ofactual generated eventsthat have occurred in the system.

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

Helps administrators track and troubleshoot event execution.

Stored in thesys_eventtable.

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

Event Registry = Defines possible events that can be triggered.

Event Log = Records actual events that have been triggered.

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

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

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

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

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

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

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

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

🔗 ServiceNow Event Management Documentation

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

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

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

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

https://docs.servicenow.com

ServiceNow Community: Best Practices for Flow Designer Triggers

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

In ServiceNow, afilter conditionconsists of three primary components:

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

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

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

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

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

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

Field:State

Operator:is

Value:New

A. Table–

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

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

ServiceNow Docs: Filtering Data in Lists and Reportshttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/use/using-lists/concept/filtering-lists.html

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

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

InServiceNow Service Catalog, anOrder Guideis a feature that allows users toorder multiple, related catalog items in a single request, simplifying the ordering process.

Helps usersrequest multiple items togetherinstead of submitting separate requests.

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

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

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

Purpose of an Order Guide:

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

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

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

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

Order Guides are forusers, not just administrators.

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

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

This is theprimary functionof an Order Guide.

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

Example:Employee Onboarding Order Guide

Laptop

Email account

VPN access

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

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

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

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

Explanation of Each Option:

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

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

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

Example Use Cases:

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

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

Additional Notes & Best Practices:

ServiceNow Docs: Order Guides Overview

https://docs.servicenow.com

ServiceNow Community: How to Configure an Order Guide

https://community.servicenow.com

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

https://docs.servicenow.com

ServiceNow Community: Best Practices for Dot-Walking

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

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

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

Ability toconfigure and customizethe platform.

Create, update, and deleterecords in any table.

Manage roles and users, including assigning roles to others.

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

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

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

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

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

In ServiceNowKnowledge Management, access to knowledge articles is controlled through access settings in theKnowledge Baserecord. The " Can Read " tab is used to specify which users, groups, or roles canview knowledge articlesin a particular Knowledge Base.

🔹 Why " Can Read " ?

TheCan Readlist defines theusers, groups, or roles that can access and view articlesin a specific Knowledge Base.

This ensures thatsensitive or restricted knowledge is only available to authorized users.

If no restrictions are set in theCan Readtab, the knowledge base ispublicly accessibleto all users.

🔹 Steps to Configure " Can Read " Permissions:

Navigate toKnowledge Management > Knowledge Bases.

Open a specificKnowledge Base record.

Go to theCan Readtab.

Add the users, groups, or roles that should be able to read the articles.

Save the record.

🔹 Incorrect Options Explained:

A. Access List– No such tab exists in Knowledge Management.

B. Can Access– Incorrect name; the correct tab isCan Read.

C. Accessible to– Does not exist in the Knowledge Base settings.

📌 Reference:

ServiceNow Knowledge Management User Roles

Managing Knowledge Base Access

Knowledge Management (KM)in ServiceNow is the process that enables users tocreate, categorize, review, approve, and browse important informationin acentralized repositorythat is shared across the organization.

Key Features of Knowledge Management:Centralized knowledge basefor storing important information.

Categorization and taggingfor easy search and retrieval.

Approval workflowsto ensure content accuracy.

Role-based access control(User Criteria) for managing visibility.

Integration with Self-Service and Service Catalogfor user assistance.

Example Use Case:A company’sIT support teamdocuments solutions to common IT issues. Employees cansearch the Knowledge Basefor solutions before opening a ticket, reducing the number of support requests.

A. Self-Service Management →Incorrect

Self-Serviceallows users to submit requests and incidents but doesnot manage knowledge articlessystematically.

C. Knowledge-Centered Management →Incorrect

No such term as " Knowledge-Centered Management " in ServiceNow.

The correct industry term isKnowledge-Centered Service (KCS), but ServiceNow usesKnowledge Management (KM).

D. Information Portal Management →Incorrect

No such concept in ServiceNow; portals provide UI access but do not manage structured knowledge bases.

E. Business Information Management →Incorrect

Business Information Management (BIM)focuses onbusiness data strategy, notknowledge sharing.

Why Other Options Are Incorrect?

Knowledge Management Overview

Creating and Managing Knowledge Articles

Official ServiceNow Documentation Reference:

In ServiceNow, theDictionaryis the component that definesevery table and fieldin the system.

Itstores metadataabout every table and field.

It contains details likedata type, field properties, default values, and relationships.

It is managed through thesys_dictionarytable.

If you navigate toSystem Definition > Dictionary, you can view and edit field properties for any table.

The Dictionary defineswhether a field is mandatory, read-only, or referenceable.

A. Data Atlas– Not a valid ServiceNow concept.

B. Table Class Manager– Managestable extensions and inheritance, but does not define individual fields.

C. Schema– Refers to theoverall structure of a database, but in ServiceNow, theDictionarymanages table and field definitions.

E. Field Map– Used fordata imports and transformations, not for defining tables and fields system-wide.

ServiceNow Dictionary Overview

ServiceNow CSA Training Module: " Understanding Tables and Fields "

What is the Dictionary in ServiceNow?Example:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

When designing Service Catalog items,Variable Setsallow you toreuse common fields across multiple catalog items.

Instead ofcreating the same four fields(Requested for, Requested by, Approving manager, Delivery instructions)80 times,

You candefine them once in a Variable Setand apply it to all catalog items.

Best Approach (Correct Answer: A)Advantages of Using a Variable Set:Reusability– The same Variable Set can be added to multiple catalog items.

Consistency– Ensures the four mandatory fields are always included.

Easier Maintenance– Changes to these fields only need to be made inone place.

B. Create a Record Producer that contains the four fields →Incorrect

ARecord Produceris used to create records in a specific table (e.g., Incident, Request, Change).

It isnot designed for defining reusable fieldsacross multiple catalog items.

C. Create a Flow Designer Action with Variable Set Data Pill →Incorrect

Flow Designeris for process automation, not fordefining form variables.

It does not allow you to create reusable fields for catalog item forms.

D. Create an Order Guide and hide variables as needed →Incorrect

Order Guidesare used for ordering multiple catalog items together.

They do not provide a structured way to manage common fields across different catalog items.

E. Create a Variable Set Template →Incorrect

There is no concept of a " Variable Set Template " in ServiceNow.

Variable Setsthemselves act as templates.

Why Other Options Are Incorrect?

Using Variable Sets in Service Catalog

Building Service Catalog Forms

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:

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

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

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

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

Modify high-security settingsin ServiceNow.

Elevate privilegesto make changes to sensitive security configurations.

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

Users with theadminrole alonecannot modify high-security settings.

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

This ensures thatonly authorized administratorscan modify security-related configurations.

B. sn_ad_admin– No such role exists in ServiceNow.

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

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

ServiceNow Security Admin Role and Elevated Privileges

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

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

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.

InServiceNow, theFavoritesfeature allows users to quickly access frequently used modules, applications, or records. Users can customizeFavoritesby changing theicon and color.

To edit a favorite, you need to:

Open theApplication Navigator.

Locate yourFavoriteslist.

Click thePencil (✏) iconnext to the favorite you want to edit.

Choose a newicon and color.

Save the changes.

A. Star

TheStar iconis used toaddorremovea favorite butnotfor editing.

B. Triangle

NoTriangle iconis used for Favorites customization.

D. Clock

TheClock iconrepresentsrecently viewed items, not Favorite customization.

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

Assignment Rulesin ServiceNow automaticallyassign tasks(such as incidents, service requests, or change requests) to theappropriate group or individualbased on predefined criteria.

Acritical, high-priority service requestis created.

TheAssignment Rulechecks conditions (e.g., priority, category, requester, etc.).

The systemassignsthe request to the correctassignment group or individual.

How Assignment Rules Work:Example Scenario:

If an incident isPriority 1 (P1)and the category isNetwork, an assignment rule canautomatically route it to the " Network Support " group.

A. User Policy

No such feature exists in ServiceNow for task assignments.

B. UI Policy

UI Policies controlform behavior (visibility, field conditions, etc.), not assignment logic.

C. Predictive Intelligence

Predictive Intelligence usesmachine learningto suggest assignments, butAssignment Rulesare the primary mechanism for automatic task allocation.

When importingspreadsheet datainto ServiceNow, thefirst stepis toDefine a Data Source.

AData Sourcedefineswhere the data is coming from(e.g., Excel, CSV, JDBC connection).

It establishes theformatandstructureof the incoming data before it can be processed by anImport Set.

Without defining theData Source, the system does not know how to handle the incoming data.

Define Data Source– Identify where the data is coming from.

Create Import Set– Temporarily store the imported data.

Set Coalesce– Define unique identifiers to prevent duplicate records.

Transform Data– Map fields to the target table.

Run the Import– Move data into the actual ServiceNow tables.

A. Create Import Set– Import Sets store the data, but they are createdafterdefining the data source.

B. Run Data Scrubber– No such step exists in ServiceNow ' s import process.

C. Set Coalesce– Coalescing ensuresno duplicate records, but it happensafter data is loaded into the import set.

E. Select Import Set– The Import Set is selected after defining the data source and loading the data.

ServiceNow Data Import Process

ServiceNow CSA Training Module: " Importing Data into ServiceNow "

Why Defining a Data Source is the First Step?Steps in the Data Import Process:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

To filter records in alist view, users can:

Click on thefilter icon.

Applyconditionsto refine the displayed records.

Scripts that run in thebrowser (client-side)help controlUI behavior, form validation, and field interactionsin real-time without needing a server request.

Types of Client-Side Scripts in ServiceNow:Client Scripts

Run directly in the user ' s browser.

Used for form validation, auto-populating fields, or UI interactions.

Example:

javascript

CopyEdit

functiononLoad() {

g_form.setValue( ' priority ' , ' 2 ' );

}

UI Policies

Controlfield visibility, mandatory status, and read-only statedynamically.

Example: Ifcategory = Hardware, makeSerial Number field mandatory.

B. Access Control Scripts →Incorrect

Access Control Lists (ACLs)runserver-side, not in the browser.

C. Script Includes →Incorrect

Script Includesrunserver-sideand are used for reusable functions and API logic.

D. Business Rules →Incorrect

Business Rulesalso run on theserver, not in the browser.

Why Other Options Are Incorrect?

Client Scripts Overview

UI Policies in ServiceNow

Official ServiceNow Documentation Reference:

Table Builderis a feature in ServiceNow that allows administrators tomanage table structures, relationships, and configurations.

The " Additional Actions " menu includes options such ascreating database indexes, which improve query performance.

Explanation of Incorrect Options:

Duplicate the selected form view (A)→ Form views are configured separately and not via Table Builder.

Add a new module (B)→ Modules are added in the Application Navigator,not Table Builder.

Schedule a job (D)→ Jobs are created in theSystem Scheduler, not Table Builder.

In ServiceNow, theHelp Panel(represented by thequestion mark icon) is an integrated resource that provides guidance for users. It offersguided tours,action instructions, and information on usinginputs and outputswithin the platform.

Guided Tours: Step-by-step walkthroughs for users to get acquainted with ServiceNow features and processes.

Instructions for Inputs/Outputs: Provides help and clarification on how to use input fields, buttons, and other interactive elements in the interface.

Access to Information: Offers contextual help for specific actions or modules within ServiceNow.

Features of the Help Panel:This makes it the most efficient resource for users needingon-the-spot assistanceas they interact with the platform.

A. Community– TheCommunityis a forum where users can discuss issues, share knowledge, and ask questions but is not directly related to in-context help or guided tours.

C. Docs– ServiceNow documentation providesin-depth guidesand best practices but is not built into the user interface for in-context help and guided tours.

D. Wiki– Similar to Docs, theWikiis more of a knowledge repository but does not provide interactive, contextual guidance in the instance.

ServiceNow Help Panel Usage

ServiceNow CSA Training Module: " User Experience: Help Panel and Guided Tours "

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

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

Navigation:System Definition > Tables & Columns

Allows admins tocreate and modify tables, including:

Adding columns (fields)

Setting relationships

Defining attributes

Navigation:System Definition > Tables

A simpler interface for creating tableswithout managing columns immediately.

B. Schema Map →Incorrect

Schema Mapvisualizestable relationships but does not allow table creation.

C. Dictionary →Incorrect

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

Creating Tables in ServiceNow

Understanding Tables & Columns

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

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

Dot Walkingis a ServiceNow feature that allows you to access and includedata from related tableswhen creating reports, conditions, scripts, and business rules.

When working with records, each table has fields that may reference another table (e.g., anIncidentrecord has an " Opened by " field that references theUsertable).

Dot Walkingallows you to traverse these relationships by using adot (.) notationto pull in data from related tables.

Example: If you want toinclude the email address of the user who created an incident, you can reference it as:

How Dot Walking Works:CopyEdit

incident.opened_by.email

This is useful forreportingwhen you need to include data from multiple related tables without needing custom joins.

A. SQL→ Incorrect. ServiceNow does not use direct SQL queries for reports. It relies on GlideRecord and Dot Walking instead.

C. Outer Join→ Incorrect. ServiceNow does not provide traditional SQL joins for reports. Instead, it usesDot Walking and Database Views.

D. Joins→ Incorrect. While Database Views allow for joins,Dot Walking is the primary method used to include related table data in reports.

In ServiceNow, anUpdate Setis a mechanism used to package and transfer customizations from one instance to another. TheDefault Update Setis automatically created for every instance and captures all unassigned configuration changes. However, it is considered abest practice not to use the Default Update Set for moving customizations between instances.

Lack of Organization & Traceability

The Default Update Set collects all modifications automatically, making it difficult to track specific changes related to a particular project or feature.

If multiple administrators or developers work in an instance, their changes will all be mixed together in the Default Update Set, leading to confusion and conflicts.

Risk of Losing Changes

Default Update Sets are not automaticallycomplete. Since users can forget to mark their customizations explicitly for an update set, some changes might not get captured.

If a system admin forgets to move a customization into a named update set, those changes may not be included in the migration process.

Cannot Be Moved Between Instances

The Default Update Setcannot be retrieved or movedbetween instances because it is system-managed. This makes itimpossibleto use it for transferring customizations effectively.

Named Update Sets, on the other hand, allow developers to package only the required changes for controlled migration.

Best Practice: Use Named Update Sets

It is highly recommended to create anamed Update Set(e.g., " Incident_Enhancements_Q1_2025 " ) for each set of related changes.

This provides a structured way to track, test, and promote configurations fromdevelopment → test → production environmentsin a controlled manner.

A. Merge Default Update Sets before moving between instancesIncorrect – The Default Update Set cannot be moved between instances, so merging it would not serve any purpose.

B. Submit Default Update Set to Application RepositoryIncorrect – The Application Repository is used forScoped Applications, not for update sets. The Default Update Set is system-managed and should not be used for structured deployments.

D. Keep Default Update Set to a maximum of 20 records, for troubleshooting purposesIncorrect – While keeping the Default Update Set small might be useful for tracking small changes, there is no such best practice limit of " 20 records. " It is still not recommended for migrations.

ServiceNow Product Documentation – Update Sets Best Practices📖 Update Set Best Practices

ServiceNow Community Best Practices – Managing Update Sets📖 Managing Update Sets

Reasons Why You Should Not Use the Default Update Set for Moving Between Instances:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. You should not use the Default Update Set for moving between instances.The best practice is to always createnamed Update Setsto ensure controlled, traceable, and reliable migrations of customizations between ServiceNow instances.

In ServiceNow, toimport articlesinto aKnowledge Base (KB), a user must have thesn_knowledge_importrole.

sn_knowledge_import→ Required to import articles into a knowledge base.

sn_knowledge_contribute→ Allows users tocreate, edit, and publishknowledge articles butnot importthem.

sn_knowledge_admin→ Grantsfull administrative accessto manage the knowledge base, including permissions, categories, and workflows.

B. sn_knowledge_contribute– This role allowscontributing and editing articlesbut doesnot grant import capabilities.

C. Can contribute– Not a valid ServiceNow role; the correct role issn_knowledge_contribute.

D. Can import– Not a recognized role in ServiceNow. The correct role issn_knowledge_import.

ServiceNow Knowledge Management Roles

ServiceNow CSA Training Module: " Managing Knowledge Bases and Importing Articles "

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

InServiceNow Flow Designer, aflowis an automated process that consists of actions, conditions, and triggers.Two key componentsdetermine when a flow should run:

Trigger

Defineswhenthe flow should execute.

Examples:

When arecord is created/updated/deleted.

When anAPI call is received.

On ascheduled basis.

Condition

Specifiesadditional criteriathat must be met for the flow to proceed.

Examples:

If thepriority is High.

If thestatus is Resolved.

Aflowis designed tosend an email notificationwhen ahigh-priority incident is assigned.

Trigger: " Incident table → When a record is updated. "

Condition: " Priority = High AND State = Assigned. "

A. Trigger and Condition Pill

No such term as " Condition Pill " exists in Flow Designer.

B. Scope and Trigger Condition

" Scope " defines theapplication boundary, not when a flow runs.

D. Trigger Criteria and Clock

" Clock " is not usedfor defining flow execution.

E. Condition and Table

Atable does not define when a flow runs; it only stores records.

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

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

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

AfterExecutes after a record has been committed to the database.

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

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

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

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

Used topopulateg_scratchpadfor client-side scripts.

The Four Timing Options for Business Rules:

Example Use Cases for Business Rule Timings:Business Rule Timing

When It Runs

Use Case

Before

Before saving to the database

Validate data, auto-populate fields

After

After saving to the database

Send notifications, update related records

Async

Shortly after the transaction completes

Call an external API, send an email

Display

Before the form loads

Pass server data to client-side scripts (g_scratchpad)

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

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

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

Incorrect Answer Choices Analysis:

ServiceNow Docs – Business Rules Overview📖 Understanding Business Rules

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

Official ServiceNow Documentation References:

InServiceNow Knowledge Management,User Criteriais used to control access toknowledge bases (KBs)andarticlesbased on user attributes such ascompany, department, group, and roles.

Understanding the Given Criteria:Criteria

Value

Companies

ACME North America

Department

HR

Groups

ACME Manager

Match All

Yes

TheMatch All: Yessetting means thatonly users who meet ALL the specified criteriawill have access.

Who Gets Access?Users must be:

Amember of the ACME Manager group

Part of the HR department

An employee of ACME North America

B. Employees of ACME North America, who are members of HR Department or the ACME Manager group →Incorrect

The " OR " conditionis incorrect becauseMatch All: Yesrequires users to meetALL conditions.

C. Users which are members of either ACME North America, or HR Department, or ACME Manager Group →Incorrect

Again,Match All: Yesmeans usersmust meet all criteria, not just one.

D. Member of the ACME Manager group, and HR department, regardless of geography →Incorrect

Company (ACME North America) is part of the criteria, so itcannot be ignored.

Why Other Options Are Incorrect?

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Official ServiceNow Documentation Reference:

✔Visual Task Boards (VTB)provide aKanban-style interfacefor tracking and managing tasks visually. Users can:

Create personal or team boardsto manage tasks.

Drag and drop task cardsbetween different lanes (e.g., " To Do, " " In Progress, " " Completed " ).

Filter and categorize workdynamically.

Types of Visual Task Boards:

Freeform Boards– Simple personal boards for organizing work.

Guided Boards– Based on ServiceNow lists and automatically updated.

Flexible Boards– A mix of Freeform and Guided boards.

Option B (Service Desk)is incorrect because it refers to theService Desk applicationfor handling incidents and tickets.

Option C (Virtual Agent Homepage)is incorrect because it is used forchatbot interactions, not task management.

Option D (Personal Task Tracker)is incorrect because there is no such feature in ServiceNow.

📌 Reference:ServiceNow Visual Task Boards (VTB) Documentation

✔Access Control Lists (ACLs)in ServiceNow definewho can read, write, create, or delete recordsin the system. ACLs apply to tables, fields, and UI elements.

Option A (Role Assignment Rules)is incorrect because rolesgrantaccess but do not define granular security controls.

Option B (Scripted User Rules)is incorrect because there is no such feature in ServiceNow.

Option C (CRUD Rules)is incorrect becauseCRUD (Create, Read, Update, Delete) permissionsare enforced through ACLs.

Option D (User Authentication Rules)is incorrect because authentication rules controllogin access, not data access.

📌 Reference:ServiceNow Security & Access Control – ACLs & Security Rules

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

Enablesautomated testing of ServiceNow applicationswithout manual effort.

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

SupportsUI testingfor forms, lists, and portals.

Reduces testing time and enhancesrelease reliability.

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

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

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

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

A. Selenium →Incorrect

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

ATF is thepreferredtesting framework for ServiceNow applications.

B. Test Driven Framework (TDF) →Incorrect

No such frameworkcalled " Test Driven Framework " in ServiceNow.

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

C. JUnit →Incorrect

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

ServiceNow scripts useJavaScript, not Java.

Why Other Options Are Incorrect?

Automated Test Framework (ATF)

Official ServiceNow Documentation Reference:

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

(A) Breadcrumb – Incorrect

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

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

(B) Favorite – Correct

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

Users canadd, remove, and reorderfavorites for better personalization.

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

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

(C) Tag – Incorrect

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

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

(D) Bookmark – Incorrect

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

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

Explanation of Each Option:

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

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

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

ServiceNow Docs: Using Favorites in the Application Navigator

https://docs.servicenow.com

ServiceNow Community: Personalizing the Application Navigator with Favorites

https://community.servicenow.com

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

To ensure data consistency across the entire ServiceNow platform, developers use Data Policies .

1. The Scope of Data Policies:

Data Policies enforce requirements on data payload at the database engine level (server-side). Because they operate at this deep layer, they act as a universal gatekeeper. It does not matter if a user types the data into a browser UI Form, if the data is bulk-loaded via an Import Set, or if it is pushed in via a REST/SOAP Web Service API—the Data Policy will evaluate the data. If the data fails the policy (for example, a mandatory field is missing), the database will reject the insert or update.

2. Comparison to UI Policies:

This is the critical distinction developers must know. UI Policies only run on the client-side (in the browser). If you make a field mandatory with a UI policy, a user on the form cannot submit it. However, an external API could easily bypass that UI Policy and insert a blank record. A Data Policy prevents that bypass.

3. Why the other options are incorrect:

B, C, and D: " Write Policies, " " Data Integrity Policies, " and " Data Submission Policies " are not standard ServiceNow platform features or terminology.

InServiceNow’s Configuration Management Database (CMDB), thecmdbtable is thebase tablefrom which allConfiguration Item (CI) tablesinherit.

cmdbis the Parent Table of All CMDB-Related Tables

Thecmdbtablecontainsbasic attributesshared by allConfiguration Items (CIs).

Every CI in ServiceNowinherits fromcmdbor one of its child tables.

Hierarchy of CMDB Tables in ServiceNow:

cmdb(Base Table)→ Stores general CI data.

cmdb_ci(Stores specific CI details)→ Extendscmdbto storedevices, applications, and services.

cmdb_rel_ci(Stores relationships between CIs)→ Used totrack dependencies.

Why iscmdbthe Correct Answer?

A.cmdb_dIncorrect– No such standard table exists in ServiceNow’s CMDB.

B.ucmdbIncorrect–uCMDB (Universal CMDB)is anHP product, not part of ServiceNow’s CMDB.

C.cmdb_rel_ciIncorrect–This table stores CI relationships, but it isnot the base table.

Incorrect Answer Choices Analysis:

ServiceNow Docs – CMDB Core Tables📖 CMDB Table Structure

ServiceNow Docs – CMDB Best Practices

Official ServiceNow Documentation References:

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.

In ServiceNow,High Security Settingsrequireelevating privilegesto make changes. Administrators need toelevate to the security_admin roleto access and modify sensitive settings.

A. Select Elevate Roles

Admins must go toUser Menu (top-right corner) > Elevate Roles.

Selectsecurity_admin, then clickOKto temporarily gainelevated privileges.

This allows access toHigh Security Settings, including ACLs and security configurations.

B. Add security_admin role to your user account

Only anexisting admin with security_admincan grant this role.

Even if a user hassecurity_admin, they still need toelevateto access high-security settings.

C. Impersonate Security Admin

Impersonation does not work for security_admin.

Users mustelevatetheir own privileges instead.

D. Use System Administrator < Elevate Roles module

There isno module named " Elevate Roles " under System Administrator.

Elevation is done via theUser Menu (top-right corner of ServiceNow UI).

TheActivity Stream icon (Live Feed)allows users tomonitor real-time updateson records assigned to them. This is particularly useful for task workers who need to trackcustomer responses, status changes, and work progresswithout manually refreshing records.

Navigate toMy Work List(or any list view showing assigned tasks).

Click theActivity Stream (Live Updates) iconat the top of the list.

Areal-time updates frameappears, showing all changes to the listed records.

A. Open an Agent Workspace tab for each record he wants to monitor

WhileAgent Workspaceoffers real-time updates, opening multiple tabs isinefficient and unnecessarywhen live updates can be monitored in a single stream.

B. Select Service Desk > My Work Dashboard

TheMy Work Dashboardprovides an overview of assigned tasks butdoes not show live updates.

C. Click on the eyeglass icon to expand the Monitor frame

There isno " eyeglass icon " used for monitoring updates in ServiceNow.

To display reminder messages or alerts to users as they interact with forms in ServiceNow, Client Scripts are used. Specifically, an onSubmit Client Script can be configured to display a message or perform validation just before the form is submitted by the user. This script runs on the client (browser) and can prevent submission or prompt the user with informational messages.

Business Rules execute on the server and cannot directly interact with the user interface in real-time. Policies and Data Policies enforce data consistency but do not provide user messages or reminders during form submission.

Therefore, the Client Script is the correct mechanism to display a reminder message dynamically as the incident is submitted.

When an administrator sets apolicy(such asData Policies) that applies toall data entered into ServiceNow, it runs on theserver-side.

Why Data Policies Run on the Server?Data Policies apply to all data sources:

UI forms

Import Sets

Web Services (APIs, integrations)

Enforces field validation at the database level

Ensuresdata consistencyacrossall entry points.

Reducesclient-side dependencyfor validation.

Applies uniformly regardless of how the data is entered

UnlikeUI Policies(which only work on forms),Data Policiesensure field rules are enforcedeverywhere.

A. Network →Incorrect

Policies are not enforced at thenetwork level.

They operate within theServiceNow application.

C. Client →Incorrect

Client-side scripts (likeUI Policies or Client Scripts)onlyenforce validation within the browser.

Data Policies run at the server level, ensuring broader enforcement.

D. Browser →Incorrect

While UI Policies and Client Scripts run in the browser,Data Policies are applied on the server.

Why Other Options Are Incorrect?

Key Differences Between Client and Server Processing:Validation Type

Runs On

Applies To

Purpose

Data Policies

Server

UI, Import Sets, Web Services

Ensures global data consistency

UI Policies

Client (Browser)

Forms (User Interface)

Controls form behavior dynamically

Client Scripts

Client (Browser)

Forms, Fields

Runs JavaScript in the user ' s browser

Business Rules

Server

Database Transactions

Executes logic when records are inserted, updated, or deleted

Data Policies in ServiceNow

UI Policies vs. Data Policies

Official ServiceNow Documentation Reference:

TheVirtual Agentin ServiceNow provides a conversational messaging interface that allows users to interact with the system via chatbots. One of its key capabilities is deliveringknowledge articlesin response to user queries, enhancing self-service support.

🔹 Why Virtual Agent?

Virtual Agent usesNatural Language Understanding (NLU)to understand user questions and deliverknowledge articlesas part of its automated responses.

It can interact throughServiceNow’s messaging interfaceslike Microsoft Teams, Slack, and Service Portal chat.

Virtual Agent integrates with theKnowledge Managementsystem, providing users with relevant knowledge articles based on their inquiries.

🔹 Incorrect Options Explained:

A. Agent Assist– This feature helps support agents by recommending knowledge articlesinside agent workspacesbut is not aconversational interfacefor end-users.

C. Now Messenger– This does not exist as a ServiceNow product or feature.

D. Connect Agent– There is no specific feature called " Connect Agent " in ServiceNow.Connect Chatis a real-time messaging tool but does not provide automatic knowledge articles.

📌 Reference:

Virtual Agent Overview – ServiceNow Docs

Virtual Agent and Knowledge Integration

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

ServiceNow Learning – Flow Designer and Automation Best Practices

ServiceNow Developer Portal – Flow Designer Action Configuration

References from Certified System Administrator (CSA) Documentation:

InServiceNow, you can add additional fields to a form using either:

Form Layout(for quick field additions)

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

Context Menu > Configure > Form Layout (B)

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

Used when only minor modifications are needed.

Context Menu > Configure > Form Design (C)

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

Allows users torearrange fields, sections, and tabseasily.

A. Context Menu > Form > Layout(Incorrect)

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

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

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

E. Context Menu > Form > Designer(Incorrect)

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

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

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

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

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

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

In ServiceNow,list filtersallow users to define and apply specific conditions to refine data displayed in a list view. If an administrator or user wants to make alist filter available to everyone, they need to:

Assign a Name→ The filter must be named so users can identify and reuse it.

Set Visibility→ The filter’s visibility needs to be adjusted to“Everyone”, a specificgroup, or anindividual user.

Save→ The filter must be saved for it to be accessible in future sessions.

Apply a filterin a list view using the filter conditions.

Click theSavebutton.

Provide anamefor the filter.

UnderVisibility, select one of the following:

Me (Private)→ Only the creator can use the filter.

Everyone (Public)→ All users can access the filter.

Group→ Assign the filter to a specific group.

ClickSaveto store the filter.

Steps to Make a List Filter Available to Everyone:

Why " B. Assign a Name, Set Visibility, and Save " is Correct:Assign a Name→ The filter needs an identifiable name for users.

Set Visibility→ Determines whethereveryone, a group, or just the creatorcan see the filter.

Save→ Saves the filter for future use.

A. Make active, set visibility, and save→Filters do not have an " Active " state; they just need to be saved with the correct visibility settings.

C. Assign a group, set visibility, and save→Assigning a group isoptionalbut does not apply to everyone.

D. Make active, assign a name, and save→ " Make active " is not required; visibility settings control availability.

Why Other Options Are Incorrect:

ServiceNow Documentation:Creating and Sharing List Filters

CSA Exam Guide:CoversList Filters and visibility settings.

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

B. Assign a Name, Set Visibility, and Save

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:

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

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

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

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

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

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

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

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

ACLs do not manageworkflowsor directly control group assignments.

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

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

D. security_admin(Incorrect)

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

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

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

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

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

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

Approvals

Task creation

Notifications

Record operations(such as updating or deleting records)

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

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

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

B. Action Sequences(Incorrect)

No such term exists in ServiceNow.

C. Action Sets(Incorrect)

No such feature exists in ServiceNow.

D. Task Flows(Incorrect)

This is not a term used in ServiceNow automation.

E. Flow Diagrams(Incorrect)

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

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

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

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

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

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

Verify Update Set is Complete

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

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

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

Retrieve Update Set

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

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

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

Preview Update Set

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

Click " Preview Update Set " to initiate validation.

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

Commit Update Set

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

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

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

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

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

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

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

ServiceNow CSA Official Documentation– Update Set Management

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

ServiceNow Community Best Practices on Update Sets

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

ServiceNow Learning Portal - Admin Fundamentals

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

References from Certified System Administrator (CSA) Documentation:

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

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:

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

Navigate to:System Notification > Email > Notifications

ClickNewto create a new notification.

Configure the notification with the following:

Name: " Network Outage Notification "

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

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

Who Will Receive:Specifyaffected users.

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

Save and test the notification.

Notifications are managed in System Notification.

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

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

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

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

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

Creating and Managing Email Notifications in ServiceNow:ServiceNow Docs

ServiceNow Notification Configuration Guide

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

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.

InServiceNow Flow Designer, adata pillrepresentsvariables, record fields, or outputs from previous stepsthat can be used dynamically in the flow.

Data pillsallow flow designers to referencerecord datawithout manually specifying table fields.

Dragging a data pillonto a flow step ensures that the correct values areautomatically mappedfrom the referenced record.

This is the recommended method for using record datawithin a flow.

Why is Option D Correct?

Why Are the Other Options Incorrect?A. Drag the table icon onto the flow definition

IncorrectbecauseFlow Designer does not use table iconsfor referencing records.

Instead, it utilizesdata pills and actionsto retrieve and manipulate record data.

B. Use the condition builder to specify the desired values

Incorrectbecause thecondition builderis used fordecision logic(e.g., If-Else conditions), not for referencing record data.

C. Specify the source table on the data pill related list

Incorrectbecause youcannot manually specifya table in a data pill.

Data pills areautomatically createdwhen an action retrieves data from a record.

E. Add the table reference using the slush bucket

Incorrectbecauseslush bucketsare used in ServiceNow for selecting multiple items (e.g., roles, groups),not for referencing record data in a flow.

ServiceNow Flow Designer - Using Data Pills

ServiceNow Flow Designer - Best Practices for Record Referencing

ServiceNow ITSM - Automating Workflows with Flow Designer

References to Official Certified System Administrator (CSA) Documentation:

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

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

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

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

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

Function fields aredesigned specifically for calculations and data transformationsin reports.

They allowadvanced data processing without requiring scripting.

A. Sourcing Fields→Incorrect

" Sourcing Fields " isnot a valid termin ServiceNow reporting.

C. Computational Fields→Incorrect

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

D. Calculation Fields→Incorrect

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

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

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

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

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

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

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:

TheFilter Navigatorin theApplication Navigatoris a powerful search tool inServiceNowthat allows users toquickly find applications and modulesby typing keywords instead of manually browsing through the navigation menu.

Quick Navigation:

Users can type thename of an application or moduleto locate it instantly.

Example: Typing " incident " in the Filter Navigator will show links to " Create New Incident, " " All Incidents, " " Open Incidents, " etc.

Dynamic Filtering:

The list of applications and modulesdynamically updatesas you type.

Helps users findrelevant sectionswithout scrolling through the full menu.

Keyboard Navigation Support:

Users canuse the keyboard (arrow keys and Enter)to navigate through the filtered results.

Time-Saving Feature:

Reduces the need toexpand and collapse menus manually.

Especially useful fornew users or users working across multiple modules.

Key Functions of the Filter Navigator:Why Option B is Correct?The Filter Navigator is specifically designed to help users quickly search and navigate to applications and modules.

Why Other Options Are Incorrect?A. Filter applications in order of use→ Incorrect

The Filter Navigatordoes not sort applications by usage; it simply filters based on text input.

C. Collapse and expand applications→ Incorrect

Expanding/collapsing applications is donemanually, but the Filter Navigator is purely forsearching and filtering.

D. List applications in order of Top Requests→ Incorrect

The Filter Navigatordoes not rank applicationsby usage or requests. It onlyfiltersbased on search input.

ServiceNow Docs – Using the Filter Navigatorhttps://docs.servicenow.com

ServiceNow Learning – Application Navigator and UI Features

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 Overview:https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/knowledge-management/reference/r_KnowledgeWorkflows.html

ServiceNow Knowledge Management Process:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/knowledge-management/concept/knowledge-management-overview.html

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official 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 Buttonshttps://docs.servicenow.com

ServiceNow Learning – Creating and Editing Records

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

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,UI Actionsare used toadd buttons, links, and context menu itemson forms and lists to enhance user interaction.

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

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

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

Examples of UI Actions include:

Submit, Update, and Deletebuttons on forms.

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

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

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

B. UI Settings:No such module in ServiceNow.

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

UI Actions Overview:ServiceNow Docs

Configuring UI Actions for Forms and Lists

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Filter Condition:PriorityisHigh

Field:Priority

Operator:is

Value:High

Another Example:Stateis notResolved

Field:State

Operator:is not

Value:Resolved

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

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

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

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

ServiceNow Docs – Creating and Applying Filtershttps://docs.servicenow.com

ServiceNow Learning – Query Builder and Conditions

ServiceNow Best Practices – Using Filters in Lists and Reports

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Access Control Rules (ACLs)determine who cancreate, read, write, delete, or executerecords within a table. Each ACL rule evaluates three main permission requirements,all of which must be truefor the rule to apply. These requirements are:

TheConditions fieldin an ACL specifies predefined logic that must be met for the rule to apply.

Example: An ACL might specify that a record is only accessible if theStatefield is set to " Open " .

Conditions areevaluated firstbefore checking roles or scripts.

ACLs can berestricted to users with specific roles.

If a user does not have the required role(s), the ACL denies access.

Example: Only users with the " itil " role can edit incidents.

If the ACL does not specify any role, all users may be eligible based on conditions and script evaluations.

ACL scripts provideadvanced conditional logicusingserver-side JavaScript.

Scripts allow complex rule evaluation, such as checking whether a user is the record’s creator.

Example: A script could restrict access to records wherecurrent.requested_for == gs.getUserID()(only allow users to see their own requests).

If a script is present in an ACL, it must returntruefor access to be granted.

Access control rules are only granted when all three evaluations return true.

Conditions act asfilters.

Roles definepermissions based on user roles.

Scripts allowadvanced access logic.

1. Conditions (A - Correct Answer)2. Roles (C - Correct Answer)3. Script (D - Correct Answer)Why " A. Conditions, " " C. Roles, " and " D. Script " are the Correct Answers?

B. Table – Incorrect

Access control appliesto specific tables, but defining a table itself is not one of the permission checks.

E. Table. " – Incorrect

This is anincorrectly formatted optionand does not relate to access control evaluation.

F. Table.none – Incorrect

" Table.none " is not an evaluation factor in ACLs. Access control applies totable-level, field-level, and record-level, but " table.none " is not an access requirement.

Explanation of Incorrect Options:

ServiceNow Docs: Access Control Rules (ACLs) Overview

ServiceNow CSA Study Guide – Security and Access Control

ServiceNow Product Documentation: Evaluating ACLs and Permissions

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,User Criteriais thebest methodfor controllingwho can see or request catalog items. To ensure that onlyHR Department Managerscan view the service catalog item, we need to applyUser Criteriaby adding theDepartment Manager group.

Navigate toService Catalog > Catalog Items.

Open the specific catalog item.

Scroll down to theAvailable Forsection.

ClickEditand selectUser Criteria.

Add theDepartment Manager group.

Save the changes.

Steps to Restrict Catalog Item Visibility Using User Criteria:🔹 Effect:Only users in theDepartment Manager groupwill be able to see and request this catalog item.

Incorrect Answer Choices Explanation:A. Specify the Dept_Mgr role on the catalog content block

Rolescontrol system permissions but are not used tofilter visibilityof catalog items.

C. Add the Department Manager group to the catalog item’s ACL

Access Control Lists (ACLs)restrict who canmodifya catalog item but do not control visibility.

D. Only publish the item in the HR service catalog

Publishing an item in a specificcatalogdoes not restrict access to a specificuser group.

E. Use a Dept_Mgr ACL on the HR service catalog

ACLs arenot the correct approachfor managing catalog item visibility;User Criteriais the best practice.

ServiceNow User Criteria for Service Catalog

Restricting Access to Service Catalog Items

Official CSA Documentation Reference:

InServiceNow, anEventis a system-generatednotificationthatindicates an occurrence within the platform. Events are triggered automatically or manually whenspecific conditionsare met and can be used to initiatenotifications, business rules, workflows, or integrations.

Events Indicate That Something Has Happened

Example: When anIncident is assigned, an event like " incident.assigned " can be triggered.

These eventsdo not execute actions themselves, but theynotify other processesto take action.

Events Are Stored in the [sys_event] Table

TheEvent Log(System Policy > Events > Event Log) records all generated events.

Administrators can monitorwhat events were triggered, their sources, and timestamps.

Events Can Be Used for Notifications & Workflows

Example: An event " incident.closed " can be configured to send a " Thank You " emailto the requester.

Example: A custom event " task.overdue " can be used to trigger a workflow escalation.

Eventssignal that something has happened, allowing other processes (like email notifications or workflows) to react.

Theydo not execute actions themselvesbut notifyscripts, business rules, or workflows.

Key Characteristics of Events in ServiceNow:Why is " B. An Event is an indication to the ServiceNow processes that something has occurred " the Correct Answer?

A. " An Event is a trigger that has a direct response in the platform " →Incorrect

Events themselvesdo not trigger direct responses; they onlynotify the systemabout occurrences.

The system must beconfigured to respond to an event(e.g., via aBusiness Rule, Notification, or Script Action).

C. " An Event is an indicator that a Priority 1 (P1) Incident has been logged " →Incorrect

While ServiceNowcan generate an event when a P1 Incident is logged, events arenot limited to incidents.

Events apply toall ServiceNow processes(incidents, changes, tasks, etc.).

D. " An Event is a recognized, scheduled occurrence of a process " →Incorrect

Eventsare not scheduled; they aretriggered by system activities(e.g., record updates, conditions met).

Scheduled Jobs or Scheduled Scripts handletime-based automation, not events.

Why the Other Options Are Incorrect?

Navigate to:System Policy > Events > Event Log

Review the event records, including event names, sources, and timestamps.

Navigate to:System Policy > Events > Registryto see predefined event names.

UseEvent Registryto create new events that triggernotifications or workflows.

How to View and Use Events in ServiceNow?

ServiceNow Docs: Events in ServiceNowhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/events/reference/r_Events.html

ServiceNow CSA Official Training Guide (Event Management & Notifications)

References from Certified System Administrator (CSA) Documentation:This confirms that " An Event is an indication to the ServiceNow processes that something has occurred " is the correct answer.

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:

When usingHigh Security Settingsin ServiceNow, administrators often gaintemporary elevated privileges. To revert to normal security levels, they mustlog out and back into refresh their session.

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

Logging outclears any temporary security settingsand restores normal administrator privileges.

This is therecommended practiceafter making security changes.

Why is Option B Correct?

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

Incorrectbecausethere is no " Normal " rolein ServiceNow.

C. Use System Administration > Normal Security module

Incorrectbecausethere is no " Normal Security " modulein ServiceNow.

D. Select Global Update Set

Incorrectbecause Update Sets controlcustomizations and configurations,not security settings.

E. End Impersonation

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

Itdoes not resetsecurity settings from High Security Mode.

ServiceNow CSA Guide - High Security Settings

ServiceNow Best Practices - Managing Security Configurations

References to Official Certified System Administrator (CSA) Documentation:

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

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

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

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

A. Star(Incorrect)

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

B. Clock(Incorrect)

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

D. Funnel(Incorrect)

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

Navigating the Application Menu:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html

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

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

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

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

Users canfilter records based on tagsfor quick access.

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

Incident Management:

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

Knowledge Base Articles:

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

Service Catalog Requests:

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

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

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

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

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

Why " C. Tags " is the Correct Answer?

A. Search – Incorrect

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

B. Favorites – Incorrect

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

D. Bookmarks – Incorrect

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

Explanation of Incorrect Options:

ServiceNow Docs: Using Tags to Organize Records

ServiceNow CSA Study Guide – Navigating and Searching in ServiceNow

ServiceNow Product Documentation: Managing and Filtering Tagged Records

References from Certified System Administrator (CSA) Documentation:

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

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

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

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

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

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

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

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

UI Policies:Data Policies:Key Differences:Feature

UI Policy

Data Policy

Scope

Affects only forms (Client-side)

Affects all data entry points (Server-side)

Execution Location

Runs in the browser

Runs on the server

Triggers

User interaction on the form

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

Enforcement

Works only when using the UI

Applies even when data is added outside the UI

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

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

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

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

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

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

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 Flow Designer, anApplication-based triggeris used to initiate a flow based on events from a specific application. Before using an application-based trigger, you must ensure that the necessaryapplication spokeand any requiredplug-insare activated.

Application Spokes:

Spokes are pre-built integration modules that allow Flow Designer to interact with different applications within ServiceNow.

Each application that provides triggers typically has its own spoke.

Plug-ins:

Some application spokes rely on additional plug-ins for full functionality.

These plug-ins must be enabled before the application-based triggers can be used.

A. Activate application trigger spoke→ Incorrect

There is no generic " Application Trigger Spoke. " Instead, each application has its own spoke that must be enabled.

B. Activate trigger security rules→ Incorrect

Security rules govern access to triggers, but they do not enable the functionality of application-based triggers.

D. Assign Application trigger role [sn_app_trigger_write] to SME→ Incorrect

Roles likesn_app_trigger_writemay provide permissions but do not activate the trigger itself.

E. Activate application plugins only→ Incorrect

While plug-ins may be necessary, you also need to activate the corresponding spoke.

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

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

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

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

Create a Template:

Navigate toSystem UI → Templates.

Define thefieldsand their default values.

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

Apply a Template to a Form:

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

The templateautomatically populatesthe pre-configured fields.

Example Use Case:

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

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

Short Description: " Password reset request "

Category: " Access "

Assignment Group: " IT Support "

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

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

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

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

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

They donot populate fields automatically.

C. Formatter→ Incorrect

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

It doesnot populate form fields.

D. Assignment Rule→ Incorrect

Assignment Rulesautomaticallyassign recordsto users or groups based on conditions.

They donot populate multiple fieldsin a form.

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

ServiceNow Learning – Templates and Data Population

ServiceNow Best Practices – Using Templates for Efficiency

References from Certified System Administrator (CSA) Documentation:

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

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

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

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

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

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

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

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

B. Information Technology Service Management (ITSM):

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

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

C. Configuration Management Database (CMDB):

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

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

D. Information Technology Infrastructure Library (ITIL):

ITIL is aset of best practicesfor IT service management.

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

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

CSDM and CMDB Best Practices Guide(ServiceNow Community and Knowledge Base)

CMDB and ServiceNow Data Model Best Practices

Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:CSDM is critical forensuring a structured and governed CMDB, enabling service visibility, and supporting ITSM and ITOM processes effectively.

AMany-to-Many (M2M) relationshipin ServiceNow allows two or more tables to be relatedbi-directionally, so that related records are visible in arelated liston both tables.

Unlike aOne-to-Many (1:M)relationship (where only one table references another), M2M relationshipslink records in both directions.

This is achieved through anintermediary table, known as aMany-to-Many table, which stores the relationships.

A Many-to-Many table contains:

Areference fieldfor each of the tables being linked.

The relationship records, which connect records between the two tables.

Suppose you want to relateIncidentstoProblemsand vice versa.

Instead of adding a reference field in each table, you create anm2m_incident_problemtable.

Now, an Incident can be linked tomultipleProblems, and each Problem can be linked tomultipleIncidents.

These relationships will be visible asrelated listsin both tables.

How Many-to-Many Relationships Work in ServiceNow:Example of a Many-to-Many Relationship:

Incorrect Answer Choices Explanation:A. Database View– Used tocombine data from multiple tablesfor reporting but does not establish abi-directional relationshipbetween tables.

C. One to Many (1:M)– Asinglerecord in one table relates tomultiplerecords in another, but the relationship isnot bi-directional.

D. Extended– Refers totable inheritance, where a table inherits fields from its parent table, not a Many-to-Many relationship.

Many-to-Many Relationships in ServiceNow

Understanding Table Relationships

Official CSA Documentation Reference:

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

Opens adrop-down menuwith options such as:

Configure Form Layout

Configure Form Design

Insert and Stay

View History

Export Options

Helps users accessquick actionswithout navigating away from the form.

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

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

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

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

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

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

Understanding the ServiceNow Form Header

ServiceNow UI Overview

Official CSA Documentation Reference:

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

Right-click on the Priority fieldin the Incident form.

Select“Show Choices”from the context menu.

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

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

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

This ensures consistency across all records using thePriorityfield.

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

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

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

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

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

Modifying Choice Lists in ServiceNow:ServiceNow Docs

How to Customize Dropdown Fields in ServiceNow

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