ServiceNow CSA - ServiceNow Certified System Administrator

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,User Criteriadefine conditions that determinewhich userscancreate, read, write, and retireknowledge articles in aKnowledge Base (KB). User Criteria help enforceaccess controland ensure that only authorized users can interact with specific knowledge bases.

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

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

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

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

Example 1: Restricting Read Access

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

User Criteria:Department = IT, OR Role = itil

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

Example 2: Controlling Who Can Contribute

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

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

Only HR Team members and Knowledge Managers can contribute.

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

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

It is a feature within theKnowledge Management application.

A. User Conditions – Incorrect

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

B. User Info – Incorrect

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

D. User Permissions – Incorrect

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

ServiceNow Docs: User Criteria for Knowledge Management

ServiceNow CSA Study Guide – Knowledge Management Permissions

ServiceNow Product Documentation: Configuring Knowledge Base Access

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

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:

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

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

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

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

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

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

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

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

Why Other Options Are Incorrect:

ServiceNow Documentation:User Interface Overview

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

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

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

ServiceNow uses a hierarchical structure to manageService Catalog requests:

REQ (Request Record)

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

It groups all requested items and their associated tasks.

Found in thesc_requesttable.

RITM (Requested Item Record)

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

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

Found in thesc_req_itemtable.

TASK (Catalog Task Record)

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

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

Found in thesc_tasktable.

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

This is thecorrect pathbecause it follows theServiceNow fulfillment structure:

REQ (Request)– Tracks the entire request.

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

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

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

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

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

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

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

Incorrectbecausenot all requests involve procurement.

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

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

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

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

ServiceNow CSA Study Guide – Service Catalog & Request Fulfillment

ServiceNow Docs: Request Fulfillment Process(ServiceNow Documentation)

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

References from the Certified System Administrator (CSA) Documentation:

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

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:

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.

ServiceNow features a built-in collaboration mechanism known as User Presence . This feature is designed to prevent collisions (two people overwriting each other ' s work) and promote real-time awareness when multiple users are on the same form.

1. User Presence Avatar (Option E):

When multiple users open the same record (like an Incident), a User Presence icon immediately appears in the form header (typically at the top right). This icon displays the avatar or initials of the other user(s) currently viewing the record. If you hover over the avatar, you can see their name.

2. Field-Level Indicators (Option C):

User Presence is not just about who is looking; it also shows what they are doing. If another user actively types into a field or changes a drop-down value, a small " presence indicator " (a colored icon or dot) appears to the left of that specific field on your screen in real-time. This warns you that the field is being modified by someone else before you attempt to edit it yourself.

3. Why the other options are incorrect:

A: The Work Notes list is for logged journal entries, not real-time presence detection.

B & D: While ServiceNow has chat features (like Connect Chat or Sidebar), these do not automatically launch or force notification pop-ups merely because two people open the same record.

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

ARecordis asingle instanceof data stored in a ServiceNowtable.

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

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

Example:

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

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

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

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

It is just a way tointeract with records.

D. Lists

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

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

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

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

In ServiceNow, 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, theService Catalogis a centralized portal where users can request IT services, hardware, software, and other business-related items. Within theService Catalog, the fundamental components are known asService Catalog Items.

Definition of Service Catalog Items:

AService Catalog Itemrepresents a specific service, product, or action that a user can request from theService Catalog.

It is thecore componentthat defines what users can request.

Examples include:

Requesting anew laptop

Submitting anaccess request

Ordering asoftware installation

Why They Are the " Building Blocks " of the Service Catalog:

All Service Catalog requests are based on catalog items—without them, the catalog has no offerings.

Each item has associated workflows, approvals, and fulfillment processesthat define how the request is handled.

They form the foundationof the Service Catalog because every service request must be tied to an item.

Understanding Service Catalog Items

Why Answer " B " is Correct:✔️ " They are the building blocks. "

Service Catalog Itemsserve as the fundamental componentsof the catalog.

They define what services and products are available for request.

Withoutcatalog items, the Service Catalog would not function as intended.

Why the Other Answers Are Incorrect:A. " They run behind the scenes. "

Incorrectbecause Service Catalog Items arevisible to usersin the Service Catalog portal.

While workflows and fulfillment processes may operate in the background, the items themselves arenot hidden.

C. " They are optional. "

Incorrectbecause Service Catalog Items aremandatoryfor a functioning Service Catalog.

Thecatalog is useless without catalog items, making them essential, not optional.

D. " They provide options. "

Incorrectbecause while Service Catalog Items can havevariables(such as dropdown selections or checkboxes), their primary role isnot just to provide options but to define the services available.

ServiceNow CSA Study Guide – Service Catalog & Request Management

ServiceNow Docs: Service Catalog Overview(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_catalog, sc_cat_item, sc_request, sc_task)

References from the Certified System Administrator (CSA) Documentation:

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

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

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

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

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

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

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

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

ServiceNow Documentation:Data Policies

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

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

A. True

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

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

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

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

The system ensuresunique sequential numberingwithin each table.

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

Navigate toSystem Definition → Number Maintenance.

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

Changes apply automatically to new records created in that table.

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

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

ServiceNow prevents duplicate numbers to maintain data integrity.

Why " False " is the Correct Answer:

Manual incrementing isnotrequired or possible for individual records.

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

Why " True " is Incorrect:

ServiceNow Documentation:Number Maintenance

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

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

B. False