A company wants to host a web application on AWS that will communicate to a database within a VPC. The application should be highly available. What should a solutions architect recommend?
A.
Create two Amazon EC2 instances to host the web servers behind a load balancer, and then deploy the database on a large instance.
B.
Deploy a load balancer in multiple Availability Zones with an Auto Scaling group for the web servers, and then deploy Amazon RDS in multiple Availability Zones.
C.
Deploy a load balancer in the public subnet with an Auto Scaling group for the web servers, and then deploy the database on an Amazon EC2 instance in the private subnet.
D.
Deploy two web servers with an Auto Scaling group, configure a domain that points to the two web servers, and then deploy a database architecture in multiple Availability Zones.
Anything that says something like "..deploy database to an instance.." is not highly scaleable.
The best way to take advantage of the available AWS services for databases.
From here, you can already rule out A,C, and D
Correct answer: B
Ans=B. Deploy a load balancer in multiple Availability Zones with an Auto Scaling group for the web servers, and then deploy Amazon RDS in multiple Availability Zones.
Folks, wouldn't the answer be C based on the fact that the question wants the APPLICATION to be highly available but doesn't mention about the DB being highly available? Also the first part of the question says they want to host an app that will communicate to a DB INSIDE a VPC? C fits both those requirements.
would the application be available if and when the database isn't? Why would you want to have a single point of failure to make application not be available.
Bro, there is no point in application servers being highly available if they cannot query the DB which is standalone and failed in case of AZ failure. The solution should work overall.
we don't know the architecture, maybe the APP. doesn't need to talk to DB all the time. C should be enough , but for real life scenario -C is the best. The description is unclear to be honest.
Why not D? The only problem I see in D is the part "configure a domain that points to the two web servers", which pretty much looks like bad wording. On the other hand, the question says "a database", NOT "a relational database". Therefore I don't think that you can jump into going forward with RDS just like that...
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
manoj101
Highly Voted 3 years, 8 months agoJohnnyS20
Highly Voted 3 years, 8 months agoYvette_Lau
3 years, 8 months agoDarthYoda
3 years, 8 months agoarchimate
Most Recent 2 years, 9 months agoSimoneP
3 years, 3 months agosimran_kaur_simmi
3 years, 7 months agoDelooo
3 years, 7 months agosyu31svc
3 years, 7 months agoKK_uniq
3 years, 7 months agoYogi
3 years, 7 months agoYogi
3 years, 7 months agoPing001
3 years, 7 months agoKampton
3 years, 7 months agosamuel1999
3 years, 6 months agonaveenagurjara
2 years, 11 months agomyutran
3 years, 7 months agoJay_12
3 years, 7 months agokauls
3 years, 7 months agokauls
3 years, 7 months agofreemun05
3 years, 7 months agoRitz40
3 years, 7 months agobleble00001
3 years, 7 months agoJoy1986
3 years, 7 months agoanpt
3 years, 7 months ago