CSA System Administrator - ServiceNow Practice Test 2026
CSA is the broadest ServiceNow certification. It jumps from users and groups to forms, lists, reporting, service catalog, and knowledge in the same sitting. This 392-question bank helps you tighten the admin basics that people usually skim.
Price is shown at checkout on Udemy. 30-day money-back guarantee.
Start practicing nowNext step: Certified Application Developer.
What's included
- 392 questions on the admin tasks every CSA candidate gets tested on
- Every answer links to the official ServiceNow documentation so you can verify it yourself.
- Wrong answers are explained too. You see why each option fails, not just which one wins.
- Current for the Zurich release and the 2026 exam blueprint.
- Lifetime access. When new questions are added, you get them at no extra charge.
- Written by an author who passed all 18 ServiceNow exams on the first attempt.
- 30-day money-back guarantee through Udemy.
15 Free Preview Questions
Answer 5 questions free. Enter your email to continue through question 15. The full course has 392 questions on Udemy.
- AAll rows are rejected; coalesce is required.
- BAll rows are treated as new records. No existing records are updated.
- CDuplicate rows are rejected from the import.
- DAll rows are treated as new records, but errors will be flagged.
Show full explanation
Correct Answer
B. All rows are treated as new records. No existing records are updated.
Source
ServiceNow Zurich - Import Sets
If the link fails, search Google for: ServiceNow Zurich import sets coalesce field
Expert Explanation
A coalesce field is the matching key that tells the import process how to identify whether an incoming row corresponds to an existing record. When you define a coalesce field (for example, email on the User table), ServiceNow compares each imported row's email value against existing records:
- If a match is found, the existing record is updated
- If no match is found, a new record is created
When no coalesce field is specified, ServiceNow skips the matching step entirely. Every single row in the import set is treated as a new insert. This means if you import 500 rows and 300 of them already exist in the target table, you will end up with 300 duplicate records.
Why the Others Are Wrong
- A - All rows are rejected: Coalesce is optional, not mandatory. The import runs successfully without one - it just inserts everything as new.
- C - Duplicate rows are rejected: ServiceNow cannot detect duplicates without a coalesce field. No rejection logic exists by default.
- D - Errors will be flagged: No errors or warnings are generated. ServiceNow treats the absence of coalesce as intentional and processes all rows cleanly as inserts.
Memory Tip
Think of coalesce like a hotel check-in desk. With a coalesce field (your reservation name), the desk finds your existing room and updates it. Without one, they just hand you a brand-new room key every time - even if you already have three rooms booked.
Real-World Example
A ServiceNow admin at a healthcare company imports 2,000 employee records from an HR CSV every Monday. The first week, she forgets to set employee_number as the coalesce field. By Friday, the User table has 10,000 entries instead of 2,000 - five copies of every employee. She has to manually clean up the duplicates and re-run with the coalesce field set to prevent future duplication.
- AA collection of subject matter experts
- BA department
- CAn escalation pod
- DA collection of users
- EA collection of tasks
Show full explanation
Correct Answer
D. A collection of users
Source
If the link fails, search Google for: ServiceNow Zurich groups users administration
Expert Explanation
A group in ServiceNow is fundamentally a collection of users. Groups are stored in the sys_user_group table and serve multiple critical functions across the platform:
- Task assignment: Incidents, changes, and other tasks are assigned to groups
- Access control: Groups can be given roles, which cascade to all members
- Approval workflows: Groups can serve as approvers in approval rules
- Notification routing: Email notifications can target entire groups
Users are added to groups through the Group Members (sys_user_grmember) table. A single user can belong to multiple groups, and groups can have a manager designated for escalation purposes.
Why the Others Are Wrong
- A - Subject matter experts: This describes a possible use case, not the definition. Groups hold any users - help desk agents, managers, or even service accounts.
- B - A department: Departments (cmn_department) are a separate entity. A department represents HR structure; a group represents operational assignment units.
- C - An escalation pod: This is not a ServiceNow concept. Groups can participate in escalations, but that is a function, not a definition.
- E - A collection of tasks: Groups contain users, not tasks. Tasks are assigned to groups, but the group itself is a user container.
Memory Tip
Think G = Gathering of Users. A group gathers users together. Everything else - departments, task queues, expertise pools - is a different ServiceNow concept with its own table.
Real-World Example
At a retail company, the ServiceNow admin creates a group called "Network Operations" with 12 members. When a network incident is logged, the assignment rule routes it to this group. Any of the 12 users can pick it up. The group manager, Sarah, gets notified if no one claims the ticket within 30 minutes. The group also holds the itil role, so all 12 members automatically get access to the Incident module.
- Asn_rec_id
- Brec_id
- Cu_id
- Dsys_id
- Esn_gu_id
- Fsn_sys_id
Show full explanation
Correct Answer
D. sys_id
Source
ServiceNow Zurich - Unique Record Identifier
If the link fails, search Google for: ServiceNow Zurich sys_id unique identifier 32 character
Expert Explanation
The sys_id is ServiceNow's universal unique identifier for every record in every table. Key characteristics:
- It is a 32-character hexadecimal string (a GUID/UUID)
- It is automatically generated when a record is created
- It is immutable - once assigned, it cannot be changed
- It is globally unique across the entire instance
- It appears in record URLs:
...sys_id=a1b2c3d4e5f6...
The sys_id is critical for GlideRecord scripting (gr.get(sys_id)), REST API calls, reference fields, and update sets. It is the backbone of how ServiceNow tracks and relates records internally.
Why the Others Are Wrong
- A - sn_rec_id: Not a real ServiceNow field. The sn_ prefix is not used for core system identifiers.
- B - rec_id: Not a standard field in any ServiceNow table. Pure fabrication.
- C - u_id: The u_ prefix is reserved for custom fields created by administrators, not system-generated identifiers.
- E - sn_gu_id: Does not exist. While it hints at "GUID," the actual field is sys_id.
- F - sn_sys_id: Incorrect combination of prefixes. The field is simply sys_id with no additional prefix.
Memory Tip
Think of sys_id as your record's Social Security Number - 32 characters of pure identity. SYStem IDentifier = sys_id. Every record is born with one, keeps it for life, and it is never shared or duplicated.
Real-World Example
A developer at a financial services firm writes an integration that syncs ServiceNow incidents with Jira. She stores the sys_id (e.g., 6816f79cc0a8016401c5a33be04be441) in Jira's custom field so the middleware can call the ServiceNow REST API with GET /api/now/table/incident/6816f79cc0a8016401c5a33be04be441 to pull updates. Without the sys_id, there would be no reliable way to match records between the two systems.
- ASchema Map
- BDependency View
- CDependency Map
- DDatabase View
Show full explanation
Correct Answer
B. Dependency View
Source
ServiceNow Zurich - Dependency Views
If the link fails, search Google for: ServiceNow Zurich dependency view CMDB CI relationships
Expert Explanation
The Dependency View is ServiceNow's graphical tool for visualizing how Configuration Items (CIs) relate to each other within the CMDB. Key features:
- Shows upstream dependencies (what the CI depends on) and downstream dependencies (what depends on the CI)
- Displays relationships like Runs on, Hosted on, Depends on, and Used by
- Accessible from any CI record by clicking the Dependency View related link
- Helps with impact analysis - if a server goes down, what services are affected?
The Dependency View is essential for Change Management (assessing change risk), Incident Management (identifying blast radius), and Problem Management (tracing root causes across infrastructure).
Why the Others Are Wrong
- A - Schema Map: Shows table-to-table relationships in the data model (database schema), not CI-to-CI infrastructure relationships. It is a developer/admin tool, not a CMDB tool.
- C - Dependency Map: Close but incorrect. The official ServiceNow name is Dependency View, not Dependency Map. Precision matters on the exam.
- D - Database View: Not a recognized CMDB visualization feature. This term conflates database concepts with CMDB functionality.
Memory Tip
Dependency View = Diagram of Vital connections. When you need to SEE (view) what depends on what, you use the Dependency VIEW.
Real-World Example
A change manager at an insurance company needs to schedule maintenance on a database server (CI: DBSRV-PROD-03). She opens the Dependency View and sees that 4 application servers run on this database, which support 2 business services used by 1,500 claims processors. She reschedules the maintenance to a weekend window and adds all affected CI owners as stakeholders on the change request.
- AFlexible
- BFreeform
- CFeature
- DGuided boards
Show full explanation
Correct Answer
C. Feature
Source
ServiceNow Zurich - Visual Task Boards
If the link fails, search Google for: ServiceNow Zurich visual task board types flexible freeform guided
Expert Explanation
ServiceNow provides three types of Visual Task Boards (VTBs):
- Freeform: An open canvas with no predefined structure. Users drag cards freely and create custom groupings. Best for brainstorming or ad-hoc task organization.
- Flexible: Users define custom lanes manually. Cards can be dragged between lanes. Good for custom workflows that do not map to existing field values.
- Guided: Lanes are automatically generated from a field's choice values (e.g., Incident State). Moving a card between lanes updates the record's field value. Best for tracking work through defined stages.
Feature is not one of the three VTB types. It is a distractor likely borrowed from Agile project management terminology (feature boards in tools like Jira or Azure DevOps).
Why the Others Are Wrong
- A - Flexible: This IS a valid VTB type. Flexible boards let users create custom lanes for organizing tasks.
- B - Freeform: This IS a valid VTB type. Freeform boards are unstructured canvases for free-form task placement.
- D - Guided boards: This IS a valid VTB type. Guided boards auto-generate lanes from field values and update records when cards move.
Memory Tip
Remember the three Fs and a G: Freeform, Flexible, and Guided. Feature starts with F too, but it is the Fake one - the imposter that does not belong.
Real-World Example
An IT manager at a university sets up three VTBs for her team of 8 analysts. She uses a Guided board for incidents (lanes: New, In Progress, Resolved, Closed), a Flexible board for a server migration project (custom lanes: Planning, Procurement, Migration, Validation), and a Freeform board for the team's weekly brainstorming session where they organize improvement ideas without any structure.
- AName: incident.None; Operation: create; Role: itil
- BName: incident.Any; Operation: write; Permission: itil
- CName: incident:*; Permission: write; Role: itil
- DName: incident.None; Permission: create; Role: itil
- EName: incident:*;Operation: write; Permission: itil
Show full explanation
Correct Answer
A. Name: incident.None; Operation: create; Role: itil
Source
ServiceNow Zurich - Access Control Rules
If the link fails, search Google for: ServiceNow Zurich ACL access control rules create operation role
Expert Explanation
Access Control Lists (ACLs) in ServiceNow define who can perform what operations on which data. An ACL rule has three critical components:
- Name (Object): Format is
table.field. Usetable.Nonefor table-level access (no specific field). Example:incident.Nonetargets the entire incident table. - Operation: The action being controlled - create, read, write, or delete.
- Role: The security role required. The itil role is the standard role for IT service desk users.
So incident.None | create | itil means: "Users with the itil role can create new incident records."
Why the Others Are Wrong
- B - incident.Any; Operation: write; Permission: itil: Uses "Any" instead of "None" (incorrect field reference), says "write" instead of "create" (wrong operation), and labels itil as a "Permission" instead of a "Role."
- C - incident:*; Permission: write; Role: itil: Uses colon+wildcard naming (
incident:*) which is not valid ACL syntax. Also specifies "write" instead of "create." - D - incident.None; Permission: create; Role: itil: Close, but "Permission: create" is wrong. The correct field label is "Operation: create." ACLs configure operations, not permissions directly.
- E - incident:*; Operation: write; Permission: itil: Wrong naming convention (colon+wildcard), wrong operation (write vs create), and itil labeled as permission instead of role.
Memory Tip
Remember the ACL formula: "What.Where | Do What | Who" - incident.None (what table, no specific field) | create (the operation) | itil (the role). None means the whole table, not nothing.
Real-World Example
A ServiceNow admin at a logistics company gets a request: "Our 45 service desk agents need to log incidents but should not be able to delete them." She creates an ACL with Name: incident.None, Operation: create, Role: itil. She verifies no delete ACL exists for itil. She tests by impersonating an itil user and confirming the New button appears on the incident list but no Delete option shows on existing records.
- AAdjust Transform Maps after loading into target
- BUse one extremely large Import Set
- CCreate a new Import Set table for each load
- DPlan time to remove obsolete or inaccurate source data
- EUse Data Scrub Workspace to clean imports
Show full explanation
Correct Answer
D. Plan time to remove obsolete or inaccurate source data
Source
ServiceNow Zurich - Import Sets Best Practices
If the link fails, search Google for: ServiceNow Zurich import sets best practices data quality
Expert Explanation
The golden rule of data imports is "garbage in, garbage out." ServiceNow's official best practices emphasize that you should always clean your source data before importing. This means:
- Removing obsolete records (terminated employees, decommissioned assets)
- Fixing inaccurate data (wrong email formats, inconsistent naming)
- Eliminating duplicates in the source before they ever reach ServiceNow
- Validating data formats (dates, phone numbers, reference values)
Cleaning source data is far less expensive than cleaning it after it has been loaded into ServiceNow, where it may have already triggered workflows, notifications, and created downstream records.
Why the Others Are Wrong
- A - Adjust Transform Maps after loading: This is backwards. Transform maps should be tested with sample data first, not adjusted after a full load has already pushed data to the target table.
- B - One extremely large Import Set: Large sets cause performance degradation and timeouts. ServiceNow recommends smaller, incremental imports for better control and error isolation.
- C - New Import Set table for each load: This creates table proliferation. Reuse existing import set tables when the source format matches. Only create new tables for structurally different data sources.
- E - Data Scrub Workspace: This is a fictional feature. No such out-of-box workspace exists in ServiceNow.
Memory Tip
Think of it like cooking: you wash the vegetables before putting them in the pot, not after the soup is made. Clean BEFORE import = best practice. Cleaning after = expensive mess.
Real-World Example
A manufacturing company plans to import 50,000 asset records from a legacy spreadsheet into ServiceNow's CMDB. The admin spends two days cleaning the source file first: removing 8,000 decommissioned assets, standardizing 3,200 location names to match ServiceNow's location table, and fixing 1,100 serial numbers with extra spaces. The import runs cleanly with a 99.2% success rate, versus a pilot test of the uncleaned data that had a 71% error rate.
- ABanner Image
- BRecord Number Format
- CBrowser Tab Title
- DSystem Date Format
- EForm Header Size
Show full explanation
Correct Answer
A. Banner Image, C. Browser Tab Title, D. System Date Format
Source
ServiceNow Zurich - Basic Configuration UI16
If the link fails, search Google for: ServiceNow Zurich basic configuration UI16 system properties
Expert Explanation
The Basic Configuration UI16 module (System Properties > Basic Configuration UI16) provides a simplified interface for administrators to customize fundamental platform settings. The configurable options include:
- Banner Image: Replace the ServiceNow logo with your organization's branding
- Browser Tab Title: Change what appears in the browser tab (e.g., "Acme IT Portal")
- System Date Format: Set the global date display format for the instance
- Banner Text: Add text next to or instead of the banner image
- System Time Format: Configure 12-hour vs 24-hour time display
This module is designed for quick branding and localization without needing to modify system properties individually.
Why the Others Are Wrong
- B - Record Number Format: Managed through Number Maintenance (System Definition > Number Maintenance), not Basic Configuration. Each table has its own number prefix and counter configuration.
- E - Form Header Size: Not a Basic Configuration setting. Form appearance is controlled through Form Layout, Form Design, UI Policies, or custom CSS modifications.
Memory Tip
Basic Configuration handles the B-B-D trio: Banner image, Browser tab title, Date format. These are the things you would customize on Day 1 of a new instance to make it look like your company's platform.
Real-World Example
During a go-live for a European bank, the admin opens Basic Configuration UI16 and makes three changes in under 5 minutes: uploads the bank's logo as the Banner Image, sets the Browser Tab Title to "BankCorp ITSM," and changes the System Date Format from MM/DD/YYYY to DD/MM/YYYY for European users. These quick changes immediately make the instance feel like a company tool rather than a generic ServiceNow deployment.
- AInstall the Bomgar plug-in
- BInitiate a Connect Chat session
- CLaunch a NowChat window
- DImpersonate the user
Show full explanation
Correct Answer
D. Impersonate the user
Source
ServiceNow Zurich - Impersonating a User
If the link fails, search Google for: ServiceNow Zurich impersonate user troubleshoot modules visible
Expert Explanation
User impersonation is a powerful administrative feature that lets an admin temporarily log in as another user without knowing their password. When impersonating:
- You see exactly what the user sees - their application menus, modules, and navigation
- You inherit their roles, groups, and ACLs
- You can test forms, lists, and dashboards from their perspective
- All actions are logged in the system audit trail under the impersonator's name
This is the go-to method for troubleshooting "I cannot see module X" tickets. Instead of guessing which role or group is missing, you impersonate the user and immediately see their exact experience.
Why the Others Are Wrong
- A - Bomgar plug-in: Bomgar provides remote desktop access to a user's computer, not a view of their ServiceNow session context. Even if you saw their screen, you would not see the underlying role/ACL configuration.
- B - Connect Chat: A messaging tool for user-to-user communication. Cannot replicate another user's security context or show their module visibility.
- C - NowChat window: Not a real ServiceNow product or feature. This is a fabricated distractor.
Memory Tip
Impersonate = I see what they see. To walk in someone's shoes in ServiceNow, you impersonate them. No chat, no remote tool - just become them temporarily.
Real-World Example
A help desk analyst at a consulting firm submits a ticket: "I cannot find the Change module." The admin impersonates the analyst and confirms the Change menu is missing. She checks the user's roles and discovers the analyst only has the itil role but is missing the change_manager role. After adding the role and impersonating again, the Change module appears. Total troubleshooting time: 3 minutes.
- AContext Menu > Form > Layout
- BContext Menu > Configure > Form Layout
- CContext Menu > Configure > Form Design
- DRight click on header > Add > Field
- EContext Menu > Form > Designer
- FRight click on header > Configure > UX Dashboard
Show full explanation
Correct Answer
B. Context Menu > Configure > Form Layout and C. Context Menu > Configure > Form Design
Source
ServiceNow Zurich - Form Design and Layout
If the link fails, search Google for: ServiceNow Zurich configure form layout form design add fields
Expert Explanation
ServiceNow provides two tools for adding fields to a form, both accessible through the form's context menu (right-click on the form header bar):
- Form Layout (Configure > Form Layout): A list-based editor with two columns - "Available" fields on the left and "Selected" fields on the right. You move fields between columns and reorder them. Best for quick, precise field management.
- Form Design (Configure > Form Design): A visual drag-and-drop editor showing a live preview of the form. You drag fields from a palette onto the form canvas. Best for visual layout work and when you want to see the result as you build.
Both tools modify the same underlying form configuration. Form Layout is the traditional approach; Form Design is the modern visual alternative.
Why the Others Are Wrong
- A - Context Menu > Form > Layout: Wrong menu path. There is no "Form" submenu - the correct submenu is "Configure."
- D - Right click > Add > Field: No "Add" submenu exists in the form header context menu. Fields are added through Configure options.
- E - Context Menu > Form > Designer: Wrong path and wrong label. It is "Configure > Form Design" not "Form > Designer."
- F - Configure > UX Dashboard: UX Dashboards are part of the Next Experience workspace framework. They are not accessed from form-level context menus and serve a different purpose entirely.
Memory Tip
Both correct answers live under Configure and both start with "Form": Form Layout (the List-based one) and Form Design (the Drag-and-drop one). Configure > Form = your two paths to adding fields.
Real-World Example
A ServiceNow admin at a telecom company receives a request to add a "Customer Tier" field to the incident form. She right-clicks the incident form header, selects Configure > Form Design, and drags the new field from the field palette to the position right below the "Caller" field. Her colleague prefers Configure > Form Layout and uses the Available/Selected column approach to do the same thing. Both methods produce the identical result on the form.
- AForm Columns
- BForm View
- CForm Buttons
- DForm Context Menu
- EForm Links
Show full explanation
Correct Answer
C. Form Buttons, D. Form Context Menu, E. Form Links
Source
ServiceNow Zurich - UI Actions
If the link fails, search Google for: ServiceNow Zurich UI Actions form buttons context menu links
Expert Explanation
UI Actions are configurable controls that add interactive functionality to forms and lists. When applied to forms, UI Actions can appear in three locations:
- Form Buttons: Displayed in the form header/footer bar. Examples include Save, Update, Delete, Resolve. Configured by checking the Form button checkbox.
- Form Context Menu: Items that appear when right-clicking the form header. Examples include Insert, Insert and Stay, Save. Configured by checking the Form context menu checkbox.
- Form Links: Clickable text links shown in the Related Links section at the bottom of a form. Examples include View Map, Copy Record. Configured by checking the Form link checkbox.
Each UI Action can have conditions, roles, and scripts attached to control when it appears and what happens when clicked.
Why the Others Are Wrong
- A - Form Columns: This refers to form layout structure (how many columns of fields appear), not interactive UI controls. Managed through Form Layout, not UI Actions.
- B - Form View: A view is a saved form layout configuration (e.g., "Default view" vs "ESS view"). Views control which fields are visible, not interactive buttons or links. Managed via sys_ui_view.
Memory Tip
UI Actions on forms come in three flavors - B-C-L: Buttons (top of form), Context menu (right-click), Links (bottom of form). Think of them as the top, middle, and bottom interaction points on any form.
Real-World Example
A ServiceNow developer at an airline creates three UI Actions for the incident form. A Form Button labeled "Escalate to Major Incident" appears in the header for priority-1 incidents. A Form Context Menu item called "Clone to Problem" appears on right-click so analysts can quickly create related problem records. A Form Link called "View Affected Flights" appears in Related Links and opens a filtered list of flight CIs associated with the incident.
- AThey direct the user to a record producer
- BThey direct the user to a catalog property
- CThey direct the user to a catalog UI policy
- DThey direct the user to a catalog client script
Show full explanation
Correct Answer
A. They direct the user to a record producer
Source
ServiceNow Zurich - Record Producers
If the link fails, search Google for: ServiceNow Zurich record producer service catalog create incident
Expert Explanation
A Record Producer is a specific type of catalog item that creates a record on a specified target table when submitted. Unlike standard catalog items (which create sc_req_item records), record producers write directly to tables like incident, change_request, or custom tables.
- Create Incident: A record producer targeting the incident table
- Password Reset: A record producer targeting a password reset or incident table
- Report Outage: A record producer targeting the incident table (often with preset fields like category = "Network")
Record producers bridge the gap between the Service Catalog (user-friendly portal experience) and back-end tables (where the actual work records live). They give end users a simplified, guided form while ensuring the right record type is created.
Why the Others Are Wrong
- B - Catalog property: Properties are metadata about the catalog item itself (price, SLA, description). They are not destinations that users navigate to.
- C - Catalog UI policy: UI policies dynamically control field behavior (visible, mandatory, read-only) on catalog forms. They run invisibly in the background, not as a user destination.
- D - Catalog client script: Client scripts execute JavaScript in the browser during form interactions. Users never "go to" a client script - it runs automatically as they fill out the form.
Memory Tip
Record Producer = Produces records on target tables. If a catalog item creates an incident, problem, or change directly (not a request item), it is a Record Producer. Create Incident produces an incident record.
Real-World Example
At a hospital, the IT Service Catalog shows three items on the portal homepage: "Report IT Issue" (creates an incident), "Request Password Reset" (creates a password reset task), and "Report System Outage" (creates a priority-1 incident with the Major Incident flag set). All three are record producers. When a nurse clicks "Report IT Issue," she fills out a simple 5-field form. Behind the scenes, the record producer creates an incident record with the category, description, and urgency pre-mapped from her responses.
- AThe fields that are not in the base table
- BThe mandatory fields for the base table
- CThe fields that are specific to the extended table
- DThe reference fields for the base table
Show full explanation
Correct Answer
A. The fields that are not in the base table and C. The fields that are specific to the extended table
Source
ServiceNow Zurich - Table Extension and Classes
If the link fails, search Google for: ServiceNow Zurich table extension inheritance fields base table
Expert Explanation
Table extension in ServiceNow uses an object-oriented inheritance model. When you extend a base table:
- The child table inherits all fields from the parent table automatically
- The child table inherits business rules, ACLs, and UI policies from the parent
- You only need to create new fields that are unique to the child table
- The child table shares the same underlying database storage concept with the parent
For example, the Incident table extends the Task table. Incident inherits fields like Number, State, Assigned to, and Short description from Task. Incident only defines its own unique fields like Category, Subcategory, Caller, and Resolve time.
Options A and C say the same thing in different words: create only the fields that are new and specific to the extended table.
Why the Others Are Wrong
- B - Mandatory fields for the base table: These are already inherited. Creating them again would be redundant and could cause conflicts. The child table automatically has access to all parent fields, including mandatory ones.
- D - Reference fields for the base table: Like all other field types, reference fields are fully inherited through table extension. No need to recreate them on the child table.
Memory Tip
Think of it like family inheritance: a child inherits everything from the parent and only needs to acquire what is new and unique to them. Do not re-buy what you already inherited - just add what is missing.
Real-World Example
A ServiceNow developer at a software company extends the Task table to create a "Code Review" table (u_code_review). She does not recreate fields like Number, State, Assignment group, or Short description - those come from Task automatically. She only creates three new fields: Repository URL (string), Pull Request Number (integer), and Review Outcome (choice). The Code Review table now has 30+ fields from Task inheritance plus her 3 custom fields, for a total of 33+ fields while only defining 3.
- AProvides IDE for complicated scripting
- BProvides built-in libraries/APIs for complex coding
- CAutomatically populates SLA records
- DNatural-language descriptions of flow logic
- ENo-code application development
- FEasy integration with third-party systems
Show full explanation
Correct Answer
D. Natural-language descriptions of flow logic, E. No-code application development, F. Easy integration with third-party systems
Source
ServiceNow Zurich - Flow Designer
If the link fails, search Google for: ServiceNow Zurich Flow Designer benefits no-code integration
Expert Explanation
Flow Designer is ServiceNow's visual automation engine that replaces traditional workflow development. Its key benefits include:
- Natural-language descriptions: Every trigger, action, and condition in a flow is displayed as a readable English sentence, making flows self-documenting and reviewable by non-technical teams
- No-code development: The drag-and-drop interface lets process owners build automations without writing JavaScript or server-side code. Actions, conditions, and data pills handle the logic visually.
- Third-party integration: Through Integration Hub and its spokes, Flow Designer connects to external systems (Slack, Teams, Jira, AWS, Azure, Salesforce) using pre-built connectors that require zero custom API work
Flow Designer is the strategic replacement for the legacy Workflow Editor, offering better usability, reusability (subflows, actions), and governance.
Why the Others Are Wrong
- A - IDE for complicated scripting: The opposite of Flow Designer's purpose. Flow Designer eliminates the need for scripting, not enables it. Script-heavy work belongs in Script Includes or Business Rules.
- B - Built-in libraries/APIs for coding: Again, this describes a developer tool, not Flow Designer. The platform has APIs (GlideRecord, REST), but these are not Flow Designer benefits.
- C - Automatically populates SLA records: SLA records are managed by the SLA Engine (Task SLA, SLA Definition). Flow Designer can trigger actions based on SLA events, but it does not auto-populate SLA records as a built-in feature.
Memory Tip
Flow Designer's three big benefits spell N-N-E: Natural language, No-code, Easy integration. Think: "Anyone (N-N-E) can automate" - because that is the whole point of Flow Designer.
Real-World Example
A process analyst at a retail company (no coding background) builds a flow in 45 minutes: when a high-priority incident is created, the flow automatically posts an alert to the #critical-ops Slack channel (third-party integration via Slack spoke), creates a Zoom bridge (Zoom spoke), and notifies the on-call manager via SMS (Twilio spoke). Her manager reviews the flow by reading the natural-language step descriptions: "When Priority = 1, then Post Message to Slack, then Create Zoom Meeting, then Send SMS." No code was written.
- AAgent Assist
- BVirtual Agent
- CNow Messenger
- DConnect Agent
Show full explanation
Correct Answer
B. Virtual Agent
Source
ServiceNow Zurich - Virtual Agent
If the link fails, search Google for: ServiceNow Zurich Virtual Agent chatbot knowledge articles conversational
Expert Explanation
Virtual Agent is ServiceNow's AI-powered chatbot that delivers self-service support through a conversational interface. Key capabilities:
- Users type questions in natural language, and Virtual Agent searches the knowledge base for matching articles
- It uses topic conversations - pre-built dialog flows that guide users through common requests
- Supports Natural Language Understanding (NLU) to interpret user intent beyond simple keyword matching
- Can create incidents, check ticket status, and perform catalog requests - all through chat
- Seamlessly escalates to a live agent when the bot cannot resolve the issue
Virtual Agent reduces ticket volume by enabling users to find answers through conversation rather than browsing knowledge portals or calling the help desk.
Why the Others Are Wrong
- A - Agent Assist: Helps human agents by suggesting articles during live support sessions. It is an agent productivity tool, not a user-facing conversational interface.
- C - Now Messenger: Not the official name of this capability. ServiceNow's conversational AI feature is specifically branded as Virtual Agent.
- D - Connect Agent: A live-chat tool for human agents to communicate with users in real-time. It requires a human on the other end - it is not an automated chatbot.
Memory Tip
Virtual Agent = Virtual (no real human) + Agent (acts like a support agent). It is the robot version of a help desk agent that chats with users and serves up knowledge articles automatically.
Real-World Example
An employee at an accounting firm opens the ServiceNow portal at 11 PM and types "my laptop won't connect to WiFi" into the Virtual Agent chat window. The bot uses NLU to identify the intent as a network connectivity issue, pulls up a knowledge article titled "WiFi Troubleshooting Steps," and walks the user through a 4-step diagnostic conversation. The employee resolves the issue without ever submitting a ticket or waiting for a human agent, saving approximately 15 minutes of help desk time.
Free exam updates. No spam. Unsubscribe anytime.
Prefer to skip the email? Get all 392 questions on Udemy. 30-day money-back guarantee.
You scored 0/15 on the 15-question preview.
The full course keeps the same answer breakdown style across all 392 questions.
A failed exam attempt costs $150 to retake.
Many students also study:
Compare all 18 practice tests, or use the cert quiz to plan what to study next.
Common questions
How many questions are in the full CSA practice test?
The full course has 392 questions on Udemy. Every answer option has its own explanation, and the explanations link to official ServiceNow documentation.
Is there a refund if the course is not right for me?
Yes. Udemy courses come with a 30-day money-back guarantee.
Will this practice test guarantee I pass?
No. Practice tests show you where you are weak. They do not replace hands-on work, so pair them with a free ServiceNow Personal Developer Instance.
How much does the real CSA exam cost?
The exam costs $300 for a first attempt and $150 for a retake. Fees can change, so check ServiceNow University before you register.
Which certification should I take first?
Most people start with CSA. If you are unsure, take the 2-minute recommendation quiz or read the certification path guide.
Read the full CSA study guide for domain weights, a study plan, and common mistakes.
Next step after CSA: Certified Application Developer. Not the right exam? Take the 2-minute quiz or compare all 18.
Browse all 18 practice tests →