A small municipal IT team needs high availability for a permits database but lacks staff to operate mirrored MySQL on EC2. What should the architect recommend?
Select an answer to reveal the explanation.
Short Explanation
A tiny IT shop shouldn’t babysit homemade MySQL mirrors. Hand HA to RDS or Aurora Multi-AZ and spend people-time on city services, not failover scripts.
Full Explanation
Citizen notifications during outages need fan-out to email, SMS, and mobile push without the city building three separate broker stacks. Amazon SNS topics with appropriate subscriptions provide that managed fan-out pattern for municipal status messages. Hand-building SMTP-only scripts on a single EC2 host without SMS or push leaves channels incomplete. Posting status only to an internal SharePoint site fails citizen reach. Publishing access keys for every notification channel inside mobile apps embeds secrets on devices. Exam caveat: SMS and push have regional and opt-in compliance requirements; prefer templates and delivery status logging for audits. Operational check: publish a test outage message to a topic, confirm email/SMS/push subscribers receive it, review delivery failure metrics, and restrict Publish permissions to the outage automation role. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure.