CSA ServiceNow Certified System Administrator Free Practice Exam Questions (2025 Updated)

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:

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 IntegrationHub, third-party API integrations within aFlow Designerflow are known asspokes. Aspokeis a scoped application containingFlow Designer actions and subflowsthat allow the flow to interact with external systems or ServiceNow applications.

Spokes in IntegrationHub

Aspokeis a collection ofpredefinedandcustomactions, subflows, and data streamsused to integrate with external systems.

Spokes provide ano-code/low-codeapproach to integrating third-party applications.

Examples ofprebuilt spokesavailable in ServiceNow include:

Slack Spoke(for Slack API integrations)

Microsoft Teams Spoke(for Teams integration)

Jira Spoke(for integrating with Atlassian Jira)

How Spokes Work

When a flow needs to interact with an external system (e.g., sending data to Jira or retrieving information from Slack), itcalls an action from a spoke.

Each spoke containsmultiple predefined actionsthat execute API requests or perform tasks like creating records, updating data, or fetching information.

Comparison with Other Options

A. an action→ Incorrect

Actions are individual steps in a flow, not the complete integration package. Actions exist inside spokes.

C. a connection→ Incorrect

Aconnectionis a configuration that stores authentication details (e.g., API keys, OAuth tokens) used by a spoke.

D. an integration step→ Incorrect

No such term as “integration step” exists in ServiceNow IntegrationHub.

ServiceNow Docs - IntegrationHub Overview:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/integrate/integrationhub/concept/integrationhub-overview.html

ServiceNow Docs - Spokes in Flow Designer:https://docs.servicenow.com/en-US/bundle/utah-integrationhub/page/administer/integrationhub-spokes/concept/available-spokes.html

Key Concepts Related to IntegrationHub and SpokesOfficial References from the Certified System Administrator (CSA) Documentation:

InServiceNow Catalog Item Workflows, anapproval processoften includes aManager Approval step, which typically requires the requester'smanager(as defined in thesys_userrecord) to approve the request.

IfBob Smith's user record does not have a manager specified, the systemcannot determine who should approve the request, which may result in the approval step beingskipped.

A. There is a business rule, excluding Bob Smith from any approvals.

While business rules can affect approvals, it isunlikelythat a rule would exist specifically to exclude Bob Smith unless explicitly configured, which is uncommon.

B. Bob Smith does not have a delegate set up on his account.

Delegates areoptionaland only apply when a manager is unavailable. This does not affect whether the approval is skipped.

D. The manager does not have a delegate assigned.

A delegate only comes into play if an approveris out of officeor unavailable. This does not impact whether an approval isskipped entirely.

E. Bob Smith is a VIP.

Being marked as aVIPdoes not automatically bypass approval workflows. Approval processes follow defined rules in workflow configurations.

ThePropertiessection in theReport Designeris used to:

Specify the report name

Select the table or data sourcefor the report

Allows renaming the reportfor better identification.

Defines the primary data source(table) for the report.

Sets report-level settingssuch as visibility, sharing options, and description.

B. Data →Incorrect

TheData sectionis used tofilter and refine the databut not to set the table or name the report.

C. Configure →Incorrect

No such section named"Configure"exists in the Report Designer.

D. Type →Incorrect

TheType sectionis used toselect the type of report(e.g., Pie Chart, Bar Chart, List, etc.).

E. Sources →Incorrect

No"Sources"section exists in the Report Designer.

Key Features of the Properties Section:Why Other Options Are Incorrect?

Report Designer Overview

Official ServiceNow Documentation Reference:

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

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

Data policies can enforce field read-only rules globally.

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

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

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

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

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

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

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

ServiceNow Data Policies Overview

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

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

Activity Formatteris a UI element in ServiceNow forms that logs allupdates, comments, and historyrelated to a task.

It consolidates user interactions and system-generated updates in one place.

