ServiceNow Updated CSA Exam Questions and Answers by sydney

In Flow Designer, a Flow Execution is initiated by a trigger. A trigger determines when and under what conditions a flow starts.

Record-Based Trigger

Executes the flow when a record is created, updated, or deleted in a specific table.

Example: A flow runs when an Incident is created with a specific priority.

Schedule-Based Trigger

Executes the flow at a specific time or on a recurring schedule.

Example: A flow runs every Monday at 8 AM to check overdue tasks.

Application-Based Trigger (Inbound Actions, API Calls, or Events)

Executes the flow when a specific event occurs in ServiceNow.

Example: A flow runs when an email is received in ServiceNow.

Types of Triggers in Flow Designer:

B. An existing subflow

Subflows are reusable flows that can be called within a parent flow.

A subflow does not initiate execution on its own; it must be triggered by a flow or script.

C. Allow logic

No such term exists in Flow Designer; logic applies within a flow but does not initiate execution.

D. An execution data pill

Data pills represent stored data within a flow but do not trigger execution.

Why Other Answers Are Incorrect:

ServiceNow Flow Designer – Triggers

ServiceNow CSA Training Module: "Building Flows with Flow Designer"

References from Certified System Administrator (CSA) Official Documentation:

✔ Update Sets are the primary method for moving customizations from one ServiceNow instance to another. An Update Set records changes made to an instance, including modifications to:

Forms, fields, and tables

Business rules, scripts, and workflows

UI policies and ACLs

How Update Sets Work:

When you modify configurations, the changes are captured in an active Update Set.

The Update Set is then exported from the development instance and imported into the target instance (e.g., from Dev to Test to Production).

Once imported, the Update Set is committed, applying the changes.

Option A (Table Templates) is incorrect because these define default field structures for tables but do not move customizations.

Option B (Application Files) is incorrect because individual application files exist within Update Sets but do not serve as a transport mechanism.

Option C (UI Script Includes) is incorrect because script includes are reusable scripts, not a method for transferring configurations.

???? Reference: ServiceNow Administration – Update Sets & Instance Migration

Dot Walking is a ServiceNow feature that allows you to access and include data from related tables when creating reports, conditions, scripts, and business rules.

When working with records, each table has fields that may reference another table (e.g., an Incident record has an "Opened by" field that references the User table).

Dot Walking allows you to traverse these relationships by using a dot (.) notation to pull in data from related tables.

Example: If you want to include the email address of the user who created an incident, you can reference it as:

How Dot Walking Works:CopyEdit

incident.opened_by.email

This is useful for reporting when you need to include data from multiple related tables without needing custom joins.

A. SQL → Incorrect. ServiceNow does not use direct SQL queries for reports. It relies on GlideRecord and Dot Walking instead.

C. Outer Join → Incorrect. ServiceNow does not provide traditional SQL joins for reports. Instead, it uses Dot Walking and Database Views.

D. Joins → Incorrect. While Database Views allow for joins, Dot Walking is the primary method used to include related table data in reports.

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: