New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 1 Question 55 Discussion

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

Universal Containers (UC) has a front-end web application and a back-end service application running on Heroku. The applications are running in the Common Runtime. Now, UC wants to prevent any public access to the back-end application. Which two Heroku features should an Architect propose?

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

Contribute your Thoughts:

0/2000 characters
Roosevelt
3 months ago
Good point about Internal Routing, but what about the DNS part?
upvoted 0 times
...
Ashleigh
3 months ago
I disagree, Private Space VPN Connections might be overkill for this.
upvoted 0 times
...
Romana
3 months ago
Wait, can you really block public access like that? Sounds tricky.
upvoted 0 times
...
Geraldo
4 months ago
I think Heroku Internal Routing is the way to go too.
upvoted 0 times
...
Karl
4 months ago
Definitely need Private Spaces DNS Service Discovery for that!
upvoted 0 times
...
Blondell
4 months ago
I don't think Apache Kafka is related to securing access; it seems more focused on messaging rather than access control.
upvoted 0 times
...
Gerald
4 months ago
I practiced a similar question, and I feel like Private Space VPN Connections might be relevant, but I can't recall the specifics.
upvoted 0 times
...
Giuseppe
4 months ago
I think Heroku Internal Routing could be a good option since it helps with communication between apps without exposing them publicly.
upvoted 0 times
...
Filiberto
5 months ago
I remember something about Private Spaces being used to isolate apps, but I'm not sure if that's the right choice here.
upvoted 0 times
...
Rasheeda
5 months ago
I'm a little confused by the wording of this question. What exactly does "prevent any public access" mean? Does that mean only allowing access from the front-end application, or completely blocking all external access? I'll need to think about the specific requirements before answering.
upvoted 0 times
...
Art
5 months ago
Okay, I've got a strategy here. Private Space VPN Connections and Private Spaces DNS Service Discovery both sound like they could be used to isolate the back-end and restrict public access. I'll go with those two options.
upvoted 0 times
...
Claribel
5 months ago
Hmm, I'm a bit unsure about this one. There are a few Heroku features mentioned, but I'm not sure which two would be the best options to prevent public access to the back-end. I'll need to think this through carefully.
upvoted 0 times
...
Son
5 months ago
This seems like a straightforward question about securing a back-end application on Heroku. I think the key is to look for Heroku features that can restrict public access to the back-end.
upvoted 0 times
...
Ressie
10 months ago
I'd say the correct answer is a classic combo of A and B. Heroku's got your back(end) when it comes to keeping things private. Time to put the 'secret' in 'secret sauce'!
upvoted 0 times
Tabetha
8 months ago
Agreed, A and B would help UC keep their back-end application private.
upvoted 0 times
...
Trina
8 months ago
Definitely, those options seem like the best choice for securing the back-end.
upvoted 0 times
...
Salena
8 months ago
I think you're right, A and B sound like the way to go.
upvoted 0 times
...
...
Vincent
10 months ago
Ah, the age-old question of how to hide your back-end from the world. I vote for A and B - Private Spaces are the way to go, no need to get fancy with Kafka or anything. Keep it simple, keep it secure!
upvoted 0 times
Rose
8 months ago
Let's not overcomplicate things, keeping it simple with Private Spaces is the most secure choice.
upvoted 0 times
...
Myrtie
9 months ago
Private Space VPN Connections and DNS Service Discovery are the best options for preventing public access.
upvoted 0 times
...
Walker
9 months ago
I agree, Private Spaces are definitely the way to go for securing the back-end.
upvoted 0 times
...
...
Dulce
10 months ago
Internal Routing sounds interesting, but I'm not sure if it's the best choice here. I'd go with the private spaces options to really lock down that back-end app.
upvoted 0 times
Fredric
9 months ago
Private Spaces DNS Service Discovery could also be a good option to restrict access to the back-end application.
upvoted 0 times
...
Hortencia
9 months ago
I think Private Space VPN Connections would be a good choice to prevent public access.
upvoted 0 times
...
Helga
9 months ago
I agree, private spaces would definitely help secure the back-end application.
upvoted 0 times
...
...
Domitila
10 months ago
Hmm, I'm not sure about Apache Kafka on Heroku. Isn't that more for data streaming? I'd stick with the Heroku-specific features like private spaces and internal routing.
upvoted 0 times
...
Victor
11 months ago
I think options A and B are the way to go. Private Space VPN Connections and Private Spaces DNS Service Discovery seem like the perfect solutions to restrict public access to the back-end app.
upvoted 0 times
Dallas
10 months ago
Yes, those options would provide the necessary security measures to prevent public access to the back-end application.
upvoted 0 times
...
Felix
10 months ago
I agree, using Private Space VPN Connections and Private Spaces DNS Service Discovery would definitely help secure the back-end app.
upvoted 0 times
...
...
Temeka
11 months ago
I'm not sure about option B) Private Spaces DNS Service Discovery. Can someone explain how it would help prevent public access?
upvoted 0 times
...
Marylin
11 months ago
I agree with Wei. Private Space VPN Connections will ensure our back-end application is secure.
upvoted 0 times
...
Wei
11 months ago
I think we should go with option A) Private Space VPN Connections to prevent public access.
upvoted 0 times
...

Save Cancel