Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 237 discussion

Option B is missing the Data Transformation to be done by Lambda

C, because it said new design and obviously IoT is what aws recommend.

Must be C. https://aws.amazon.com/tw/blogs/iot/building-an-iot-solution-to-securely-transmit-mqtt-messages-under-private-networks/

Option B could also work. The key why it is not correct is because it says there is a single broker, so it will not be HA, therefore it won't prevent the crashing problem. So C is the correct option.

MSK can't transforms the data

b ANS B. Amazon MSK with NLB: Pros: Highly available and managed Kafka service. Scalable to accommodate increasing data volume. NLB automatically distributes sensor data across healthy brokers. Cons: Requires migration from on-premises Kafka server. Potential cost increase for managed service.

Option C.

C :Anshttps://docs.aws.amazon.com/lambda/latest/dg/services-kinesisfirehose.html

Answer: C To me C is still the best option as it is not wrong and there is an uncertainty regarding NLB support for MQTT protocol. You can, yes, however, not out of the box, you would need solutions like HiveMQ, for example: https://github.com/mqtt/mqtt.org/wiki/Server%20support Now, when I read this part of the question "Recently, the Kafka server crashed. The company lost sensor data while the server was being restored", to me it seems that it would be OK for the company to look for different ways in having their data stored in S3, be it using a Kafka server or not. Therefore and, just because the question doesn't say anything regarding cost effectiveness, least operational overhead, least dev overhead and so on, it's safe to assume (to me) that IoT Core would be the option AWS wants us to think about.

Both B and C will work? NLB + MSK is a well defined pattern. MSK is highly available and scaleable. MQTT will pass through NLB as it's just a network port. No changes to the application. C would also work, but seems to involve more refactoring.

It's B, because MSK can handle the lightweight MQTT protocol.

its a C mqtt->IoT core

IoT perfect for MQTT. Option D could have the same problem as on-premises

It's C. Anytime you see sensors, your best bet is IoT. It's not D because you'll have one Kafka EC2 instance and it's not HA.

MODERATOR - please remove my previous comment. Looks is C is correct answer

IOT core is designed to handle this. and NLB does not support MQTT.

Agree with C