Pass the ServiceNow Certified System Administrator CSA Questions and answers with ExamsMirror

In ServiceNow,Data Policiesare rules thatenforce data consistencyby ensuring that specific fields meet certain conditionsbefore being saved to the database. They apply toall data operations, including form submissions, web services, and data imports.

Work at the server-side level, ensuring data integrity before it is stored.

Canmake fields mandatoryorread-onlyacross different interfaces (e.g., forms, API calls, imports).

UnlikeUI Policies, which apply only toforms, Data Policies apply to alldata transactions, including integrations and imports.

Help maintaindata quality and consistencyacross the system.

Making a Field Mandatory:

Ensure that the"Short Description"field is always filled before saving anIncident.

Enforcing a Read-Only Field:

Prevent users from modifying the"Created Date"field.

Standardizing Data on Import:

When importing employee data, ensure that the"Department"field is always set and not left blank.

Data Policies ensuredata accuracy and integritybefore it is stored.

They apply toforms, web services, import sets, and background processes.

They help organizationsmaintain standardized and structured data.

A. Data Policies enforce security – Incorrect

Security is enforced usingAccess Control Lists (ACLs), not Data Policies.

B. Data Policies standardize data in Update Sets – Incorrect

Update Sets trackconfiguration changes, not data validation.

D. Data Policies apply to lists to standard data – Incorrect

Data Policies do not specifically target lists; they enforce rules at thedatabase level.

ServiceNow Docs: Data Policies Overview

ServiceNow CSA Study Guide – Data Policies vs. UI Policies

ServiceNow Product Documentation: Enforcing Data Consistency with Data Policies

Key Features of Data Policies:Example Use Cases of Data Policies:Why "C. Data Policies enforce data consistency" is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

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:

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:

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,Import Setsallow administrators toimport and transform datafrom external sources into ServiceNow tables. The platform supports multiple file formats for importing data, includingXML, CSV, and Excel.

XML (Extensible Markup Language)

Used for structured data exchange between systems.

ServiceNow canimport XML filescontaining records formatted according to its schema.

CSV (Comma-Separated Values)

One of the most common formats for bulk data imports.

ServiceNow can processCSV filesand map them to target tables.

Excel (XLS/XLSX)

ServiceNow allows direct imports fromMicrosoft Excel spreadsheets.

Users can upload Excel files via the Import Set UI.

Supported Data Formats for Import Sets:

Import Data:The user uploads a supported file (XML, CSV, or Excel) into an Import Set table.

Mapping:The imported data is mapped to target tables using aTransform Map.

Transformation & Processing:Data is transformed, validated, and inserted into the correct destination tables.

How Import Sets Work in ServiceNow:

A. CSS, SOAP, and Excel→CSS is a styling language, and SOAP is a protocol, not a data format.

C. SOAP, REST, and XML→SOAP and REST areweb service protocols, not file formats used for import sets. XML is valid but alone is insufficient.

D. XML, SOAP, and CSS→SOAP and CSS are incorrect as they are not standard import file formats.

Why Other Options Are Incorrect:

ServiceNow Documentation:Importing Data into ServiceNow

CSA Exam Guide:Coverssupported data formats for Import Sets (XML, CSV, and Excel).

ATransform Mapin ServiceNow is a tool used to define relationships betweenfields in an import set tableandfields in a target table. It helps map incoming data to the appropriate fields within the ServiceNow database when importing data from external sources.

Data is loadedinto anImport Set Table.

ATransform Mapis created to define how fields from the import set correspond to fields in the target table.

TheTransformation Processis executed, applying the mapping rules.

The data is stored in theTarget Tablewith any specified transformations applied.

Supportsfield mapping,scripted transformations, andcoalesce fields(for avoiding duplicate records).

Allows fordata cleansing and standardizationduring the transformation process.

Can be reused for multiple data imports.

A. Transform Schema→ No such concept exists in ServiceNow.

B. Schema Map→ Provides a visual representation of table relationships but does not define field mappings for imports.

C. Dictionary Map→ Used for mapping between dictionary definitions, not for transforming import set data.

E. Field Transformer→ Not a ServiceNow tool.

