CSA - Instance Configuration (10% of the exam) - Section 2

Installing applications and plugins

Activating plugins from All Available Applications, installing applications from the ServiceNow Store, the difference between a plugin and a Store application, dependencies, entitlement, and what an administrator can and cannot uninstall once a plugin is active.

ServiceNow product documentation, pluginsServiceNow Store

Practice question for this objective

Free sampleInstance Configurationmedium

A business unit asks for a certified integration built by a partner. The administrator searches All Available Applications on the instance and the application does not appear there, although it is listed on the ServiceNow Store. What is the correct way to get the application onto the instance?

  • AObtain the entitlement for the application and install it from the ServiceNow Store, since it is distributed as a Store application rather than as a plugin. Correct
  • BActivate the closest matching plugin from All Available Applications, because every application published on the Store also appears there as a plugin entry.
  • CCreate a scoped application on the instance and rebuild the integration in house, since anything absent from the plugin list has to be built by the administrator.
  • DRaise a support case asking for the application to be added to All Available Applications on this instance so that it can then be activated as a plugin.
Distinguish plugins activated from All Available Applications from Store applications that require entitlement and installation from the ServiceNow Store. Plugins are components delivered with the platform and switched on from All Available Applications. Applications published by ServiceNow or its partners on the Store are distributed separately, so the instance must be entitled to the application before it can be installed.

Why A is correct: Correct because plugins ship with the platform and are activated from All Available Applications, while Store applications are separately distributed and require entitlement before installation.

Why B is wrong: Tempting because both routes end in working functionality, but Store applications are distributed as installable applications and are not mirrored into the plugin list, so no matching plugin exists to activate.

Why C is wrong: Tempting when the plugin list looks like the whole catalog of available functionality, but the application already exists on the Store, so rebuilding it duplicates certified work at high cost.

Why D is wrong: Tempting because support does handle some plugin requests, but partner applications are distributed through the Store and are not added to the instance plugin list on request.

See more CSA practice questions, answers explained.

Exam traps in Instance Configuration

Answers that look right on this material and are not. Each one is a distractor from a different question in the CSA bank for this domain.

  • A plugin is downloaded from an external repository each time it is switched on, whereas a Store application ships inside the base platform build and only needs activating.

    Why it is wrong: Tempting because both mechanisms end with new functionality appearing on the instance, but the description is the wrong way round: the plugin is the part already delivered with the platform and the Store application is the part retrieved from outside the instance.

  • A scheduled job on the instance activates every plugin that shares an application scope with the plugin the administrator requested, so the two entries were switched on with it.

    Why it is wrong: Tempting because scheduled jobs do perform background work, but no platform job activates plugins by shared scope, and the stem rules out a configured scheduled activation.

  • The application is published only for instances running the newest family release, so the instance has to be upgraded before the install option becomes available on the page.

    Why it is wrong: Tempting because Store listings do state version compatibility, but an incompatible release produces a compatibility message rather than converting the control into a request.

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