An enterprise wants to track availability metrics across different geographies for a global email service offering. Each region has a different uptime target and maintenance window. How should the implementation specialist configure this in ServiceNow SPM?
Service Offerings sit beneath a parent Service in SPM and each carries its own availability target, maintenance window and support hours. Creating one per region lets the specialist apply distinct uptime commitments and maintenance windows while still reporting against the single global email service.
Why this answer
In ServiceNow SPM, a Service Offering represents a specific variant of a service delivered to a particular audience, region, or with distinct commitments. Creating separate Service Offerings under the parent email service for each region allows each offering to carry its own SLA definitions, uptime targets, and maintenance windows while still rolling up to the same Business Service. This is the CSDM-aligned way to model regional variations of a global service.
Exam trap
CIS-ITSM often tests the confusion between Business Service and Service Offering, tempting candidates to attach SLAs to the Business Service when regional variations require Service Offerings.
How to eliminate wrong answers
Option A is wrong because attaching multiple SLA definitions with different targets to a single Business Service record creates ambiguity — SLA processing would not know which target applies to which region, and the Business Service is meant to be the aggregate, not the per-region commitment holder. Option B is wrong because domain separation is a data segregation mechanism for multi-tenant instances, not a modeling technique for regional service variants; creating multiple portfolios would fragment reporting and misrepresent the service hierarchy. Option D is wrong because modifying base system SLA workflows with dynamic script includes is a customization that breaks upgradeability and is not the intended configuration approach for regional commitments.