Free ServiceNow CSA Practice Exam with Questions & Answers | Set: 8

In ServiceNow, anUpdate Setis a mechanism used to package and transfer customizations from one instance to another. TheDefault Update Setis automatically created for every instance and captures all unassigned configuration changes. However, it is considered abest practice not to use the Default Update Set for moving customizations between instances.

Lack of Organization & Traceability

The Default Update Set collects all modifications automatically, making it difficult to track specific changes related to a particular project or feature.

If multiple administrators or developers work in an instance, their changes will all be mixed together in the Default Update Set, leading to confusion and conflicts.

Risk of Losing Changes

Default Update Sets are not automaticallycomplete. Since users can forget to mark their customizations explicitly for an update set, some changes might not get captured.

If a system admin forgets to move a customization into a named update set, those changes may not be included in the migration process.

Cannot Be Moved Between Instances

The Default Update Setcannot be retrieved or movedbetween instances because it is system-managed. This makes itimpossibleto use it for transferring customizations effectively.

Named Update Sets, on the other hand, allow developers to package only the required changes for controlled migration.

Best Practice: Use Named Update Sets

It is highly recommended to create anamed Update Set(e.g., "Incident_Enhancements_Q1_2025") for each set of related changes.

This provides a structured way to track, test, and promote configurations fromdevelopment → test → production environmentsin a controlled manner.

A. Merge Default Update Sets before moving between instancesIncorrect – The Default Update Set cannot be moved between instances, so merging it would not serve any purpose.

B. Submit Default Update Set to Application RepositoryIncorrect – The Application Repository is used forScoped Applications, not for update sets. The Default Update Set is system-managed and should not be used for structured deployments.

D. Keep Default Update Set to a maximum of 20 records, for troubleshooting purposesIncorrect – While keeping the Default Update Set small might be useful for tracking small changes, there is no such best practice limit of "20 records." It is still not recommended for migrations.

ServiceNow Product Documentation – Update Sets Best Practices????Update Set Best Practices

ServiceNow Community Best Practices – Managing Update Sets????Managing Update Sets

Reasons Why You Should Not Use the Default Update Set for Moving Between Instances:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. You should not use the Default Update Set for moving between instances.The best practice is to always createnamed Update Setsto ensure controlled, traceable, and reliable migrations of customizations between ServiceNow instances.

InServiceNow,Related Listsdisplayrecords that are linked to the current recordthrough relationships. Tomanage records within a Related List, the following buttons are commonly used:

1. "New" ButtonCreates a new record in the related list

Example: In theUser Form, the "Groups" related list has a "New" button toadd a new Group membership.

2. "Add" ButtonAdds an existing record to the related list

Example: In theIncident Form, the "Affected CIs" related list has an "Add" button toassociate existing CIswith the incident.

3. "Edit" ButtonModifies existing relationships

Opens amulti-record selection view, allowing users toadd or remove multiple related records at once.

Example: EditingUser Rolesin theUser Formallows selectingmultiple rolesat once.

A. PublishIncorrect– "Publish" is used inKnowledge Managementfor articles, not related lists.

D. ManageIncorrect– There isno standard "Manage" buttonin Related Lists.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Related Lists Overview????Using Related Lists

ServiceNow Docs – Configuring Related Lists????Configuring Related Lists

Official ServiceNow Documentation References:

UI Policiesin ServiceNow allow administrators to dynamically control the behavior of form fieldsbased on user input or conditions. If you want aUI Policy to apply to all form views, you must set theGlobalfield totrue.

D. Global

When theGlobalfield is set totrue, the UI Policy appliesto all viewsof the form.

This ensures that fields remainconsistentacross different layouts, regardless of the view being used.

Example:

AUI Policyhides the "Resolution Notes" fieldunlessthe "State" isResolved.

SettingGlobal = trueensures this rule appliesin all form views(Default, Mobile, or Workspace).

A. Inherit

Not a standard UI Policy fieldin ServiceNow.

Likely confused withrole inheritancein security settings.

B. Reverse if false

"Reverse if false"onlyreverses the policy's actionwhen the condition isnot met.

It doesnotcontrol whether the UI Policy applies to all views.

C. On lowed

Incorrect and not a valid ServiceNow UI Policy field.

Possibly atypoor misunderstanding of "Allowed Roles".

TheActivity Streamin ServiceNow records allupdates, comments, work notes, and system eventsrelated to a record.

Tofilter the Activity log to show only Work Notes, follow these steps:

Locate theActivity Streamsection on the form.

Click theFunnel (Filter) icon.

SelectWork Notesto display only the relevant updates.

This allows thesubject matter expertto focus only onwork notesleft by other users, ensuring quick access to important information.

A. Click Context menu > Work Notes View

There isno default "Work Notes View" optionin the context menu for filtering the Activity log.

B. Click Personalize icon and select Activity Stream

ThePersonalize iconis used forUI preferences, not for filtering work notes.

C. Right-click form header > Form Layout > Add Work Notes Section

