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 configurereplication to
provide a redundant database.
Second ELB is for cross region fail over. by nature ELB is fault tolerant so Ans should be A.
0
0
a
0
0
You need another internet gateway. ELB is multi-AZ so fine. ELB is multi-AZ so fine. But you have one internet gateway, so if the subnet that is in is in an AZ that dies, you’re internetless.
0
1
You can only have one gateway to your VPC
0
0
The answer is A
B is incorrect because you can only have one IGW per VPC
C is incorrect because this ELB is reffered to a redundant which is already inherent to ELBs. If they restated this a adding a replicated VPC in another region and then added route 53 fail-over that would be Disaster Recovery and not really simple single-point-of-failure
D is incorrect because you already have a multi-AZ RDS instance
2
0
a
0
0
Ans: A
0
0