Question 1
UnclassifiedA read-heavy app serves users in North America and Europe. Latency is high for European users. What should the architect evaluate?
Correct answer: C
Explanation
Multi-region replication and read-region placement reduce latency by serving reads from a nearby region instead of sending European users to North America. For a read-heavy app, placing replicas closer to users follows the principle of minimizing network distance to improve response time.
Why each option is right or wrong
A. A shorter subscription name.
B. Whether to delete all indexes.
C. Multi-region replication and read-region placement.
For a read-heavy workload with users split across North America and Europe, the architect should assess whether the database supports multi-region replication and whether read replicas can be placed in the European region so requests do not traverse the Atlantic on every read. In AWS terms, this is the standard RDS/Aurora read-scaling pattern: replicas are asynchronous, can be promoted, and are used to offload reads from the primary; the relevant design concern is regional placement to reduce round-trip latency, not increasing compute in a single region.
D. Moving all users to one time zone.