ServiceNow Certified System Administrator (CSA) Practice Exam

What the ServiceNow Certified System Administrator (CSA) exam covers

• User Interface and Navigation119 questions
• Collaboration95 questions
• Database Administration127 questions
• Self-Service and Automation142 questions
• Data and Reporting103 questions
• Administration and Security112 questions
• Data Management and Migration95 questions

Free CSA practice test questions

A sample of 10 questions with answers and explanations. Sign up free to practice all 793.

1. Question 1Administration and Security

   Which table stores individual user records in ServiceNow, such as name, email, and login information?

   • Asys_userCorrect
   • Bsys_user_group
   • Csys_user_has_role
   • Dsys_user_grmember
   ✓ Correct answer: A

   sys_user is the platform's core User table, storing each person's identity fields such as name, email, and login information directly on the record. The sys_user_* variants are separate join or child tables: sys_user_group holds group definitions, sys_user_has_role links users to roles, and sys_user_grmember links users to groups. Recognizing that pattern - sys_user for the person, sys_user_x for relationships - is a fast way to navigate ServiceNow's user administration data model.

   Why the other options are wrong

   • Bsys_user_group stores the group records themselves, such as name and manager, not the user's own identity data.
   • Csys_user_has_role is a join table linking a user to a role; it does not hold the user's personal details.
   • Dsys_user_grmember records which groups a user belongs to; it does not store the user's core profile fields.
2. Question 2Administration and Security

   Following the principle of least privilege when assigning access, which approach is most appropriate for a new fulfiller who only works incidents and problems?

   • AGrant the security_admin role so they can adjust ACLs as needed
   • BGrant no role at all, since itil is optional for working tasks
   • CGrant the itil role rather than the broader admin roleCorrect
   • DGrant the admin role so no future access issues arise
   ✓ Correct answer: C

   Following least privilege, a new fulfiller who only works incidents and problems should be granted the itil role, which is scoped specifically to that fulfillment work, rather than the far broader admin role or the security-focused security_admin role. The key concept is granting exactly the access needed for the job and nothing more, which limits the damage a compromised or misused account can do. Applied here, itil gives the fulfiller what they need for incident and problem work without also handing them instance-wide configuration or security control. Granting no role at all is not a least-privilege option either, since the fulfiller would then lack the access actually required to do the job. The takeaway is that least privilege means the minimum role that still lets someone do their actual work, not zero access.

   Why the other options are wrong

   • Asecurity_admin is scoped to security configuration, not to the routine work of a task fulfiller; granting it here far exceeds what is needed.
   • BGranting no role at all would leave the fulfiller without the access typically needed to work incidents and problems; some scoped role is still required.
   • DGranting admin far exceeds what a fulfiller needs for incident and problem work and directly contradicts least privilege.
3. Question 3Self-Service and Automation

   What is a knowledge article?

   • AA piece of content in a knowledge base documenting information for self-help readingCorrect
   • BA record producer that is specifically configured to write directly to the Incident table
   • CA variable set that is shared for reuse across several different catalog items
   • DA Catalog Task record that has been assigned to a specific fulfillment group
   ✓ Correct answer: A

   An article is the actual unit of documentation content, living inside a knowledge base, that end users and agents can search for or browse to find information and resolve their own questions without needing to open a formal request. This is distinct from every other catalog or fulfillment object in the platform, since an article's purpose is purely informational rather than transactional. The other options each describe a different kind of record: a record producer targeting Incident is a catalog object that creates task records, a shared variable set is a catalog form-building object, and a Catalog Task is a fulfillment record assigned to a group, none of which is documentation content. The takeaway is that an article's job is to inform, not to trigger or track a request.

   Why the other options are wrong

   • BA record producer configured to write to the Incident table is a catalog object used to create records, not a piece of documentation content.
   • CA variable set shared across catalog items is a form-building object used on catalog items, unrelated to knowledge documentation.
   • DA Catalog Task assigned to a fulfillment group is a fulfillment record, not a piece of self-help reading content.
4. Question 4Self-Service and Automation

   What is a Data Lookup Rule commonly used for?

   • AAutomatically populating default field values from matching conditionsCorrect
   • BDefining the schedule that an SLA definition uses for business hours
   • CPublishing a new version of a classic workflow after editing
   • DSending a notification once a task record has been approved
   ✓ Correct answer: A

   A is correct: a data lookup rule matches values on an incoming record, such as category or location, against a lookup table and then automatically fills in fields like assignment group, reducing the amount of manual data entry needed on new or changed records. B is wrong because an SLA's business-hours schedule is configured directly on the SLA Definition record, unrelated to data lookup rules. C is wrong because publishing a new classic workflow version is a separate administrative action with no connection to data lookup rules. D is wrong because sending an approval notification is handled through the notification system, not through data lookup rules, which only populate field values rather than send messages. Data lookup rules exist purely to default fields based on matched data.

   Why the other options are wrong

   • BAn SLA definition's business-hours schedule is configured directly on the SLA Definition record, unrelated to data lookup rules.
   • CPublishing a new classic workflow version is a separate administrative action with no connection to data lookup rules.
   • DSending an approval notification is handled by the notification system, not by a data lookup rule, which only sets field values.
