MENU
When the asynchronous messages produced by one producer should go to more than one consumer, what tools we should use?
Suggested Answer: B, C, D
Get Premium ACA-CloudNative Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
GE
Gerald
12 months ago
Yeah, Kafka is the best choice here, no doubt.
AL
Alethea
12 months ago
Surprised no one mentioned RabbitMQ!
NI
Nicolette
1 year ago
Kafka is the go-to for pub/sub scenarios.
RA
Raylene
1 year ago
I thought MySQL could handle it too?
MA
Malcom
1 year ago
Definitely Apache Kafka for that!
SA
Salina
1 year ago
My notes say something about using databases for messaging, but I don't think MySQL is the right tool for this scenario.
MI
Mitsue
1 year ago
I practiced a similar question, and I think Kafka is definitely the right choice for asynchronous messaging.
FR
Freeman
1 year ago
I'm not entirely sure, but I feel like Tomcat is more about serving web applications rather than message distribution.
LA
Lavonda
1 year ago
I remember studying message brokers, and I think Kafka was mentioned as a good option for handling multiple consumers.
JO
Josephine
1 year ago
Ah, I remember learning about SIPOC in my operations management class. The missing word is definitely "Process" - it's the core of the SIPOC framework.
MA
Margret
1 year ago
Hmm, I'm not sure about this one. The date could mean August 10th or October 8th. I'll have to think it through carefully.
OL
Olga
2 years ago
I was gonna go with CDN, but then I realized that's for serving static content, not routing messages. Gotta love these trick questions, am I right?
AJ
Aja
1 year ago
C) Apache Kafka
RE
Reid
1 year ago
Oh yeah, I almost fell for that too!
BL
Blythe
1 year ago
C) Apache Kafka
AL
Alyce
1 year ago
A) Apache Tomcat
TA
Tamar
2 years ago
If I had a dollar for every time someone tried to use a database as a message queue, I'd be sipping a mojito on a beach somewhere. Kafka is the clear winner here.
IR
Irving
2 years ago
Hmm, I was considering MySQL Server, but that's more for persistent data storage, not message distribution. Kafka is definitely the way to go here.
GI
Gilma
1 year ago
MySQL Server is for storing data, not distributing messages.
WI
William
1 year ago
CDN is for content delivery, not message distribution.
CR
Cristal
1 year ago
Tomcat and Maven are more for web applications, not message distribution.
PE
Peggie
1 year ago
I agree, Kafka is perfect for distributing messages to multiple consumers.
FA
Fairy
1 year ago
Using Apache Kafka will ensure efficient distribution of messages to multiple consumers.
WI
Willard
1 year ago
Apache Kafka is designed for handling asynchronous messages to multiple consumers.
ZO
Zona
1 year ago
I agree, MySQL Server is more for storing data, not for message distribution.
KA
Karon
1 year ago
I think Kafka is the best option for distributing messages to multiple consumers.
OT
Otis
2 years ago
I was thinking Apache Tomcat, but then I remembered that's a web server, not a message broker. Kafka makes much more sense for this scenario.
AB
Abel
1 year ago
Yes, Kafka is a great choice for handling asynchronous messages from one producer to multiple consumers.
LE
Leah
1 year ago
I think Apache Kafka is the right tool for this.
RI
Rima
2 years ago
C) Apache Kafka sounds like the right tool for the job. It's designed for handling high-throughput, low-latency, and fault-tolerant distribution of data across multiple consumers.
MA
Maurine
2 years ago
I'm not sure, but I think Apache Tomcat is also used for handling multiple consumers.
MI
Micheline
2 years ago
I agree with Lachelle, Apache Kafka is designed for handling asynchronous messages to multiple consumers.
LA
Lachelle
2 years ago
I think we should use Apache Kafka for that.