Free Practice Questions for ServiceNow CSA Exam

TheCatalog Admin [catalog_admin]role:

Inherits permissions from both:catalog role(Basic Service Catalog access)user_criteria_admin role(User Criteria management)

Has additional permissions to:Create and manage Catalog Items and ServicesConfigureCatalog Categories, Order Guides, and Variables

A. Item Admin [sn_item_admin] →Incorrect

This role does not inherituser_criteria_adminpermissions.

It isspecific to managing Catalog Itemsbut does not have full Catalog Admin permissions.

B. Sys Admin [sys_admin] →Incorrect

Thesys_adminrole has full system access but is notService Catalog-specific.

D. Catalog Author [sn_catalog_write] →Incorrect

TheCatalog Authorrole canedit catalog itemsbutcannot create new ones.

Why the Other Options Are Incorrect?

ServiceNow Catalog Roles

Official ServiceNow Documentation Reference:

In ServiceNow, toimport articlesinto aKnowledge Base (KB), a user must have thesn_knowledge_importrole.

sn_knowledge_import→ Required to import articles into a knowledge base.

sn_knowledge_contribute→ Allows users tocreate, edit, and publishknowledge articles butnot importthem.

sn_knowledge_admin→ Grantsfull administrative accessto manage the knowledge base, including permissions, categories, and workflows.

B. sn_knowledge_contribute– This role allowscontributing and editing articlesbut doesnot grant import capabilities.

C. Can contribute– Not a valid ServiceNow role; the correct role issn_knowledge_contribute.

D. Can import– Not a recognized role in ServiceNow. The correct role issn_knowledge_import.

ServiceNow Knowledge Management Roles

ServiceNow CSA Training Module:"Managing Knowledge Bases and Importing Articles"

Key Knowledge Management Roles:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Service Catalog, theUser Criteriafeature is used to specify which users are eligible to access (view or order) aService Catalog Item. User Criteria allows administrators todefine rules that determine whether a user can see or request a catalog item based on attributes such as roles, groups, departments, and locations.

User Criteria is createdto define the conditions (e.g., users in the IT department can order a laptop).

It is thenapplied to Catalog Items, Categories, or Access Control Rules.

If a user meets the criteria, they can see and order the item. If not, it remains hidden.

A. Can Read Role→ Incorrect. There is no such feature named "Can Read Role" in ServiceNow Service Catalog.

B. Catalog User Role→ Incorrect.ServiceNow does not have a predefined "Catalog User Role." However, thecatalog_adminrole can manage catalog items, but it does not control access for end users.

C. Can Order Tab→ Incorrect. This is not a valid ServiceNow feature. Ordering permissions are controlled throughUser Criteria.

TheCI Dependency Viewin ServiceNowvisualizes relationships between Configuration Items (CIs), allowing IT teams totrace dependenciesbetween infrastructure components, such as servers, applications, and services.

Relationships define dependenciesbetweenConfiguration Items (CIs)in theConfiguration Management Database (CMDB).

TheCI Dependency Viewusesrelationshipstomap infrastructure componentsand theirservice dependencies.

AServer (CI)hosts aDatabase (CI)→ The database supports anApplication (CI)→ The application provides aService (CI).

By viewingCI Relationships, you cantrace failures upstream or downstreamto understand the impact.

Key Concept: CI RelationshipsExample Scenario:

A. Service Tracer →Incorrect

No such feature called"Service Tracer"exists in ServiceNow.

B. Automapping Utility →Incorrect

Auto-Discovery toolshelp populate theCMDB, but they do not enable tracing in theCI Dependency View.

D. Transform Map →Incorrect

Transform Mapsare used inImport Setsto map data between tables,not for dependency mapping.

Why Other Options Are Incorrect?

CI Dependency Views

Understanding CMDB Relationships

Official ServiceNow Documentation Reference:

In ServiceNow, every table has asystem name (platform name)that follows a consistent naming convention. TheGroup tablestores information about user groups and isnamed:

sys_user_group

sys_user_group= System table for user groups.

sys_user= Table for individual user records.

sys_user_role= Table for user roles.

B. sys_group– No such table exists in ServiceNow.

C. group– This is not the correct system name; ServiceNow uses "sys_user_group" for clarity.

D. sys_groups– Incorrect pluralization; ServiceNow tables are typically singular (e.g., sys_user, sys_user_role).

ServiceNow Tables and Data Structure

ServiceNow CSA Training Module:"User and Group Administration"

Understanding the Naming Convention:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow, impersonation allows administrators toact as another userto troubleshoot, test permissions, or verify user experiences.

Tolog impersonation eventsin theSystem Log, the system property:

CopyEdit

glide.sys.log_impersonation

must beaddedand set totrue(true).

Key Features ofglide.sys.log_impersonation:Logswho impersonated whomin theSystem Log.

Capturestimestamp, user details, and session activity.

Helps withauditing and security compliance.

Navigate toSystem Definition > System Properties.

Search forglide.sys.log_impersonation.

If it doesn’t exist, create it:

Name:glide.sys.log_impersonation

Type:True/False

Value:true

Save the property and test impersonation.

How to Enable Impersonation Logging:

A. glide.user_setting →Incorrect

Not related to impersonation logging.

Deals withuser preferences and settings.

B. glide.sys.all_impersonation →Incorrect

No such property exists in ServiceNow.

D. glide.impersonation_setting →Incorrect

Incorrect property name; does not exist.

E. glide.sys.admin_login →Incorrect

Logsadmin logins, not impersonation events.

Why Other Options Are Incorrect?

Impersonating Users in ServiceNow

System Logs & Impersonation Tracking

Official ServiceNow Documentation Reference:

UI Policiesare the preferred method to dynamically control the visibility, read-only state, or mandatory status of form fieldswithout requiring a page reload.

Best Practicesuggests usingUI Policiesover Client Scripts whenever possible because UI Policies execute on the client side and are easier to manage.

Theydo not require scriptingin most cases and provide asimple rule-based approach.

Explanation of Incorrect Options:

Client Scripts (A)→ Used for executing JavaScript logic in the browser, but making fields mandatory or hidden should be done via UI Policies.

Business Rules (C)→ Run on the server-side and do not directly affect form fields in real-time.

UI Actions (D)→ Used for creating buttons, links, or context menu actions;not for modifying field properties.

To rename a field label in ServiceNow (such as changing "Priority" to "PValue"), you must eitherupdate the dictionary definitionorchange the field label.

Right-click on the "Priority" field labelin the form.

Select"Configure Dictionary".

Update the"Label" fieldto "PValue".

Save the changes.

The new label will now be reflected across the system where applicable.

Right-click on the "Priority" field labelin the form.

Select"Configure Label".

Update thelabel textto "PValue".

Save the changes.

This methodonly changes the field labelfor display purposeswithout affecting the underlying database structure.

B. Right-click on Priority and select Configure Display Settings

There isno "Configure Display Settings"option when right-clicking on a field label in ServiceNow.

D. Right-click on Priority and select Configure Column

"Configure Column" is used forlist views, not for changing field labels on forms.

ServiceNow Field Labels and Dictionary

ServiceNow CSA Training Module:"Configuring Forms and Fields"

Option 1: Configure Dictionary (Recommended for Full Customization)Option 2: Configure Label (Quick Change for Display Purposes)Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation: