professionalPractice AvailableBlueprint updated January 2026

CIS-SP Practice Questions with Explanations

Certified Implementation Specialist - Service Provider

Domain separation explained for the CIS-Service Provider exam: how tenants' data and processes are kept apart, mapped to the blueprint, with worked scenarios, logistics and the retirement dates.

Maintained by the SNReady teamLast updated AI-drafted, human review in progress

See blueprint
Questions on the exam
See blueprint
Duration
Not published
Cut Score
$450
Exam Cost
100
Practice Questions
15
Free Questions

ServiceNow does not publish the cut score, and the official exam blueprint says it is not always 70%. Exams are registered and paid for in ServiceNow University, scheduled through Pearson VUE (source).

CIS-Service Provider is an exam about domain separation: running many customers on one ServiceNow instance while keeping their data apart and letting their processes differ where they need to. The questions are less about menus than about consequences. Which domain will this record land in? Who can see it? Which version of a business rule runs for it? This page explains the model behind those answers, and it starts with the dates that decide whether sitting the exam still makes sense for you.

CIS-SP is being retired

According to the CIS-SP blueprint (KB0011569, v11.0), 31 December 2026 is the last day to take the exam, and the certification itself retires on 31 March 2027. Until then, no maintenance exam or CMP fee is needed. The domains and weights are unchanged in this version.

In practice: if you pass, you hold the credential until 31 March 2027 at the latest. If you are deciding whether to book, ask whether you can be ready before the end of December, and whether a credential that ends in March 2027 is worth the exam fee to you or your employer. The domain separation knowledge itself doesn't retire. The documentation linked below stays useful for anyone running a multi-tenant instance.

Blueprint

What the CIS-SP exam tests

The CIS-Service Provider blueprint (KB0011569) has five domains:

CIS-SP blueprint domain weightsProcess Separation36%Data Separation/Visibility24%Foundational Data Management20%Domain Support in Applications11%Initial Domain Setup and Service Provider Architecture9%
Domain weights from the official CIS-SP exam blueprint (KB0011569, updated January 2026).

1. Initial Domain Setup and Service Provider Architecture (9%)

  • •System Properties
  • •Domain Map / Company relationships
  • •Architecture and non-domain scenarios – multi-instance
  • •Integrations

2. Data Separation/Visibility (24%)

  • •Given a scenario sys_domain field
  • •Data flow/ direction
  • •Contains relationship
  • •Visibility groups
  • •Special Considerations

3. Process Separation (36%)

  • •Given a scenario sys_overrides field
  • •Process/Automation
  • •UI Configuration
  • •Choice Lists
  • •Data-Driven Process

4. Foundational Data Management (20%)

  • •Imports & Transforms

5. Domain Support in Applications (11%)

  • •Domain Support Levels
  • •Service Catalog
  • •Knowledge Management
  • •Mobile
  • •Service Portal
  • •Emerging applications/Other (CSM, ITOM)

Process Separation (36%) is the largest domain: the sys_overrides field, process and automation, UI configuration, choice lists and data-driven process. Data Separation/Visibility (24%) covers the sys_domain field, the direction data flows, Contains relationships, visibility groups and special considerations. Foundational Data Management (20%) is imports and transforms. Together those three make up 80% of the exam. Domain Support in Applications (11%) covers support levels and how Service Catalog, Knowledge, Mobile, Service Portal and other applications behave. Initial Domain Setup and Service Provider Architecture (9%) covers system properties, the domain map and company relationships, multi-instance architecture and integrations (blueprint).

The blueprint's suggested pre-requisites are Welcome to ServiceNow, ServiceNow Administration Fundamentals and ServiceNow Platform Implementation, among others. Its recommended specialization courses include Service Provider Architecture. It also points to the domain separation documentation and the recommended practices for service providers.

Mental model

How domain separation fits together

One instance, many tenants, some things shared. Domain separation separates data, processes and administrative tasks into domains within a single instance. Some global properties, data and processes are still shared across all domains. If you need total separation of every system property and don't need global reporting or processes, ServiceNow says separate instances are the better option (Exploring domain separation). Domain separation is described in terms of data separation, UI separation, business logic separation, hierarchical modelling and cross-tenant intelligence (Domain separation explained).

