Your development team requires a message to be consumed by multiple consumers in an application. You also need to ensure that the metadata can be sent along with the messages. Which of the following would you implement for this purpose?

Answer options:

A.Implement as SNS topic and use different endpoints for the different types of metadata.
B.Use SQS queues and create different queues for the different type of metadata.
C.Use a FIFO SQS queue to maintain order of messages and fan them out.
D.Use an SNS topic and add message attributes to the messages.

Answer – D
The AWS Documentation mentions the following.
Amazon SNS supports the delivery of message attributes which let you provide structured metadata items (such as timestamps, geospatial data, signatures, and identifiers) about the message. Each message can have up to 10 attributes.
https://docs.aws.amazon.com/sns/latest/dg/sns-message-attributes.html
Options A is not correct because you are asked to send metadata information along with the message. Here it`s referring to work with many custom endpoints (which is much more overhead).
Option B is invalid since you cannot mimic the functionality of SNS Topics through many SQS queues. This would be a bad practice.
Option C is not the intended use for FIFO SQS. While it does maintain the order of items in the queue and their underlying message attributes, it does not fan output to endpoints. 
For more information specifically on SQS message attributes, please refer to the below URL-
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-message-attributes.html