CSA Exam Dumps - ServiceNow Certified System Administrator

UI Policies and UI Actionsare both part of theServiceNow user interface customizationbut serve different purposes.

Used todynamically change form field behaviorsbased on specific conditions.

Canmake fields read-only, mandatory, or hiddenwithout requiring scripts.

Runson the client-side (browser)to improve performance and responsiveness.

Example:

If theCategoryisHardware, theSerial Numberfield becomesmandatory.

Used tocreate buttons, links, and context menu actions.

Can executescriptsto perform specific actions when clicked.

Runs on theserver-side or client-sidedepending on configuration.

Example:

A"Save" buttonthat becomesvisible only to users with a specific role.

UI Policy(not UI Action) is responsible for making fieldsread-only, mandatory, or hidden.

UI Action(not UI Policy) is responsible for making aSave button visiblefor specific users.

ServiceNow Docs: UI Policy Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIPolicies.html

ServiceNow Docs: UI Action Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_UIActions.html

UI Policy:UI Action:Why Option A is Incorrect?References from Certified System Administrator (CSA) Documentation:

When a new table is created inServiceNowby extending another table, it followstable inheritanceprinciples. This means the newly created table (child table) receives all the fields from its parent table. Additionally, the new table can includecustom fieldsthat are unique to itself.

Here’s how inheritance works in ServiceNow when a table is extended:

Fields Inheritance:

The child table automatically inherits all fields from its parent table.

These inherited fieldscannot be removedfrom the child table but can be modified or overridden.

The child table can also have additionalcustom fieldsthat do not exist in the parent table.

Business Rules, Client Scripts, and UI Policies:

Unlike fields, these components arenot automatically inherited.

However, they can still affect the child tableif they are defined on the parent table using conditions that include the child table.

To apply them specifically to the child table, they need to beexplicitly definedfor the new table.

Access Control Rules (ACLs):

ACLs are not automatically inherited.

Each table in ServiceNow has its own set ofAccess Control Rules, which must be explicitly configured for the child table if different permissions are required.

Database Structure:

The child table creates aone-to-one relationshipwith the parent table, meaningall fields in the parent are available in the child table.

The new table is stored as a separate entity but references the parent table’s structure.

The child tableinherits all fieldsfrom the parent table.

The child table can also have its owncustom fields.

Business Rules, Client Scripts, UI Policies, and ACLs arenot automatically inherited, meaning options B and D are incorrect.

The tabledoes not archivethe parent table (making option A incorrect).

ServiceNow Product Documentation – Table Inheritance:https://docs.servicenow.com

ServiceNow Fundamentals – Table Relationships

ServiceNow Developer Portal – Extending Tables

ServiceNow Best Practices – Access Controls & Security Rules

Why Option C is Correct?References from Certified System Administrator (CSA) Documentation:

In ServiceNow, every table has a uniqueplatform name(also known as thedatabase nameorsys_id). The table that stores user records in ServiceNow is called"sys_user".

Table Name:sys_user

Purpose:Stores user records, including their roles, group memberships, and personal details.

Location in ServiceNow:You can access this table by navigating to:All → Users and Groups → Users

Key Fields in sys_user Table:

User ID (user_name)– Unique identifier for the user.

Name (name)– Full name of the user.

Email (email)– Email address of the user.

Roles (roles)– Defines user permissions in the system.

Active (active)– Indicates if the user is active in the system.

A. u_users– Incorrect. The prefixu_is typically used forcustom tablescreated by administrators. This is not a default system table.

B. sys_users– Incorrect. The correct name issys_user(singular), notsys_users. ServiceNow follows a singular naming convention for system tables.

C. x_users– Incorrect. The prefixx_is reserved forScoped Applicationscreated within an instance. The User table is a core system table, not a scoped one.

ServiceNow Product Documentation → User Administration → sys_user Table

ServiceNow Tables Reference → sys_user

ServiceNow CSA Study Guide → User and Data Administration

Understanding the sys_user Table:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

Thesix methods available for user authenticationin ServiceNow are:

Local Database– The user authenticates using a username and password stored in theinstance database.

Multifactor Authentication (MFA)– The user provides their username, password, and apasscode(e.g., from Google Authenticator).

LDAP (Lightweight Directory Access Protocol)– The user authenticates using credentials stored in a corporateLDAP directory.

SAML 2.0 (Security Assertion Markup Language)– The user is authenticated via an externalSAML Identity Provider (IdP).

OAuth 2.0– The user authenticates via anOAuth identity provider(such as Google, Microsoft, or Facebook).

Digest Token Authentication– The user authenticates using anencrypted tokenrather than directly submitting a password.

Thus, the correct answer is:

A, B, C, D, E, F

ServiceNow supports multiple authentication methods to provideflexibility, security, and integration capabilitieswith external identity providers.

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

This method is commonly used when no external authentication provider is configured.

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

Passcodefrom a registered device (such as Google Authenticator, Microsoft Authenticator).

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

Allows users toauthenticate against an external LDAP directory(such as Microsoft Active Directory).

The user must have amatching record in the ServiceNow user table ([sys_user]).

ServiceNowdoes not store passwordswhen using LDAP; it only validates credentials against the directory.

SAML 2.0 Authentication:

Users authenticate via aSAML Identity Provider (IdP)such asOkta, Microsoft Azure AD, or Ping Identity.

ServiceNow acts as aService Provider (SP)and does not store passwords.

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

Allows authentication viaOAuth providers(Google, Facebook, Microsoft, etc.).

Users do not need to store passwords in ServiceNow; instead, authentication is delegated to theOAuth identity provider.

Digest Token Authentication:

Uses anencrypted token(instead of a plaintext password) to authenticate users.

Often used forAPI-based authenticationor scenarios where passwords should not be transmitted over the network.

Each method aligns with ServiceNow's authentication mechanisms as per official documentation.

ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.

ServiceNow Docs – Authentication Methodshttps://docs.servicenow.com

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

Why These Are the Correct Methods?References from Certified System Administrator (CSA) Documentation:

In ServiceNow,metricsare essential tools used to track and measure key performance indicators (KPIs) related to IT Service Management (ITSM) processes. They help organizations assess how effectively they are meeting their objectives by collecting data over time.

Definition of a Metric:

Ametricin ServiceNow refers to a method of measuring and evaluating the performance and effectiveness ofIT service management processesover time.

It allows organizations to track changes in records and measure how long specific conditions exist within a workflow.

Key Characteristics of a Metric:

It is used toassess process performanceandevaluate efficiencywithin IT services.

It providesquantifiable datato analyze trends and improvements in Service Management.

Common use cases include trackingincident resolution times,change request approvals, andSLA compliance.

Understanding ServiceNow Metrics:Why Answer "C" is Correct:✔️"A metric is used to measure and evaluate the effectiveness of IT service management processes."

This definition aligns precisely with how ServiceNow definesmetrics—theytrack, measure, and analyzethe efficiency of various ITSM processes over time.

Metrics help organizations understand service performance trends and make data-driven decisions.

Why the Other Answers Are Incorrect:A. "A metric is a report gauge used on homepages to display real-time data."

Incorrectbecausegaugesare UI elements thatvisualizedata from reports or metrics but are not themselves metrics. Metricscollect and measuredata, whereasgaugesdisplay the information.

B. "A metric is a time measurement used to report the effectiveness of workflows and SLAs."

Incorrectbecause whiletime-based metricsexist (e.g., tracking how long an incident stays in a particular state), metrics in ServiceNow arebroaderand not limited to time measurement alone.

D. "A metric is a comparative measurement used to report the effectiveness of workflows and SLAs."

Incorrectbecause metrics are not necessarilycomparative; they areabsolute measuresof process effectiveness. Metrics provideraw performance data, which can later be compared or analyzed over time.

ServiceNow CSA Study Guide – Reporting & Performance Analytics

ServiceNow Docs: Metrics Definition & Configuration(ServiceNow Docs - Metrics)

ServiceNow Performance Analytics & Reporting Overview

References from the Certified System Administrator (CSA) Documentation:

AUI Actionin ServiceNow can be configured toprompt or notify users when an action is completed, such as submitting an Incident. UI Actions are used to createbuttons, links, or context menu itemsthat trigger specific actions.

AUI Action(e.g., a "Submit" button on the Incident form) can be configured with asuccess messageusing thegs.addInfoMessage()function.

This message is displayed after the form submission to inform the user that theirIncident has been successfully submitted.

How UI Actions Can Prompt a Success Message:Example of a UI Action Script:javascript

CopyEdit

