CLF-C02 Cloud Concepts Practice Question
A company is designing a system where a failure in one component does not cause cascading failures across the entire application. Which architectural concept does this represent?
⚠ Common exam trap
AWS often tests the confusion between loose coupling and horizontal scaling, where candidates mistakenly think scaling out instances prevents cascading failures, but scaling alone does not decouple component dependencies.
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
✓
Loose coupling
Loose coupling is the architectural concept that ensures components are independent, so a failure in one component does not cascade to others. In AWS, this is achieved through services like Amazon SQS for asynchronous messaging or Amazon SNS for event-driven decoupling, where each component can fail and recover independently without affecting the rest of the system.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Tight coupling
Why it's wrong here
Tight coupling creates direct, synchronous dependencies between components. In this design, a single component's failure or latency spike can cascade, quickly exhausting downstream resources and causing widespread outage. Because components must coordinate and share state, they also cannot be deployed, scaled, or replaced independently, which undermines the resilient distributed architecture that the AWS Well-Architected Framework encourages.
- ✓
Loose coupling
Why this is correct
Loose coupling isolates components through intermediate boundaries such as queues, event streams, or APIs, allowing each piece to operate independently. A consumer does not need to be online or at the same scale as the producer, so failures are contained and retries are simple. This design enables independent scaling, deployment, and replacement, making it the core pattern for building fault-tolerant cloud workloads on AWS.
- ✗
Vertical scaling
Why it's wrong here
Vertical scaling, or scaling up, means adding more CPU, memory, or disk to a single resource such as an EC2 instance. It has no bearing on how components interact; a vertically scaled instance can still be tightly coupled to other services. This approach also has hard limits and a single point of failure, so it does not address the dependency isolation that loose coupling provides.
- ✗
Monolithic architecture
Why it's wrong here
A monolithic architecture packages all application functions into one deployable unit, so even if the code is well-structured, components share the same process, database, and lifecycle. This coupling forces coordinated releases and makes partial failures or independent elasticity nearly impossible. Monoliths are often contrasted with loosely coupled microservices because every change carries risk across the entire system, whereas loose coupling contains the blast radius of change and failure.
Go deeper
Related to this question
About these practice questions
One of 988 original CLF-C02 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 CLF-C02 practice question is part of Courseiva's free Amazon Web Services 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 CLF-C02 exam.