A rehosted municipal intranet previously ran on a single tower server and must gain elasticity after landing in AWS. Which compute platform selection best fits?
Select an answer to reveal the explanation.
Short Explanation
One lonely tower server is a single point of oops. Put the intranet on EC2 Auto Scaling behind an ALB so traffic and failures share the load like a team, not a hero machine.
Full Explanation
A rehosted municipal intranet that previously ran on a single tower server must gain elasticity after landing in AWS. Select Amazon EC2 Auto Scaling behind an Application Load Balancer instead of a single tower server so staff intranet traffic can scale and survive instance failure across civic working hours. One oversized EC2 instance in a single Availability Zone with no load balancer fails elasticity and AZ resilience. A dedicated hardware appliance shipped to each department lobby fails cloud platform selection and multiplies unmanaged appliances. AWS Snowball Edge as the permanent production web tier fails because Snowball Edge is for edge/data transfer use cases, not the standing municipal intranet platform. Exam caveat: rehost targets should add ALB and Auto Scaling rather than recreating a single tower. Operational check: place instances in multiple AZs behind an ALB, define scaling policies from CPU or request metrics, health-check the intranet app, and retire the tower mental model in the runbook. Document the decision in the municipal architecture decision record and re-verify controls after the first production wave so auditors see continuous improvement, not one-time tribal knowledge.