SAP-C02 Practice Question: Design Solutions for Organizational Complexity
Which THREE design patterns are recommended for decoupling components in a microservices architecture on AWS?
⚠ Common exam trap
Watch out — candidates often confuse network connectivity solutions (Direct Connect) or load balancing (ELB) with true decoupling patterns, but decoupling in microservices requires asynchronous, event-driven or message-based integration, not synchronous request/response or network links.
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
✓
Use Amazon EventBridge for event-driven integration.
Amazon EventBridge (A) is correct because it provides an event bus that routes events between producers and consumers based on rules, so services publish events without knowing subscribers, achieving asynchronous decoupling. Amazon SNS topics (C) are correct because the publish/subscribe model lets a publisher fan out messages to multiple subscribing endpoints (SQS, Lambda, HTTP/S, email) without direct coupling to consumers. Amazon SQS queues (D) are correct because point-to-point queues buffer messages between services, letting producers and consumers operate independently and absorb traffic spikes or consumer downtime. AWS Direct Connect (B) is not a decoupling pattern but a dedicated private network connection for hybrid connectivity, and Elastic Load Balancing (E) distributes synchronous traffic across targets but still requires the caller to know and directly invoke the load balancer endpoint, so neither decouples components in the event-driven sense.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Amazon EventBridge for event-driven integration.
Why this is correct
Amazon EventBridge provides asynchronous, event-driven integration so producers publish events without knowing consumers, satisfying the decoupling requirement. Its routing rules and schema registry let services evolve independently, and native AWS service targets remove direct point-to-point calls. This contrasts with synchronous request-response patterns, which tightly couple availability and latency between microservices.
- ✗
Use AWS Direct Connect for private connectivity.
Why it's wrong here
Direct Connect provides dedicated private network links between on-premises infrastructure and AWS, not asynchronous messaging between microservices. It is tempting because it decouples hybrid connectivity from the public internet, and would be correct when the requirement is private, consistent bandwidth to on-premises systems rather than service-to-service decoupling.
- ✓
Use Amazon SNS topics for pub/sub messaging.
Why this is correct
Amazon SNS topics implement the publish/subscribe pattern, letting producers broadcast events to multiple subscriber endpoints without knowing their identities. This satisfies the decoupling requirement by removing direct service-to-service dependencies, so failures or scaling changes in consumers do not affect publishers, and new subscribers can be added without modifying the producer.
- ✓
Use Amazon SQS queues between services.
Why this is correct
SQS provides asynchronous, point-to-point buffering so producers and consumers operate independently, absorbing traffic spikes and failures without direct coupling. This satisfies the decoupling requirement by removing synchronous runtime dependencies between microservices, unlike tightly coupled request-response calls.
- ✗
Use Elastic Load Balancing to distribute traffic.
Why it's wrong here
Elastic Load Balancing distributes synchronous request traffic across targets; it does not decouple components, since callers still block on responses and depend on downstream availability. It is tempting because it removes single points of failure at the entry tier, and would be correct when the requirement is spreading inbound HTTP traffic across healthy instances.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 984 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 SAP-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 SAP-C02 exam.