A sample service provider domain hierarchy: processes flow down from TOP, data rises up, and a Default domain catches unassigned recordsTOPprocess domain, no usersDefault“lost” records to triageUnrestrictedor Restricted, per customerCustomer ACustomer BCustomer Cprocess flows downdata rises up“Global” is not a box here: it is the absence of a domain on a record
Hierarchy shape from Domain separation hierarchies; flow directions from Domain separation explained. A mental model, not an official diagram.

Process flows down, data rises up. Users have no access to data in parent domains, peer domains or other branches of the hierarchy (source). In ServiceNow's sample hierarchy, TOP is a process domain that never contains users, and the Default domain catches records that weren't assigned anywhere, so they can be triaged. “Global” isn't really a domain: it is the absence of a domain on a record, and global records are available to all users unless security restricts them (Domain separation hierarchies). Without a default domain, new tasks and users land in global, where anyone can see them (Default domain).

Data: the sys_domain field

Each record has exactly one domain, stored in sys_domain. It is set by the user's company, a business rule, the module or form template used, the parent record's domain, or the domain of the creating user. A change task inherits its change request's domain. Some tables can never be domain separated, including ACLs, script includes, system properties and the dictionary (Domain assignment).

Process: the sys_overrides field

When an admin in a lower domain edits a policy that belongs higher up, the update becomes an insert in the admin's current domain, with sys_overrides pointing at the original. For a record, the platform looks for a policy in the record's domain first and walks up the hierarchy to global. The record's domain takes precedence over the user's (Process administration). The Domain Override Viewer lists every override across the instance (source). Choice lists can be domain specific too: pick the domain, then Configure Choices. A choice later added in global appears at the end of lower domains' lists (source).

Three ways a user can see data in another domain, and what each one affectsParent / childdomain hierarchyaffects data AND processparent sees child dataContainsdomain-to-domain, many-to-manyaffects data onlyfollows the domain pickerVisibilityuser or group to domainaffects data onlyalways on, ignores picker
From Visibility domains and Contains domains and Domain separation hierarchies. A mental model, not an official diagram.

Three ways to widen what someone sees. Parent/child relationships affect both process and data. A Contains relationship is domain-to-domain and grants data visibility only. Processes are unaffected, and it follows the domain picker. A Visibility domain is granted to a user or group, isn't controlled by the picker, and ServiceNow advises against overusing it (Visibility and Contains). Many Contains relationships add OR conditions to queries and can hurt performance (Contains queries). ServiceNow's suggested pattern is to group customers under Unrestricted and Restricted domains, so a single Contains on Unrestricted covers most customers (hierarchies).

Session context and record context. At login the domain picker is set to the user's home domain, and that domain plus its children is appended to every database query. Integration service accounts are limited in the same way. When the user opens a record, the record's domain decides which process and UI elements apply (Context and domain separation).

Applications support it at different levels. ServiceNow defines No support, Basic (data goes to the right domain), Standard (the service provider can vary processes per customer) and Enhanced (tenants can configure their own business logic safely) (Application support). Service Catalog and Knowledge Management are Standard (Catalog, Knowledge). Service Portal is listed as No support: portals, pages and widgets aren't domain separated, though widget data still respects the user's domain (Service Portal).

Architect's shorthand

sys_domain decides where a record lives. The hierarchy decides who sees it and which process runs. sys_overrides records where a tenant's process differs. Contains and Visibility widen data access but never change process. When in doubt, ask whose domain the record is in, not the user's.

Worked scenarios

Industry scenarios

These are illustrative situations written by SNReady, not taken from the exam.

Managed services

A new customer's users and tickets show up for everyone

A provider onboarded a customer by bulk-loading users through an integration account. Agents for other customers can now see some of the new customer's incidents.

Records with no domain are global and visible to everyone unless security restricts them. If no default domain is set, unassigned tasks and users go to global (source). The quickest way to place users is to assign them to a company, because records then inherit the user's domain. If no other rule applies, a record takes the domain of the user who creates it, which is why the integration account's own domain matters (source).

What the exam is checking: Predicting which domain a record will land in from how it was created.

Outsourced IT

One customer wants close notes mandatory, the others don't

A customer's auditors require close notes on every resolved incident. The provider's global process doesn't enforce it, and other customers don't want it.

Switch to that customer's domain and modify the policy there. The platform inserts a domain-specific copy with sys_overrides pointing to the global one, and that copy applies to records in that domain. Don't edit the global policy and then change its Domain field, because that creates no override and removes the original from the higher level (source). This “mandatory for one tenant, not another” case is ServiceNow's own example of Standard support (source).

What the exam is checking: Knowing how sys_overrides is created, and the anti-pattern of re-domaining a global record.

Telecommunications

A shared escalation team needs to see three customers' data

A tier-3 team sits in the provider's domain but has to work tickets for three specific customers, and only those three.

A Visibility domain on the team's group gives members ongoing access to those domains' data. A Contains relationship would widen what an entire domain sees (source). Either way, only data access changes. Processes for those tickets still come from each record's own domain (source). Keep the number of these grants low: Contains relationships add OR conditions to every query (source).

What the exam is checking: Choosing between Contains and Visibility, and knowing neither changes process.

Professional services

Each customer wants its own catalog and its own portal look

A provider wants catalog items that only one customer can order, plus a branded portal per customer.

With the Service Catalog domain separation plugin, catalog items, record producers and order guides are domain separated as data, while catalogs, categories and variables stay global. Items shared across domains are published in global and restricted with user criteria (source). Service Portal itself isn't domain separated, so ServiceNow suggests separate portals with their own URLs for different experiences (source).

What the exam is checking: Knowing which parts of an application are domain separated and which stay global.

Misconceptions

Common CIS-SP misconceptions

Misconception

“Global is the top domain.”

What the sources say

Global is the absence of a domain on a record, and global records are visible to all users unless security restricts them (Domain separation hierarchies).

Misconception

“Contains and Visibility also share processes.”

What the sources say

Both grant data access only. Processes follow the parent/child hierarchy and the record's domain (Visibility and Contains; Process administration).

Misconception

“We can switch domain separation on later, or remove it if it doesn't work.”

What the sources say

ServiceNow recommends activating the plugin at the start of development. Enabling it late puts existing records in global and risks performance and process (plugin). It can be disabled but not removed from an instance (Exploring domain separation).

Misconception

“Every application is fully domain separated.”

What the sources say

Support ranges from No support to Enhanced, and varies by application (Application support). Service Portal, for example, is listed as No support (Service Portal).

Logistics

CIS-SP logistics and prerequisites

Booking and delivery

  • Exams are registered and paid for in ServiceNow University and scheduled through Pearson VUE, signing in with SSO. Exam vouchers no longer exist (ServiceNow Community, Jan 2026; see also this July 2026 thread).
  • Training: on-demand courses are free but don't include an exam attempt; instructor-led training is paid ($1,900 for 2 days, $2,700 for 3 days) and includes the first attempt (source). Sources differ on whether a course is mandatory: the January 2026 summary says completing the course unlocks eligibility, while a May 2026 reply describes the recommended courses as “not required but highly recommended” (CAD thread). Check the registration page for your exam.
  • Once registered, you must sit the exam within 90 days or the attempt is forfeited. Exam payments are non-refundable, but you can reschedule without a fee inside the rescheduling window (source).

CIS-SP format, fees and scoring

  • We couldn't find a public ServiceNow source for the current question count and time limit, so we don't quote one. Check the official CIS-SP blueprint after signing in to Now Learning.
  • Exam fee: $450 USD excluding tax (ServiceNow University). Retake fee: $225 USD (source).
  • ServiceNow doesn't publish the cut score: each exam is scored against a predetermined cut score that is not shared with candidates, and it is the same for everyone (ServiceNow Community, Jul 2026). Treat any “70% to pass” claim as a guess.
