ITIL4F Four Dimensions of IT Service Management Practice Question
A global financial services firm is expanding its online trading platform to handle increased market volatility. The platform currently uses a monolithic architecture hosted in a private cloud. The IT team has noticed that during peak trading hours, the system experiences latency spikes and occasional timeouts. The business requires 99.99% uptime and rapid scaling to handle sudden volume surges. The team has been asked to propose improvements within the 'Information and Technology' dimension. They are evaluating several options. Which course of action best addresses the symptoms while aligning with the four dimensions?
⚠ Common exam trap
It's easy for candidates to confuse vertical scaling (Option A) as a quick fix for capacity, ignoring the architectural limitations of a monolith, or assume process improvements (Option B) can compensate for technology deficiencies, while the question explicitly targets the 'Information and Technology' dimension.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Migrate to a microservices architecture using container orchestration and implement auto-scaling policies to handle demand spikes.
Directly addresses the root cause (monolithic architecture unable to scale dynamically) by migrating to microservices with container orchestration (e.g., Kubernetes) and auto-scaling policies. This aligns with the 'Information and Technology' dimension by redesigning the technology architecture to handle sudden volume surges, achieving 99.99% uptime through horizontal scaling and fault isolation, rather than vertical scaling or reactive processes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the capacity of existing servers by adding more CPU and RAM to handle peak loads.
Why it's wrong here
This approach, known as vertical scaling or "scaling up," involves adding more resources to a single server. While it can provide a short-term performance boost, it inherently faces physical limits and does not address the fundamental architectural constraints of a monolithic application, such as single points of failure or inefficient resource utilization for distinct services. It's a reactive fix that eventually hits a ceiling, failing to provide sustainable scalability for a global financial services firm.
- ✗
Implement a new incident management process to reduce response times during outages.
Why it's wrong here
Implementing a new incident management process primarily improves the organizational response to failures and outages, aiming to restore service faster. However, it is a process-level improvement within the "Processes and Value Streams" dimension, not a technological solution to prevent the underlying issues of latency, timeouts, or lack of scalability in the first place. It addresses the symptoms rather than the root cause of the performance problems, offering no preventative measure against demand spikes.
- ✓
Migrate to a microservices architecture using container orchestration and implement auto-scaling policies to handle demand spikes.
Why this is correct
This solution directly tackles the core challenges by re-architecting the application into independent, smaller services (microservices). Container orchestration (e.g., Kubernetes) provides the platform for deploying, managing, and scaling these services efficiently, while auto-scaling policies dynamically adjust resource allocation based on real-time demand. This approach ensures high availability, resilience, and elastic scalability, preventing latency and timeouts during peak loads by distributing the workload and scaling only necessary components.
- ✗
Outsource the platform management to a third-party provider with proven uptime guarantees.
Why it's wrong here
Outsourcing platform management shifts the operational burden and accountability for uptime to an external partner, falling under the "Partners and Suppliers" dimension. While it might leverage external expertise and guarantees, it does not inherently improve the internal technological architecture or address the fundamental scalability and performance issues of the existing system. The underlying monolithic architecture and its limitations would persist, merely managed by a different entity, potentially introducing new integration and governance complexities rather than solving the technical problem.
Go deeper
Related to this question
About these practice questions
Courseiva writes every ITIL4F question from scratch — 805 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.