Adding a "Work Notes" field to the formdoes not filterthe existing activity log.

E. Click Context menu > History

TheHistory optiontracks user navigation and doesnot filter Work Notesin the Activity log.

Tochange the default layout of a task listin ServiceNow, you shouldright-click on any column headerand selectConfigure > List Layout.

Navigate to the Task list view(e.g., Incident, Change, or another task-based list).

Right-click on any column header(e.g., "Number" or "Short Description").

SelectConfigure > List Layout.

Add, remove, or reordercolumns as required.

ClickSaveto apply changes.

B. Right-click List Gear icon > Configure > Columns

TheGear icon(⚙) allowspersonalizing columns for an individual user, butdoes not change the default list layout for all users.

C. Click List Context Menu > Personalize List

Personalization only affects the user’s view, not theglobal list layout.

D. Click List Context Menu > Configure Columns

There isno "Configure Columns" optionin the list context menu; the correct path is"Configure > List Layout".

ServiceNow List Layout Configuration

ServiceNow CSA Training Module:"Working with Lists and Configuring Layouts"

Steps to Modify the Task List Layout:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Client Scriptsin ServiceNow are scripts that runon the client-side (browser)and execute in real-time based on user interactions with a form.

B. A client script

Runs in the user’s browserwhen they interact with the form.

Can trigger alerts, field changes, or validationsinstantly.

Example:

If a user changes thePriorityfield on anIncident form, aClient Scriptcan:

Display analert

Change other field values (e.g., auto-setImpact and Urgency)

Validate input before submission

A. A server script

Server-side scripts executeon the server, not in the browser.

These includeBusiness Rules, Script Includes, and Scheduled Jobs.

They runafter form submission, not during real-time user interactions.

C. A fix script

Fix scripts areone-time scriptsused fordata correctionsorinstance updates.

They donotexecute based on form interactions.

D. A business rule

Business Rulesrunon the serverand typically triggeron record insert, update, or delete.

They donotprovide real-time alerts in the user’s browser.

InServiceNow, when acustom tableis created, the systemautomatically generates four Access Control Rules (ACLs)to control the basic operations on that table. These rules define who cancreate, read, update, and delete recordsin the table.

Read (ACL: table_name.*.read)Allows users to view (read) recordsin the table.

Without this ACL, userscannot see any recordsin the table.

Create (ACL: table_name.*.create)Allows users to insert new recordsinto the table.

Without this ACL, userscannot add new records.

Update (ACL: table_name.*.update)Allows users to modify (edit) existing recordsin the table.

Userscannot edit recordsif this ACL is missing.

Delete (ACL: table_name.*.delete)Allows users to remove (delete) recordsfrom the table.

Userscannot delete recordswithout this ACL.

Default Access Control Rules Created for a New Table:

C. executeIncorrect– Theexecutepermission applies toScripts or UI Actions, not table records.

NoexecuteACL is automatically created for tables.

F. writeIncorrect–"Write" is NOT an ACL permission in ServiceNow.

Instead,"update"is the correct term for editing records.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Rules (ACLs)????Access Control Best Practices

ServiceNow Docs – Creating Custom Tables????Custom Tables and Security

Official ServiceNow Documentation References:

InServiceNow, theFavoritesfeature allows users to quickly access frequently used modules, applications, or records. Users can customizeFavoritesby changing theicon and color.

To edit a favorite, you need to:

Open theApplication Navigator.

Locate yourFavoriteslist.

Click thePencil (✏) iconnext to the favorite you want to edit.

Choose a newicon and color.

Save the changes.

A. Star

TheStar iconis used toaddorremovea favorite butnotfor editing.

B. Triangle

NoTriangle iconis used for Favorites customization.

D. Clock

TheClock iconrepresentsrecently viewed items, not Favorite customization.

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:

In ServiceNow, theApprover [approver-user] roleis specifically designed for users who need toauthorize requestsbut should not have any other permissions or administrative access to the platform.

Canapprove or reject requests(e.g., Change Requests, Service Catalog Requests).

No additional platform permissions(cannot create, modify, or view records beyond approvals).

Assigned automatically tousers designated as approversin approval workflows.

AnIT Managerreceives an approval request for a new laptop.

Themanager logs in and sees only the approval request(no other system access).

Theyapprove/rejectthe request without modifying any records.

Key Features of the Approver Role:Example Use Case:

B. Authorize [authorize-user] →Incorrect

No such role exists in ServiceNow.

C. Reviewer [reviewer_user] →Incorrect

No such role exists in ServiceNow.

D. Approver Group [approval_group] →Incorrect

Approval groupsallow multiple users to approve a request collectively, but it is not a standalone role.

Theapprover-user roleis the correct answer for individual approvals.

E. Verification [verify_user] →Incorrect

No such role exists in ServiceNow.

Why Other Options Are Incorrect?

Approval Configuration

User Roles in ServiceNow

Official ServiceNow Documentation Reference: