Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 297 discussion

To reduce the frequency of blocked write operations in an Amazon Aurora PostgreSQL global database, particularly when you're using a 60-second Recovery Point Objective (RPO), the goal is to improve replication performance so that the lag between the primary cluster and its secondary regions does not exceed the 60-second threshold.

Removing a secondary cluster can help alleviate write contention on the primary cluster, improving overall performance.

Enabling write forwarding for an Amazon Aurora global database can be a viable solution to improve write performance and reduce the frequency of blocked write operations. Write forwarding allows secondary clusters in a global database to forward write requests to the primary cluster. This can help distribute the write load and improve the overall performance of the global database.

Explanation: Aurora global databases use asynchronous replication by default to provide fast cross-region replication. However, asynchronous replication can cause delays in synchronizing data between regions, and if the RPO is set too aggressively, it can cause write operations to block when replication is behind. By configuring synchronous replication, writes to the primary region will only be acknowledged once the changes are successfully replicated to the secondary regions, reducing the likelihood of replication lag. This means that write operations will be blocked if the replication is lagging and the RPO setting is not met, but the frequency of blocked writes may be reduced because synchronous replication guarantees data consistency across regions.