Exactprep CSA Questions

In ServiceNow, Client Scripts are scripts that execute in the user's web browser rather 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.

Runs in the web browser when a form is loaded, changed, or submitted.

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

Uses GlideForm (g_form) and GlideUser (g_user) APIs.

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

A. Server script:

Runs on the server-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:

When importing spreadsheet data into ServiceNow, the first step is to Define a Data Source.

A Data Source defines where the data is coming from (e.g., Excel, CSV, JDBC connection).

It establishes the format and structure of the incoming data before it can be processed by an Import Set.

Without defining the Data Source, the system does not know how to handle the incoming data.

Define Data Source – Identify where the data is coming from.

Create Import Set – Temporarily store the imported data.

Set Coalesce – Define unique identifiers to prevent duplicate records.

Transform Data – Map fields to the target table.

Run the Import – Move data into the actual ServiceNow tables.

A. Create Import Set – Import Sets store the data, but they are created after defining the data source.

B. Run Data Scrubber – No such step exists in ServiceNow's import process.

C. Set Coalesce – Coalescing ensures no duplicate records, but it happens after data is loaded into the import set.

E. Select Import Set – The Import Set is selected after defining the data source and loading the data.

ServiceNow Data Import Process

ServiceNow CSA Training Module: "Importing Data into ServiceNow"

Why Defining a Data Source is the First Step?Steps in the Data Import Process:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Detailed Explanation:To assign a task to themselves, users in ServiceNow can:

Option A: Use the check box to select the record, then click the Person icon to assign it.

Option B: Select the Task number and use the Assign to me UI action available on the form. These methods provide quick ways for users to take ownership of tasks directly from the list view. (Reference: ServiceNow Documentation - Task Assignment and List Actions)

The Configuration Management Database (CMDB) in ServiceNow is a core component of IT Service Management (ITSM), allowing organizations to track Configuration Items (CIs) and their relationships. There are three key tables that form the foundation of the CMDB:

cmdb (Base CMDB Table):

This is the parent table for all Configuration Items (CIs) in the CMDB.

It contains the foundational structure upon which all other CMDB-related tables are built.

It does not store CI records itself but serves as the primary reference table.

cmdb_ci (CI Base Class Table):

This is the base class for all Configuration Items (CIs).

All specific CI classes (such as servers, applications, networks) extend from this table.

It holds general CI attributes that are common across all CI types.

cmdb_rel_ci (CMDB Relationship Table):

This table defines relationships between different Configuration Items.

It stores dependencies and associations between CIs, such as a server hosting an application.

Relationships are critical for impact analysis and dependency mapping.

B. sn_cmdb_bak & E. cmdb_bak:

These tables do not exist in the standard CMDB schema. They may be mistaken for potential backup tables, but they are not official CMDB tables.

D. sn_cmdb & G. sn_cmdb_ci:

Prefix "sn_" generally indicates Scoped Application Tables in ServiceNow.

Standard CMDB tables exist in the global scope without the "sn_" prefix.

"sn_cmdb" and "sn_cmdb_ci" are not key tables in the global CMDB architecture.

Official ServiceNow CSA (Certified System Administrator) Training Documentation

ServiceNow Product Documentation: CMDB Tables and Relationships

ServiceNow CMDB Overview and Best Practices: CMDB Guide

Incorrect Answer Choices Explained:References: