CSA Exam Dumps - ServiceNow Certified System Administrator

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:

To translateService Catalog itemsinto multiple languages in ServiceNow, theTranslation Framework plugin (com.glide.translation_framework)must be activated. This plugin enablesautomatic translation of text fields, including:

Service Catalog items

Knowledge Base articles

Field labels

UI components

Providesmulti-language supportfor catalog items.

Usesmachine translation or manual translation mapping.

Works with theServiceNow Language Packsto provide localized experiences.

Key Features of the Translation Framework Plugin:

TheTranslation Framework plugin (com.glide.translation_framework)is specifically designed to supportmulti-language content translationfor the Service Catalog.

It allows translation of catalog item descriptions, labels, and options without custom scripting.

Why " B. Translation Framework Plugin " is the Correct Answer?

A. Localization Framework Plugin (com.glide.localization_framework) – Incorrect

This plugin helps withlocalization settingsbut is not specifically for catalog item translation.

C. Multiple Language Framework Plugin (com.glide.multiple.language_framework) – Incorrect

No such plugin exists in ServiceNow.

D. Language AI Framework Plugin (com.glide.language.ai_framework) – Incorrect

This is not a valid ServiceNow plugin.

Explanation of Incorrect Options:

ServiceNow Docs: Translation Framework Plugin

ServiceNow CSA Study Guide – Multi-language Support

ServiceNow Product Documentation: Translating Service Catalog Items

References from Certified System Administrator (CSA) Documentation:

InServiceNow, Favorites allow users to quickly access frequently usedmodules, records, lists, or reports. Favorites can be customized, including renaming them, changing their icons, or modifying their colors.

Changing the Label of a FavoriteTorename or edit a Favorite, you must use thePencil icon (✏️), which indicatesedit mode.

Navigate to theApplication Navigatoron the left-hand side.

Locate theFavoritessection.

Hover over the favorite item you want to rename.

Click on thePencil icon(✏️) to open the edit menu.

Update thelabel(name) and other properties like color or icon.

ClickSaveto apply changes.

A. Clock(Incorrect)

TheClock icontypically representsrecently accessed items, not Favorites.

B. Hamburger(Incorrect)

TheHamburger menu (☰)represents navigation menus but is not used to edit Favorites.

D. Three dots(Incorrect)

TheThree dots (â‹®)often indicate a menu with additional options but do not specifically edit Favorites.

E. Triangle(Incorrect)

NoTriangle iconis used for renaming Favorites.

F. Star(Incorrect)

TheStar icon (⭐)is used toadd or removeFavorites, but not to rename them.

ServiceNow Favorites Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateFavorites.html

Steps to Change the Label of a Favorite:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

In ServiceNow, when applying filters, theFunnel iconopens the condition builder, allowing users to set criteria for displaying records.

Understanding the requirement:

The user wants to seeIncidents where the state is ClosedORIncidents where the Assignment Group is Network.

The key word here isOR, meaning records satisfyingeithercondition should be displayed.

Steps to apply this filter in ServiceNow:

Click theFunnel iconto open the condition builder.

Define thefirst condition→ SelectState = Closed.

Click theORbutton (since we want records meeting either condition).

Define thesecond condition→ SelectAssignment Group = Network.

PressEnterto apply the filter.

Since the user wantseither condition to be true,ORis the correct logical operator.

PressingEnterafter defining the second conditionexecutes the filter.

A. Define the first condition; click AND button; define second condition; click Run:Incorrect becauseANDwould requireboth conditions to be true simultaneously, which is not what the user wants.

B. Define the first condition; click AND button; define second condition; press enter:Same issue as option A—AND willnarrow the resultsinstead ofexpanding them.

D. Define the first condition; click > icon on breadcrumb, define second condition; click Run:Thebreadcrumb navigationis used to modify filtersafter applying them, not to create them initially.

E. Define the first condition; click > icon on breadcrumb, define second condition; press enter:Same issue as option D—breadcrumb navigation is for modifying, not for initial filter creation.

Using Filters and Condition Builder in ServiceNow:ServiceNow Docs

ServiceNow Querying and Filtering Best Practices

Why is the Correct Answer " C " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:UsingORensures both conditions are considered independently, displaying incidents that are eitherClosedor assigned toNetwork.

Update Setsare the standard way to capturecustomizationsand move them from one ServiceNow instance to another. These customizations include:

Business Rules

UI Policies

Script Includes

Fields and Tables

Workflows

Update Setstrack changes in an instance and allow them to beexportedandimportedinto other environments (e.g., fromDevelopmenttoTestand then toProduction).

They ensure thatconfiguration changesare preserved and applied consistently across instances.

Why is Option A Correct?Why Are the Other Options Incorrect?B. Code Sets

There is no concept ofCode Setsin ServiceNow.

C. Update Packs

Update Packsdo not exist in ServiceNow. The correct term isUpdate Sets.

D. Configuration Logs

Configuration Logsrecord system activity butdo not package customizationsfor migration.

E. Remote Sets

Remote Update Setsexist, but they are just a variation ofUpdate Setsused when moving changes betweenremote instances.

The broader term " Update Sets " is more accurate.

F. Local Sets

No such termexists in ServiceNow.

G. Code Packs

There is no " Code Pack " in ServiceNow.

ServiceNow CSA Guide - Update Sets and Customization Migration

ServiceNow Developer Documentation - Using Update Sets

ServiceNow Best Practices - Moving Configuration Between Instances

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default.

Homepages (A) –Correct

Homepages are stored asuser-specific or global content, and they are not included in update sets by default.

To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable.

Data (B) –Correct

Update Setsdo not include actual data, such as incident records, user records, or CMDB data.

Onlyconfiguration changes(like fields, forms, and workflows) are captured.

Data migration must be handled separately usingData Export or Integration methods.

Published Workflows (C) –Correct

Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set.

To capture it, you mustmanually updatethe workflow before moving it in an Update Set.

Report Definitions (H) –Correct

Reports and their configurations are not automatically included in Update Sets.

You mustmanually include themby marking them as " Captured in Update Set. "

D. Business Rules(Captured in Update Sets)

E. Schedules(Captured in Update Sets)

F. Database changes(Captured in Update Sets)

G. Related Lists(Captured in Update Sets)

I. Scheduled Jobs(Captured in Update Sets)

J. Client Scripts(Captured in Update Sets)

K. Views(Captured in Update Sets)

ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/c_UpdateSets.html

ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/update-set-best-practices.html

Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default):Official References from 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: