ServiceNow CSA Exam Blueprint: Domains and Practice Tasks
Map all 30 published ServiceNow CSA subskills to practical exercises and checkpoints, with domain weights, format facts and a coverage record.
The official scope source is ServiceNow’s CSA Mainline Exam Blueprint , updated January 2026 and checked September 16, 2026. The practice tasks below are our study suggestions; consult the complete blueprint for its subtopics and qualifications.
Domain weights and our public practice allocation
| Official domain | Weight | Questions in our fixed 60-question set |
|---|---|---|
| Platform Overview and Navigation | 7% | 4 |
| Instance Configuration | 10% | 6 |
| Configuring Applications for Collaboration | 20% | 12 |
| Self Service & Automation | 20% | 12 |
| Database Management and Platform Security | 30% | 18 |
| Data Migration and Integration | 13% | 8 |
Our allocation rounds the published weights to whole questions. It is an editorial distribution, not a claim about the exact composition of a live exam form. One administrative situation may connect several domains.
Notice an easy mapping mistake: the blueprint places Importing Data in Domain 5, while UI policies, Business Rules, update sets and scripting sit in Domain 6. Follow the listed subtopics rather than guessing scope from a domain title.
A practical map of the 30 published subskills
The rows below paraphrase the blueprint’s published subskills. The exercises and completion evidence are our own learning suggestions. ServiceNow describes its subskill list as non-exhaustive; this map is not a promise that every possible exam task appears here.
1. Platform overview and navigation - 7%
| Scope area | Applied exercise |
|---|---|
| Platform fundamentals | Explain how a shared platform can support several business applications without making their workflows identical. |
| Capabilities and services | Given a need to collect work, automate a response or display information, identify the relevant capability before choosing a screen. |
| Instance fundamentals | Identify the environment in which a change is made. Explain why a successful development test does not establish the state of production. |
| Unified navigation | Find a function through navigation, then distinguish an application, module, favorite and history entry. |
Checkpoint: a colleague cannot find a module. Identify what would distinguish a navigation problem from absent functionality or denied data access. Do not begin by assigning a powerful role without understanding the missing capability.
2. Instance configuration - 10%
| Scope area | Applied exercise |
|---|---|
| Application and plugin installation | Inspect dependencies, entitlement and activation requirements. Describe a test plan before proposing installation. |
| Personal versus shared changes | Compare one user’s preference with a configuration that affects other users. State the intended audience and scope. |
| Platform interfaces | Compare the same work in the interfaces available to your lab; identify differences in navigation, view and supported behavior. |
Checkpoint: one user’s preferred columns changed, but a colleague’s did not. Explain why that observation may be correct for personalization. Contrast it with a requirement to change the shared form used by a team. Keep the table, view and user context explicit.
3. Collaboration configuration - 20%
| Scope area | Applied exercise |
|---|---|
| Lists, condition filters and tags | Predict which records match a grouped condition; inspect tag sharing before relying on it for team organization. |
| List/form structure | Distinguish a record, field, column, section, activity stream and related list in an actual task. |
| Form layout | Place relevant fields in the intended view and verify the result as the intended user. |
| Templates and save behavior | Apply reusable values, inspect what changed and distinguish stored results from an unsaved form. |
| More advanced form configuration | Follow a reference or related-record relationship and explain which definition or presentation setting controls the observed behavior. |
| Managing tasks | Interpret assignment group, individual assignee, state and journal communication without assuming one field determines all workflow outcomes. |
| Visual boards | Predict what a card move means for the declared board type and verify the associated record. |
| Analytics and dashboards | Define the source population, filter, aggregation and time basis; distinguish a current snapshot from a historical indicator. |
| Notifications | Trace the qualifying event/change, condition, recipient resolution and generated message. |
Checkpoint: a chart and a list show the same count. Explain why that is not enough to prove they contain the same records. Worked case 7 demonstrates this with four tasks. Then use case 8 to distinguish a trigger failure from an empty recipient.
4. Self service and automation - 20%
| Scope area | Applied exercise |
|---|---|
| Knowledge | Distinguish article lifecycle from reader access, and test the intended audience in the relevant knowledge-base context. |
| Catalog services | Choose between an item, producer and order guide; follow collected variables to the intended target and fulfillment work. |
| Workflow Studio | Trace trigger conditions, inputs, actions and results. Separate a saved design, a test execution and an active production behavior. |
| Conversational service | Follow a Virtual Agent topic through information collection, action result and a supported human-handoff or recovery path. |
Checkpoint: a catalog submission succeeded but no requested item exists. Explain when that is expected for a record producer. Then determine what evidence would establish that an automation or conversation completed its promised work. These are different questions from whether the user saw a confirmation screen.
5. Data and platform security - 30%
| Scope area | Applied exercise |
|---|---|
| Data structure | Interpret a table definition, inherited field, reference and related records. Separate a display label from record identity. |
| Application and data authorization | State the user, object and operation; evaluate the applicable table/field access requirements and decision types. |
| Importing records | Trace staging, field mapping and target matching; reconcile results and inspect the actual updated identities. |
| Configuration/service data | Use CI relationships to explain a service dependency; distinguish the CMDB repository from CSDM modeling guidance. |
| Security posture | Interpret a finding, identify its responsible owner, and verify an authorized correction rather than treating detection as remediation. |
| Shared control responsibilities | Separate provider-operated infrastructure from customer decisions about configuration, users, access and data. |
Checkpoint: two source rows share a contact code but belong to different suppliers. Predict matching when both supplier and contact coalesce. Then construct an access test with an allowed user and a denied user. A successful import and an administrator’s successful read do not by themselves prove correct identity matching or appropriate access.
This is the largest domain by weight. Give its distinct mechanisms separate practice; repeatedly answering definitions of “table” or “role” does not exercise imports, relationships and authorization decisions.
6. Migration, integration and platform logic - 13%
| Scope area | Applied exercise |
|---|---|
| Conditional form policies | Predict visible, mandatory and read-only behavior from the supplied condition, view, On load and Reverse if false settings. |
| Server-side record rules | Choose suitable timing for the stated outcome and distinguish before, after, asynchronous and display processing. |
| Configuration transport | Identify tracked changes and dependencies; separate retrieval, preview, conflict resolution, commit and target verification. |
| Foundational scripting | Trace a short JavaScript condition in its stated execution context. Explain when an available declarative mechanism meets the need. |
Checkpoint: a form script works during interactive entry but its effect is missing from imported data. Identify the absent execution path before proposing a fix. Then explain why an update-set preview cannot establish that transaction data moved or that the resulting application works. Cases 4–6 connect these distinctions.
Connect related domains without losing the main task
A single onboarding request can involve navigation, catalog variables, automation, task assignments, notifications and ACLs. Practise those connections, but identify the actual question being asked:
| Symptom in the same process | Primary investigation |
|---|---|
| Employee cannot find the offering | Catalog availability, navigation and the specific user’s context. |
| Submission creates the wrong record type | Choice of item/producer and target configuration. |
| Correct target exists, but work does not start | Qualifying trigger and execution evidence. |
| Work exists, but another employee cannot read it | The relevant record/field authorization. |
| Dashboard overstates pending work | Population, status filter and aggregation. |
These are original study cases, not an expansion of ServiceNow’s formal domain weights. Broader scenarios should deepen reasoning rather than introduce unrelated specialist material.
Official format and practice scoring
ServiceNow specifies 60 questions in 90 minutes, with single-answer and stated-count multiple-select items. Multiple-select items receive no partial credit. The passing cut score is not publicly shared; do not treat a commonly quoted 70% as an official rule. These facts come from the official blueprint .
Our free set mixes single-answer and Select TWO questions. Its format proportions are a practice choice, not a published ServiceNow distribution. Score a multiple-select practice item as correct only when the selected set exactly matches the explained set. A raw practice percentage is not a pass prediction.
Build a coverage record
For each task above, record studied, performed or traced, explained without notes, and revisited with different facts. A checked topic name alone provides little evidence of usable understanding. Treat an accurately guessed answer as a reason to review the explanation.
Use the study plan for scheduling, the cheat sheet for recall, and worked scenarios for application. The official resources page separates learning, product documentation and credential administration.