Salesforce Exam Heroku Architect Topic 5 Question 13 Discussion

Actual exam question for Salesforce's Heroku Architect exam

Question #: 13
Topic #: 5

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?

AEnsure that the apps consume mutually excliusive sets of Kafka topics

BAttach the existing Kafka add-on to both apps

CDesignate one app as a producer and the other as a consumer

DAttach the existing Kafka add-on to one app and attach a new Kafka add-on to the other app

Show Suggested Answer

Suggested Answer: A, C, E

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

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Bobbye

23 days 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

25 days 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

25 days 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

Stephaine

11 days ago

I agree, Option B seems like the most efficient choice.

upvoted 0 times

...

Ivan

1 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

19 days ago

That's a good point. Maybe Option A would be a better choice then.

upvoted 0 times

...

Corrina

21 days ago

But wouldn't it be better to have them consume different Kafka topics to avoid any conflicts?

upvoted 0 times

...

Janella

1 months ago

I agree, Option B seems like the most straightforward solution.

upvoted 0 times

...

Patti

2 months ago

But wouldn't it be easier to just attach the existing Kafka add-on to both apps?

upvoted 0 times

...

Simona

2 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

Lizbeth

13 days 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

15 days 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

27 days ago

I agree, it's important to maintain separation of concerns when refactoring the app.

upvoted 0 times

...

Theron

1 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

2 months ago

I agree with Nieves. It will help in maintaining separation of concerns between the two apps.

upvoted 0 times

...

Nieves

2 months ago

I think we should ensure that the apps consume mutually exclusive sets of Kafka topics.

upvoted 0 times

...