A municipal database VM that cannot easily shard is saturating CPU and RAM. Which short-term scaling approach fits best?
Select an answer to reveal the explanation.
Short Explanation
When you can’t easily split the filing cabinet, you buy a bigger cabinet—that’s vertical scaling. More CPU and RAM on the same database VM buys headroom when sharding isn’t practical yet. It’s not forever architecture, but it’s the right short-term lever.
Full Explanation
Vertical scaling increases the resources of an existing instance rather than adding peers. Databases that are difficult to shard or distribute often use vertical scaling to relieve CPU and memory pressure. Operators should still plan longer-term architecture, but Cloud+ expects recognition of vertical scaling as the appropriate approach in this scenario.