F. Import Designer→ No such module in ServiceNow.

Importing data into ServiceNow from a spreadsheet involves a structured process to ensure data integrity and proper mapping. The three main steps in the process are:

The first step in importing data into ServiceNow is to load the spreadsheet into an Import Set table.

This can be done through theSystem Import Sets > Load Datamodule.

The system will create a temporary table (Import Set) where the data will be staged before being transformed into target tables.

ATransform Mapis required to map fields from the Import Set table to the target table in ServiceNow.

Transform Maps define how data from the source (Import Set table) will be transferred and transformed into the destination table (e.g., Incident, User, CMDB, etc.).

The Transform Map allows for additional transformations such ascoalescing records(to avoid duplicates) and scripting for data manipulation.

After configuring the Transform Map, the final step is toRun Transform, which applies the mappings and moves the data from the Import Set table to the target table.

This process ensures that the imported data is correctly integrated into the ServiceNow instance and adheres to the configured rules.

Option A: "Select Data Source, Schedule Transform"– Incorrect because selecting a data source is part of data import, but "scheduling" a transform is not a required step in the standard import process.

Option C: "Define Data Source, Select Transform Map, Run Transform"– Incorrect because "Define Data Source" is more relevant when setting up external data imports. The process must begin with "Load Data" rather than defining the data source.

Option D: "Select Import Set, Select Transform Map, Run Transform"– Incorrect because an Import Set must first be created by loading data before it can be selected.

ServiceNow Docs: Importing Data Overview

ServiceNow Docs: Creating a Transform Map

ServiceNow Docs: Running a Transform Map

Step 1: Load DataStep 2: Create Transform MapStep 3: Run TransformWhy Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:

In ServiceNow, theEvent Registryis a module thatstores and defines all system eventsthat can be triggered within the platform. Events in ServiceNow are used to trigger business rules, notifications, workflows, and integrations based on specific system activities.

TheEvent Registry [sysevent_register]table containspredefined and custom event definitions.

It allowsdevelopers and administratorsto definenew custom events.

Events can betriggered manually (via scripts) or automaticallybased on system actions.

Events arenot tied to a specific timeframebut are available for use whenever triggered.

Triggering a Notification

When an incident is assigned, an event such as"incident.assigned"is triggered, which can send an email notification to the assigned user.

Initiating an Automated Workflow

When a new user is onboarded, an event like"user.onboarded"can trigger a workflow to create necessary accounts and permissions.

Logging Custom Events for Reporting

Custom events like"asset.verified"can be used to track when an asset verification process is completed.

Key Features of the Event Registry:Example Use Cases of the Event Registry:

TheEvent Registryisnot a log of completed eventsbut arepository of event definitionsthat can be triggered.

It defines bothdefault and custom eventsthat can be used across different system processes.

It is used forevent-driven automationin ServiceNow.

Why "C. The Event Registry is a module that provides Event definitions" is the Correct Answer?

A. The Event Registry lists all Events that have successfully completed within a 24-hour period – Incorrect

This describes theEvent Log [sysevent]table, not the Event Registry.

B. The Event Registry is a list of all Events that originate through an integration – Incorrect

TheEvent Registryis not specific to integrations; it applies to all events in the system.

D. The Event Registry is a list of all Events that have successfully completed after being Invoked by a script – Incorrect

Events triggered by scripts are logged in theEvent Log, not theEvent Registry.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding the Event Registry

ServiceNow CSA Study Guide – Event Management

ServiceNow Product Documentation: Creating and Managing Events

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Visual Task Boards (VTBs)provide aKanban-style interfaceto manage and track work. There arethree main typesof Visual Task Boards, but "Feature"is notone of them.

Freeform Board (Valid Type)

Manually created boards wherecards can be moved freelywithout predefined conditions.

Users canadd and organize tasks as needed.

Example: Personal task management.

Guided Board (Valid Type)

Createdfrom a list viewandlinked to a ServiceNow table(e.g., Incident, Change, Task).

Cards on the boardautomatically updatebased on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (Valid Type)

Similar toGuided Boards, but allows users tomanually reordertasks within lanes.

