A planning department wants predictable performance for GIS map tiles during council meetings. Which cloud benefit theme addresses that need?
Select an answer to reveal the explanation.
Short Explanation
Council night is showtime for the map tiles. Predictability is knowing the system can deliver steady performance when the room is full—not hoping a mystery server finds a second wind. Cloud capacity you can plan for beats finger-crossing.
Full Explanation
Predictable performance for GIS map tiles during council meetings falls under predictability of performance and capacity: cloud resources can be planned and sized so workloads behave consistently when demand is known. Council night is a known peak; capacity planning toward steady tile performance is the benefit theme—not hoping a mystery server finds a second wind mid-meeting.
Defining predictability as performance that must randomly change every meeting contradicts the word. Claiming cloud forbids capacity planning and only allows surprise outages is false. Barring GIS from cloud because predictability is supposedly impossible online invents a restriction that is not a fundamentals rule.
Exam caveat: predictability does not mean infinite free performance—you still choose sizes, tiers, and caching strategies; the benefit is that you can plan capacity deliberately rather than hoping mystery hardware keeps up. Known demand is exactly when planning pays off.
Operational check: before council sessions, run a map-tile load rehearsal at expected concurrent users, record latency and error rates, and adjust instance count or tier until results stay within the agreed performance band for meeting night; keep the rehearsal results with the runbook.