Question 290 - DBS-C01 discussion

Explanation from Amazon documents:Amazon Aurora PostgreSQL supports cluster cache management, which is a feature that helps reduce the impact of failover on query performance by preserving the cache of the primary DB instance on one or more Aurora Replicas. Cluster cache management allows you to assign a promotion priority tier to each DB instance in your Aurora DB cluster. The promotion priority tier determines the order in which Aurora Replicas are considered for promotion to the primary instance after a failover. The lower the numerical value of the tier, the higher the priority.By enabling cluster cache management for the Aurora DB cluster and setting the promotion priority for the writer DB instance and replica to tier-0, the database specialist can minimize the performance degradation after failover. This solution will ensure that the primary DB instance and one Aurora Replica have the same cache contents and are in the same promotion priority tier. In the event of a failover, Aurora will promote the tier-0 replica to the primary role, and the cache will be preserved. This will reduce the number of cache misses and improve query performance after failover.Therefore, option A is the correct solution to minimize the performance degradation after failover. Option B is incorrect because setting the promotion priority for the writer DB instance and replica to tier-1 will not preserve the cache after failover. Aurora will first try to promote a tier-0 replica, which may have a different cache than the primary instance. Option C is incorrect because enabling Query Plan Management and performing a manual plan capture will not affect the cache behavior after failover. Query Plan Management is a feature that helps you control query execution plans and improve query performance by creating and enforcing custom execution plans. Option D is incorrect because enabling Query Plan Management and forcing the query optimizer to use the desired plan will not affect the cache behavior after failover. Forcing the query optimizer to use a desired plan may improve query performance by avoiding suboptimal plans, but it will not prevent cache misses after failover.