Overview
Domain 2 covers three things an administrator does early in an instance's life. First, extending the instance by activating plugins and installing applications from the ServiceNow Store through Application Manager. Second, changing how the instance looks and behaves at different levels: a user personalizing their own view, an administrator configuring for everyone with platform tools such as branding and system properties, and customizing, which means changing out-of-the-box logic and carries upgrade cost.
Third, it covers the common user interfaces and who uses each: the Core UI of lists and forms for administrators and fulfillers, Service Portal and Employee Center for requesters, configurable workspaces for agents, and the mobile apps. The domain connects to Domain 1 through the instance model and to Domain 3, where the same personal-versus-global question appears for lists and forms.
How it's tested
Questions in this domain usually describe a request from a user or manager and ask which approach meets it with the least impact. Expect BEST or MOST appropriate wording, where several options technically work but only one limits the change to the right audience or avoids altering out-of-the-box code. Plugin questions test where activation happens and what follows from it.
-
Scope of change
A request affects one user or all users, and you choose personalization or configuration accordingly.
-
Least invasive option
Several solutions work, and the right one uses configuration instead of customizing out-of-the-box records or scripts.
-
Right interface for the audience
A persona is described (requester, fulfiller, administrator, mobile user) and you pick the interface built for them.
A department head wants the company logo and colours in the instance header for everyone. Options include editing each user's preferences, modifying the out-of-the-box header script, creating a theme for Next Experience, and asking users to personalize. Branding is a global configuration done with platform tools, so the theme is right. Editing the header script is customization with upgrade risk, and per-user preferences do not scale.
Objectives 3
Official objectives from the ServiceNow outline, in outline order.
2.1 Installing applications and pluginsExtending the instance through Application Manager and the Store.
- What it means
- Plugins are ServiceNow-provided components that add features (for example a module set or an integration) and applications are packaged products, many from the ServiceNow Store. Administrators activate or install both through Application Manager.
- What to understand
- Activating a plugin can also activate the plugins it depends on, may offer optional demo data, and in most cases cannot be reversed, so activation belongs in a sub-production instance first. Some plugins need a subscription entitlement or a request to ServiceNow, and Store applications carry their own versions that can be updated separately from the release family.
- How it shows up
- A question asks what an administrator should do before activating a plugin in production, expecting a test activation in a sub-production instance and a review of dependencies.
- Common confusion
- Assuming a plugin can simply be turned off after a trial, the way a feature toggle works.
2.2 Personalizing/customizing the instancePersonalization, configuration and customization, and their reach.
- What it means
- Personalization is a user changing their own experience (list columns through the list gear, theme, language, date format, notification preferences). Configuration is an administrator changing the instance for others with platform tools (branding, system properties, list and form layouts). Customization is changing out-of-the-box code or records, such as editing a base business rule.
- What to understand
- Personal choices are stored as user preferences and affect only that user, while system properties and themes affect everyone. Customizations are the costly level: modified out-of-the-box records are skipped during upgrades and must be reviewed, so the preferred answer is usually configuration over customization.
- How it shows up
- A requirement is given and you choose whether it should be met by a user preference, a configuration change or, rarely, a customization.
- Common confusion
- Treating any administrator change as customization, when the exam reserves that word for altering out-of-the-box logic or code.
2.3 Common user interfaces in the PlatformCore UI, portals, workspaces and mobile, matched to their users.
- What it means
- The platform offers several interfaces on the same data: the Core UI (Next Experience lists and forms) for administrators and fulfillers, Service Portal and Employee Center for self-service requesters, configurable workspaces for agents handling queues, and mobile apps for both requesters and fulfillers.
- What to understand
- The interface changes how data is presented and what actions are offered, not the underlying records or the access controls on them. Requesters are steered to the portal, agents to workspaces, and administrators work mostly in the Core UI where configuration tools live.
- How it shows up
- A persona and a goal are described (an employee requesting a laptop, an agent working a queue) and you pick the interface intended for that persona.
- Common confusion
- Thinking each interface has its own copy of the data, or that hiding a field in one interface secures it in all of them.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Plugin
A ServiceNow-provided package of features, tables and scripts activated in an instance to add capability.
- Remember
- Most plugins cannot be deactivated after activation, so test them in sub-production first.
- Tested as
- Questions about adding a feature safely expect a sub-production trial and a dependency review.
- Trap
- Choosing to activate in production and deactivate if problems appear.
-
Application Manager
The console where administrators find, install, update and activate ServiceNow applications and plugins, including Store apps.
- Remember
- It shows installed versions and available updates for Store applications.
- Tested as
- The correct location answer for installing or updating applications.
- Trap
- Looking for Store apps in Update Sets, which move custom configuration, not entitled products.
-
Plugin dependencies and demo data
Activating a plugin may automatically activate the plugins it relies on and may offer optional demonstration records.
- Remember
- Demo data is optional and usually unwanted in production.
- Tested as
- Appears in questions about what else changes when a plugin is activated.
- Trap
- Loading demo data in production because it was offered by default.
-
User preference
A per-user setting, such as list columns, theme or time zone, stored as a preference record for that user.
- Remember
- Personal changes affect only the user who makes them.
- Tested as
- The answer when a single user wants something different without affecting colleagues.
- Trap
- Choosing an administrator configuration change that alters the view for everyone.
-
System property
An instance-wide setting stored in the System Properties table that controls platform behaviour.
- Remember
- Properties apply to every user, so change them deliberately and test first.
- Tested as
- Used when behaviour must change globally without scripting.
- Trap
- Expecting a system property change to affect only the administrator who made it.
-
Configuration vs. customization
Configuration uses platform tools to adjust behaviour; customization changes out-of-the-box code or records.
- Remember
- Customized out-of-the-box records are flagged during upgrades and need review, which adds cost.
- Tested as
- Drives most 'best approach' questions in this domain.
- Trap
- Picking a script edit because it is quicker, when a configuration option exists.
-
Next Experience themes (branding)
Branding such as logo and colours is applied globally through themes in Next Experience.
- Remember
- Branding is configuration, not customization, and affects all users who receive the theme.
- Tested as
- The answer for company logo and colour requests.
- Trap
- Editing interface scripts or style sheets directly.
-
Service Portal and Employee Center
Self-service web interfaces where requesters browse the catalog, read knowledge and track requests.
- Remember
- They present the same records as the Core UI in a simpler, requester-friendly layout.
- Tested as
- The expected interface for non-technical end users.
- Trap
- Sending requesters to the Core UI list of incidents.
-
Configurable workspaces
Agent-focused interfaces that combine lists, record pages and contextual tools for working queues.
- Remember
- Workspaces are opened from the Workspaces menu and are aimed at fulfillers, not requesters.
- Tested as
- The answer when an agent needs a consolidated working view.
- Trap
- Choosing the portal for agents because it looks simpler.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Personalization vs. configuration vs. customization
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Personalization | A user changes their own view or settings | Affects one user; stored as user preferences | Expecting colleagues to see the change |
| Configuration | An administrator adjusts the instance with platform tools | Affects everyone in scope; low upgrade risk | Calling it customization |
| Customization | Changing out-of-the-box code or records | Changed records are skipped on upgrade and need review | Choosing it when configuration would work |
Core UI vs. portal vs. workspace
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Core UI | Next Experience lists and forms | Where administrators configure and fulfillers can work | Pointing end users here |
| Service Portal / Employee Center | Self-service site for requesters | Catalog, knowledge and request tracking in a simple layout | Assuming it holds separate data |
| Configurable workspace | Agent interface for working queues | Combines lists, records and context for fulfillers | Using it for requesters |
Plugin vs. Store application
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Plugin | ServiceNow component activated in the instance | Generally cannot be deactivated once active | Treating activation as reversible |
| Store application | Packaged app installed from the ServiceNow Store | Has its own version and can be updated independently of the release family | Moving it between instances with an update set |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Reversible plugin
- What candidates pick
- Activate the plugin in production and roll back if users complain.
- Why it looks right
- Feature toggles in other products work that way.
- Why it's wrong
- Most plugins cannot be deactivated once activated, and their dependencies stay active too.
Clue to watch for The stem says the team wants to 'evaluate' or 'try' a plugin.
-
Global fix for a personal wish
- What candidates pick
- Configure the list layout so one user sees an extra column.
- Why it looks right
- It definitely puts the column on the screen.
- Why it's wrong
- Configuring the list layout changes the default for every user; the user can personalize their own columns instead.
Clue to watch for Only one user asked, and others are not mentioned.
-
Script edit for branding
- What candidates pick
- Modify the interface style sheet or header script to add the logo.
- Why it looks right
- Direct edits feel precise and quick.
- Why it's wrong
- Branding is handled through themes as configuration; editing interface code is customization that adds upgrade work.
Clue to watch for The request is about logo, colours or look and feel.
-
Customize the base record
- What candidates pick
- Edit an out-of-the-box business rule or script to change behaviour.
- Why it looks right
- It solves the problem at its source.
- Why it's wrong
- Changed out-of-the-box records are skipped during upgrades and must be reconciled; the exam prefers a configuration route or a new record.
Clue to watch for Options include both a configuration choice and editing an out-of-the-box item.
-
Interface as security
- What candidates pick
- Hide sensitive fields from the portal to protect them.
- Why it looks right
- Users of the portal will no longer see the field.
- Why it's wrong
- Interfaces only present data; access control rules protect it everywhere, including lists, APIs and other interfaces.
Clue to watch for The requirement says data must be protected or secured, not just hidden.
-
Demo data in production
- What candidates pick
- Accept the option to load demo data when activating in production.
- Why it looks right
- It appears as part of the standard activation flow.
- Why it's wrong
- Demo records clutter production with fake data that then needs cleaning up.
Clue to watch for The activation is happening in a production instance.
Answer framework
Use these steps whenever a question asks how to change the instance's capabilities or appearance.
- Decide who the change is for: a single user points to personalization, while a group, a role or everyone points to administrator configuration.
- Prefer platform configuration tools, such as themes, system properties, list layouts and form layouts, over editing out-of-the-box code or records.
- If new capability is needed, look for a plugin or Store application in Application Manager before building anything custom.
- Activate or install in a sub-production instance first, review the dependencies it pulls in, and skip demo data for production.
- Match the interface to the persona: requesters use the portal or Employee Center, agents use workspaces, and administrators use the Core UI.
Practice question
Want more like this? The ServiceNow CSA practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Begin with the personalization, configuration and customization distinction, because it drives most questions here and reappears in later domains. Write one example of each from your own instance: a list column you personalized, a system property you changed, and an out-of-the-box script you would not edit and why.
Next, practise plugin activation in a Personal Developer Instance. Activate a small plugin, note which dependencies it pulled in, look at the demo data option, and confirm you cannot deactivate it afterwards. Browse Application Manager to see how Store applications show versions and updates.
The area candidates underestimate is the interface topic. Open the same incident in the Core UI, in Service Portal and in a workspace, and notice that the record and its access rules are identical while presentation and available actions differ.
After this domain, move to Configuring Applications for Collaboration, where the same personal-versus-global question applies to lists and forms, and drill mixed practice questions that ask for the BEST or least invasive option.
FAQ
Is Instance Configuration a hard domain?
The facts are few, but the questions test judgment about scope and upgrade impact. Candidates who can explain why configuration beats customization usually find it manageable.
Can I deactivate a plugin after testing it?
Generally no. Most plugins stay active once activated, which is why the safe answer is to evaluate them in a sub-production instance.
What counts as a customization on the exam?
Changing out-of-the-box code or records, such as editing a base business rule or interface script. Using platform tools like themes, properties and layouts is configuration.
How many questions are in this domain?
At 10% of 60 questions, plan for about six. ServiceNow does not publish per-domain question counts, so treat this as an estimate.
Do I need to know UI Builder for the CSA?
You should know that configurable workspaces exist, who uses them and how users reach them. Building workspace pages in depth is beyond what this domain's objectives describe.
How does this domain relate to update sets?
Configuration and customization you make in development are captured in update sets and moved to production, which Data Migration and Integration covers. Plugins and Store applications are installed per instance rather than carried in update sets.
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 2 knowledge
You have seen how plugins, personal preferences, global configuration and interfaces differ in reach and risk. Test whether you can pick the least invasive option under exam conditions.
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