gs.addInfoMessage("The incident has been successfully submitted.");

This will display aconfirmation messageat the top of the page when an Incident is submitted.

Why "True" is the Correct Answer:UI Actions can display confirmation messages usinggs.addInfoMessage()or similar methods.

Why "False" is Incorrect:UI Actionscanbe used to provide user feedback, including success messages for actions like submitting an incident.

AnUpdate Setin ServiceNow is a mechanism thattracks and packages customizations and configuration changesso they can be transferred between instances (e.g., fromDevelopmenttoTestorProduction).

It is primarily used ininstance migrationandchange management, ensuring that changes made in one environment can beapplied consistentlyin another.

Tracks Customizations– Records changes to system configurations, such as Business Rules, Client Scripts, UI Policies, and Workflows.

Facilitates Deployment– Enables controlled migration of changes from one ServiceNow instance to another.

Reduces Manual Effort– Instead of manually reconfiguring settings in different environments, administrators can package updates into asingle unit.

Version Control– Ensures that onlyintended changesare moved between instances.

Key Features of Update Sets:

Why the Correct Answer is A:A. An Update Set allows administrators to group a series of changes into a named set and then move this set as a unit to other systems(Correct)

This accurately describes the primary function of anUpdate Set.

Administratorsgroupmultiple changes into anUpdate Set, export it, and apply it to another instance.

Example Workflow:

Admin makes configuration changes(e.g., modifies a Business Rule, updates a Workflow).

Update Set captures those changesin a structured format.

The Update Set is exportedfrom the Development instance.

The Update Set is importedinto the Testing/Production instance and applied.

Why the Other Options Are Incorrect:B. By default, an Update Set includes customizations, Business Rules, and homepages(Incorrect)

Update Setsdo include customizations and Business Rules, but theydo notinclude homepages by default.

Dashboards and homepagesrequire a separate process usingsys_portal_page and sys_ui_page tables.

C. An Update Set is a group of customizations that is moved from Production to Development(Incorrect)

Update Sets are typically movedfrom Development to Test/Production, not the other way around.

Best practice is to make changes inDevelopment, test them inTest/UAT, and then deploy them toProduction.

D. By default, the changes included in an Update Set are visible only in the instance to which they are applied(Incorrect)

This is misleading becausean Update Set can be exported and applied to multiple instances.

Once an Update Set isimported and committed, its changes become active in that instance.

Best Practices for Using Update Sets:✔Always preview an Update Set before committing itto ensure it contains the correct changes.

✔Use Named Update Sets, not the default "Default Update Set," to track changes effectively.

✔Ensure all related changes are included(e.g., dependencies such as script includes and tables).

✔Test Update Sets in a sub-production instancebefore applying them inProduction.

In ServiceNow,Favoritesallow users to quickly accessapplication menus and modulesthat they frequently use. By marking an application menu or module as a favorite, it appears under theFavorites tab in the Application Navigator, making navigation faster and more efficient.

(A) Breadcrumb – Incorrect

Breadcrumbs in ServiceNow show thenavigation pathwithin a list view or form.

They help users filter data quickly but donotstore shortcuts for quick access.

(B) Favorite – Correct

TheFavorite featurein ServiceNow allows users to save frequently used menus and modules for quick access.

Users canadd, remove, and reorderfavorites for better personalization.

Located in theApplication Navigator, favorites appear at the top for easy access.

Favorites can include forms, records, reports, or dashboards.

(C) Tag – Incorrect

Tagsare used toorganize and categorize records(e.g., incidents, problems, change requests).

Tags help users group related records but donotcreate direct menu shortcuts.

(D) Bookmark – Incorrect

ServiceNow doesnotuse the term "Bookmark" for quick access to menus and modules.

While users can bookmark URLs in a web browser, this is different from ServiceNow’s built-inFavoritesfeature.

Explanation of Each Option:

Users cancustomize Favoritesby renaming them or selecting an icon for better visibility.

Admins canpre-configure favoritesfor users based on roles to improve productivity.

Favorites improveuser efficiencyby reducing the number of clicks needed to reach frequently used items.

ServiceNow Docs: Using Favorites in the Application Navigator

https://docs.servicenow.com

ServiceNow Community: Personalizing the Application Navigator with Favorites

https://community.servicenow.com

Additional Notes & Best Practices:References from Certified System Administrator (CSA) Documentation: