An organization has configured a VPC with an Internet Gateway (IGW). pairs of public and private subnets
(each with one subnet per Availability Zone), and an Elastic Load Balancer (ELB) configured to use the public
subnets The application s web tier leverages the ELB. Auto Scaling and a mum-AZ RDS database instance The
organization would like to eliminate any potential single points ft failure in this design.
What step should you take to achieve this organization’s objective?
A.
Nothing, there are no single points of failure in this architecture.
B.
Create and attach a second IGW to provide redundant internet connectivity.
C.
Create and configure a second Elastic Load Balancer to provide a redundant load balancer.
D.
Create a second multi-AZ RDS instance in another Availability Zone and configure replication to provide a
redundant database.
C should be correct, there should be one ELB in each AZ to provide HA.
0
1
I would think its A as adding as ELB can span multi-AZ with a region. Also you will need something like Route53 to pair up the 2 ELB names.
1
0
There’s no need to configure ELB for HA,
per
https://media.amazonwebservices.com/architecturecenter/AWS_ac_ra_ftha_04.pdf
“Most of the higher-level services, such as … Amazon Elastic Load Balancing (ELB), have been built with fault tolerance and high availability in mind
0
0
Why you presume that they won’t be any failure with the ELB ? It will be safe to have secondary ELB.
0
0
A is the right answer, there is no single point of failure in this architecture according to A CLOUD GURU!! Cheers…
0
0
A is correct. An ELB is used to load balance across AZs
0
0
I think it is A, because to create 2 ELB names across regions we need Route 53 DNS Failover. So, it is possible create HA for ELB but with Route 53.
DNS Failover for Elastic Load Balancing
https://aws.amazon.com/elasticloadbalancing/
0
0
Right answer should be C. Because what will happen if AZ will go down where we have ELB in public subnet.
0
0
Definitely A
ELB is designed to be HA across Availability Zones. You need multiple ELB if you want HA across regions.
“AWS Load Balancer – Cross Network
Many times it happens that after setting up your ELB, you experience significant drops in your performance. The best way to handle this situation is to start with identifying whether your ELB is single AZ or multiple AZ, as single AZ ELB is also considered as one of the Single Points of Failures on AWS Cloud. Once you identify your ELB, it is necessary to make sure ELB loads are kept cross regions.”
https://www.botmetric.com/blog/eliminating-single-points-of-failures-on-aws-cloud/
0
0
A
0
0
As most guys mentioned the answer is A.
ELB is already HA over multiple Zones. Only problem would be if all AZ in the Region have problem, but in that case too the solution is Route53 , which is not among the possible anssers.
0
0
A is the right answer
0
0
A, for the same reasons RZ stated.
0
0
Aardvark
0
0
A
0
0