- A
Elasticity
Why wrong: Elasticity is the ability to automatically provision and de-provision compute resources as demand changes. It does not address how independent components interact or fail, so it does not prevent cascading failures between modules.
- B
High availability
Why wrong: High availability ensures that a system remains operational even during infrastructure failures, such as an Availability Zone outage, by using redundant resources. While it improves overall uptime, it does not isolate failures within the application architecture; a single module failure could still bring down tightly coupled components.
- C
Loose coupling
Loose coupling is an architectural principle where components are designed to have minimal dependencies on each other. They communicate asynchronously (e.g., via queues, events, or APIs) so that a failure in one component does not cascade to others. This approach directly solves the company's problem of isolating module failures.
- D
Disaster recovery
Why wrong: Disaster recovery refers to plans and processes for restoring IT infrastructure and data after a catastrophic event (e.g., natural disaster, large-scale outage). It is not a daily resilience pattern for preventing cascading failures between application modules.
Quick Answer
The answer is loose coupling, the cloud design concept that enables independent module operation through minimal dependencies and well-defined interfaces. In the scenario described, applying loose coupling means each module—user authentication, payment processing, and inventory management—communicates via APIs or message queues rather than direct calls, so a failure in payment processing cannot cascade to crash the entire application. On the AWS Certified Cloud Practitioner CLF-C02 exam, this concept tests your understanding of how cloud architectures achieve fault isolation and resilience, often appearing in questions about migrating monolithic applications to microservices. A common trap is confusing loose coupling with high availability or load balancing, but remember: loose coupling is about reducing interdependencies, not just adding redundancy. Memory tip: think of loose coupling like a set of independent LEGO blocks—if one breaks, the rest stay intact.
CLF-C02 Cloud Concepts Practice Question
This CLF-C02 practice question tests your understanding of cloud concepts. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is migrating a legacy monolithic e-commerce application to AWS. The application has three tightly integrated modules: user authentication, payment processing, and inventory management. In the current design, a failure in the payment processing module often causes the entire application to crash. The company wants to redesign the application so that each module runs independently, and a failure in one module does not cascade to other modules. Which cloud computing concept should the company apply to achieve this goal?
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
The correct answer is C, loose coupling. Loose coupling is a cloud computing concept where components are designed to have minimal dependencies on each other, communicating through well-defined interfaces or APIs. By decoupling the user authentication, payment processing, and inventory management modules, a failure in one module (e.g., payment processing) will not cascade and crash the entire application, as each module can operate independently and handle its own failures gracefully.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Elasticity
Why it's wrong here
Elasticity is the ability to automatically provision and de-provision compute resources as demand changes. It does not address how independent components interact or fail, so it does not prevent cascading failures between modules.
- ✗
High availability
Why it's wrong here
High availability ensures that a system remains operational even during infrastructure failures, such as an Availability Zone outage, by using redundant resources. While it improves overall uptime, it does not isolate failures within the application architecture; a single module failure could still bring down tightly coupled components.
- ✓
Loose coupling
Why this is correct
Loose coupling is an architectural principle where components are designed to have minimal dependencies on each other. They communicate asynchronously (e.g., via queues, events, or APIs) so that a failure in one component does not cascade to others. This approach directly solves the company's problem of isolating module failures.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Disaster recovery
Why it's wrong here
Disaster recovery refers to plans and processes for restoring IT infrastructure and data after a catastrophic event (e.g., natural disaster, large-scale outage). It is not a daily resilience pattern for preventing cascading failures between application modules.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse high availability with fault isolation, thinking that making a system highly available (e.g., with multiple instances) will prevent cascading failures, but high availability does not address the tight coupling between modules that causes one failure to bring down others.
Detailed technical explanation
How to think about this question
Loose coupling is often implemented using asynchronous messaging patterns, such as Amazon Simple Queue Service (SQS) or Amazon Simple Notification Service (SNS), where modules send messages to a queue or topic rather than making direct synchronous calls. This allows the receiving module to process the message when it is ready, and if it fails, the message can be retried or moved to a dead-letter queue without affecting the sender. In a real-world scenario, an e-commerce application might use SQS to decouple payment processing from inventory management, ensuring that a payment failure does not block inventory updates.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Concepts practice questions
Targeted practice on this topic area only
- →
All CLF-C02 questions
1,024 questions across all exam domains
- →
AWS Certified Cloud Practitioner CLF-C02 study guide
Full concept coverage aligned to exam objectives
- →
CLF-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related CLF-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Cloud Concepts practice questions
Practise CLF-C02 questions linked to Cloud Concepts.
Security and Compliance practice questions
Practise CLF-C02 questions linked to Security and Compliance.
Cloud Technology and Services practice questions
Practise CLF-C02 questions linked to Cloud Technology and Services.
Billing, Pricing, and Support practice questions
Practise CLF-C02 questions linked to Billing, Pricing, and Support.
AWS shared responsibility model practice questions
Practise CLF-C02 questions linked to AWS shared responsibility model.
AWS IAM practice questions
Practise CLF-C02 questions linked to AWS IAM.
AWS pricing practice questions
Practise CLF-C02 questions linked to AWS pricing.
AWS support plans practice questions
Practise CLF-C02 questions linked to AWS support plans.
AWS S3 practice questions
Practise CLF-C02 questions linked to AWS S3.
AWS EC2 practice questions
Practise CLF-C02 questions linked to AWS EC2.
Practice this exam
Start a free CLF-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this CLF-C02 question test?
Cloud Concepts — This question tests Cloud Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Loose coupling — The correct answer is C, loose coupling. Loose coupling is a cloud computing concept where components are designed to have minimal dependencies on each other, communicating through well-defined interfaces or APIs. By decoupling the user authentication, payment processing, and inventory management modules, a failure in one module (e.g., payment processing) will not cascade and crash the entire application, as each module can operate independently and handle its own failures gracefully.
What should I do if I get this CLF-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.