Pass the ServiceNow Certified System Administrator CSA Questions and answers with ExamsMirror

When an item isordered from the Service Catalog, two main records are created in ServiceNow:

sc_req_item(Requested Item - RITM)

Representseach individual itemin the order.

Tracks the approval process, fulfillment, and delivery for that specific item.

sc_task(Service Catalog Task - SCTASK)

Used toassign workto different fulfillment teams (e.g., IT, HR).

A singlesc_req_itemmay generate multiplesc_taskrecords.

A user orders aMacBook Profrom the Service Catalog.

ARequest (REQ#)is created.

ARequested Item (RITM#)is generated to track the MacBook order.

One or moreService Catalog Tasks (SCTASK#)are created for fulfillment (e.g., Procurement, Shipping).

C. A change record

Change records (chg_request) are created only if thecatalog item is linked to Change Management, which is not always the case.

D. An Incident record

Incidents (incident) are created forissues or break/fix cases, not for service requests.

E. A problem record

Problem records (problem) are used forroot cause analysis, not service catalog requests.

In ServiceNow, thewait timefor end users is influenced by theround-trip timebetween the client (browser) and the server. The round-trip consists of two key activities:

Request– The client sends a request to the server (e.g., when a user opens a record, submits a form, or performs an action).

Response– The server processes the request and sends back the required data to the client.

This cycle directly affects the perceived performance of the ServiceNow instance, as delays in request processing or data retrieval can lead to a slower user experience.

Minimizing client-server interactionsis a best practice for optimizing performance.

Using GlideAjax or Asynchronous Callscan help reduce unnecessary round-trips.

Client-side scripting best practices(e.g., reducing the number of server lookups) improve response times.

Performance Considerations:Incorrect Answers Explanation:B.Save + Update– Saving and updating are database operations, but they do not define the full round-trip.

C.Write + Read– Writing and reading refer to database interactions, not the client-server exchange process.

D.Submit + Query– Submission and querying are user actions, but they do not encompass the entire round-trip process.

E.Insert + Verify– Inserting a record and verifying it are database actions, not the round-trip process.

ServiceNow Documentation→"Client-Side Scripting Best Practices"

ServiceNow Performance Best Practices→ "Understanding Client-Server Round-Trips"

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,scripts that run in the browser (client-side)includeUI PoliciesandClient Scripts. These scripts execute on theuser’s web browser, allowing real-time interaction with forms and fields without requiring a server request.

Executed in the user’s browserwhen a form is loaded, saved, changed, or submitted.

Used forreal-time form validation, auto-population, and dynamic UI changes.

Written inJavaScriptand runs on the client side.

Applyrulesto make fieldsmandatory, visible, or read-onlydynamically.

Moreefficientthan Client Scripts because theydon’t require scriptingin most cases.

A. Script Include Scripts– Theserun on the server, not in the browser. They are reusable functions that can be called from different scripts.

B. Business Rule Scripts– Business Rulesexecute on the server-side, triggered by database operations (Insert, Update, Delete).

C. Access Control Scripts– These areserver-side security rules(ACLs) that restrict user access to records and fields.

ServiceNow Client Scripts and UI Policies

ServiceNow CSA Training Module:"Client-Side Scripting in ServiceNow"

1. Client Scripts:2. UI Policies:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

To rename a field label in ServiceNow (such as changing "Priority" to "PValue"), you must eitherupdate the dictionary definitionorchange the field label.

Right-click on the "Priority" field labelin the form.

Select"Configure Dictionary".

Update the"Label" fieldto "PValue".

Save the changes.

The new label will now be reflected across the system where applicable.

Right-click on the "Priority" field labelin the form.

Select"Configure Label".

Update thelabel textto "PValue".

Save the changes.

This methodonly changes the field labelfor display purposeswithout affecting the underlying database structure.

B. Right-click on Priority and select Configure Display Settings

There isno "Configure Display Settings"option when right-clicking on a field label in ServiceNow.

D. Right-click on Priority and select Configure Column

"Configure Column" is used forlist views, not for changing field labels on forms.

ServiceNow Field Labels and Dictionary

ServiceNow CSA Training Module:"Configuring Forms and Fields"

Option 1: Configure Dictionary (Recommended for Full Customization)Option 2: Configure Label (Quick Change for Display Purposes)Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Thesecurity_adminrole in ServiceNow is required to make changes toHigh Security Settings(now part ofSystem Security Settings).

Modify high-security settingsin ServiceNow.

Elevate privilegesto make changes to sensitive security configurations.

Manage Access Control Lists (ACLs)to define security rules.

Users with theadminrole alonecannot modify high-security settings.

Thesecurity_adminrole requireselevationvia the"Elevate Role" optionin the user menu.

This ensures thatonly authorized administratorscan modify security-related configurations.

B. sn_ad_admin– No such role exists in ServiceNow.

C. high_sec_admin– This is not a valid ServiceNow role.

D. admin– Theadmin role alonedoesnot grant access to high-security settingswithoutelevating to security_admin.

ServiceNow Security Admin Role and Elevated Privileges

ServiceNow CSA Training Module:"Managing Security Settings and Access Controls"

What Can the security_admin Role Do?Why Elevation is Required?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Knowledge Management, access towho can write articlesin aknowledge baseis controlled using the"Can Contribute"permission.

The"Can Contribute"tab allows administrators to specifywhich users or groups can create, edit, and manage knowledge articleswithin a specific knowledge base.

For example:

If a user isgranted "Can Contribute" access, they canwrite and editknowledge articles.

If a useronly has "Can Read" access, they canviewarticles butcannotcreate or modify them.

A. Can Read–Defines whocan viewknowledge articles, butnot who can writethem.

B. Can Write–No such tab exists in ServiceNow knowledge base settings. Instead, the correct term is"Can Contribute."

D. Can Author–"Can Author" is not an official permission setting in ServiceNow. The correct term is"Can Contribute."

E. Cannot Author–No such option exists in ServiceNow Knowledge Base permissions.

InServiceNow Access Control Lists (ACLs), rules can be applied atdifferent levels:

Table-level– Applies to all fields and records in a table.

Field-level– Applies to specific fields within a table.

To create an ACL rule that applies toall rows and all fieldsof theIncident table, the correctobject nameis:

➡incident.*

incident.*–Grants or restricts access toall fields and recordsin theIncident table.

incident.number– Restricts access to the"Number" fieldin the Incident table.

incident.short_description– Controls access to the"Short Description" fieldonly.

B.incident.all

No such ACL naming convention exists in ServiceNow.

C.incident.!

This is not a valid ACL syntax in ServiceNow.

D.incident.None

This is not a recognized ACL format in ServiceNow.

SpokesinServiceNow IntegrationHubare pre-built connectors that allow organizations to integrate with external systemswithout requiring custom scripting. They providelow-code/no-codesolutions, making integrations faster and more scalable.

A. Reduces the need for code

Spokes come withprebuilt actions, reducing the need forcustom scripting.

Example: Instead of writing aREST API scriptto send a message viaSlack, aSlack Spokeprovides anactionfor it.

B. Features scale and control mechanisms

Spokes supportenterprise scalabilitywith built-ingovernance, security, and controlmechanisms.

Example:Rate limitsprevent excessive API calls, ensuring stability inlarge-scaleintegrations.

D. Ensures discoverability and reuse

Spokes allowactionsto bereusedacross different flows and automations.

Thisenhances maintainabilityby ensuring integrations are not duplicated.

C. Free spokes are available in the ServiceNow Store

Whilesomespokes are free,many require a separate license.

IntegrationHub Standard and Enterprisesubscriptions cover most advanced spokes.

E. Automated event management

Event Managementis part ofITOM, notIntegrationHub Spokes.

While spokestrigger actionsbased on events, theydo not manage eventslike ITOM Event Management.

In theServiceNow Service Catalog module, tables have aOne-to-Many (1:M) relationship, meaning a single record in one table can relate to multiple records in another table. This is especially important for handling Service Catalog requests, as multiple items, approvals, and tasks may be associated with a single request.

One Request can have many Requested Items (REQ → RITM)

ARequest (REQ)is a container for multipleRequested Items (RITM).

When a user submits a catalog request, multiple items (such as a laptop and a phone) can be ordered in the same request.

Table Relationship:sc_request(Request) →sc_req_item(Requested Item)

One Requested Item can have many Approvals (RITM → Approval)

SomeRequested Items (RITM)require approval before being fulfilled.

For example, a laptop purchase might need approvals from both the IT department and a manager.

Table Relationship:sc_req_item(Requested Item) →sysapproval_approver(Approval)

One Requested Item can have many Catalog Tasks (RITM → SCTASK)

ARequested Item (RITM)can generate multipleCatalog Tasks (SCTASK)for different fulfillment teams.

For example, if an employee requests a new laptop, one task might go to IT to set it up, while another goes to finance for cost approval.

Table Relationship:sc_req_item(Requested Item) →sc_task(Catalog Task)

Breakdown of Correct Answers:Incorrect Answers Explanation:A.One Approval can have many Requests

Approvals do not relate to multiple requests. Instead, a request may contain multiple approvals.

E.One Cart can have many Requests

TheCartis only a temporary storage of items before checkout. Once submitted, it generates asingle Request (REQ), not multiple requests.

ServiceNow Product Documentation→ "Understanding Service Catalog Tables and Relationships"

ServiceNow Data Model→ "Request, Requested Item, and Catalog Task Relationships"

References from Certified System Administrator (CSA) Documentation:

TheConfiguration 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 threekey tablesthat 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 thebase classfor 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 donotexist 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 indicatesScoped Application Tablesin ServiceNow.

Standard CMDB tables exist in theglobal scopewithout the "sn_" prefix.

"sn_cmdb" and "sn_cmdb_ci" arenotkey tables in theglobal CMDB architecture.

In ServiceNow,tagsare used to categorize and organize records for quick access. When managing tags, users can control theirvisibilityby settingwho can see them.

B. Everyone

The tag ispublicand visible to all users in the instance.

Example: AService Desk teamcreates a"High Priority"tag that everyone can use.

C. Groups and Users

Tags can be restricted to specificgroupsorindividual users.

Example: ASecurity Teamcreates a tag only visible toIT Security staff.

E. Me

Tags can beprivate, meaning only the creator (you) can see them.

Example: A user creates a"Follow-up"tag for theirownpersonal tracking.

A. Admins

Incorrect—Admins can manage tags, but "Admins" isnota visibility setting.

Instead, visibility is set toEveryone, Groups, or Me.

D. Roles and Permissions

Incorrect terminology—ServiceNowdoes notprovide a tag visibility setting based on "Roles and Permissions."

Tags are assigned based onspecific users or groups, not roles.