A statewide emergency FAQ assistant needs high availability for Cosmos DB writes, but cost still matters. What tradeoff should the architect evaluate?
Select an answer to reveal the explanation.
Short Explanation
Multi-region Cosmos is the statewide firehouse network—worth the tab when the emergency FAQ must stay up everywhere, but you still weigh that cost against a quieter single-region setup.
Full Explanation
Statewide emergency FAQ assistants on Cosmos DB often need geographic write availability, but multi-region writes carry ongoing cost. The sound architectural move is to compare multi-region write topology against single-region cost and enable multi-region only where the emergency SLA truly requires that resilience. Always enabling unlimited multi-region writes with no cost review for every municipal FAQ container overspends on containers that do not need statewide write paths. Never using multi-region Cosmos even when statewide emergency SLAs demand geographic resilience undercuts the availability requirement the scenario states. Replacing Cosmos with on-premises USB drives shipped between counties abandons a managed globally distributed store for an offline, high-latency, high-risk distribution model unfit for emergency FAQ operations. Exam caveat: expect cost-versus-availability tradeoff questions rather than “always multi-region” absolutes for civic Cosmos data planes. Operationally, map which FAQ containers serve statewide emergency SLAs, price multi-region write configurations for those only, and validate failover or multi-region read/write behavior in a controlled drill before production cutover.