Predictive Intelligence (PI)in ServiceNow is anAI-powered frameworkthat helpsautomate classificationanddecision-makingbased on historical data. It canautomatically populate values for fields like Priority and Categorybased on theShort Descriptionfield value.

D. Predictive Intelligence

Usesmachine learning modelsto analyze patterns in previous records.

Automaticallysuggests or assigns valuesfor fields likePriority, Category, and Assignment Group.

Example:

If a user submits anincident with "Email not working"in theShort Description, Predictive Intelligence can:

SetCategorytoEmail

SetPrioritytoMedium

Assign the ticket to the appropriateSupport Group

A. UI Policy

UI Policiescontrolform behavior(e.g., showing/hiding fields) butdo notdynamically assign values based on machine learning.

B. Assignment Rule

Assignment Rulesdeterminewho gets assigneda record based on conditions butdo not populate Priority or Category automatically.

C. Action

"Action"is not a framework—it refers toFlow Designer actions, which require manual configuration.

E. CSDM (Common Service Data Model)

CSDMis adata frameworkfor managing CIs and services, but it doesnot handle automatic field population.

Performance Analytics (PA)in ServiceNow allows users tocreate dashboards with widgetsthatvisualize trends over timeto monitor and improve processes.

Key Features ofPerformance Analytics:

✔Data Visualization:Users can track KPIs, measure performance trends, and create meaningful insights.

✔Dashboards & Widgets:Custom dashboards with interactive widgets display real-time analytics.

✔Historical & Trend Analysis:Unlike standard reports, PAanalyzes trends over time, helping organizations improve their services.

✔Predictive Insights:Uses historical data toidentify patternsand drive informed decisions.

A. Analytics Reports

No such feature existsin ServiceNow under this name. The correct term isPerformance Analytics.

C. Scheduled Reports

Scheduled reports allow users toautomate report delivery, but they donotprovideinteractive dashboardsortrend analysis.

D. Reporting

Standard Reportingprovidessnapshot views of databut does not supporttrend analysisover time likePerformance Analytics.

InFlow Designer, when an action is executed, its output (data) is stored as aData Pill. TheseData Pillscan be used insubsequent actionswithin the same flow.

Data Pillsrepresent pieces of data produced by previous steps in the flow.

They arevisually represented as draggable tokensin Flow Designer.

Users candrag and dropData Pills into fields of subsequent actions to dynamically use the stored data.

A"Create Record"action generates a new incident.

TheIncident Numberis stored as aData Pill.

A subsequent"Send Email"action can use thisIncident Number Data Pillin the email subject/body.

A. Field Icon– No such term exists in Flow Designer.

B. Field Value– Field values exist on forms but are not used for storing action data in Flow Designer.

D. Data Element– This is a general term but does not specifically refer to Flow Designer storage.

E. Data Trigger– A triggerinitiatesa flow but does not store action data.

ServiceNow Flow Designer – Data Pills

ServiceNow CSA Training Module:"Using Data in Flow Designer Actions"

What is a Data Pill?Example Scenario:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

In ServiceNow, when building filter conditions using theCondition Builder, there are three key components:

Field (Filter Criteria):The specific database field you are filtering on.

Operator:A choice list that defines the condition (e.g., "is", "contains", "starts with").

Value:The value you are checking against.

Among these components,the Operator is always a choice list, as it provides predefined options for filtering. The Operator determines how the Field and Value should be compared. For example:

"State is Active"(where "is" is the Operator)

"Priority is greater than 2"(where "is greater than" is the Operator)

Other components, such as Filter Criteria (fields) and Match Criteria, do not always function as choice lists.

When importing data into ServiceNow via anImport Set, the system determines whether to update existing records or create new ones based on theCoalescefield setting.

If noCoalesce Fieldis defined,ServiceNow treats every imported row as a new record.

The import process doesnotcheck for existing records, meaning no records in the target table are updated.

This can result induplicate entriesif the imported data includes records that already exist in the target table.

ACoalesce Fieldis used tomatchincoming data to existing records.