Minimum waiting periods between exam attemptsAttempt 1Attempt 2wait 3 daysAttempt 3wait 30 daysAttempt 4+wait 6 months each
Waiting periods between attempts, per the 2026 rules summarised on the ServiceNow Community.

Our blueprint source data doesn't list a mandatory prerequisite certification for CIS-SP, and it lists the courses above as recommended. Confirm the current requirements on the exam registration page. Remember the hard stop: the last day to test is 31 December 2026, and the certification retires on 31 March 2027 (blueprint).

Beyond the exam, ServiceNow's reference architectures compare a shared domain-separated instance, dedicated instances per customer and a hybrid of the two (reference architecture; hybrid), along with the trade-offs of separate instances versus one instance without domains (alternatives). Those are the design decisions the certification was built around.

Practice

Practise predicting the domain

Start with the free sample questions further down this page, then work through CIS-SP practice questions by topic. For each question, answer three things before you look at the options: which domain the record is in, who can see it, and which version of the process runs. The ServiceNow certification paths page shows what else is available if you decide not to sit CIS-SP before it retires.

Sources

Every exam fact and product behaviour on this page links to one of these ServiceNow sources. Check them before you book: exam rules change between releases.

  1. CIS-SP exam blueprint, KB0011569 (updated January 2026)
  2. Welcome to ServiceNow (Now Learning course page)
  3. ServiceNow Administration Fundamentals (Now Learning course page)
  4. ServiceNow Platform Implementation (Now Learning course page)
  5. Service Provider Architecture (Now Learning course page)
  6. Domain separation
  7. Exploring domain separation
  8. Domain separation explained
  9. Domain separation recommended practices for service providers
  10. Domain separation plugin
  11. Domain assignment
  12. Visibility domains and Contains domains
  13. Contains queries and domain access
  14. Domain separation hierarchies
  15. Importance of the Default domain
  16. Context and domain separation
  17. Process administration (domain separation)
  18. Domain Override Viewer
  19. Create a domain-specific choice list
  20. Application support for domain separation
  21. Domain separation and Service Catalog
  22. Domain separation and Knowledge Management
  23. Domain separation and Service Portal
  24. Service provider reference architecture
  25. Service provider reference architecture for hybrid
  26. Alternatives to domain separation
  27. “Cost of Mainline certification exams”, ServiceNow University KB0013317
  28. Mark Roethof, “2026 exam vouchers, courses, exams & retakes – major changes explained”, ServiceNow Community, 18 Jan 2026
  29. “Exam vouchers eligibility”, ServiceNow Community, 6–8 Jul 2026
  30. “CAD Voucher”, ServiceNow Community Developer forum, 3 May 2026
  31. “CSA Exam” (cut score question), ServiceNow Community SysAdmin forum, 16 Jul 2026

CIS-SP practice questions

100 questions from 5 topics, 15 free

Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made

1
knowledge

What is the primary purpose of domain separation in ServiceNow?

ATo improve database query performance
BTo separate data, processes, and administrative tasks into logical groupings
CTo provide backup and disaster recovery capabilities
DTo enable multiple users to log in simultaneously

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: B. To separate data, processes, and administrative tasks into logical groupings

Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

  • Why A is wrong: Performance optimization is not the primary purpose of domain separation; it's about data and process segregation for multi-tenancy
  • Why C is wrong: Backup and disaster recovery are separate platform features unrelated to domain separation
  • Why D is wrong: Multiple simultaneous logins are handled by standard platform capabilities, not domain separation
2
understanding

Which plugin must be activated to enable domain separation functionality in ServiceNow?

AService Provider Portal
BData Archive
CDomain Support — Domain Extension Installer
DMulti-Instance Management

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. Domain Support — Domain Extension Installer

The Domain Support — Domain Extension Installer plugin must be activated to enable domain separation capabilities. This plugin adds the necessary infrastructure for creating and managing domains.

  • Why A is wrong: Service Provider Portal is a different feature for customer-facing portals, not domain separation infrastructure
  • Why B is wrong: Data Archive is for archiving old records, unrelated to domain separation
  • Why D is wrong: Multi-Instance Management is for managing multiple ServiceNow instances, not domains within a single instance
