Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Heroku Architect Topic 1 Question 55 Discussion

Actual exam question for Salesforce's Heroku Architect exam
Question #: 55
Topic #: 1
[All Heroku Architect 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:

Ressie
1 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
Trina
1 days ago
Definitely, those options seem like the best choice for securing the back-end.
upvoted 0 times
...
Salena
3 days ago
I think you're right, A and B sound like the way to go.
upvoted 0 times
...
...
Vincent
1 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
3 days ago
Let's not overcomplicate things, keeping it simple with Private Spaces is the most secure choice.
upvoted 0 times
...
Myrtie
22 days ago
Private Space VPN Connections and DNS Service Discovery are the best options for preventing public access.
upvoted 0 times
...
Walker
1 months ago
I agree, Private Spaces are definitely the way to go for securing the back-end.
upvoted 0 times
...
...
Dulce
2 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
7 days 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 days ago
I think Private Space VPN Connections would be a good choice to prevent public access.
upvoted 0 times
...
Helga
16 days ago
I agree, private spaces would definitely help secure the back-end application.
upvoted 0 times
...
...
Domitila
2 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
2 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
1 months ago
Yes, those options would provide the necessary security measures to prevent public access to the back-end application.
upvoted 0 times
...
Felix
1 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
2 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
2 months ago
I agree with Wei. Private Space VPN Connections will ensure our back-end application is secure.
upvoted 0 times
...
Wei
2 months ago
I think we should go with option A) Private Space VPN Connections to prevent public access.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77