The answer is to create a separate Aurora cluster for the write-heavy microservice and point that microservice to the new cluster’s endpoint. This physically isolates the write-heavy workload, preventing its I/O and replication overhead from contending with the read queries of other microservices, which is the core problem of shared resource contention in a single writer cluster. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of workload isolation patterns versus vertical scaling or read replicas—common traps include suggesting a larger instance (which doesn’t isolate) or RDS Proxy (which handles connections, not write contention). The key insight is that Aurora’s single writer architecture means all writes funnel through one node, so separating the write-heavy microservice into its own cluster is the only way to guarantee zero impact on other services without code changes. Memory tip: “Isolate the writer, not the reader—separate clusters for separate burdens.”
SAP-C02 Practice Question: Accelerate Workload Migration and Modernization
This SAP-C02 practice question tests your understanding of accelerate workload migration and modernization. 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 modernizing its application by migrating from a monolithic architecture to microservices on Amazon ECS Fargate. The application uses an on-premises Oracle database, which is being migrated to Amazon Aurora PostgreSQL as part of the modernization. The team has refactored the application into several microservices, each with its own database schema in the same Aurora cluster. During load testing, the team notices that one microservice's heavy write operations cause increased latency for other microservices' read queries. The Aurora cluster uses a single writer and multiple readers. The team needs to isolate the write-heavy microservice without changing the application code. What should the solutions architect do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a separate Aurora cluster for the write-heavy microservice and point the microservice to that cluster.
Using a separate Aurora cluster for the write-heavy microservice physically isolates the workload, preventing impact on other microservices. The application code points to different cluster endpoints. Using a larger instance might help but does not isolate; read replicas do not help with write contention; RDS Proxy is for connection pooling, not isolation.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
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 RDS Proxy to manage database connections.
Why it's wrong here
RDS Proxy helps with connection management but does not isolate workloads.
✓
Create a separate Aurora cluster for the write-heavy microservice and point the microservice to that cluster.
Why this is correct
A separate cluster provides complete isolation of write operations.
Related concept
Standard ACLs match source addresses.
✗
Configure Aurora read replicas to offload read queries from the writer.
Why it's wrong here
Read replicas only handle read traffic; write contention on the writer remains.
✗
Increase the instance size of the Aurora writer to handle the write load.
Why it's wrong here
Scaling up may reduce latency but does not isolate the write-heavy microservice; other queries may still be affected.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.
TExam Day Tips
→Check inbound versus outbound direction.
→Read the ACL from top to bottom.
→Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SAP-C02 ACL questions on filtering logic and placement.
Accelerate Workload Migration and Modernization — This question tests Accelerate Workload Migration and Modernization — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Create a separate Aurora cluster for the write-heavy microservice and point the microservice to that cluster. — Using a separate Aurora cluster for the write-heavy microservice physically isolates the workload, preventing impact on other microservices. The application code points to different cluster endpoints. Using a larger instance might help but does not isolate; read replicas do not help with write contention; RDS Proxy is for connection pooling, not isolation.
What should I do if I get this SAP-C02 question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SAP-C02 ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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 →
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.
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.
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.