CSA domain - 10% of the exam

Instance Configuration

Instance Configuration is 10% of the CSA exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

34
Practice questions
3
Objectives
34
Medium

Where people go wrong

  • Treating personalisation as a shared layout

    The wrong answers assume that a column or field change made through the personalise control reaches colleagues, or that an update set, impersonation or a cache flush will carry it across. Personalisation is stored against the individual user. Configuring the list layout or using Form Design writes the arrangement to the view itself, so everyone who opens that view receives it unless they have personalised their own.

    See it in a sample question
  • Using a per-user setting for instance-wide branding

    A personal theme, a stored preference or a UI policy looks like a way to change what every user sees. A personal theme only reaches the person who picked it, and the platform does not seed new accounts from an administrator's preferences. UI policies act on fields in a form. Instance branding values and the system property for the product name are held once and read for every session.

    See it in a sample question
  • Matching an interface to the wrong audience

    The wrong answers hand a fulfiller interface to requesters, or a requester interface to fulfillers. Employee Center is the delivered self-service front door for staff with no fulfiller role, covering catalog, knowledge and request tracking. A Configurable Workspace keeps the queue, the open record and a side panel together for agents. On phones, Now Mobile serves requesters and Mobile Agent serves fulfillers.

    See it in a sample question
  • Expecting an administrator to remove an active plugin

    Deleting the entry in All Available Applications, reverting an update set, or cloning production from a sub-production instance each look like a way to undo an activation. None of them reverses what the activation created. An administrator cannot undo plugin activation from within the instance. Removal goes to ServiceNow, and the practical response meanwhile is to leave the plugin active and disable the configuration it added.

    See it in a sample question
  • Ignoring entitlement on a Store application

    The wrong answers blame the missing install option on the admin role, the current scope, version compatibility, dependencies or a rule about non-production instances. A paid Store application is gated by entitlement held for the customer account. Until the instance is entitled, the Store offers a request in place of an install, and such an application never appears in the plugin list.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleInstance Configurationmedium

A user adjusts which columns appear on their incident list using the personalisation control offered on the list, saves the change, and then asks why a colleague opening the same list still sees the original columns. What accounts for the difference?

  • AList personalisation is stored as a preference for the individual user, so it alters that user's own view of the list and no other. Correct
  • BThe colleague holds a different role, and column choices are stored against each role rather than against the list record itself.
  • CThe change waits for the next instance cache flush, after which every user opening that list receives the revised column set.
  • DThe list was reached from a different application menu entry, so only the layout attached to that entry governs what appears.
Recognise that personalising a list changes the view for the individual user alone, while a shared layout requires an administrator to configure it. Personalisation records the user's chosen columns as a preference attached to that user, so the platform reads it only when that person opens the list. Everyone else continues to receive the layout configured for the table, which is why a colleague sees no change until an administrator alters the shared list layout.

Why A is correct: Correct because personalisation writes a preference tied to the user who made it, which is why the colleague continues to receive the shared layout.

Why B is wrong: Tempting because roles do govern much of what a user sees on the platform, but column selection is not stored against a role, so this misplaces where the setting lives.

Why C is wrong: Tempting because some administrative changes do need a cache to clear, but no flush will ever promote a personal list choice into a shared layout.

Why D is wrong: Tempting because navigation can open different views, but the menu entry used to reach a list does not turn a personal column choice into a shared one.

Free sampleInstance Configurationmedium

Staff work in both a production instance and a sub-production instance during a project and keep confusing the two while editing records. An administrator wants every user of the sub-production instance to meet an obvious visual difference on every page they open there. Which approach achieves this?

  • ASet the branding values on the sub-production instance, so the banner colour and header text render differently for every session there. Correct
  • BAsk every user to pick a distinct personal theme on the sub-production instance, since that choice follows the user into each instance.
  • CPublish an announcement on the sub-production instance, which shows a banner until each user dismisses it and then leaves both identical.
  • DConfigure a UI policy on the sub-production instance so the page header renders in a different colour whenever any form is opened.
Recognise that branding values are set per instance by an administrator, giving every session on that instance a consistent visual identity. Branding is stored on the instance rather than against any user, so once the values differ between production and sub-production the interface renders differently for whoever signs in. Nothing depends on a user making a choice, and the difference persists across sessions instead of disappearing once a message is dismissed.

Why A is correct: Correct because branding is instance-wide configuration held on that instance, so every user of the sub-production instance meets the difference without acting themselves.

Why B is wrong: Tempting because a personal theme does change how the interface looks, but it depends on each user acting and it is stored per instance, so newcomers see nothing.

Why C is wrong: Tempting because an announcement does put a visible message in front of users, but it is dismissible and temporary, so the two instances soon look the same again.

Why D is wrong: Tempting because UI policies do alter what a user sees, but they act on the fields of a record in a form and cannot restyle the interface header.

Free sampleInstance Configurationmedium

A service desk agent spends the day picking up assigned incidents from a queue, reading each caller's record, checking related records and posting updates, and complains about constantly losing place while moving between separate list and form pages. Which interface is intended for this pattern of work?

  • AEmployee Center, because it gives the agent a single searchable place to find knowledge articles and follow the progress of submitted requests
  • BThe Now Mobile app, because it presents assigned work in a task list the agent can act on from a phone without opening a desktop browser
  • CA Configurable Workspace, because it combines the queue, the record and contextual information on one screen with records held open in tabs Correct
  • DThe classic UI form and list interface, because personalising the list layout and the form sections removes most of the navigation the agent repeats
Identify Configurable Workspaces as the fulfiller and agent interface that keeps queue, record and context on one screen instead of separate pages. A Configurable Workspace targets high volume record processing by holding the list, the open record and related context in one layout with tabbed records, so an agent moving between assigned items keeps working context that a separate list page and form page cannot preserve.

Why A is wrong: Tempting because Employee Center is modern and search led, but it is a requester experience for consuming services, not a surface for working an assigned queue of records.

Why B is wrong: Tempting because mobile apps do surface work items, but Now Mobile serves employee self-service and is neither the desktop queue tool nor the fulfiller mobile experience.

Why C is correct: Correct: Configurable Workspaces are built for fulfillers and agents, keeping lists, the open record and contextual panels together so context is not lost between items of work.

Why D is wrong: Tempting because personalisation genuinely reduces clutter, but the agent still moves between separate list and form pages, which is the friction the requirement names.

Free sampleInstance Configurationmedium

Some weeks after a plugin was activated on a production instance, the business decides the functionality is not wanted and asks the administrator to remove it entirely. What is true of removing an active plugin?

  • ADeleting the plugin's entry from All Available Applications reverses the activation and removes the tables, roles and records that the plugin created on the instance.
  • BReverting the update set that the platform created when the plugin was activated reverses every table, role and record change that the activation introduced on the instance.
  • CAn administrator cannot undo the activation from within the instance, so removal has to be raised with ServiceNow, and the usual practical response is to leave the plugin active and stop its functionality being used. Correct
  • DThe plugin is uninstalled from the Application Manager in the same way as an application installed from the ServiceNow Store, which removes its artefacts and the records they hold.
Know that an activated plugin cannot be reversed by the administrator, unlike an installed Store application, so restricting its use is the practical response. Activation writes plugin artefacts into the instance and other configuration can then depend on them, so the platform does not expose a self-service reversal. This asymmetry with a Store application, which an administrator can remove, is the reason plugins should be trialled on a sub-production instance before production.

Why A is wrong: Tempting because deleting a record usually undoes what it represents, but the entry is a catalogue of available functionality and removing it would not unwind anything the activation created.

Why B is wrong: Tempting because update sets do capture configuration changes, but plugin activation is not delivered through a customer update set, so there is nothing of that kind to revert.

Why C is correct: Correct because plugin activation is not a self-service reversal: the administrator's practical options are to raise the removal with ServiceNow or to restrict the functionality so nobody reaches it.

Why D is wrong: Tempting because Store applications genuinely can be removed by an administrator, but that is precisely where the two mechanisms diverge, and a plugin does not offer the same self-service removal.

Free sampleInstance Configurationmedium

An administrator with the admin role browses the ServiceNow Store, finds a paid application that meets a business need, and discovers that the instance offers no way to install it. What is the most likely explanation?

  • APaid applications from the ServiceNow Store can be installed only on a sub-production instance, so the administrator must install it there and then move it with an update set.
  • BThe application requires an entitlement, and the customer's instance has not been entitled to it, so it cannot be installed until that entitlement is in place for the instance. Correct
  • CThe application is delivered as a plugin rather than an application, so it is switched on from All Available Applications instead of being installed from the ServiceNow Store.
  • DThe admin role does not cover Store installations, so a user holding a dedicated security administrator elevation must perform the installation on the administrator's behalf.
Explain that a paid ServiceNow Store application becomes installable only once the customer holds an entitlement covering the target instance. Store applications are licensed to a customer and mapped to specific instances. Until that entitlement exists, the instance is not permitted to retrieve the application, so the install action is withheld no matter which roles the administrator holds.

Why A is wrong: Tempting because testing on a sub-production instance first is good practice, but there is no rule confining paid applications to non-production, and update sets are not how Store content is distributed.

Why B is correct: Correct because paid Store content is licensed per customer and per instance, and the install action becomes available only once the entitlement covering that instance exists.

Why C is wrong: Tempting because the two delivery mechanisms are easy to confuse, but content listed in the ServiceNow Store is installed from there, and the listing itself tells the administrator which mechanism applies.

Why D is wrong: Tempting because some sensitive actions do require elevated privilege, but the barrier described here is commercial rather than a role that the administrator is missing.

Other domains in this exam

See also the CSA cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ServiceNow. Original, blueprint-aligned practice material only.