IT Service Manager ExaminationStudy guide

Grasp how ITIL 4's Service Value System (SVS), the seven guiding principles, the four dimensions, and the Service Value Chain (SVC) mesh together to co-create value, from a service manager's decision-making viewpoint.

Understand the requirements of the service management system (SMS) defined by JIS Q 20000, and the roles of PDCA continual improvement and third-party certification, from the angle of designing operations that withstand audit.

Grasp that a service's value is not set by the provider alone but co-created with the consumer, and that across the service lifecycle, SLM (service level management) sustains and improves the agreed value—from an operational-judgment viewpoint.

Understand how the service catalogue makes live services visible from the customer's view, and the place of service level management that agrees and sustains SLAs on top of it—framed by balancing customer expectations against cost.

Covers the three-layer structure of the SLA agreed between provider and customer, the OLA between internal operations teams, and the UC (underpinning contract) with external suppliers, how SLM maintains and improves them, and how to design service-level targets amid trade-offs of availability, cost, and feasibility.

Covers choosing among three change paths—standard changes that are pre-approved and routine, normal changes assessed by the CAB, and emergency changes decided by the ECAB and documented afterward—and how to make changes to a live service safely through risk assessment and a back-out (rollback) plan.

Covers release and deployment management, which safely delivers approved changes to production: designing the release unit (what is packaged together), choosing a deployment approach such as phased rollout or a pilot, and how to plan distribution to a live service through the separation of build, test, and deploy.

Covers configuration management, which accurately manages the CIs (configuration items) that make up a service in the CMDB, its linkage with change management and release management, and how it differs from IT asset management, whose main purpose is grasping owned assets—all from the practical angle of impact analysis and maintaining accuracy.

Covers how, at the design stage, to realize an availability target derived from requirements—redundant design that eliminates a single point of failure, series (product) and parallel (1−(1−a)ⁿ) availability, and designing capacity from a future demand forecast—all amid trade-offs with cost.

Centered on the fact that the purpose of incident management is the rapid restoration of service, not the investigation of root cause, this section covers prioritization by impact x urgency, escalation (functional and hierarchical), the separate handling of a major incident, and when to apply a workaround to restore service even before the root cause is known—together with how to judge these under SLA-target constraints.

Covers how the purpose of problem management is to prevent recurrence through root-cause identification and a permanent fix (in contrast with incident management, whose purpose is rapid restoration), the flow of raising a problem from recurring faults or major incidents and performing root-cause analysis (RCA), the use of a known error database (KEDB) that accumulates causes and workarounds, and choosing between reactive (waiting for a fault) and proactive (getting ahead via trend analysis) problem management.

Covers event management, which monitors state changes of components, catches signs that exceed a threshold, and can automatically raise incidents (distinguishing informational, warning, and exception events), and request fulfilment, which handles routine, low-risk service requests such as password resets or access grants through a flow separate from ordinary incidents—together with judging which report to route to which process.

Covers the role of the service desk as the single point of contact (SPOC) for users (centralizing communication and maintaining user satisfaction) and the structural patterns—local, centralized, virtual, and follow-the-sun—together with the judgment of which pattern to choose under constraints such as site distribution, language, the need for 24-hour coverage, and cost.

Covers IT service continuity management (ITSCM), which restores a service within a target time after a major disruption such as a disaster; its relationship to the BCP (the business-wide continuity plan); the numeric recovery objectives RTO (recovery time objective), RPO (recovery point objective), and MTPD (maximum tolerable period of disruption); and the choice of recovery site among hot, warm, and cold sites, building judgment for selecting a continuity approach under constraints of business impact and cost.

Covers the availability rate, computed as MTBF / (MTBF + MTTR); the distinction between the mean time between failures (reliability, MTBF) and the mean time to repair (maintainability, MTTR); estimating overall availability as the product of availabilities for a series configuration and as 1 - (1 - a)^n for parallel redundancy; and eliminating a single point of failure (SPOF) through redundancy.

Covers capacity management and its three sub-processes (business capacity management, service capacity management, and component capacity management), which secure exactly the performance and volume a service needs; demand management, which levels demand itself; early detection via threshold monitoring and trend analysis; and identifying the bottleneck, building judgment for choosing between augmentation and demand suppression.

Covers the differences and recovery procedures among full backup, incremental backup, and differential backup; generation management that retains multiple generations; off-site storage as protection against disaster; and how backup methods correspond to the recovery objectives (RTO, RPO), building judgment for selecting a method from business requirements.

Covers the operational controls that keep information security running in live service delivery-priority judgment for patch management and vulnerability management, log collection and monitoring, the SIEM that correlates multiple logs, and the handoff that connects detected incidents into incident management-framed as the judgments of an operator upholding SLA targets.

Covers access management, which controls who is allowed what in service operations-the principle of least privilege, the provisioning (granting) and periodic review (revocation) of privileges, privileged access management that handles powerful rights strictly, and the authentication that verifies identity-framed as an operator's judgment to prevent risks such as insider misuse and dangling leaver accounts.

Covers supplier management, which aligns externally dependent parts with the SLA-the UC (underpinning contract) with external suppliers, aligning the customer SLA with UCs/OLAs, supplier evaluation and review, the demarcation of responsibility during faults, and the shared responsibility model when using the cloud-framed as the judgment of a service manager who ultimately upholds the SLA target.

Covers the mechanisms that keep service management running and improving-the internal audit that detects nonconformities, the corrective action for findings (a permanent fix to the root cause, not a stopgap), CSI (continual service improvement), the PDCA cycle, and the KPIs/metrics that steer improvement by the numbers-framed as the judgment of a service manager improving the service based on measurements.

Covers monitoring items (CPU, memory, disk, response time) and the design of thresholds and alerts that catch anomalies early, job scheduling that protects the SLA, the dependencies and abnormal-end handling (abort, rerun, skip) of a job net that ties multiple jobs together, and two-stage warning/critical thresholds that suppress false alarms.

Covers operational automation that hands routine work to machines, the runbook / operating procedures that document steps, human-error prevention through double-checks and call-and-response, and safely applying configuration changes (change-management linkage and rollback) to production. The key is separating routine work to automate from exceptions requiring human judgment.

Covers the UPS (uninterruptible power supply) and on-site generator that bridge a momentary outage to standby power, the air conditioning that cools equipment and the power distribution that delivers electricity, seismic/base-isolation protection against earthquakes, access control preventing unauthorized entry, and the data-center Tier levels that stage a facility's availability. The key is choosing the degree of redundancy by trading off the availability target against cost.

Covers operations design that builds the operating structure and procedures, the design of shifts and staffing that runs a 24-hour operation seamlessly, cost optimization that balances investment and running cost, KPIs that measure operational quality numerically, and supplier / resource / budget management that governs external suppliers, resources, and budget. The key is building a structure that is neither excessive nor deficient within the SLA-versus-cost trade-off.