Which of the below mentioned configurations will not meet the requirements of the multi-site solution scenario?
Configure data replication based on RTO.
Keep an application running on premise as well as in AWS with full capacity.
Setup a single DB instance which will be accessed by both sites.
Setup a weighted DNS service like Route 53 to route traffic across sites.
Explanations:
Configuring data replication based on the RTO is essential for a multi-site solution. It ensures that data is synchronized between the sites, allowing for quick failover in case of a disaster.
Running the application with full capacity on both on-premises and AWS environments is a key characteristic of an active-active multi-site setup. This minimizes RTO because the application is already running and ready to take over traffic.
Using asingledatabase instance accessed by both on-premises and AWS environments creates a single point of failure. If that database instance fails, both sites are affected, defeating the purpose of a multi-site solution for high availability and low RTO. Each site should ideally have its own database or a replicated database setup.
Using a weighted DNS service like Route 53 allows for traffic distribution between the on-premises and AWS sites. This is important for load balancing and failover scenarios. If one site goes down, DNS can be reconfigured to direct all traffic to the other site.