5. Question 5Collaboration

   An administrator wants normal changes above a certain risk level to automatically require CAB approval, while low-risk changes skip it. How is this typically achieved?

   • AThrough approval rule conditions that generate CAB approval only when the risk threshold is metCorrect
   • BBy manually emailing the CAB chair individually for every single change regardless of risk
   • CBy changing the change request record's number prefix format
   • DBy deleting the risk field from the change request form entirely
   ✓ Correct answer: A

   The administrator achieves risk-based CAB approval by writing the approval rule's condition to check the change's risk field, so a CAB approval record is generated only when that risk threshold is met, letting lower-risk changes skip the step automatically (option A). This is the intended use of approval rule conditions: rather than hardcoding behavior per change, the rule evaluates the record's actual data at the moment it needs an approval and reacts accordingly. This fits the scenario precisely because the requirement is conditional, above a threshold, rather than universal, which is exactly what a condition-based rule is designed to express. Manually emailing every time, changing number formats, or deleting the risk field would either defeat the automation goal or remove the very data the rule depends on. Takeaway: condition-based approval rules let risk, or any other field, determine whether a specific approval is generated.

   Why the other options are wrong

   • BManually emailing the CAB chair for every single change regardless of risk defeats the purpose of automated, condition-based approval routing.
   • CChanging the change request's number prefix format has no bearing on which changes require CAB approval.
   • DRemoving the risk field would eliminate the exact data the approval rule's condition needs to evaluate, breaking the intended automation entirely.
6. Question 6Data Management and Migration

   Which of the following changes would normally be captured in an update set moved between instances?

   • AA change to a UI policy's conditionCorrect
   • BA new record in the Incident table
   • CA user adding a value to a Company record
   • DA new attachment on a Change request
   ✓ Correct answer: A

   Option A is correct: UI policies are configuration records the platform tracks for update sets, so modifying one, including its condition, gets captured for promotion to another instance. A new record in the Incident table is transactional data rather than configuration, which update sets are designed to exclude, ruling out option B. A user adding a value to a Company record is a data edit on a reference record, not a configuration change, so option C is also wrong. A new attachment on a Change request is likewise treated as data tied to a transactional record, not application configuration, making option D incorrect. Takeaway: configuration objects like policies, rules, and forms travel; data on records does not.

   Why the other options are wrong

   • BA new record in the Incident table is transactional data, which update sets are designed to exclude from capture.
   • CA user adding a value to a Company record is a data change on a reference record, not application configuration.
   • DA new attachment on a Change request is data tied to a transactional record, not a configuration change.
7. Question 7Database Administration

   Which field type is designed to hold multiple record references at once, such as multiple watchers on a record?

   • AChoice
   • BString
   • CGlide ListCorrect
   • DReference
   ✓ Correct answer: C

   C is correct - unlike a standard Reference field, which points to exactly one record, Glide List is designed to store a set of multiple sys_ids, letting one field represent several related records simultaneously. This makes Glide List the right choice whenever the relationship between the field and other records is genuinely one-to-many from that field's perspective, such as tracking every watcher rather than a single one. Multiple watchers on a record is a textbook Glide List use case, since any number of people could need to be tracked in that one field. Choice stores fixed option values with no record-pointing behavior at all, String stores plain text rather than references, and Reference is capped at a single related record rather than a list of them. When a single field needs to reference many records at once, Glide List is the type built for that.

   Why the other options are wrong

   • AChoice stores a value from a fixed predefined list; it does not point to records on another table at all.
   • BString stores plain text; it has no capability to reference or point to other records.
   • DA standard Reference field is limited to exactly one related record, not a set of multiple references.
8. Question 8Data and Reporting

   Which report type displays individual records in rows with selected columns, essentially mirroring what a filtered list view of a table shows, without grouping or aggregating the data?

   • AList reportCorrect
   • BColumn chart
   • CHeatmap
   • DFunnel chart
   ✓ Correct answer: A

   A is correct: a List report deliberately skips aggregation, presenting matching records exactly as a filtered list view would, with the chosen fields as columns. This is the one report type built for showing actual records rather than a summarized count, useful whenever the audience needs to see the records themselves. Column charts and heatmaps both require grouping to produce their visuals, and a funnel chart tracks staged counts rather than listing records. List report is essentially a report-native version of a filtered list view.

   Why the other options are wrong

   • BA column chart groups records and plots aggregated counts as vertical bars; it does not list individual records.
   • CA heatmap shows a color-coded matrix of two grouped dimensions, not individual records.
   • DA funnel chart shows counts narrowing across sequential stages, not a row-by-row record list.
9. Question 9Data and Reporting

   A team wants a dashboard tab that shows both a Performance Analytics scorecard trend and a real-time incident report side by side. Is this combination possible on one dashboard?

   • AYes, a dashboard tab can host multiple widget types togetherCorrect
   • BNo, a dashboard can only ever contain Performance Analytics content
   • CNo, a dashboard can only contain standard reports, never PA content
   • DNo, each dashboard tab can only ever hold exactly one widget
   ✓ Correct answer: A

   The correct answer is yes, a dashboard tab can host multiple widget types together, because dashboards are specifically designed to combine different kinds of content, including standard, real-time reports and Performance Analytics scorecards, side by side on the same tab. The key concept is that a dashboard's widget catalog is not restricted to one content family; it deliberately spans multiple sources so different perspectives can be viewed together. This directly answers the scenario's need to combine a PA trend view with a live incident report, since that mixing is exactly what dashboards support rather than something requiring a workaround. Dashboards are not restricted to only PA content, nor are they restricted to only standard reports, and a tab is not limited to a single widget, since multiple widgets of any supported type can share the same tab, which is why each of the other three answers overstates a limitation that does not exist.

   Why the other options are wrong

   • BDashboards are not restricted to only Performance Analytics content; standard reports and other widget types can also be added freely.
   • CDashboards are not restricted to only standard reports either; Performance Analytics scorecards and indicators can be added as widgets too.
   • DA dashboard tab can hold multiple widgets at once; it is not limited to exactly one widget per tab.
10. Question 10User Interface and Navigation

    A UI Policy makes a field mandatory only when Category equals Hardware. What happens when that condition is false?

    • AThe field stays mandatory regardless of the condition
    • BThe mandatory requirement is not enforcedCorrect
    • CThe field is permanently deleted
    • DThe record cannot be saved at all
    ✓ Correct answer: B

    B is correct: because the UI Policy only ties the mandatory requirement to Category equaling Hardware, that requirement only takes effect while the condition actually evaluates to true; the instant Category is anything other than Hardware, the condition is false, and the field reverts to whatever its normal, non-mandatory state would otherwise be, so it is not required and the record can be saved without a value in it. This conditional, on-or-off enforcement is the entire point of building a UI Policy around a condition rather than making a field permanently mandatory, and it is the concept being tested. The field certainly does not stay mandatory regardless of the condition, that would defeat the entire purpose of adding a condition in the first place. The field is not deleted either, UI Policies never remove fields from the table, they only adjust behavior like visibility or mandatory status. And the record can absolutely still be saved, since nothing is blocking it once the condition is false and the requirement lifts. Remember: a conditional UI Policy is only 'on' while its condition holds true.

    Why the other options are wrong

    • AA conditional UI Policy's requirement only applies while its condition is true; it does not stay mandatory regardless of the condition.
    • CUI Policies adjust field behavior like visibility or mandatory status; they never permanently delete a field from the table.
    • DOnce the condition is false, the mandatory requirement lifts and the record can be saved normally; saving is not blocked.

Who this ServiceNow Certified System Administrator (CSA) practice exam is for

This practice set is for anyone preparing for the ServiceNow Certified System Administrator (CSA) exam at the intermediate level - from first-time candidates building a foundation to experienced ServiceNow practitioners doing a final review before test day. If you learn best by working through realistic questions and reading why each answer is right or wrong, it is built for you.

How to use this ServiceNow Certified System Administrator (CSA) practice exam

1. Start with the free sample questions above to gauge your current baseline.
2. Read the full explanation on every question, including why each wrong option is wrong.
3. Track your weak domains and focus your study where you are losing the most marks.
4. Once you are scoring consistently well, take a timed, full-length mock exam.
5. Use your readiness score to decide when you are ready to book the real ServiceNow Certified System Administrator (CSA) exam.

Related ServiceNow resources

• ServiceNow Certified System Administrator (CSA) study guideKey concepts
• ServiceNow practice examsAll ServiceNow
• Certification pathWhere this fits
• Certification exam guides & tipsBlog
• Plans & pricingFree & paid
• How these questions are written and reviewedMethodology
• Report a problem with a questionCorrections
• ServiceNow Certified Application Developer (CAD) practice examRelated

ServiceNow Certified System Administrator (CSA) practice exam FAQ