ServiceNow CSA - ServiceNow Certified System Administrator

InServiceNow Notification Configuration, dot-walking allows administrators to reference related records dynamically.

✔To send a notification to theCaller ' s Manager, you need to:

Open theNotification record.

Navigate to the‘Send to’ tab.

Add theCaller field.

Usedot-walkingto select theCaller ' s Manager field(e.g., caller_id.manager).

Option Ais incorrect because dot-walking is configured under the‘Send to’ tab, not the‘Who will receive’ tab.

Option Bis incorrect because while Flow Designer can trigger notifications, it does not specifically configure recipients based on dot-walking.

Option Cis incorrect because setting " Who will receive " toSubscribableis used for opt-in notifications, not direct notifications to the Caller ' s Manager.

📌 Reference:ServiceNow Administration – Notification Configuration & Dot-Walking

Detailed Explanation:

To edit the title of an application menu in ServiceNow:

Option C:Using the Navigator, selecting the application name, and clicking the pencil icon allows quick title adjustments.

Option D:Going toSystem Definitions > Application Menusand selecting the application provides comprehensive options for editing the application menu title and related settings. These approaches streamline menu customization and improve navigation. (Reference: ServiceNow Documentation - Application Menu Customization)

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

In ServiceNow, when viewing alist view, you can easily filter out specific values byright-clicking on the field value and selecting " Filter Out " . This action dynamically updates the filter to exclude records with that value.

Navigate to theIncident List.

Locate a record withState = Resolved.

Right-clickon the " Resolved " value in theStatecolumn.

Select " Filter Out " from the context menu.

The list automatically refreshes, showing only incidentsexcluding " Resolved " .

A. On the list of records, locate the right-click on the Resolved value, select Exclude.

" Exclude " isnot an optionin the ServiceNow list filter menu. The correct option is " Filter Out " .

B. Click Funnel icon, click AND, Select Resolved, is Not State click Run.

Thefunnel iconopens the filter panel, but this answer is unnecessarily complex.Right-clicking and filtering out is faster.

C. On state column title, right-click, select Filter Out > Resolved.

Youcannot right-click the column titleto filter out a specific value; you must right-click on aspecific field value.

D. On Search, select State, type not Resolved, press enter.

The correct syntax in the filter bar is " State != Resolved " , butright-clicking is a more user-friendly method.

ServiceNow Filtering and List Views

ServiceNow CSA Training Module: " Working with Lists and Filters "

Steps to Exclude Incidents with the State " Resolved " :Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Service Catalog, approvals forcatalog item requestsare handled through workflows. Since the approval policy is based on thetotal cost of a request, it is managed within theService Catalog Request workflow.

C. Service Catalog Request

This workflowhandles approvals for catalog item requests, includingpurchase approvals.

Since the policy change involvesadjusting an approval threshold, this workflow needs to be updated.

The approval logic is likely configured in aconditional activity (if total cost > $3,100, require approval), which must be modified to$3,150.

A. Services Approval Processing

Not a standard ServiceNow workflowfor managing purchase approvals.

Service approvals are typically handled within theService Catalog Requestworkflow.

B. 6 Services Catalog Item Request

Likely acustom workflow, but not adefault ServiceNow workflowfor purchase approvals.

D. Purchasing Process Flow

There isno default " Purchasing Process Flow " in ServiceNow.

Theapproval workflow for purchasesis managed withinService Catalog Request workflows.

When selecting aTarget Tablefor anImport Set, you must choose a table that exists within the ServiceNow system and falls within your scope of permissions. The following types of tables are eligible as target tables:

Tables within the Global Scope(A - Correct Answer)

If the table exists within theglobal application scope, it is accessible from all applications.

Example:Task [task],User [sys_user] ,Configuration Item [cmdb_ci]

Tables within the Existing Application Scope(B - Correct Answer)

Tables belonging to the same application scope as the import set can be selected.

Example: If you are working in a scoped application likeHR Service Delivery, you can import data intoHR-related tables.

Related Tables Using Dot Walk(E - Correct Answer)

You can select related tables usingdot-walkingto reference data from linked tables.

Example: If importing intoIncident [incident], you can reference data fromCaller (sys_user)via dot-walking.

C. Tables outside of ServiceNow

ServiceNowcannotdirectly import data into external databases or non-ServiceNow tables.

Instead, you can export data to an external system after processing.

D. Tables which allow write access to other applications

ServiceNow enforcesscope protection, so you cannot write to tables in a different application scope unless explicitly allowed.

You needcross-scope privilegesto modify tables in another application.

Importing Data into ServiceNow

Understanding Application Scope

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow,Core Tablesare foundational tables that are included by default in the platform. These tables store essential records used across various applications and modules.

🔹 Key Core Tables in ServiceNow:

Task (task)– A core table that serves as the parent for several other tables, such as Incident, Change, and Problem.

User (sys_user)– Stores all user records in the instance.

Incident (incident)– A child table oftask, used to track issues and requests reported by users.

🔹 Why Option C is Correct?

User (sys_user)– Essential for user management in ServiceNow.

Task (task)– A fundamental table that many other tables extend from.

Incident (incident)– A widely used table in IT Service Management (ITSM), which extends fromtask.

🔹 Incorrect Options Explained:

A. Configuration, Connect, Chat– Configuration is broad and does not refer to a single table, and Connect and Chat are part of ServiceNow’s communication framework but are notcoretables.

B. Team, Party, Awards– These tables do not exist in ServiceNow’s core platform.

D. Work, Caller, Timecard– WhileCallermay refer to users, andTimecardis a table used in time-tracking applications, these are not considered core tables.

📌 Reference:

Creating Tables in ServiceNow

ServiceNow Task Table Documentation

Understanding Core Tables in ServiceNow

The Dependency View provides a visual representation of the relationships between configuration items (CIs) in ServiceNow. It allows you to see how CIs are connected and how changes to one CI may impact others.

In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.

Definition of a Role:

Aroleis a collection ofpermissionsthat grant access to different parts of the system.

Example:Theadminrole grants full access, while theitilrole allows incident management access.

sys_user_role Table:

This tablestores role recordsand their associated metadata.

Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).

Users are linked to roles through thesys_user_has_roletable.

How Roles Work in ServiceNow:

A user assigned a role gainsall the permissionsassociated with that role.

Roles can behierarchical(one role can inherit permissions from another).

Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.

Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.

B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.

C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.

ServiceNow Docs – Roles and Role Managementhttps://docs.servicenow.com

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

References from Certified System Administrator (CSA) Documentation:

Thesix methods available for user authenticationin ServiceNow are:

Local Database– The user authenticates using a username and password stored in theinstance database.

Multifactor Authentication (MFA)– The user provides their username, password, and apasscode(e.g., from Google Authenticator).

LDAP (Lightweight Directory Access Protocol)– The user authenticates using credentials stored in a corporateLDAP directory.

SAML 2.0 (Security Assertion Markup Language)– The user is authenticated via an externalSAML Identity Provider (IdP).

OAuth 2.0– The user authenticates via anOAuth identity provider(such as Google, Microsoft, or Facebook).

Digest Token Authentication– The user authenticates using anencrypted tokenrather than directly submitting a password.

Thus, the correct answer is:

A, B, C, D, E, F

ServiceNow supports multiple authentication methods to provideflexibility, security, and integration capabilitieswith external identity providers.

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

This method is commonly used when no external authentication provider is configured.

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

Passcodefrom a registered device (such as Google Authenticator, Microsoft Authenticator).

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

Allows users toauthenticate against an external LDAP directory(such as Microsoft Active Directory).

The user must have amatching record in the ServiceNow user table ([sys_user]).

ServiceNowdoes not store passwordswhen using LDAP; it only validates credentials against the directory.

SAML 2.0 Authentication:

Users authenticate via aSAML Identity Provider (IdP)such asOkta, Microsoft Azure AD, or Ping Identity.

ServiceNow acts as aService Provider (SP)and does not store passwords.

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

Allows authentication viaOAuth providers(Google, Facebook, Microsoft, etc.).

Users do not need to store passwords in ServiceNow; instead, authentication is delegated to theOAuth identity provider.

Digest Token Authentication:

Uses anencrypted token(instead of a plaintext password) to authenticate users.

Often used forAPI-based authenticationor scenarios where passwords should not be transmitted over the network.

Each method aligns with ServiceNow ' s authentication mechanisms as per official documentation.

ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.

ServiceNow Docs – Authentication Methodshttps://docs.servicenow.com

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

Why These Are the Correct Methods?References from Certified System Administrator (CSA) Documentation:

AnUpdate Setin ServiceNow is a mechanism thattracks and packages customizations and configuration changesso they can be transferred between instances (e.g., fromDevelopmenttoTestorProduction).

It is primarily used ininstance migrationandchange management, ensuring that changes made in one environment can beapplied consistentlyin another.

Tracks Customizations– Records changes to system configurations, such as Business Rules, Client Scripts, UI Policies, and Workflows.

Facilitates Deployment– Enables controlled migration of changes from one ServiceNow instance to another.

Reduces Manual Effort– Instead of manually reconfiguring settings in different environments, administrators can package updates into asingle unit.

Version Control– Ensures that onlyintended changesare moved between instances.

Key Features of Update Sets:

Why the Correct Answer is A:A. An Update Set allows administrators to group a series of changes into a named set and then move this set as a unit to other systems(Correct)

This accurately describes the primary function of anUpdate Set.

Administratorsgroupmultiple changes into anUpdate Set, export it, and apply it to another instance.

Example Workflow:

Admin makes configuration changes(e.g., modifies a Business Rule, updates a Workflow).

Update Set captures those changesin a structured format.

The Update Set is exportedfrom the Development instance.

The Update Set is importedinto the Testing/Production instance and applied.

Why the Other Options Are Incorrect:B. By default, an Update Set includes customizations, Business Rules, and homepages(Incorrect)

Update Setsdo include customizations and Business Rules, but theydo notinclude homepages by default.

Dashboards and homepagesrequire a separate process usingsys_portal_page and sys_ui_page tables.

C. An Update Set is a group of customizations that is moved from Production to Development(Incorrect)

Update Sets are typically movedfrom Development to Test/Production, not the other way around.

Best practice is to make changes inDevelopment, test them inTest/UAT, and then deploy them toProduction.

D. By default, the changes included in an Update Set are visible only in the instance to which they are applied(Incorrect)

This is misleading becausean Update Set can be exported and applied to multiple instances.

Once an Update Set isimported and committed, its changes become active in that instance.

Best Practices for Using Update Sets:✔Always preview an Update Set before committing itto ensure it contains the correct changes.

✔Use Named Update Sets, not the default " Default Update Set, " to track changes effectively.

✔Ensure all related changes are included(e.g., dependencies such as script includes and tables).

✔Test Update Sets in a sub-production instancebefore applying them inProduction.

InServiceNow, theNumber Maintenanceapplication is used toconfigure and modify numbering formats for specific tables. This application allows administrators to control how records are numbered across different modules.

Customization of Number Formats

Administrators can defineprefixes, number sequences, and suffixesfor records in different tables.

Example:INC0001001forIncidents,REQ0002001forRequests.

Resetting or Adjusting Number Sequences

You can manually adjust the numbering sequence if needed.

Example: Resetting incident numbering to start from a specific value.

Supports Multiple Tables

Works for standard tables likeIncidents, Problems, Requests, Change Requests, etc.

Can also be configured forcustom tables.

Application Navigation

Path:

Go toAll → System Definition → Number Maintenance

Locate the table and modify its numbering settings.

Key Features of Number Maintenance:Why Option A (Number Maintenance) is Correct? " Number Maintenance " is the official ServiceNow application for managing number formats per table.

Why Other Options Are Incorrect?B. System Maintenance– Incorrect; no such module in ServiceNow manages numbering formats.

C. Table Maintenance– Incorrect; this does not exist as an application in ServiceNow.

D. Record Maintenance– Incorrect; not a valid ServiceNow feature for modifying number formats.

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

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow System Definition – Number Format Best Practices

References from Certified System Administrator (CSA) Documentation:

InServiceNow, aRecordrepresents all thedata saved within a particular form. Each record corresponds to a single entry in atableand contains multiplefieldsstoring different pieces of information.

ARecordis asingle instanceof data stored in a ServiceNowtable.

When a user fills out and submits aform, arecord is createdor updated in the respective table.

Each record has a uniqueSys ID(a 32-character identifier).

Example:

AnIncidentrecord contains fields such asNumber,Caller,Short Description, andPriority.

AChange Requestrecord contains fields likeChange Number,Requested By, andAssignment Group.

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

AFormis auser interfaceto enter and display data, but it does not store data itself.

It is just a way tointeract with records.

D. Lists

AListdisplaysmultiple recordsfrom a table, but each row in a list represents asingle record.

Lists are used for filtering, sorting, and searching records but do not represent a single data entry.

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

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

In ServiceNow,Tables & Columnsis the module that allows administrators to view and managefield settingsfor a table. This module provides a list of tables in the system along with details about theircolumns (fields), data types, and attributes.

Displaysall fields (columns)within a selected table.

Showsdata types, attributes, and configurationsof each field.

Allows admins toadd, modify, or removefields.

Provides details onrelationships between tables(e.g., reference fields, one-to-many relationships).

Navigate to:System Definition > Tables & Columns

Select a table to view itsfield settings.

B. Access Control – Incorrect

This module managessecurity rules (ACLs)for accessing records but does not display table field settings.

C. Columns and Fields – Incorrect

No such module exists in ServiceNow.

D. Tables and Fields – Incorrect

The correct module name is " Tables & Columns " , not " Tables and Fields " .

ServiceNow Docs: System Definition – Tables & Columns

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Managing Fields in a Table

Key Features of the " Tables & Columns " Module:How to Access Tables & Columns in ServiceNow:Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation: