Pass CSA Exam Guide

When creating acustom table in ServiceNow, the platform automatically assigns a table name prefixed with " u_ " to differentiatecustomtables fromout-of-the-box (OOB) tables.

The default prefix " u_ " is applied to allcustom global tables.

The table name follows the format: " u_ " + [custom name].

Example:

If you create a table named " abc " , the system assigns it the table name:u_abc.

All custom tables created by usersautomatically receive the " u_ " prefix.

Prevents conflicts withServiceNow’s internal tables.

Ensurescustom tables are easy to identify.

Naming Convention for Custom Tables:Why " C. u_abc " is Correct?

A. snc_abc – Incorrect

" snc_ " is not used for custom tables; it is reserved forinternal ServiceNow functionality.

B. abc – Incorrect

Custom tablesdo not use raw names; they always include a prefix (u_).

D. sys_abc – Incorrect

" sys_ " is reserved forsystem tables(e.g.,sys_user,sys_db_object).

Explanation of Incorrect Options:

ServiceNow Docs: Creating Custom Tables

ServiceNow CSA Study Guide – Table Administration

ServiceNow Product Documentation: Understanding Table Naming Conventions

References from Certified System Administrator (CSA) Documentation:

InServiceNow IntegrationHub, third-party API integrations within aFlow Designerflow are known asspokes. Aspokeis a scoped application containingFlow Designer actions and subflowsthat allow the flow to interact with external systems or ServiceNow applications.

Spokes in IntegrationHub

Aspokeis a collection ofpredefinedandcustomactions, subflows, and data streamsused to integrate with external systems.

Spokes provide ano-code/low-codeapproach to integrating third-party applications.

Examples ofprebuilt spokesavailable in ServiceNow include:

Slack Spoke(for Slack API integrations)

Microsoft Teams Spoke(for Teams integration)

Jira Spoke(for integrating with Atlassian Jira)

How Spokes Work

When a flow needs to interact with an external system (e.g., sending data to Jira or retrieving information from Slack), itcalls an action from a spoke.

Each spoke containsmultiple predefined actionsthat execute API requests or perform tasks like creating records, updating data, or fetching information.

Comparison with Other Options

A. an action→ Incorrect

Actions are individual steps in a flow, not the complete integration package. Actions exist inside spokes.

C. a connection→ Incorrect

Aconnectionis a configuration that stores authentication details (e.g., API keys, OAuth tokens) used by a spoke.

D. an integration step→ Incorrect

No such term as “integration step” exists in ServiceNow IntegrationHub.

ServiceNow Docs - IntegrationHub

ServiceNow Docs - Spokes in Flow

Key Concepts Related to IntegrationHub and SpokesOfficial References from the Certified System Administrator (CSA) Documentation:

In ServiceNow, theEvent Registryis a module thatstores and defines all system eventsthat can be triggered within the platform. Events in ServiceNow are used to trigger business rules, notifications, workflows, and integrations based on specific system activities.

TheEvent Registry [sysevent_register]table containspredefined and custom event definitions.

It allowsdevelopers and administratorsto definenew custom events.

Events can betriggered manually (via scripts) or automaticallybased on system actions.

Events arenot tied to a specific timeframebut are available for use whenever triggered.

Triggering a Notification

When an incident is assigned, an event such as " incident.assigned " is triggered, which can send an email notification to the assigned user.

Initiating an Automated Workflow

When a new user is onboarded, an event like " user.onboarded " can trigger a workflow to create necessary accounts and permissions.

Logging Custom Events for Reporting

Custom events like " asset.verified " can be used to track when an asset verification process is completed.

Key Features of the Event Registry:Example Use Cases of the Event Registry:

TheEvent Registryisnot a log of completed eventsbut arepository of event definitionsthat can be triggered.

It defines bothdefault and custom eventsthat can be used across different system processes.

It is used forevent-driven automationin ServiceNow.

Why " C. The Event Registry is a module that provides Event definitions " is the Correct Answer?

A. The Event Registry lists all Events that have successfully completed within a 24-hour period – Incorrect

This describes theEvent Log [sysevent]table, not the Event Registry.

B. The Event Registry is a list of all Events that originate through an integration – Incorrect

TheEvent Registryis not specific to integrations; it applies to all events in the system.

D. The Event Registry is a list of all Events that have successfully completed after being Invoked by a script – Incorrect

Events triggered by scripts are logged in theEvent Log, not theEvent Registry.

Explanation of Incorrect Options:

ServiceNow Docs: Understanding the Event Registry

ServiceNow CSA Study Guide – Event Management

ServiceNow Product Documentation: Creating and Managing Events

References from Certified System Administrator (CSA) Documentation: