CSA domain - 7% of the exam

Platform Overview and Navigation

Platform Overview and Navigation is 7% of the CSA exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

24
Practice questions
4
Objectives
24
Medium

Where people go wrong

  • Treating the instance as a shared multi-tenant database

    The wrong answers describe ServiceNow as a multi-tenant cloud product in which customers share one database and are separated by a field on each row, or as a shared application tier over a private database. Each customer is instead provisioned with dedicated instances, each with its own application server, its own database and its own instance URL. Configuration and upgrade timing are therefore specific to the instance, and a sub-production instance gives a place to test away from live data.

    See it in a sample question
  • Treating applications as separate tools needing integration

    The wrong answers describe Incident Management, Service Catalog and similar applications as separately bought tools that need an integration, a synchronisation job or a private set of services to work together. A ServiceNow application is a configured set of platform components such as tables, forms, access controls and flows. Incident, change and knowledge records therefore point at one user record on a single data model, and a custom application gets approvals, notifications and reporting from the same shared services.

    See it in a sample question
  • Misreading what impersonation does

    The wrong answers treat impersonation as a fresh sign in, a role grant or an addition to the administrator's own access. Impersonation layers the selected user's identity over the administrator's session, so roles, access control rules and navigation are evaluated as that user, with no password needed. The platform records the impersonation, work done during it is attributed to the selected user, and it never elevates that user's own access.

    See it in a sample question
  • Picking the wrong entry point in the navigation header

    The wrong answers pick the nearest menu in the unified navigation header instead of the one built for the job. Favorites holds only items the user has starred, History is the trail of recently visited records and modules, and the header search matches typed terms. Admin Center is where administrators see the available applications and begin guided setup. A stable personal shortcut therefore needs a starred module, and reopening a morning's work needs History.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free samplePlatform Overview and Navigationmedium

During a design review a stakeholder asks whether the organisation's ServiceNow data sits in a database shared with other ServiceNow customers, and what that means for configuration and upgrade timing. Which statement is accurate for the Now Platform?

  • ACustomers share one database and are separated by a company field on each record, so a configuration change made by one customer reaches the others.
  • BCustomers share one database while each holds a private application layer, so every customer is moved onto a new release at the same moment.
  • CEach customer is provisioned with its own instance holding its own database, so configuration and upgrade timing are specific to that instance. Correct
  • DEach customer receives a separate copy of the application code while the data for all customers is held in one central reporting store.
Understand that each ServiceNow customer runs its own instance with its own database, which is why configuration and upgrade timing stay independent. ServiceNow provisions a dedicated instance per customer, comprising the platform, the applications and the database that holds the records. Because nothing is shared with another customer, an administrator can change configuration or schedule an upgrade without coordinating with anyone outside the organisation.

Why A is wrong: Tempting because many cloud products do partition a shared database by tenant, but wrong because ServiceNow separates customers at the instance level, not by a field on shared rows.

Why B is wrong: Believable because a split of shared data and private code exists in some products, but wrong because customers schedule their own upgrades rather than moving together.

Why C is correct: Correct, because an instance is a self contained deployment of the platform and its data, which is what lets one customer configure and upgrade independently of any other.

Why D is wrong: Attractive because central reporting stores are common in large estates, but wrong because customer data stays within the customer's own instance rather than pooling centrally.

Free samplePlatform Overview and Navigationmedium

An administrator updates the job title on a user record. The new title appears immediately on every incident, change request and knowledge article that references that user, and no integration or synchronisation job runs on the instance. Which characteristic of the Now Platform accounts for this?

  • AEach application stores its own user table and a scheduled import job reconciles those tables against one another overnight.
  • BA data integration between the applications propagates the changed field to each downstream copy as soon as the record is saved.
  • CThe applications run on one platform with a single data model, so they all reference the same user record rather than separate copies. Correct
  • DThe user record is cached in the browser session, so every open application reads the updated title from that shared client cache.
Recognise that Now Platform applications share one data model, so a record updated once is the same record every application reads. The Now Platform holds one set of tables per instance and every application reads and writes those same tables. A user is stored once, and incident, change and knowledge records reference that single row, so an edit is visible everywhere without copying, syncing or integrating anything.

Why A is wrong: This describes how separately purchased tools are usually joined, which makes it a familiar assumption, but it is wrong here because the update was visible immediately and no reconciliation job exists on the instance.

Why B is wrong: Tempting because instant propagation can be achieved by integration in other architectures, but wrong because ServiceNow applications are not separate systems needing an integration to stay in step.

Why C is correct: Correct, because incident, change and knowledge records all point at the same user record on the shared data model, so there is one value to update and nothing to propagate.

Why D is wrong: Plausible because the browser does cache some data for the session, but wrong because other users on other sessions see the change too, so the consistency comes from the stored record and not from a client cache.

Free samplePlatform Overview and Navigationmedium

An administrator must reproduce a fault that only one service desk agent reports, and must see the platform as that agent sees it without learning or resetting the agent's password. The administrator uses the impersonation feature. What does the instance do during the impersonated session?

  • AIt retains the administrator's underlying session but evaluates roles, access control rules and navigation as the selected user, and writes the impersonation event to the system log. Correct
  • BIt signs the administrator out and opens a fresh session owned by the selected user, so the administrator must log in again with their own credentials afterwards.
  • CIt grants the selected user the administrator's roles for the duration of the test, so the agent can reproduce the fault from their own device while the administrator observes the result.
  • DIt copies the selected user's roles onto the administrator's account until they are removed by hand, so the administrator keeps that access after the test finishes.
Impersonation evaluates the platform as another user within the administrator's own audited session, without changing either account's roles or requiring a password. Impersonation is a session level feature rather than a security change. The platform substitutes the target user's identity for role checks, access control evaluation and navigator filtering while the administrator's real session remains the one being logged, which is why the audit trail still names the administrator and why ending the impersonation restores their own view immediately.

Why A is correct: Correct. Impersonation layers the selected user's identity over the administrator's session so security and navigation are evaluated as that user, and the platform records who impersonated whom for auditing.

Why B is wrong: Tempting because impersonation does present the selected user's view, which looks like a new sign in. It is wrong because the administrator's own session is retained underneath, and ending the impersonation returns them to their own identity without a fresh login.

Why C is wrong: Tempting because granting a role is a genuine way to change what a user can reach. It is wrong because impersonation changes what the administrator sees, and it never elevates the target user's own access.

Why D is wrong: Tempting because the administrator does gain the selected user's view of the platform. It is wrong because nothing is written to the administrator's user record, and the effect ends the moment the impersonation is ended.

Free samplePlatform Overview and Navigationmedium

A service desk agent opens the Incident module dozens of times a day and wants a one click entry point that belongs to her account, survives logging out and does not change position as she works through other modules. Which action in the unified navigation header meets this requirement?

  • AOpen the History menu and keep the recent Incident entry there, since History retains visited items for the account.
  • BOpen the All menu, find the Incident module, and select its star so it is saved under Favorites for her account. Correct
  • CAsk an administrator to add the Incident module to the Admin Center so it appears at the top of her navigation.
  • DType Incident into the navigation search each time, since the search box remembers the last module it filtered to.
Starring a module from the All menu saves it under Favorites for that user, giving a persistent personal shortcut that History and search cannot provide. Favorites are stored against the individual user as a preference, so the starred module keeps a fixed place in the Favorites menu between sessions. History is a rolling activity trail that reorders as the user moves around, and the navigation search filter is a transient narrowing of the menu rather than a saved link.

Why A is wrong: Tempting because History does sit in the same header and does show the Incident module after she has opened it, but History is a rolling record of recent activity that is reordered and displaced as she visits other places, so it is not a stable shortcut.

Why B is correct: Correct because starring a module from the All menu writes a favourite against her own user, and the Favorites menu then presents it in a fixed position that persists across sessions.

Why C is wrong: Tempting because the Admin Center is a genuine landing place in Next Experience, but it exists for administrators to review and set up applications on the instance and is not a personal shortcut list for one agent.

Why D is wrong: Tempting because filtering by name is the fastest way to reach an unfamiliar module, but the search box narrows the menu for that moment rather than saving a durable shortcut she can click straight away.

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.