An organization has an on-premises messaging application. They want to migrate this application to the AWS cloud without making much code changes while running an on-prem system parallel with the AWS cloud in the hybrid model.
How would Solution Architect migrate the highly available solution and support JMS APIs, AMQP, and MQTT protocols?

Answer options:

A.Design the solutions using SNS that also supports integration with other AWS services.
B.Design the solutions using SQS that also supports integration with other AWS services.
C.Design the solutions using SQS, SNS and Lambda.
D.Design the solutions using Amazon MQ in 2 private subnets across multiple Availability Zones.

Correct Answer : D
Key points to note in this question are hybrid running two systems. Systems should be highly available, cloud migration, supports both queues and topics (pub and sub), supports JMS API and MQTT protocols, without making code change.
Option A is incorrect: SNS is a highly available AWS service that provides topics but doesn`t make code change requirements and hybrid running of two systems. SNS supports the push model of asynchronous communications in the following picture.
Option B is incorrect: SQS is a highly available AWS service that provides queues but doesn`t make code change requirements and hybrid running of two systems.
Option C is incorrect: SQS and SNS are highly available AWS services that provide queues and topics but don`t make code change requirements. This will be a good solution for the long run if I need to rewrite with SNS and SQS that supports other AWS services.
Option D is CORRECT: Amazon MQ is a managed AWS service for Apache Active MQ that meets both SQS (queues) and SNS (Topics) functionality.It also supports JMS API and other key protocols like MQTT etc. This is a good fit to migrate on-prem applications using traditional message brokers.
Reference:
https://aws.amazon.com/amazon-mq/?amazon-mq.sort-by=item.additionalFields.postDateTime&amazon-mq.sort-order=des