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

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

Data Loading from External Sources:

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

Allows data fromexternal systemsto be brought into ServiceNow.

Staging Area for Data Processing:

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

Data can then betransformedbefore being committed to the target table.

Data Mapping and Transformation:

UsesTransform Mapsto map fields from theImport Set Tableto theTarget Table.

Supportsautomatic field mappingandscripted transformations.

Data Cleansing and Validation:

Duplicate records can bedetected and removed.

Invalid or missing data can becorrected before insertion.

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

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

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

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

Verify the datain the target table.

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

TheSystem Import Setsmodule loads this data into astaging table.

ATransform Mapmoves the data into theUser [sys_user]table.

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

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

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

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

B. Configuration→ Incorrect

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

D. System Update Sets→ Incorrect

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

ServiceNow Docs – Importing Data with System Import Setshttps://docs.servicenow.com

ServiceNow Learning – Data Import & Transformation Best Practices

ServiceNow Developer Portal – Using Import Sets Efficiently

References from Certified System Administrator (CSA) Documentation:

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:

ServiceNow allowsa single Catalog Itemto be published tomultiple service catalogs, avoiding duplication while ensuring accessibility for the right users.

Instead ofcreating duplicate catalog items(which would require managing two separate items with the same functionality), we createone Catalog Itemandpublish it in both catalogs (HR and Facilities).

This approach ensurescentralized managementwhile maintaining accessibility for both departments.

It simplifies updates—any changes to the form or workflow will apply toboth catalogs automatically.

Why is Option B Correct?

Why Are the Other Options Incorrect?A. Create one Catalog Item for HR Event Room Set Up and one for Facilities Event Room Set Up; then publish each to the appropriate Catalog.

Incorrectbecause it createsduplicate catalog itemswith thesame functionality, increasing maintenance effort.

C. Create one Catalog Item for Event Room Set Up; then publish to the Parent Catalog, which is accessible to both HR and Facilities.

Incorrectbecausethere is no " Parent Catalog " conceptin ServiceNow.

ServiceNow allowspublishing a single item to multiple catalogs, but there is no need for aparent catalog.

D. Create one Catalog Item for Event Room Set Up; then use ACLs to control access.

Incorrectbecause ACLsrestrict access at a field, table, or record level, but theydo not control where a Catalog Item appears.

Thecorrect approachis topublish the item to multiple catalogsrather than using ACLs.

ServiceNow Service Catalog Management - Publishing Items to Multiple Catalogs

ServiceNow ITSM - Best Practices for Catalog Item Reusability

ServiceNow CSA Guide - Managing Service Catalogs and Items

References to Official Certified System Administrator (CSA) Documentation:

AnUpdate SetinServiceNowis a mechanism for capturing and migratingcustomizations and configurationsfrom one instance to another (e.g.,Development → Test → Production).

What is Captured in an Update Set?Update Sets recordconfiguration changes, such as:

Tables & Database Schema Changes(e.g., new tables, modified fields)

Form Layout & UI Changes(e.g., changes in form views, UI policies)

Schedules(e.g., Scheduled Jobs, Business Rules with scheduled actions)

Client Scripts(e.g., JavaScript running on the client side)

Business Rules, UI Actions, UI Policies

Workflows, Script Includes, ACLs (Access Control Rules)

Email Notifications, Dictionary Entries, Application Menus

What is NOT Captured in an Update Set?Data Records (e.g., Incident, Change Request, CMDB data)

Group Memberships & User Data

System Properties (some properties may require manual migration)

Attachments & Scheduled Reports

B. Changes made to tables, forms, views, and fields(Incorrect)

Views and Fieldsare part of UI changes, butschedules and client scriptsare also included in Update Sets, makingOption A more complete.

C. Changes made to tables, forms, Business Rules, and data records(Incorrect)

Data records (actual table entries like incidents or change requests) are NOT captured in Update Sets.

D. Changes made to tables, forms, groups, and configuration items (CIs)(Incorrect)

Groups and CIs (CMDB data) are considered data and are NOT included in Update Sets.

Instead,CIs should be migrated using Import Sets or CMDB data export/import.

Why Other Options Are Incorrect?

Understanding Update Sets

Update Sets Overview

What Gets Captured in Update Sets?

Best Practices for Using Update Sets

References from ServiceNow CSA Documentation:

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:

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

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

SelectImpersonate User.

Search for and select theuser’s name.

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

Navigate to theApplication Navigatorand check for missing modules.

Once done, clickStop Impersonation.

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

Speeds up troubleshootingby allowing admins to replicate user issues.

Helps verify role-based access permissions.

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

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

This is asecurity violationand not an acceptable practice.

B. Initiate a Connect Chat session

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

C. Install the Bomgar plug-in

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

E. Launch a NowChat window

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

Impersonate Users in ServiceNow

User Roles and Permissions

Official CSA Documentation Reference:

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:

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

Why These Options Are Correct?C. My reports

Displaysreports created by the logged-in user.

These reports areprivateunless explicitly shared.

E. Dashboards

Dashboardsconsolidate multiple reports andmake them visible to specific audiences.

Users canshare dashboardswith groups or individuals.

F. Global

Global reportsare available toall users with reporting access.

These reports arenot restrictedto a specific user or group.

I. All

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

Personal reports

