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

TheCI Dependency View Mapin ServiceNow is a graphical representation of therelationshipsanddependenciesbetween Configuration Items (CIs) within theConfiguration Management Database (CMDB). Right-clicking on a CI in the Dependency View provides additional options for analyzing its impact and history.

A. View Affected CIs

Shows all CIsimpactedby the selected CI.

Example: If adatabase servergoes down, this option lists all applications and services affected.

B. View Related Tasks

Displays tasks (e.g.,Incidents, Changes, Problems) associated with the selected CI.

Example: Viewing allopen Incidentsrelated to aserver CI.

C. View Recent Outages

Showsrecently reported outageslinked to the selected CI.

Useful for analyzing recurring issues or identifying historical failures.

D. View Cases

Casesare used inCustomer Service Management (CSM), not in CMDB CI dependency maps.

E. View Knowledge

WhileKnowledge Articlesmay reference a CI, this is not an option in theCI Dependency View Map.

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,related listsdisplay records that have a relationship with the current record based onreference fieldsordatabase relationships. When adding a related list to a form, users select from aList Collector, which shows available related lists based on table relationships.

B. Catalog Task → Parent

Catalog Tasksare individual work items that belong to aRequest Item (RITM).

TheParentfield links a Catalog Task to its correspondingRITM.

This related list allows users to view all Catalog Tasks associated with a parent request.

C. HR Case → Parent

InHR Service Delivery (HRSD), HR Cases track employee requests.

TheParentfield links an HR Case to a parent HR Case or HR Service Request.

This related list allows HR agents to see all related sub-cases.

D. Problem → Parent

Problem Recordscan have aParent-Childrelationship where a child problem is linked to a larger problem.

TheParentfield is used to establish this hierarchy.

This related list helps track all sub-problems linked to a main problem.

A. Release Phase == Parent

"Release Phase" is not a standard related list in ServiceNow.

TheRelease Management moduleusesphases, but they do not typically function as aParentreference.

E. Outage → Task Number

WhileOutagescan be linked toTasks, they arenotcommonly referenced as a related list in standard implementations.

A more appropriate relationship would be"Affected CI"rather thanTask Number.

InServiceNow, afieldis asingle data pointin a table, similar to acell in a spreadsheet.

Fields store specific datain a table, such as:

Short Description(text field)

Priority(choice field)

Assignment Group(reference field)

Each record consists of multiple fields

Example: In theIncident table, a singleIncident recordcontains multiple fields such as:

Number(INC0012345)

State(In Progress)

Assigned To(John Doe)

Fields have different data types

Text, Integer, Choice, Date/Time, Reference, etc.

Understanding Fields in ServiceNow:

B. A field is a table rowIncorrect– Atable rowrepresents anentire record, not just asingle field.

Arecordconsists of multiplefields(columns).

C. A field is an item that appears in a menu listIncorrect– Menu items areUI elements, not database fields.

Afieldispart of a table, while a menucontains navigation links.

D. A field is a record in a tableIncorrect– Arecordis afull row of data, which includesmultiple fields.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Understanding Tables, Records, and Fields????Tables and Fields Overview

ServiceNow Docs – Field Types and Definitions????Field Data Types

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

A. A field is a table cell that stores data.

Afieldis asingle piece of datawithin a record, much like acell in a spreadsheet.

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

Lack of Organization & Traceability

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

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

Risk of Losing Changes

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

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

Cannot Be Moved Between Instances

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

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

Best Practice: Use Named Update Sets

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

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

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

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

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

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

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

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

InVisualization Designer, used in thePerformance Analytics and Reportingspace of ServiceNow, the"Preview"button is used to execute the current visualization setup and show how the filters and conditions apply to your data. This allows the report builder to validate the design without finalizing or publishing it.

Try: Not an available action in Visualization Designer.

Execute: More related to scripting or automation contexts.

Run: Used in reports or scripts but not the specific action in Visualization Designer.

Detailed Explanation:

In ServiceNow, thesys_idfield serves as a unique identifier for every record within the platform’s database. The sys_id is a 32-character globally unique identifier (GUID) that ServiceNow automatically generates for each record, ensuring that every record is uniquely identifiable and can be referenced across the system. This sys_id is essential for integrations, queries, and relationships between records. (Reference: ServiceNow Documentation - Record Identification and sys_id Field)

=================

InService Catalog Management,categoriesare used tologically group catalog itemsto make navigation easier for users. Categories help organize items into meaningful sections, ensuring that users canquickly locatethe services they need.

For example:

"Software Requests" can be a category containing catalog items like "Microsoft Office," "Adobe Photoshop," and "VPN Access."

"Hardware Requests" can include items like "Laptops," "Monitors," and "Keyboards."

A. Variable Sets–Variable sets are reusable groups of variables for catalog items, but they do not organize items into groups.

B. Catalog Items–Catalog items refer to individual service requests (e.g., "Request a Laptop"), but they are grouped usingcategories, not other catalog items.

C. Sections–Sections are used informsto group related variables together, not for organizing catalog items.

In ServiceNow,User Criteriais the mechanism used to control and determine user access toknowledge bases (KBs) and knowledge articles. User criteria define which users, groups, or roles canread, write, and contributeto a knowledge base or specific articles within it.

How User Criteria Works:User Criteria are applied at both theknowledge baselevel and theknowledge articlelevel to manage access. They can be configured with specific conditions to allow or restrict access based on:

Users(specific users can be added directly)

Groups(access can be granted to a specific user group)

Roles(users with specific roles can be given access)

Advanced conditions(such as department, company, location, etc.)

A knowledge base can havemultiple user criteria, and a single user criterion can apply to multiple knowledge bases.

Read User Criteria– Determines who can view the knowledge base or an article.

Write User Criteria– Determines who can create, edit, or contribute knowledge articles.

Exclusions– You can exclude users or groups from accessing specific knowledge bases or articles even if they meet other conditions.

A. sn_kb_read, sn_article_read:

These are not standard ServiceNow permissions for controlling knowledge access.

In ServiceNow, permissions are managed through roles and user criteria, not direct ACL names like these.

B. Privacy Settings:

ServiceNow does not use "Privacy Settings" as an access control mechanism for knowledge bases.

Privacy settings might be relevant in other contexts, such asuser profiles or system preferences, but not for knowledge access control.

C. Read Access Flag:

There is no "Read Access Flag" in ServiceNow's knowledge management module.

Access is controlled viaUser Criteria, Roles, and Knowledge Base Settings.

Key Features of User Criteria in Knowledge Management:Why Other Options Are Incorrect?Official ServiceNow Documentation References:For more details, refer to the official ServiceNow documentation:

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Knowledge Management User Criteria

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

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

UI forms

Import Sets

Web Services (APIs, integrations)

Enforces field validation at the database level

Ensuresdata consistencyacrossall entry points.

Reducesclient-side dependencyfor validation.

Applies uniformly regardless of how the data is entered

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

A. Network →Incorrect

Policies are not enforced at thenetwork level.

They operate within theServiceNow application.

C. Client →Incorrect

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

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

D. Browser →Incorrect

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

Why Other Options Are Incorrect?

Key Differences Between Client and Server Processing:Validation Type

Runs On

Applies To

Purpose

Data Policies

Server

UI, Import Sets, Web Services

Ensures global data consistency

UI Policies

Client (Browser)

Forms (User Interface)

Controls form behavior dynamically

Client Scripts

Client (Browser)

Forms, Fields

Runs JavaScript in the user's browser

Business Rules

Server

Database Transactions

Executes logic when records are inserted, updated, or deleted

Data Policies in ServiceNow

UI Policies vs. Data Policies

Official ServiceNow Documentation Reference:

InServiceNow Knowledge Management,User Criteriais used to controlwho can view, contribute, or editknowledge articles and knowledge bases.

Scenario Requirements Breakdown:TheHR Knowledge Baseis already restricted to HR department members.

Anew knowledge articleneeds to be published in theQuarterly Reviewcategory.

OnlyHR Managersshould be able to read this specific article.

Best Approach (Correct Answer: D)Torestrict access to the article itself(not the entire knowledge base or category), we:

Open the knowledge article

Go to the "Can Read" field

Add a User Criteria that includes the "HR Manager" group

Publish the article

This ensures thatonly HR Managers can read this specific articlewhile the rest of the HR departmentcannotsee it.

A. On the Knowledge Base, add User Criteria with a Manager Can Read script to the Can Read list, publish article to any category

This would restrictall articlesin the knowledge base, not just the single article.

B. Add User Criteria for HR Manager Group on the Category’s Can Read list

User criteria canonly be applied at the Knowledge Base or Article level, not at the category level.

C. On the Knowledge Article, add an Access Control for HR Manager Group on the Can Read list, then publish article to any category

ACLs (Access Controls)are not used forKnowledge Article permissions. User Criteria is the correct method.

Managing User Criteria in Knowledge Management

Restricting Article Access

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

InServiceNow, theimpersonation featureallows users totemporarily act as another userwithout having to log out and log back in. This is particularly useful fortesting and troubleshooting.

Allows Users to Switch Between Accounts Without Logging Out

Users with theimpersonator rolecanimpersonate other usersfrom theUser Menu(top-right of the screen).

This allows them tosee what the other user sees, includingroles, permissions, and UI settings.

Commonly Used in Testing and Troubleshooting

Helpstest permissions, workflows, and security settingswithout needing multiple login sessions.

QA and testing teams often useimpersonationto validate how different users interact with the system.

Does Not Grant Admin-Level Permissions

Unlike theadmin role,impersonatoronly allows switching between users, without providing system-wide control.

Why is "impersonator" the Correct Answer?

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

SelectImpersonate Userfrom the dropdown.

Search for and select the user to impersonate.

ServiceNow will reload, and you will now be acting as that user.

How to Impersonate a User in ServiceNow:

A. service_deskIncorrect– This is a functional role forService Desk agentsbutdoes not allow impersonation.

C. adminIncorrect– Whileadmins can impersonate users, theadmin role is not requiredfor impersonation. Theimpersonator role alone is sufficient.

D. incognitoIncorrect– No such role exists inServiceNow.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Impersonation Feature????How to Impersonate a User

ServiceNow Docs – Roles and Permissions????Understanding the Impersonator Role

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. impersonator

Theimpersonator roleallows users toswitch between user accountswithout logging out, making it ideal fortesting and troubleshooting.

To monitor which users are performing impersonations in a ServiceNow instance, administrators can activate thesystem propertyglide.sys.log_impersonation. When enabled, this property logs impersonation activities in the system logs, providing full traceability of who is impersonating whom.

Here’s how it works:

By default, impersonation is not loggedunless this system property is explicitly activated.

Once enabled, all impersonation activities are recordedin thesyslogtable (System Log > All), making it easy to track when and by whom impersonations were performed.

This helps in security audits and compliance tracking, ensuring that only authorized users impersonate others in the system.

????Steps to Enable Logging of Impersonations:

Navigate toSystem Definition > System Properties.

In the filter navigator, search forglide.sys.log_impersonation.

Set the value totrue.

Save the changes.

????Alternative Verification Methods:

Check logs manually: Navigate toSystem Logs > Alland filter logs bymessagecontaining"impersonation".

Audit the impersonation role assignments underSystem Security > Roles.

????Reference:

ServiceNow KB Article:KB0717055 – How to Log Impersonations

ServiceNow Docs: Logging and Monitoring in ServiceNow

InServiceNow, thetable configuration pageallows administrators tomodify table settings, fields, relationships, and properties.

To access this page from aform view, you must use theForm Context Menu (☰in the top-left corner of the form)and navigate to:

????Configure > Table

This willopen the Table Configuration Page, where you can:

View and edittable properties.

Managefields, relationships, and indexing.

Configuresecurity settings (ACLs)for the table.

Open a record in a form view(e.g., a Catalog Task form).

Click the Form Context menu(☰at the top-left).

Select "Configure"from the dropdown.

Click "Table"to access theTable Configuration Page.

Step-by-Step Navigation:

Why "Configure > Table" is the Correct Answer?Directly accesses the table's configuration page

Allows modification of table-level settings

Best practice method for modifying table properties

A. The Form Context menu > View > TableIncorrect– There is no"View > Table"option in the context menu.

C. The Form Context menu > Configure > DictionaryIncorrect– The"Dictionary"option allowsediting individual field propertiesbutnot the entire table configuration.

D. The Form Context menu > View > Show TableIncorrect– No such"Show Table"option exists in theForm Context Menu.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Configuring Tables????Table Administration

ServiceNow Docs – Modifying Table Properties????Configuring a Table

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

B. The Form Context menu > Configure > Table

This is the correctnavigation pathto access thetable configuration pagefrom a form in ServiceNow.

Employee Self-Service (ESS)is the interface in ServiceNow that allows employees to:

Search for knowledge articles.

Submit service requests.

View notifications and communication updates.

ESS is designed to provide a simple, user-friendly interface for employees to interact with IT and other departments.

Explanation of Incorrect Options:

Customer Service Management (A)→ Used for customer support,not internal employee requests.

Service Portal (B)→ A broader framework that ESS can be built on, butESS is the specific user interfacefor employee interactions.

One Stop Shop (D)→ Not a standard ServiceNow term or interface.