ServiceNow CIS-CSA - Certified System Administrator

Domain 1: Platform Overview and Navigation — 7%

Platform navigation provides the foundation for nearly every administrative task covered elsewhere on the exam.

You’ll need to understand the unified navigation model, applications, modules, favorites, history, filters, lists, forms, and the major interfaces used across the platform. Focus on what each navigation element helps a user accomplish rather than memorizing screen layouts. Practice opening records, following references, creating filters, personalizing lists, and using context menus. Pay attention to the difference between ordinary user navigation and administrative capabilities. The exam may describe where a user should go or what action they need to perform without naming the feature directly, so hands-on familiarity matters more than memorized definitions.

Domain 2: Instance Configuration — 10%

Instance configuration establishes the environment in which users, applications, and processes operate.

You’ll need to understand system properties, branding, localization, time zones, languages, user preferences, plugins, and common administrative settings. Pay attention to the scope and impact of each change. Some settings affect the entire instance, while others apply only to an individual user or a specific application. Don’t confuse personalization with configuration or customization. A small property change can alter behavior across multiple applications, so administrators should understand ownership, dependencies, and upgrade implications before changing global settings. The exam often tests who will be affected by a configuration and where that setting is controlled.

Domain 3: Configuring Applications for Collaboration — 20%

Collaboration features help teams share information, route work, and interact with records consistently.

You’ll need to understand forms, lists, views, templates, notifications, tasks, visual task boards, assignment rules, activity streams, and related configuration tools. Each feature serves a different purpose. A notification pushes information, a report summarizes it, a template speeds up data entry, and an assignment rule routes work to the correct owner. Study field types, related lists, filters, form layouts, and list behavior. Use configuration before custom scripting when the platform already supports the requirement. Strong collaboration design reflects how work moves between people rather than simply reproducing one administrator’s preferred screen layout.

Domain 4: Self-Service and Automation — 20%

Self-service works when users can request the right service, provide useful information, and receive a predictable result without opening a vague ticket.

You’ll need to understand the service catalog, catalog items, record producers, variables, knowledge, approvals, Flow Designer, SLAs, and common automation patterns. Follow how a user submission creates records, triggers approvals, generates fulfillment work, and communicates progress. Common failures include unclear variables, approval loops, missing ownership, and flows that fail without visible errors. Don’t automate a poorly defined process. Simplify the steps, establish ownership, and make exceptions easy to identify before building automation. The goal is reliable fulfillment and useful self-service, not simply replacing a manual form with an online one.

Domain 5: Database Management and Platform Security — 30%

This is the largest CSA domain and combines the platform’s data model with the controls used to protect it.

You’ll need to understand tables, fields, references, dictionary entries, table extensions, schema relationships, users, groups, roles, and access control rules. Study how child tables inherit fields and behavior from parent tables, and how table-, record-, and field-level ACLs combine to determine access. Hiding a field on a form doesn’t secure the underlying data. User-interface behavior and authorization serve different purposes. Practice using schema tools and security debugging to trace why a user can or can’t perform an operation. Reliable administration depends on both a clean data model and understandable access rules.

Domain 6: Data Migration and Integration — 13%

Data migration and integration move records or configuration between systems while preserving meaning, ownership, and relationships.

You’ll need to understand data sources, import sets, transform maps, coalescing, web-service concepts, update sets, and application delivery. Record data and configuration metadata require different movement methods, so don’t treat every transfer as the same type of migration. Study how incoming data is staged, mapped, transformed, and validated before reaching a target table. A successful import can still create duplicates or broken references when identifiers and mappings are wrong. Configuration movement also requires planning for dependencies, conflicts, testing, and rollback. The goal is a repeatable process that validates results rather than merely confirming that an export or import completed.