Overview
Domain 1 covers the foundations: what the ServiceNow Platform is, which capabilities and shared services it provides, what an instance is and how it is hosted, and how to move around it with Next Experience Unified Navigation. You need to know that every application (ITSM, HR, customer service, custom apps) runs on one data model and one set of platform services, and that each customer gets a dedicated instance with its own database rather than a shared multi-tenant database.
The navigation half is practical. You should know the All, Favorites, History and Workspaces menus, the application navigator filter, the user menu (preferences, impersonation, role elevation), and the filter-navigator shortcuts such as table.list and table.LIST. Domains 2 and 3 build directly on this vocabulary, because questions about configuring forms or lists assume you already know where those screens live.
How it's tested
Domain 1 questions are mostly direct identification: which menu holds a feature, what a shortcut does, which statement about the instance or architecture is true. A few are mini scenarios where an administrator needs to reach a list, test as another user, or find a recently viewed record. Precise interface terms decide the answer, so learn the Next Experience names exactly.
-
Where do I find it
You are told what a user wants to reach (a recent record, a saved module, a workspace) and must pick the Unified Navigation menu or feature that gets there.
-
Shortcut behaviour
A filter-navigator entry such as incident.list, incident.LIST or incident.form is given and you identify what it opens and where.
-
Architecture truth
Several statements describe instances, hosting or the data model, and you choose the accurate one, often contrasting multi-instance with shared multi-tenant designs.
A question says an administrator must check what a fulfiller sees on an incident form without knowing the fulfiller's password. Options include resetting the password, granting the admin the itil role, elevating to security_admin, and impersonating the user. Only impersonation shows the platform exactly as that user's roles and groups allow. Role elevation adds privileges to the admin, which is the opposite of the goal.
Objectives 4
Official objectives from the ServiceNow outline, in outline order.
1.1 ServiceNow Platform overviewOne platform, one data model, many applications.
- What it means
- ServiceNow is a cloud platform on which every product (IT service management, HR service delivery, customer service, custom apps) shares the same database model, user records, security model and workflow engine.
- What to understand
- Because applications share one data model, a record created in one app (for example a configuration item) can be referenced by another (an incident or change) without integration work. The platform is delivered as a service, so ServiceNow upgrades the code by release family while customers configure on top of it.
- How it shows up
- A question asks why a new HR case can reference the same user and location records already used by IT, and the answer is the single shared data model.
- Common confusion
- Candidates picture each application as a separate product with its own database and integration layer, which is how many legacy tool stacks work but not how ServiceNow works.
1.2 Platform capabilities and servicesThe shared services every application inherits.
- What it means
- Capabilities such as workflow automation, notifications, reporting and analytics, knowledge, the Service Catalog, mobile and portal interfaces, integrations and AI features are platform services that any application can use.
- What to understand
- Know which needs are met by a built-in platform service rather than custom code: approvals and automation through Workflow Studio, user-facing requests through the Service Catalog, dashboards through Platform Analytics, chat through Virtual Agent. Recognising the right capability is the first step in many later-domain questions.
- How it shows up
- A business requirement is described in plain language and you choose the platform capability that satisfies it without scripting.
- Common confusion
- Confusing a capability with an application: Platform Analytics or Virtual Agent are services usable by many apps, while Incident Management is an application built on those services.
1.3 The ServiceNow InstanceA dedicated, hosted copy of the platform.
- What it means
- An instance is a single customer's deployment of the platform, reached at a URL such as company.service-now.com, with its own application logic and its own database, hosted in paired ServiceNow data centers.
- What to understand
- ServiceNow uses a multi-instance architecture, so customer data is not mixed in a shared database with other customers. Organisations normally run a production instance plus sub-production instances (development, test) and move configuration between them with update sets, while clones copy production data down to sub-production.
- How it shows up
- Scenarios ask where to build and test a change safely, expecting a sub-production instance rather than production.
- Common confusion
- Treating multi-instance as multi-tenant: in a multi-tenant design customers share one database, whereas each ServiceNow instance keeps its own.
1.4 Next Experience Unified NavigationThe All, Favorites, History and Workspaces menus and their tools.
- What it means
- Next Experience is the current core user interface. Unified Navigation gives a top bar with the All menu (application navigator with a filter field), Favorites, History, Workspaces, a contextual app pill, global search and a user menu.
- What to understand
- The All menu lists application menus and the modules under them; typing in its filter narrows them or accepts shortcuts such as incident.list (list in the current tab), incident.LIST (list in a new tab) and incident.form (new record). Favorites stores starred modules, lists and records; History shows recently visited lists and records; the user menu holds preferences, impersonation and role elevation.
- How it shows up
- You are asked how a user returns to a record viewed earlier today (History) or keeps one-click access to a filtered list (Favorites).
- Common confusion
- Mixing up History and Favorites, or assuming lowercase and uppercase shortcuts behave the same when the uppercase form opens a new browser tab.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Multi-instance architecture
Each customer runs on a dedicated instance with its own application logic and its own database, rather than sharing a database with other customers.
- Remember
- Isolation is at the instance level, which is why one customer's upgrade schedule and data never affect another's.
- Tested as
- Architecture statements often hinge on whether customer data is shared, and the correct answer is that it is not.
- Trap
- Choosing an option that calls ServiceNow a shared multi-tenant database because many cloud products work that way.
-
Production and sub-production instances
Production serves real users; sub-production instances (often named dev and test) exist for building and testing changes.
- Remember
- Build in development, test in test, then move configuration to production with update sets.
- Tested as
- Any question about trying a plugin, form change or script safely expects a sub-production instance.
- Trap
- Selecting 'make the change in production after hours', which still exposes real data and users to an untested change.
-
Application menu and module
An application menu groups related links in the All menu; each module is one link that opens a list, form, report, page or URL.
- Remember
- Modules can be restricted by role, so two users can see different modules under the same application menu.
- Tested as
- Questions about why a user cannot see a link usually turn on module roles.
- Trap
- Assuming a missing module means the user lacks access to the underlying table, when only the link may be hidden.
-
Filter navigator shortcuts
Typing a table name followed by a suffix into the All menu filter opens that table directly.
- Remember
- table.list opens the list in the current tab, table.LIST in a new tab, table.form a new record in the current tab and table.FORM a new record in a new tab.
- Tested as
- Shortcut behaviour is a classic one-line recall item.
- Trap
- Treating the uppercase and lowercase versions as identical.
-
Favorites
A personal menu of starred modules, lists or records, which a user can rename and reorder.
- Remember
- A filtered list can be saved as a favorite, keeping the filter for one-click reuse.
- Tested as
- Appears when a user wants permanent quick access to something they use daily.
- Trap
- Answering History, which only shows recent items and does not persist the user's choice.
-
History
A menu of lists and records the user recently visited, ordered by time.
- Remember
- History is automatic and personal; nothing needs to be saved for an item to appear there.
- Tested as
- The answer when a user needs to get back to a record they opened earlier.
- Trap
- Choosing global search, which works but requires knowing a search term instead of recalling the visit.
-
Impersonation
An administrator can act as another user from the user menu to see exactly what that user's roles and groups allow.
- Remember
- Anything done while impersonating is recorded as that user, so impersonate for testing in sub-production where possible.
- Tested as
- The standard answer when an admin must verify another user's view or access.
- Trap
- Picking a password reset or role change, which alters the account instead of observing it.
-
Role elevation (security_admin)
Some high-privilege roles, notably security_admin, are elevated roles that must be activated for the session from the user menu before use.
- Remember
- Holding security_admin is not enough; you elevate to it, typically to edit access control rules.
- Tested as
- Explains why an admin cannot edit an ACL even though the role is assigned.
- Trap
- Thinking the admin role alone can create or change ACLs.
-
Workspaces menu
Lists the configurable workspaces (task-focused agent interfaces) the user can open, such as Service Operations Workspace.
- Remember
- Workspaces are separate experiences from the classic list and form views, opened from their own menu.
- Tested as
- Appears when a fulfiller needs a consolidated agent view rather than the classic interface.
- Trap
- Looking for a workspace inside the All menu modules instead of the Workspaces menu.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Favorites vs. History vs. global search
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Favorites | Items the user deliberately starred | Persistent and user-curated, including filtered lists | Expecting items to appear without starring them |
| History | Lists and records recently visited | Automatic and time-ordered; older items fall off | Using it for permanent quick access |
| Global search | Keyword search across configured sources | Finds records you have never opened | Picking it when the question says the user visited the record earlier |
Multi-instance vs. multi-tenant
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Multi-instance (ServiceNow) | Each customer has its own instance and database | Data, upgrades and performance are isolated per customer | Calling ServiceNow multi-tenant |
| Multi-tenant | Many customers share one application and database, separated logically | One shared schema and upgrade path for everyone | Assuming isolation guarantees are the same |
Impersonation vs. role elevation
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Impersonation | Act as another user | You see less or different access, exactly as that user | Using it to gain privileges |
| Role elevation | Activate an elevated role you already hold | You gain more privilege for the session | Using it to test what an ordinary user sees |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Multi-tenant wording
- What candidates pick
- A statement that all customers share one database separated by tenant ids.
- Why it looks right
- Most SaaS products are built that way, so it sounds like standard cloud design.
- Why it's wrong
- ServiceNow gives every customer a dedicated instance with its own database; isolation is physical at the instance level.
Clue to watch for Any option mentioning a shared database or shared schema across customers.
-
History for permanent access
- What candidates pick
- History when a user wants a filtered list available every morning.
- Why it looks right
- History does show lists the user opened before.
- Why it's wrong
- History is temporary and does not keep a chosen filter as a named item; Favorites saves the filtered list permanently.
Clue to watch for Words like 'every day', 'quick access' or 'save' point to Favorites.
-
Shortcut case ignored
- What candidates pick
- incident.list when the requirement is to open the list in a new tab.
- Why it looks right
- It is the shortcut most people remember.
- Why it's wrong
- Lowercase .list opens the list in the current tab; uppercase .LIST opens it in a new browser tab.
Clue to watch for The phrase 'new tab' or 'new window' in the stem.
-
Granting roles to test
- What candidates pick
- Temporarily add the itil role to the admin account to see a fulfiller's view.
- Why it looks right
- It seems to reproduce the fulfiller's access.
- Why it's wrong
- The admin keeps all admin access, so the view is not what the fulfiller sees; impersonation reproduces the real user's roles and groups.
Clue to watch for The goal is to see what a specific user sees.
-
Admin can do everything
- What candidates pick
- The admin edits an ACL directly with only the admin role active.
- Why it looks right
- Admin is described as the most powerful role.
- Why it's wrong
- ACL changes require the security_admin role, which must be elevated for the session first.
Clue to watch for The task involves access control rules or other security settings.
-
Testing in production
- What candidates pick
- Activate a new plugin in production during a quiet period.
- Why it looks right
- It avoids the effort of keeping instances aligned.
- Why it's wrong
- Plugins and configuration should be validated in a sub-production instance first; some plugins cannot be deactivated once active.
Clue to watch for The stem mentions trying, evaluating or testing something new.
Answer framework
Use these steps to answer navigation and architecture questions in Domain 1.
- Identify whether the question is about architecture (instances, data, hosting) or interface (menus, shortcuts, user menu) before reading the options.
- For architecture, test each option against the multi-instance model: one customer, one instance, one database, with sub-production instances for building and testing.
- For navigation, match the user's goal to the menu: saved access means Favorites, recently visited means History, agent experiences mean Workspaces, and everything else starts in All.
- For shortcuts, read the suffix and its case exactly, because .list and .LIST differ only in where the list opens.
- For testing another user's view, choose impersonation; for gaining privilege such as editing ACLs, choose role elevation to security_admin.
Practice question
Want more like this? The ServiceNow CSA practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the architecture topics (1.1 to 1.3) because they are short and conceptual: be able to explain the single data model, the multi-instance design and the purpose of sub-production instances in a sentence each. Then move to Unified Navigation, which is better learned by doing than by reading.
Use a free Personal Developer Instance and spend an hour navigating only with the All menu filter. Open lists with .list and .LIST, create records with .form, star a filtered list into Favorites, find it again in History, impersonate a demo user such as an ITIL fulfiller, and elevate to security_admin. Note what changes in the interface each time.
The area candidates underestimate is precise naming: Next Experience labels differ from the older UI16 interface, and the exam uses the current names. Write a one-page map of the top bar and user menu from memory.
Afterwards, move straight to Domain 2, Instance Configuration, and practise a short set of Domain 1 recall questions mixed in with it rather than as a separate block.
FAQ
How many questions come from Platform Overview and Navigation?
The domain is weighted at 7% of a 60-question exam, which works out to roughly four questions as a planning estimate. ServiceNow does not publish per-domain counts.
Is the exam based on UI16 or Next Experience?
Current CSA material uses Next Experience Unified Navigation, so learn its menu names and layout. Older UI16 knowledge still helps for concepts like modules, but labels and locations differ.
Do I need a Personal Developer Instance for this domain?
It is the fastest way to learn navigation, because questions describe actions you can repeat in a few minutes on a real instance. Reading alone makes shortcut and menu questions harder to answer confidently.
What is the difference between an instance and an application?
An instance is the customer's whole hosted deployment with its own database; applications such as Incident or Knowledge run inside it and share its data and services.
Why can an administrator not edit an ACL right away?
Editing access control rules requires the security_admin role, which is an elevated role. The administrator must elevate to it from the user menu for the session before the change is allowed.
How does this domain connect to the rest of the exam?
Instance Configuration and Configuring Applications for Collaboration assume you can reach lists, forms and modules quickly. The multi-instance model also underpins update sets in Data Migration and Integration.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have just worked through instances, Unified Navigation and the shortcuts that trip people up. Check that you can recall them under time pressure with a short practice set.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ServiceNow CSA AI tutor Get any concept explained your way