3
understandingSelect all that apply

Which of the following are valid benefits of implementing domain separation for customers? (Choose three)

AMaintain some global processes and global reporting in a single instance
BEnforce absolute data segregation between business entities
CCustomize business process definitions and user interfaces for each domain
DAutomatic database replication across data centers
EEliminate the need for user authentication

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Maintain some global processes and global reporting in a single instance; B. Enforce absolute data segregation between business entities; C. Customize business process definitions and user interfaces for each domain

Domain separation is best for customers who need to: (1) enforce absolute data segregation between business entities (data separation), (2) customize business process definitions and user interfaces for each domain (delegated administration), and (3) maintain some global processes and global reporting in a single instance.

  • Why D is wrong: Database replication is handled by infrastructure and high availability features, not domain separation
  • Why E is wrong: Domain separation does not affect authentication requirements; users still must authenticate to access the platform
4
knowledge

Which field is added to tables to enable domain separation?

Asys_domain
Bsys_tenant
Csys_scope
Ddomain_id

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. sys_domain

By default, domain separation adds a sys_domain field to the Task [task] and Configuration Items [cmdb_ci] tables and their extensions. This field stores the domain to which each record belongs.

  • Why B is wrong: sys_tenant is not a standard domain separation field
  • Why C is wrong: sys_scope is used for application scoping, not domain separation
  • Why D is wrong: The correct field name is sys_domain, not domain_id
5
understanding

In a domain hierarchy, a user in a parent domain can view records from which domains by default?

AAll domains in the instance
BTheir domain, child domains, and domains they have visibility into
COnly the global domain
DOnly their own domain

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: B. Their domain, child domains, and domains they have visibility into

From a domain, users can see records in the global domain, their specific domain, any child domain of that domain, or any domain that gets directly or indirectly contained by that domain. This follows the platform's visibility domains and contains domains rules.

  • Why A is wrong: Users cannot see all domains by default; visibility is limited by domain hierarchy and explicit visibility grants
  • Why C is wrong: While global domain records are visible, users also see their own domain and child domains
  • Why D is wrong: Users in parent domains can see child domain records by default, not just their own domain
6
application

Which statement accurately describes what happens when records are automatically generated in a domain-separated environment?

ARecords are always created in the global domain
BRecords inherit the domain of the parent table
CThe domain of the record is the same as the domain of the user creating or generating the records
DRecords are randomly assigned to available domains

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. The domain of the record is the same as the domain of the user creating or generating the records

For records that are automatically generated (and for any record that is manually generated), the domain of the record is the same as the domain of the user responsible for creating or generating the records. This is critical for ensuring records are visible to the right set of users.

  • Why A is wrong: Records are not always created in the global domain; they inherit the creating user's domain
  • Why B is wrong: Records inherit the user's domain, not the parent table's domain configuration
  • Why D is wrong: Domain assignment is deterministic based on the user's domain, not random
7
understanding

In a domain-separated GRC implementation, how is the domain determined for records that are automatically generated based on their parent object?

ARecords are randomly distributed across available domains
BRecords are placed in the lowest domain in the hierarchy
CRecords inherit the domain of their parent object or creating user's domain
DRecords are always placed in the global domain

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. Records inherit the domain of their parent object or creating user's domain

Records that are automatically generated either through scheduled jobs or background scripts are domain separated based on their parent object or user domain for all Policy and Compliance objects. Controls, risks, or risk assessments that are auto-generated based on the entities must also be domain separated following this rule.

  • Why A is wrong: Domain assignment is deterministic based on parent object or user, not random
  • Why B is wrong: There is no rule to place records in the lowest domain; it's based on parent/user domain
  • Why D is wrong: Auto-generated records do not default to global domain; they follow parent/user domain
8
understandingSelect all that apply

Which tables are used for reconciliation rules and DO have sys_domain, sys_overrides, and sys_domain_path fields? (Choose three)

AReconciliation Definition (cmdb_reconciliation_definition)
BIdentifier (cmdb_identifier)
CDatasource Precedence (cmdb_datasource_precedence)
DIdentifier Entries (cmdb_identifier_entry)
EData Source Staleness Definitions (cmdb_datasource_staleness)

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Reconciliation Definition (cmdb_reconciliation_definition); C. Datasource Precedence (cmdb_datasource_precedence); E. Data Source Staleness Definitions (cmdb_datasource_staleness)

The reconciliation definition rules that are used during the reconciliation process can be defined for different domains. Tables with sys_domain field include: Reconciliation Definition (cmdb_reconciliation_definition), Datasource Precedence (cmdb_datasource_precedence), and Data Source Staleness Definitions (cmdb_datasource_staleness).

  • Why B is wrong: Identifier (cmdb_identifier) does NOT have a sys_domain field; identification rules are global
  • Why D is wrong: Identifier Entries (cmdb_identifier_entry) does NOT have a sys_domain field; these are global
9
understanding

How does the CMDB Health dashboard handle domain separation when displaying health failures and scores?

AIt aggregates and reports based on user's domain visibility of CIs
BHealth data must be manually filtered by domain
CIt only shows global domain CI health data
DIt shows all CI health data regardless of domain

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. It aggregates and reports based on user's domain visibility of CIs

If the Domain Support — Domain Extensions Installer plugin is activated, then the CMDB Health dashboard is domain aware. It aggregates and reports health failures and scores based on user's domain visibility of CIs. If domain visibility lets a user see a CI, then the audit rule in that user's domain applies to that CI.

  • Why B is wrong: Domain filtering is automatic based on user visibility, not manual
  • Why C is wrong: The dashboard shows data for the user's visible domains, not only global
  • Why D is wrong: The dashboard respects domain visibility; it does not show all CI data
10
knowledge

Which domain separation support level includes the ability for service providers to create or modify processes per customer?

AEnhanced
BAdvanced
CStandard
DBasic

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. Standard

At the Standard support level, business logic allows the service provider (SP) to create or modify processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.

  • Why A is wrong: Enhanced level adds tenant-configurable business logic, but Standard is where SP process customization begins
  • Why B is wrong: Advanced is not a defined domain separation support level
  • Why D is wrong: Basic level ensures data goes into the proper domain but does not specifically enable per-customer process customization
11
understandingSelect all that apply

Which business logic and processes can be domain separated by the instance owner in Security Incident Response? (Choose three)

AEmail parsing rules for incident creation
BDatabase connection strings
CWorkflows for incident response orchestration
DPlatform user authentication methods
ESecurity incident SLAs

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Email parsing rules for incident creation; C. Workflows for incident response orchestration; E. Security incident SLAs

Business logic and processes that can be domain separated by instance owner include: Email parsing rules for incident creation, Security incident SLAs, Workflows for incident response orchestration, as well as user groups, integrations, business rules, risk score calculators, escalation paths, and process definitions.

  • Why B is wrong: Database connection strings are infrastructure-level configurations, not domain-separated business logic
  • Why D is wrong: Platform user authentication methods are not domain-separated; they are global platform configurations
12
understanding

In a domain-separated Event Management environment, which statement is true about MID Server configuration?

AEach MID Server can serve only one domain according to the integration user it uses
BMultiple MID Servers must share the same service account
CMID Servers are not affected by domain separation
DA single MID Server can serve all domains simultaneously

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Each MID Server can serve only one domain according to the integration user it uses

In a multi-domain environment, each MID Server can serve only one domain according to the integration user that it uses. In the configuration of the connector instance, you must make sure that the MID Server uses the same domain as the Connector instance.

  • Why B is wrong: Different domains require different service accounts/integration users for their MID Servers
  • Why C is wrong: MID Servers are affected by domain separation through their integration user configuration
  • Why D is wrong: MID Servers are domain-specific based on their integration user; they cannot serve all domains
13
knowledge

At which domain separation support level are application properties domain-aware as needed?

ABasic
BNone - properties are never domain-aware
CStandard
DEnhanced

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: C. Standard

At the Standard support level, application properties are domain-aware as needed. This level includes all aspects of Basic level support plus the ability for service providers to create or modify processes per customer, with the instance owner configuring MVP business logic per tenant.

  • Why A is wrong: Basic level focuses on data going into proper domains, not property domain-awareness
  • Why B is wrong: Properties can be domain-aware starting at the Standard support level
  • Why D is wrong: Enhanced level builds on Standard; property domain-awareness starts at Standard
14
understandingSelect all that apply

Which features are available in the extended domain separation functionality for Performance Analytics with the Domain Separation Support plugin? (Choose three)

AAutomatic data backup per domain
BCollect aggregate scores across domains
CDashboard filtering by domain
DCross-instance domain replication
EHierarchical multi-domain configurations

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: B. Collect aggregate scores across domains; C. Dashboard filtering by domain; E. Hierarchical multi-domain configurations

The extended functionality available in the Performance Analytics — Domain Separation Support plugin includes: (1) Hierarchical multi-domain configurations to group domains and control score collection, (2) Collect aggregate scores by combining scores from multiple domains in a domain configuration, and (3) Dashboard filtering by domain to show scores by domain or domain aggregate.

  • Why A is wrong: Automatic data backup is not a PA domain separation feature
  • Why D is wrong: Cross-instance domain replication is not a feature of the PA Domain Separation Support plugin
15
understanding

Evaluate the following statements about domain separation in Event Management: Statement 1: Impact calculation in Event Management is supported with segregation based on how CIs are segregated. Statement 2: The discovery process automatically segregates CIs by domain in Event Management. Which statements are TRUE?

AStatement 1 only
BBoth statements
CStatement 2 only
DNeither statement

👆 Click an option above to select your answer

Show answer and explanation

Correct answer: A. Statement 1 only

Statement 1 is TRUE: Impact calculation is supported in Event Management domain separation, with segregation based on the manner in which CIs are segregated. Statement 2 is FALSE: The discovery process does NOT segregate CIs by domain - this is explicitly noted as a limitation in the documentation.

  • Why B is wrong: Statement 2 is false; the discovery process does not automatically segregate CIs by domain
  • Why C is wrong: Statement 2 is false; discovery does NOT segregate CIs by domain. Statement 1 is true about impact calculation.
  • Why D is wrong: Statement 1 is true; impact calculation IS supported with CI-based segregation

Get Full CIS-SP Access

Unlock all 100 practice questions with detailed explanations

CIS-SP Only — Lifetime

$9
  • All CIS-SP questions
  • Timed mock exams
  • Personalized study plan generator
  • Detailed explanations
  • Lifetime access — never expires
BEST VALUE

Lifetime Access

$49
  • ALL certifications included
  • All practice questions
  • Timed mock exams
  • Personalized study plan generator
  • Detailed explanations
  • Lifetime access — never expires
  • Future updates included

15 free questions available to try first • One-time payment, no subscription

CIS-SP exam FAQ

Is there a free CIS-SP practice test?

15 of our 100 CIS-SP practice questions are free on this page, with explanations. The full set and timed mock exams cost $9 one-time.

Is there a CIS-SP mock exam?

Yes. The CIS-SP mock exam is timed and draws from the full question bank, with an explanation for every answer when you finish. It is included with full access.

Are these real CIS-SP exam questions?

No. SNReady questions are original practice questions, drafted with AI assistance against ServiceNow's documentation and the CIS-SP exam blueprint. They are not copied from the exam, and human review of them is still in progress. See how the questions are made.

What does the CIS-SP exam cover?

The official blueprint (KB0011569, updated January 2026) has 5 domains. The heaviest is Process Separation at 36% of the exam. Every domain and objective is on the CIS-SP blueprint, explained.

What is the CIS-SP passing score?

ServiceNow does not publish the cut score, and the official exam blueprint says it is not always 70%.

Ready to Start Practicing?

Begin with our free questions to assess your current knowledge level.