A user has configured ELB with three instances. The user wants to achieve High Availability as well as
redundancy with ELB. Which of the below mentioned AWS services helps the user achieve this for ELB?
A.
Route 53
B.
AWS Mechanical Turk
C.
Auto Scaling
D.
AWS EMR
Explanation:
The user can provide high availability and redundancy for applications running behind Elastic Load Balancer by
enabling the Amazon Route 53 Domain Name System (DNS. failover for the load balancers. Amazon Route 53 is
a DNS service that provides reliable routing to the user’s infrastructure.
C.
Auto Scaling
ELB’s can be created in multiple Availability Zones and are used with instances you launch in the same Zone. Users create Redundancy in two ways.
* Running multiple instances behind the ELB and using AutoScaling.
* Launching paralel ELB configurations in multiple Zones.
ELB’s will scale in their capacity to handle increases in traffic. So redundancy to accommodate increases in traffic are built into the functionality your ELB.
https://forums.aws.amazon.com/thread.jspa?threadID=48774
C is correct
” High Availability as well as redundancy with ELB” AutoScaling cannot give redundancy with ELB. It has to be Route 53 So correct Answer is:
(A)
A
A.
A
C
Auto Scaling provides high availability
and ELB is already providing redundancy .
For Route53 to be an answer there would be Multiple ELBs which is not the case .
Redundancy with 3 Instances being in three AZs behind the ELB (ELB itself is HA). and AutoScaling with its AZRebalance will ensure that is the case in case any instance goes down in one AZ.
a
The Answer should be A. The questions is to provide “high availability and redundancy with ELB”.
Using Autoscaling, doesn’t make sense in the distribution of the traffic or fail-over to the load balancers.
The question says…”Which of the below mentioned AWS services helps the user achieve this for ELB?”……FOR ELB ?? Route53 is the correct answer.
*Great* question
answer should be A, if you want redundant ELB, you must use Route53.
I will go with C.
ELB only provide health check and traffic distribution, but the instances may have problem. In this case, you need Auto Scaling to terminate instances or create new instance.
wanna go with A
The ELB can be set up cross regions, Route53 weighted/latency records can be placed to route traffic to the ELB in different regions. So the answer is A
A
Question is: “High Availability as well as redundancy with ELB.”
With 3 instances you have HA already.
But to have ‘redundancy with ELB’ – you need to implement DNS (failover) – which also would require additional ELB. None of these are mentioned in the Q or Ans – but essentially that is what will be needed.
ASG will help – but we have some already and only 1 choice.
So A Rt53
A.
Route 53