What should a SysOps administrator do to scale the database when traffic increases?
Configure Aurora Auto Scaling to add or remove Aurora Replicas in the cluster based on the average CPU utilization of the Aurora Replicas.
Configure Aurora Auto Scaling to increase or decrease the size of the Aurora Replicas based on the average CPU utilization of the Aurora Replicas.
Configure AWS Auto Scaling to monitor the Aurora cluster. Configure AWS Auto Scaling to add or remove Aurora Replicas in the cluster based on the average CPU utilization of the primary instance.
Configure AWS Auto Scaling to monitor the Aurora cluster. Configure AWS Auto Scaling to add or remove Aurora Replicas in the cluster based on the average CPU utilization of the existing Aurora Replica.
Explanations:
Aurora Auto Scaling can add or remove Aurora Replicas based on the average CPU utilization of the replicas, which is ideal for scaling read-heavy workloads without affecting the primary instance.
Aurora Auto Scaling does not increase or decrease the size of the replicas; it only manages the number of replicas to handle read scaling.
AWS Auto Scaling does not manage Aurora databases directly; Aurora Auto Scaling should be used to scale Aurora Replicas, and primary instance utilization is not the target for read scaling.
AWS Auto Scaling cannot manage Aurora Replicas. Only Aurora Auto Scaling can add or remove replicas based on replica CPU utilization.
I think the answer is:
Configure Aurora Auto Scaling to add or remove Aurora Replicas in the cluster based on the average CPU utilization of the Aurora Replicas.