Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Confluent Exam CCDAK Topic 1 Question 39 Discussion

Actual exam question for Confluent's CCDAK exam
Question #: 39
Topic #: 1
[All CCDAK Questions]

An ecommerce wesbite sells some custom made goods. What's the natural way of modeling this data in Kafka streams?

Show Suggested Answer Hide Answer
Suggested Answer: C

JDBC connector allows one task per table.


Contribute your Thoughts:

Afton
1 months ago
I'll take 'Things I Don't Want to See in My Kafka Cluster' for 500, Alex. A purchase stream? What is this, Black Friday at Walmart?
upvoted 0 times
Sommer
2 days ago
C) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Stephaine
4 days ago
B) Purchase as stream, Product as table, Customer as table
upvoted 0 times
...
Nell
14 days ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Georgene
2 months ago
Option C is the only one that makes sense to me. I mean, who wants to be on the receiving end of a 'purchase stream'? Sounds like a recipe for a data firehose.
upvoted 0 times
...
Ngoc
2 months ago
I was totally going to choose option A, but then I realized that's just way too many streams. Maybe if we had a really complex use case, but for a simple ecommerce site, that seems overkill.
upvoted 0 times
Louvenia
6 days ago
D) Purchase as stream, Product as table, Customer as stream
upvoted 0 times
...
Carmen
8 days ago
I agree, having separate streams for each entity might be too much for a simple ecommerce site.
upvoted 0 times
...
Jaclyn
17 days ago
B) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Valene
1 months ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Geoffrey
2 months ago
I see your point, Lemuel. Having Purchase as stream and Product as table could provide more flexibility and scalability in the long run.
upvoted 0 times
...
Lemuel
2 months ago
I disagree, I believe B) Purchase as stream, Product as table, Customer as table makes more sense for this scenario.
upvoted 0 times
...
Paola
2 months ago
Option D seems interesting, but I'm not sure why we'd want the customer to be a stream. Wouldn't that make it harder to look up customer information?
upvoted 0 times
Dana
1 months ago
B) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Cristy
2 months ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Izetta
2 months ago
I think A) Purchase as stream, Product as stream, Customer as stream is the natural way to model this data.
upvoted 0 times
...
Silva
2 months ago
I think option B is the most natural way to model this data. Purchases are events, but products and customers are more like tables that we need to look up.
upvoted 0 times
Emeline
15 days ago
That's true, it provides a good balance between real-time processing and the ability to look up historical data.
upvoted 0 times
...
Elmer
19 days ago
But having purchases as a stream allows for real-time processing and analysis of the data.
upvoted 0 times
...
Merissa
1 months ago
I agree, having products and customers as tables makes it easier to query and join data.
upvoted 0 times
...
Denny
2 months ago
I think option B is the most natural way to model this data. Purchases are events, but products and customers are more like tables that we need to look up.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77