If a matching record is found, it is updated instead of inserting a new one.

If no matching record is found, a new record is created.

Behavior When No Coalesce Field is Specified:How Coalescing Works:Incorrect Answers Explanation:A.All rows are rejected from the import, as coalesce field is required

This is incorrect because the import does not require a coalesce field to proceed. The system will still import all rows.C.Duplicate rows are rejected from the import

Without a coalesce field, duplicates arenotrejected. Instead, every row is inserted as a new record, even if it already exists in the target table.D.All rows are treated as new records, but errors will be flagged in the import log

Errors are only flagged in cases ofdata mismatches, validation failures, or incorrect mappings, not just because coalescing is missing.

ServiceNow Documentation→ "Importing Data - Coalescing Best Practices"

ServiceNow Import Set Documentation→ "Understanding Import Set Behavior Without Coalescing"

References from Certified System Administrator (CSA) Documentation:

When importing spreadsheet data into ServiceNow using theImport Setprocess, data is transferred in multiple stages. The step where data getswritten to the receiving tableis called"Run Transform."

Load Data:The spreadsheet or data file is uploaded to a temporary table (Import Set table).

Run Transform:The system processes the import set data andwrites it to the target table.

Verify Data:After transformation, the data is checked for accuracy.

Load Data:

The spreadsheet or external data is first imported into astaging table (Import Set table)in ServiceNow.

At this stage, the data is not yet written to the actual destination table.

Run Transform (Correct Answer):

TheTransform Mapapplies field mappings and business logic.

The data is processed and written from the import set table to the target table (e.g., Incident, CMDB, or any other receiving table).

Any data transformation (such as field mappings, lookups, or script-based modifications) happens here.

Verify Data:

After transformation, users shouldvalidate the imported recordsto ensure that data was written correctly.

B. Run Import:

This steponly loads the data into a temporary Import Set table.

It does not write data to the receiving table.

C. Import Dataset:

"Import Dataset" isnot an actual stepin the ServiceNow data import process.

D. Execute Transform:

There is no "Execute Transform" step in ServiceNow.

The correct term is"Run Transform."

E. Schedule Transform:

While youcanschedule transforms, this is not the step where data gets written to the final table.

The actual transformation and writing occur during"Run Transform."

Import Set Process in ServiceNow:Explanation of Each Step:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:For more details, refer to the official ServiceNow documentation:

Importing Data into ServiceNow

Transform Maps in Import Sets

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

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

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

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

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

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

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

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

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

A. Their user account failed LDAP authentication →Incorrect

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

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

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

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

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

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

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

Why Other Options Are Incorrect?

User Roles in ServiceNow

Assigning Roles and Group Memberships

Official ServiceNow Documentation Reference:

In ServiceNow,Client Scriptsare scripts that execute in the user'sweb browserrather than on the server. They are used to enhance user experience by dynamically controlling form behavior, validating user input, or performing real-time updates without requiring a server request.

Types of Scripts in ServiceNow:Script Type

Runs On

Purpose

Client Script

Web browser (client-side)

Modify UI behavior, perform field validations, or respond to user interactions.

Server Script

ServiceNow backend (server-side)

Processes data, enforces business rules, and performs background operations.

Database Script

Database layer

Used for stored procedures or database triggers (not applicable in ServiceNow).

Local Script

Not an actual ServiceNow script type

No such category exists in ServiceNow.

Runsin the web browserwhen a form is loaded, changed, or submitted.

Can manipulate field values, display messages, or enforce rules in real time.

UsesGlideForm (g_form)andGlideUser (g_user)APIs.

Reduces server load by executing logic without sending requests to the backend.

A. Server script:

Runs on theserver-side, not in the browser.

Examples:Business Rules, Script Includes, Scheduled Jobs.

B. Local script:

No such script type in ServiceNow.

C. Database script:

ServiceNow does not allow direct database scripting.

Client Scripts Overview

Scripting Best Practices

Key Features of Client Scripts:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference: