Court e-filing feels underpowered at peak while sandbox accounts sit overbuilt all month. What rightsizing strategy should architects adopt?
Select an answer to reveal the explanation.
Short Explanation
Don’t starve the e-filing counter while the sandbox feast never ends. Let the metrics tell you what to grow and what to trim.
Full Explanation
When court e-filing feels underpowered at peak while sandbox accounts sit overbuilt all month, architects should rightsize from observed metrics: lift underpowered production capacity and shrink chronically idle sandbox footprints. Guessing larger sizes for every environment without CloudWatch or Cost Explorer review overspends and may still miss the real bottleneck. Keeping production undersized permanently to save money despite missed SLAs fails citizen service levels. Rightsizing only sandboxes once a year and never revisiting production leaves the painful tier unchanged. Exam caveat: rightsizing must consider burst patterns and scheduled peaks such as filing deadlines—averages alone can undersize. Operational check: pull CPU, memory, and queue metrics for e-filing and sandboxes, propose target sizes, apply changes in a window, and verify latency and monthly cost move in the intended directions. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure.