mediumMultiple ChoiceObjective-mapped
Cloud Digital Leader Practice Question: Planning a cloud architecture and needs to decide…
A company is planning a cloud architecture and needs to decide between a monolithic application design and a microservices architecture. What is the most significant operational trade-off between these two approaches in a cloud environment?
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
✓
Microservices enable independent deployment and scaling per component but introduce distributed systems complexity (network overhead, distributed tracing, service discovery, consistency challenges); monoliths are simpler to operate but scale and deploy as a unit
Monoliths are simpler to develop, test, and deploy initially but scale as a unit and create tight coupling — a change to one part requires deploying the whole application. Microservices enable independent deployment and scaling of components but introduce distributed systems complexity (network calls, service discovery, distributed tracing, eventual consistency). Neither is universally better — the trade-off depends on team size, domain complexity, and operational maturity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monoliths can only run on-premises, while microservices were designed specifically for cloud environments
Why it's wrong here
Monoliths are not confined to on-premises data centers; they run equally well in cloud environments on virtual machines or container platforms like Google Kubernetes Engine. Conversely, microservices were not specifically designed for cloud—they can be deployed on-premises too—but the cloud's elasticity and managed services amplify their strengths in independent scaling and fault isolation. The real distinction is architectural style, not deployment location.
- ✓
Microservices enable independent deployment and scaling per component but introduce distributed systems complexity (network overhead, distributed tracing, service discovery, consistency challenges); monoliths are simpler to operate but scale and deploy as a unit
Why this is correct
This accurately captures the key trade-off. Microservices' benefits (independent scale, isolated failures, technology diversity) come with real operational costs: inter-service communication adds latency and failure modes, distributed tracing replaces simple stack traces, and data consistency across services requires careful design.
- ✗
Microservices are always cheaper to operate in the cloud because each service uses fewer resources than a monolith
Why it's wrong here
Microservices are not inherently cheaper; each service may consume fewer resources individually, but the total footprint often grows due to multiple service replicas, sidecar proxies, service meshes, API gateways, and service discovery mechanisms. These distributed systems components add compute, memory, and network overhead that can exceed the cost of a well-tuned monolith for the same workload. Cost depends on operational efficiency, not just the size of individual components.
- ✗
Monolithic applications cannot be scaled horizontally in cloud environments
Why it's wrong here
Horizontal scaling is absolutely possible for monolithic applications—stateless monoliths can be replicated into multiple identical instances behind a load balancer to distribute traffic. The limitation is that all instances must share the same codebase and scale together, whereas microservices can scale each component independently. Thus, horizontal scaling is a cloud capability available to both architectures, not an exclusive feature of microservices.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
Key term
Service discovery
Service discovery is the process by which networked services automatically locate each other to communicate, without needing manual configuration of network addresses.
About these practice questions
One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud 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 GCDL exam.