An application uses an Amazon Aurora MySQL DB cluster that includes one Aurora Replica.

Aurora Auto Scaling can automatically add or remove Aurora Replicas based on target metrics, including average connections across Aurora Replicas. AWS documentation lists “Average connections of Aurora Replicas” as a target metric when adding an auto scaling policy to an Aurora DB cluster. Because performance degrades above 200 connections and baseline usage is around 180, setting a target near 195 allows scaling to begin before the connection count crosses the problem threshold. Option A is vertical scaling and does not automatically respond to fluctuating demand. Option B is not how Aurora switches between provisioned and serverless modes during spikes. Option C is unnecessary and does not address read scaling with replicas. Therefore, an Aurora auto scaling policy using the database connections metric is correct.

===============