You are managing a legacy application Inside VPC with hard coded IP addresses in its configuration. Which two mechanisms will allow the application to failover to new instances without the need for reconfiguration? (Choose two.)
A.
Create an ELB to reroute traffic to a failover instance
B.
Create a secondary ENI that can be moved to a failover instance
C.
Use Route53 health checks to fail traffic over to a failover instance
D.
Assign a secondary private IP address to the primary ENIO that can be moved to a failover instance
B & C : are Good to adress failover infrastructure in NEW INSTANCES where the legacy application has hard IP configured inside:
B: to recuperate THÉ SAME IP ADRESS in a new EC2
C : ROUTE 53 to adress the failover under a new VPC
Correct Answers: B & D
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
Here you can choose either the option of creating a Secondary Network interface which can be moved to the failover instance or have a secondary IP Address which can be moved to the failover instance. For both cases, you can do this at the time of defining the EC2 instance.
A | C are the answers
ELB can automatically re-route traffic to a fail over instance when the target instance becomes unhealthy (A)
Route53 is also capable to re-route traffic to a fail over instance when the primary instance fails (C)
Not in this case, that we have a hard coded IP addresses in a legacy application configuration. ELB and Route53 would work fine if it wasn't like that.
Correct Answers: B & D
B. Create a secondary ENI that can be moved to a failover instance
D. Assign a secondary private IP address to the primary ENIO that can be moved to a failover instance
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.
a_w_s
Highly Voted 3 years, 2 months agoKittieHearts
Most Recent 8 months, 2 weeks agodexdinh91
1 year agoGianiluca
2 years, 2 months agoTroyMcLure
3 years, 1 month agoRicardoD
3 years, 1 month agoTroyMcLure
3 years, 1 month agofabianvera19822
3 years, 2 months agowaterzhong
3 years, 2 months agoAWS_Noob
3 years, 2 months agoAWS_Noob
3 years, 2 months agoawscertified
3 years, 2 months ago