A township finance Aurora cluster feels slow, and staff want to jump to a much larger instance class immediately. What should the architect do first to avoid unnecessary cost?
Select an answer to reveal the explanation.
Short Explanation
Don't buy a bigger truck until you check whether the trailer hitch is the problem. Performance Insights and CloudWatch tell you what to right-size before you open the wallet.
Full Explanation
Cost-aware capacity planning measures wait events, CPU, memory, and I/O with Performance Insights and CloudWatch before upsizing Aurora. Blindly selecting the largest class or every Region increases spend without evidence. Disabling monitoring removes the data needed to right-size. Cross-Region replicas address locality or DR, not unexplained local slowness, and add replication cost.