Offers moreflexibilitywhile still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

"Feature" is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term"Feature"in Agile Development (for tracking high-level product functionalities), but it is not related to VTBs.

Types of Visual Task Boards in ServiceNow:Why is "Feature" Incorrect?

Why Other Options Are Correct?Guided, Flexible, and Freeformare thethree valid typesof Visual Task Boards in ServiceNow.

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

References from ServiceNow CSA Documentation:

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

Groups are stored in thesys_user_grouptable

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

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

Groups are used for role assignments

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

Groups can be used for approvals and task assignments

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

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

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

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

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

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

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

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

Groups in ServiceNow

Managing User Groups

User and Group Management

ServiceNow User and Group Administration

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

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

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

Every record in every table in ServiceNow has asys_idfield.

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

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

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

Number:INC0012345

sys_id:9d72f6141b122200d37a85e15b2d6fe6

Key Characteristics of sys_id:Example:

Thesys_id is always 32 characters long.

It is acritical part of the ServiceNow database structure.

Used forrelationships, APIs, scripting, and querying records.

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

B. A client-side Business Rule – Incorrect

Business Rulesdo not generate sys_ids; they control logic execution.

C. A server-side Business Rule – Incorrect

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

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

The correct length of sys_id is32 characters, not 64.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding sys_id

ServiceNow CSA Study Guide – Database Architecture

ServiceNow Product Documentation: Unique Identifiers in ServiceNow

References from Certified System Administrator (CSA) Documentation:

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

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

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

Example:

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

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

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

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

A. snc_abc – Incorrect

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

B. abc – Incorrect

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

D. sys_abc – Incorrect

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

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

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.

AUI Policyis the preferredno-codeapproach in ServiceNow to dynamically control themandatory, read-only, or visibilitystate of form fields based on specified conditions. Unlike Client Scripts, which require JavaScript coding, UI Policies provide aneasy-to-configure, rule-based solution.

They allow administrators tocontrol form behaviorwithout scripting.

They arefaster and more efficientthan Client Scripts.

Theyrun on the client-side, meaning changes occur dynamically as users interact with the form.

Defineconditions(e.g., "Priority is High").

Setactions(e.g., make "Due Date" mandatory, read-only, or hidden).

Apply the UI Policy to the form automatically when the condition is met.

A. UI Action→ UI Actions create buttons, links, or context menu items; they do not control form fields.

B. Client Script→ While Client Scripts can achieve similar functionality, they require JavaScript coding, making them alow-coderather than ano-codesolution.

C. UI Script→ UI Scripts are reusable JavaScript libraries, not designed for controlling form fields.

D. UI Rule→ No such feature exists in ServiceNow.

AConfiguration Item (CI)is any component thatneeds to be managed to deliver IT services. In ServiceNow, CIs are stored in theConfiguration Management Database (CMDB)and can include servers, applications, databases, network devices, and more.

Tracking & Management: Helps organizations track IT assets and their relationships.

Service Impact Analysis: Identifies how an issue with one component can affect related services.

Change Management Support: Ensures changes to IT assets are controlled and well-documented.

Incident & Problem Resolution: Provides insights into troubleshooting and root cause analysis.

Hardware: Servers, network devices, storage systems.

Software: Applications, databases, operating systems.

Services: Business services, IT services.

Documentation: Policies, SLAs, knowledge articles.

Why Are Configuration Items Important?Examples of Configuration Items (CIs):

Incorrect Answer Choices Explanation:A. CSDM Items– TheCommon Service Data Model (CSDM)is a framework for structuring CMDB data, but individual components in the CMDB are calledConfiguration Items (CIs).

B. CMDB– TheCMDB (Configuration Management Database)is thedatabasethat stores Configuration Items, but it is not a CI itself.

D. Service Offerings– AService Offeringrepresents a set of capabilities available to customers but is not the same as a CI.

E. Asset– AnIT Assetrefers to aphysical or virtual resourceowned by the organization, butnot all assets are CIs(e.g., a computer mouse may be an asset but not a CI).

ServiceNow CMDB Overview

Configuration Items (CIs)

Official CSA Documentation Reference: