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 2 Question 73 Discussion

A client wants to create a scalable set of microservices that communicate with each other, where multiple microservices have a public REST API.Which architecture strategy allows this on Heroku?
C) Each microservice is a separate private space. The microservices communicate byusing DNS Service Discovery.
A) Each microservice is a separate Heroku app. The microservices communicate byusing Apache Kafka as a message bus.
B) Each microservice is a separate process type in a single Heroku app. The microservices communicate by using Redis as a message bus.
D) Each microservice is a separate process in a single Heroku app. The microservices communicate by using shared memory.

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 2 Question 73 Discussion

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

A client wants to create a scalable set of microservices that communicate with each other, where multiple microservices have a public REST API.

Which architecture strategy allows this on Heroku?

Show Suggested Answer Hide Answer
Suggested Answer: C

- httDs://devcenterheroku.com/artJcles/event-driven-microservices-with-aDache-kafka


by Ricarda at Apr 08, 2026, 06:13 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
Louisa
3 days ago
I agree with A. Microservices need to be independent.
upvoted 0 times
...
Ona
8 days ago
D seems too limiting. Shared memory isn't scalable.
upvoted 0 times
...
Otis
13 days ago
C sounds interesting, but DNS might complicate things.
upvoted 0 times
...
Matthew
18 days ago
I feel like B could work too. Redis is fast for communication.
upvoted 0 times
...
Telma
23 days ago
I think option A is the best. Kafka is great for scalability.
upvoted 0 times
...
Sheron
29 days ago
B is solid too. Redis can handle high loads well.
upvoted 0 times
...
Marnie
1 month ago
I feel like A gives the most flexibility for growth.
upvoted 0 times
...
Melodie
1 month ago
D seems limiting. Shared memory isn't ideal for microservices.
upvoted 0 times
...
Gerald
1 month ago
C sounds interesting, but DNS Service Discovery can be complex.
upvoted 0 times
...
Felix
2 months ago
I’m leaning towards B. Redis is simple and effective for communication.
upvoted 0 times
...
Michell
2 months ago
I think option A is the best. Kafka is great for scalability.
upvoted 0 times
...
Man
2 months ago
Wait, can microservices really communicate effectively with DNS Service Discovery?
upvoted 0 times
...
Stanton
2 months ago
D) seems outdated, shared memory isn't ideal for microservices.
upvoted 0 times
...
Yoko
2 months ago
C) sounds interesting, but is it really practical?
upvoted 0 times
...
Novella
4 months ago
I think B) is more efficient for smaller projects.
upvoted 0 times
...
Twana
4 months ago
A) is the best choice for scalability.
upvoted 0 times
...
Cherry
5 months ago
I’m a bit confused about option D; shared memory doesn’t seem right for microservices since they should be independent, right?
upvoted 0 times
...
Davida
5 months ago
I think we had a practice question about Heroku and microservices, and I might lean towards option C because DNS Service Discovery seems like a good way to manage multiple services.
upvoted 0 times
...
Tammi
5 months ago
I'm not entirely sure, but I feel like option B could work too since Redis is a common choice for message passing.
upvoted 0 times
...
Julian
5 months ago
I remember we discussed microservices in class, and I think option A sounds familiar since Kafka is often used for communication between services.
upvoted 0 times
...

Save Cancel