Shared reports

Global reports

Reports from dashboards

Why the Other Options Are Incorrect?A. Group

There isno " Group " sectionin the Reports page.

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

B. Department

Departments do not determine report visibilityin the Reports page.

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

D. Team

Teams are not a standard report visibility categoryin ServiceNow.

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

G. Admin

There isno " Admin " sectionin the Reports page.

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

H. Analytics

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

It is not a standardreport visibility section.

J. Company

There isno " Company " sectionin the Reports page.

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

ServiceNow Reports - Managing Visibility and Access

ServiceNow Reporting Guide - Sections of the Reports Page

ServiceNow Dashboards and Report Sharing Best Practices

References to Official Certified System Administrator (CSA) Documentation:

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 (and databases in general), data is stored intables, which consist of:

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

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

Key Concepts:Table

Columns (Fields)

Rows (Records)

Incident

Number, Caller, Priority, Description

Each unique incident entry

User

Name, Email, Role, Department

Each individual user record

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

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

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

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

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

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

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

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

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

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

ServiceNow Docs: Understanding Tables and Fieldshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/metadata/concept/c_TablesAndFields.html

References from Certified System Administrator (CSA) Documentation:

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

Navigate to the Number Maintenance Application:

Go toAll → System Definition → Number Maintenance

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

Modify the Prefix:

Open the existingIncident numbering record.

Change thePrefixfrom " INC " to " IN " .

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

Save the Changes:

ClickUpdateto apply the new prefix.

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

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

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

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

Business Rulesdo not control number generation.

Number generation is managed byNumber Maintenanceat the system level.

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

The prefixCAN be changedusing theNumber Maintenanceapplication.

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

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

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

ServiceNow Docs – Number Maintenance Configurationhttps://docs.servicenow.com

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow Developer Portal – Number Prefix Best Practices

References from Certified System Administrator (CSA) Documentation:

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

InServiceNow ' s System Import Sets, administrators canimport data from external sources(such as CSV, Excel, or databases) intoany tablewithin the platform usingTransform Maps.

ATransform Mapdefines how data from an Import Set table is mapped to fields in atarget table (destination table).

Administrators can select any tablein the system as the destination, including bothstandard and custom tables.

Thedestination table is not limitedto Task-related tables (Incident, Problem, Change, etc.).

Users can also applycoalesce rulesto determine if records should be updated or inserted during the transformation.

ServiceNowallows administrators to select any tableas the destination when setting up a Transform Map.

This includes standardITSM tables (Incident, Problem, Change, Task, Service Catalog)as well ascustom tablescreated by administrators.

There areno restrictionson which table can be a destination.

A. " The Task table is the only table that can be a destination " →Incorrect

TheTasktable is widely used, but it isnot the only tablethat can receive imported data.

B. " Only Incident, Problem, Change, Task, and Service Catalog tables can be destinations " →Incorrect

These are common ITSM tables, butany table in the systemcan be selected as a destination.

C. " Only the Incident, Problem, and Change tables can be destinations " →Incorrect

This istoo restrictivebecause other tables, including custom ones, can also be used.

Navigate to:System Import Sets > Create Transform Map

Select the Import Set Tableas thesource.

Choose any available tablein ServiceNow as thedestination.

Definefield mappingsbetween the source and target table.

Configurecoalesce rulesto update or insert records.

ServiceNow Docs: Creating and Using Transform Mapshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/import-sets/concept/c_TransformMap.html

ServiceNow CSA Official Training Guide (Import Sets & Data Management)

Key Points About Transform Maps & Data Import:Why is " D. Any ServiceNow table " the Correct Answer?Why the Other Options Are Incorrect?How to Configure a Transform Map in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms thatany ServiceNow tablecan be adestination tablefor imported data when using Transform Maps inSystem Import Sets.

TheCommon Service Data Model (CSDM)is a framework provided by ServiceNow that ensures your application ' s data correctly maps to theConfiguration Management Database (CMDB)tables. It standardizes howconfiguration items (CIs), services, and relationshipsare structured within the CMDB.

Standardized Data Model:Ensures consistent and correct CMDB data structuring.

Alignment with CMDB Best Practices:Helps businesses align their IT assets, services, and business functions effectively.

Better Service Mapping:Provides structured relationships between business services and their technical components.

Compliance & Governance:Ensuresdata integrityby enforcing best practices for CMDB population.

Key Functions of CSDM:

Incorrect Answer Choices Explanation:B. Service Mapping Utility (SMU)– Service Mapping is used fordiscovering and mapping dependenciesbut is not a data model framework.

C. Service Schema Map (SSM)– No such official term exists in ServiceNow documentation.

D. CMDB Class Manager (CMDBCM)– This is a tool used tomanage CI classesbut does not define a data model framework like CSDM.

E. CI Class Manager (CICM)– Incorrect term; CMDB Class Manager is used for CI class hierarchy management, not for mapping applications to CMDB tables.

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

ServiceNow CMDB Best PracticesCMDB and CSDM Alignment

Official CSA Documentation Reference:

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

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

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

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

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

Changes to system configuration (not transactional data)

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

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

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

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

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

Why Other Options Are Incorrect:

ServiceNow Documentation:Update Sets and What They Capture

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

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

B. They are not captured in an Update Set