Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Confluent CCDAK Exam - Topic 1 Question 39 Discussion

An ecommerce wesbite sells some custom made goods. What's the natural way of modeling this data in Kafka streams?
C) Purchase as table, Product as table, Customer as table
A) Purchase as stream, Product as stream, Customer as stream
B) Purchase as stream, Product as table, Customer as table
D) Purchase as stream, Product as table, Customer as stream

Confluent CCDAK Exam - 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.


by Minna at Jul 29, 2023, 03:25 AM

Limited Time Offer

25%

Off

Get Premium CCDAK Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lacey
8 months ago
Not sure about this, can someone explain why B is better?
upvoted 0 times
...
Denny
8 months ago
D could work too, but I lean towards B.
upvoted 0 times
...
Justine
8 months ago
Wait, why would you use a table for Product? Seems off.
upvoted 0 times
...
Providencia
8 months ago
Totally agree, B is the way to go!
upvoted 0 times
...
Tiffiny
9 months ago
I think B makes the most sense for this scenario.
upvoted 0 times
...
Isidra
9 months ago
I feel like option B might be right, but I'm confused about whether customers should be streams or tables.
upvoted 0 times
...
Daniel
9 months ago
I practiced a similar question, and I think having customers as streams makes sense because they can change over time.
upvoted 0 times
...
Herminia
9 months ago
I'm not entirely sure, but I think products should be modeled as tables since they have a fixed set of attributes.
upvoted 0 times
...
Theron
9 months ago
I remember we discussed that purchases are usually events, so they might be better as a stream.
upvoted 0 times
...
Dion
9 months ago
Ah, I remember this from the lecture! I'm pretty sure the answer has to do with the board type, but I can't recall the specifics. Gotta focus and think this through.
upvoted 0 times
...
Luis
9 months ago
Okay, I think the key here is to look for any faults or health issues related to the EPG. That might give me a clue as to what happened and who was involved.
upvoted 0 times
...
Jamie
9 months ago
I'm feeling pretty confident about this one. The file blocking profile is definitely the way to go to prevent users from downloading malicious files, rather than just blocking all web access.
upvoted 0 times
...
Tawna
10 months ago
This looks like a straightforward question about IP filters on the Nokia 7750 SR. I should be able to handle this.
upvoted 0 times
...
Afton
1 year 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
1 year ago
C) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Stephaine
1 year ago
B) Purchase as stream, Product as table, Customer as table
upvoted 0 times
...
Nell
1 year ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Georgene
1 year 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
1 year 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
1 year ago
D) Purchase as stream, Product as table, Customer as stream
upvoted 0 times
...
Carmen
1 year ago
I agree, having separate streams for each entity might be too much for a simple ecommerce site.
upvoted 0 times
...
Jaclyn
1 year ago
B) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Valene
1 year ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Geoffrey
1 year 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
1 year 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
1 year 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 year ago
B) Purchase as table, Product as table, Customer as table
upvoted 0 times
...
Cristy
1 year ago
A) Purchase as stream, Product as stream, Customer as stream
upvoted 0 times
...
...
Izetta
1 year 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
1 year 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
1 year 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
1 year ago
But having purchases as a stream allows for real-time processing and analysis of the data.
upvoted 0 times
...
Merissa
1 year ago
I agree, having products and customers as tables makes it easier to query and join data.
upvoted 0 times
...
Denny
1 year 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