A latency-sensitive GIS app tier chats constantly with Redis and a database. Architects also require Multi-AZ resilience for the overall stack. How should they place resources?
Select an answer to reveal the explanation.
Short Explanation
Chatty neighbors should live on the same street for speed, but the city still needs a spare street if one floods. Keep caches and DBs close for latency, and keep Multi-AZ so an AZ loss is not a total outage.
Full Explanation
Resource placement for performance minimizes cross-AZ or cross-Region chatter for latency-sensitive app–cache–database paths while still using Multi-AZ architectures for high availability. Forcing all dependencies into a far Region, isolating caches without connectivity, or abandoning Multi-AZ entirely trades away either latency or resilience.