CSA Exam Dumps - ServiceNow Certified System Administrator

InServiceNow List Views, users cancustomize and personalizethe displayed columns to fit their needs.

Open anylist view(e.g., Incidents, Requests).

Click theGear icon (âš™)in the top-right corner of the list.

ThePersonalize List Columnswindow appears.

Select or remove columns as needed.

ClickSaveto apply changes.

Steps to Personalize List Layout (Columns):This customization isuser-specific, meaning it only affects the logged-in user’s view.

B. Select the column to be personalized > Click Edit icon (Penal) > Choose options to personalize

NoEdit icon (Pencil) for column customizationexists in List Views.

C. Context Menu > View > Personalize

TheContext Menu (right-click menu)allows you to filter or sort data but doesnot customize columns.

D. Select the column to be personalized and right-click the header > Choose options to personalize

Right-clicking the column header providessorting and grouping options, not full column customization.

TheConfiguration Management Database (CMDB)inServiceNowstores information aboutconfiguration items (CIs)and theirrelationships.

cmdb (Configuration Management Database)The main parent table for all CMDB-related data.

Storescore configuration item (CI) data.

Other CMDB-related tables inherit from this table.

cmdb_ci (Configuration Items Table)Stores individual configuration items (CIs).

Every CI (e.g., servers, network devices, software) is stored in this table or one of its child tables.

This tableextendscmdb.

cmdb_rel_ci (CI Relationships Table)Stores relationships between CIs.

Defines how CIsconnect to each other(e.g., "server hosts application").

Helps withService Mapping and Impact Analysis.

The Three Key CMDB Tables:

A. omadb_rel_ciIncorrect– Not a standard ServiceNow CMDB table.

B. sn_emdbIncorrect–sn_emdbisnot a CMDB tablein ServiceNow.

C. sn_emdb_ciIncorrect– No such table inServiceNow CMDB architecture.

E. sn_emdb_bakIncorrect– No suchbackup tablein ServiceNow CMDB.

G. emdb_bakIncorrect– No suchServiceNow CMDB tableexists.

Incorrect Answer Choices Analysis:

ServiceNow Docs – CMDB Core Tables📖CMDB Tables Overview

ServiceNow Docs – Understanding CI Relationships📖CMDB Relationship Tables

Official ServiceNow Documentation References:

To manipulate a form in real-time while the user is viewing it (the browser session), you use a Client Script.

1. Requirement Analysis:

"When Caller field is populated...": This describes an event happening in the browser before the data is sent to the database. This requires an onChange Client Script. When the "Caller" value changes, the script executes (often using GlideAjax to fetch server data) to populate the "Location" field dynamically.

"Add notice... when record is submitted": This describes an action triggered when the user clicks "Save" or "Submit." This requires an onSubmit Client Script. The script can validate data or display a message using g_form.addInfoMessage() before the form data is finalized.

2. Why other options are incorrect:

A (UI Script): UI Scripts are typically used to create reusable libraries of JavaScript that can be called from other scripts, or for global UI modifications. They are not the standard tool for specific table-level form logic like "When Caller changes on Incident."

B (Server script): Server scripts (like Business Rules) run after the browser sends data to the database. While a Business Rule could set the location after the fact, it cannot update the screen in real-time while the user is still typing, nor can it easily show a message "at the top of the page" during the submit process in the same way.

D (JavaScript): While Client Scripts are written in JavaScript, "JavaScript" is a language, not the specific ServiceNow feature/object used to configure this behavior.

Understanding Data Imports in ServiceNow:

When importing data into ServiceNow, you need to determine how incoming datamatches existing recordsto avoid duplication.

Coalescing fieldsare used to identify whether anincoming record already existsin the target table.

Why "Coalesce Fields" is the Correct Answer:

Coalescing means using specific fields as unique identifiersto determine if a record should beupdatedorinserted as a new record.

If a match is found based on the coalesce field, ServiceNowupdatesthe existing record.

If no match is found, anew record is inserted.

Why Other Answers Are Incorrect:

A. Match Fields→ Not an official ServiceNow term related to import sets. Matching is done through coalescing, but "Match Fields" is not the correct terminology.

C. Key Fields→ This is a general database term, but in ServiceNow, "Coalesce Fields" is the term used for identifying unique keys during imports.

D. Sys IDs→ TheSys IDis a unique identifier for each record in ServiceNow, but it is not used for coalescing unless explicitly set as the coalesce field.

Best Practice Solution:

Set asingleormultiplefields ascoalesce fieldsin theTransform Mapto ensure proper data deduplication.

Navigate toSystem Import Sets → Transform Maps, select the relevant transform map, and mark the coalescing fields.

Access to Knowledge Bases (KB) is controlled via User Criteria. On the Knowledge Base definition record, these criteria are attached via Related Lists (often appearing as tabs at the bottom of the form).

Can Read: This Related List defines which users, groups, roles, or companies are allowed to view articles within this specific Knowledge Base.

Can Contribute: This Related List defines who can create or modify articles.

"Available to" is terminology used in the Service Catalog, not Knowledge Management. "Can Access" and "Accessible to" are not standard Related List names for KB security.

In ServiceNow, to modify the available choices for a choice field like "Priority" on a form, an administrator must use the"Configure Choices"option. This can be accessed by:

Right-clicking the field label (e.g., Priority).

Selecting"Configure Choices"from the context menu.

Adding, editing, or removing available choice values for that field.

This method ensures that only the available choices are displayed to users.The "Priority" field in a Catalog Task is a choice field, so modifying its options requires "Configure Choices".

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: