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

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 5 Question 13 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect (Plat-Arch-206) exam
Question #: 13
Topic #: 5
[All Salesforce Certified Heroku Architect (Plat-Arch-206) Questions]

A client has a Heroku app that uses Apache Kafka on Heroku. They want to refactor the app into 2 distinct appsthat will both continue to use Kafka (because they probably don't have so much to do in their life). Based on this refactoring, what should an Architect recommend?

Show Suggested Answer Hide Answer
Suggested Answer: A, C, E

by Glen at Jan 09, 2023, 06:58 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Germaine
5 months ago
I’m surprised they want to split it up like that! Why not keep it together?
upvoted 0 times
...
Jarod
6 months ago
Option A could work too, but it might complicate things.
upvoted 0 times
...
Huey
6 months ago
Wait, why not just use the same Kafka add-on for both? Seems simpler.
upvoted 0 times
...
Deandrea
6 months ago
Agree, having one producer and one consumer is a solid approach.
upvoted 0 times
...
Delsie
6 months ago
I think option C makes the most sense!
upvoted 0 times
...
Pamella
6 months ago
If one app is a producer and the other is a consumer, that might streamline the process. I think option C could be the right approach here.
upvoted 0 times
...
Kanisha
6 months ago
I’m a bit confused about whether both apps can share the same Kafka add-on. I feel like option B could work, but I’m not entirely sure.
upvoted 0 times
...
Lashawnda
6 months ago
I think I saw a similar question where we had to decide how to manage Kafka topics between multiple apps. It feels like option A makes sense for that.
upvoted 0 times
...
Annelle
7 months ago
I remember something about ensuring that apps have distinct roles when using Kafka, but I'm not sure if that means they should consume different topics or not.
upvoted 0 times
...
Horace
7 months ago
This question seems a bit confusing. I'm not sure if it's asking about the duration of the certification or something else.
upvoted 0 times
...
Mammie
7 months ago
This is a tricky one. There are a few different ways a broker could handle a non-payment, so I'll need to really focus on the nuances of each option to pick the best answer.
upvoted 0 times
...
Bobbye
11 months ago
I bet the client wishes they had fewer hobbies and more time to work on this app. Option C is the way to go - let one app be the boss, and the other can be the worker bee.
upvoted 0 times
...
Gearldine
11 months ago
Option A sounds like a good way to keep the apps isolated, but I'm not sure how practical it is. Wouldn't that require careful coordination of the Kafka topics? Maybe I'm just lazy, but Option C seems like the path of least resistance.
upvoted 0 times
...
Bernardo
11 months ago
Hmm, Option D seems like a lot of unnecessary work. Why create a new Kafka add-on when the existing one can be shared? I'd go with Option B and save myself the hassle.
upvoted 0 times
Nancey
9 months ago
True, but ensuring that the apps consume mutually exclusive sets of Kafka topics is also important for scalability.
upvoted 0 times
...
Daniel
9 months ago
That's a good point, but sharing the existing add-on could save time and resources.
upvoted 0 times
...
Lilli
10 months ago
But wouldn't it be better to have separate Kafka add-ons for each app to avoid any potential conflicts?
upvoted 0 times
...
Stephaine
11 months ago
I agree, Option B seems like the most efficient choice.
upvoted 0 times
...
...
Ivan
12 months ago
I think Option B is the way to go. Attaching the existing Kafka add-on to both apps will make the migration easier and ensure they can still communicate with the same Kafka cluster.
upvoted 0 times
Carmen
11 months ago
That's a good point. Maybe Option A would be a better choice then.
upvoted 0 times
...
Corrina
11 months ago
But wouldn't it be better to have them consume different Kafka topics to avoid any conflicts?
upvoted 0 times
...
Janella
11 months ago
I agree, Option B seems like the most straightforward solution.
upvoted 0 times
...
...
Patti
1 year ago
But wouldn't it be easier to just attach the existing Kafka add-on to both apps?
upvoted 0 times
...
Simona
1 year ago
Option C makes the most sense to me. Designating one app as a producer and the other as a consumer will keep the responsibilities separate and maintain the benefits of using Kafka.
upvoted 0 times
Lizbeth
11 months ago
Ensuring that the apps consume mutually exclusive sets of Kafka topics could help prevent any potential conflicts in data processing.
upvoted 0 times
...
France
11 months ago
I think attaching the existing Kafka add-on to both apps could also work well to ensure they both have access to the necessary data streams.
upvoted 0 times
...
Candida
11 months ago
I agree, it's important to maintain separation of concerns when refactoring the app.
upvoted 0 times
...
Theron
12 months ago
Option C makes the most sense to me. Designating one app as a producer and the other as a consumer will keep the responsibilities separate and maintain the benefits of using Kafka.
upvoted 0 times
...
...
Stevie
1 year ago
I agree with Nieves. It will help in maintaining separation of concerns between the two apps.
upvoted 0 times
...
Nieves
1 year ago
I think we should ensure that the apps consume mutually exclusive sets of Kafka topics.
upvoted 0 times
...

Save Cancel