What should a solutions architect do to accomplish this?
Install SQL Server on Amazon EC2 in a Multi-AZ deployment.
Migrate the data to Amazon RDS for SQL Server in a Multi-AZ deployment.
Deploy the database on Amazon RDS for SQL Server with Multi-AZ Replicas.
Migrate the data to Amazon RDS for SQL Server in a cross-Region Multi-AZ deployment.
Explanations:
Installing SQL Server on Amazon EC2 in a Multi-AZ deployment provides high availability, but it requires more operational management overhead, such as handling backups, patching, and failover management manually. This does not minimize operational overhead as the company desires.
Migrating the data to Amazon RDS for SQL Server in a Multi-AZ deployment offers high availability and is a managed service, which minimizes operational and management overhead. RDS handles backups, patching, and failover automatically.
While deploying the database on Amazon RDS for SQL Server with Multi-AZ Replicas provides high availability, it doesn’t exist in the context of RDS for SQL Server. Multi-AZ deployments provide synchronous replication for high availability, but “Multi-AZ Replicas” is not a valid option in this scenario, as it misrepresents RDS features.
Migrating the data to Amazon RDS for SQL Server in a cross-Region Multi-AZ deployment would provide high availability and disaster recovery, but it is unnecessary for this scenario and adds complexity and potential latency. The company aims to minimize operational overhead, making this option less ideal.