Hard1 markMultiple Choice
Domain 3.4: Reliability ImprovementReliabilityEC2Auto ScalingEvent-Driven

AWS SAP-C02 · Question 53 · Domain 3.4: Reliability Improvement

A company is designing a highly available architecture for a stateful legacy application that cannot be containerized. The application runs on EC2 instances and requires a persistent IP address. If an instance fails, a new one must be launched automatically and retain the same IP address. Which TWO actions should the architect take? (Select TWO)

Answer options:

A.

Place the EC2 instance in an Auto Scaling group with a minimum and maximum size of 1.

B.

Use an Amazon EventBridge rule triggered by the EC2 instance launch lifecycle event to invoke a Lambda function that attaches an Elastic IP address.

C.

Configure an Application Load Balancer in front of the EC2 instance.

D.

Use AWS Global Accelerator to route traffic to the EC2 instance.

E.

Store the application state in Amazon ElastiCache.

F.

Use AWS OpsWorks to manage the instance lifecycle.

How to approach this question

Combine an ASG of size 1 for self-healing with event-driven automation (EventBridge + Lambda) for IP attachment.

Full Answer

Place the EC2 instance in an Auto Scaling group with a minimum and maximum size of 1. Use an Amazon EventBridge rule triggered by the EC2 instance launch lifecycle event to invoke a Lambda function that attaches an Elastic IP address.
An Auto Scaling group with min=1, max=1 ensures high availability (if the instance dies, a new one is launched). To maintain the persistent IP, an EventBridge rule can detect the launch and trigger a Lambda function to reassign the Elastic IP to the new instance.

Common mistakes

Thinking an ALB solves the persistent IP requirement for the backend instance.

Practice the full AWS Solutions Architect Professional SAP-C02 Practice Exam 1

75 questions · hints · full answers · grading

More questions from this exam