MENU
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?
Suggested Answer: A, C, E
Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
RO
Roosevelt
11 months ago
Good point about Internal Routing, but what about the DNS part?
AS
Ashleigh
11 months ago
I disagree, Private Space VPN Connections might be overkill for this.
RO
Romana
12 months ago
Wait, can you really block public access like that? Sounds tricky.
GE
Geraldo
12 months ago
I think Heroku Internal Routing is the way to go too.
KA
Karl
1 year ago
Definitely need Private Spaces DNS Service Discovery for that!
BL
Blondell
1 year ago
I don't think Apache Kafka is related to securing access; it seems more focused on messaging rather than access control.
GE
Gerald
1 year ago
I practiced a similar question, and I feel like Private Space VPN Connections might be relevant, but I can't recall the specifics.
GI
Giuseppe
1 year ago
I think Heroku Internal Routing could be a good option since it helps with communication between apps without exposing them publicly.
FI
Filiberto
1 year ago
I remember something about Private Spaces being used to isolate apps, but I'm not sure if that's the right choice here.
RA
Rasheeda
1 year 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.
AR
Art
1 year 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.
CL
Claribel
1 year 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.
SO
Son
1 year 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.
RE
Ressie
1 year 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'!
TA
Tabetha
1 year ago
Agreed, A and B would help UC keep their back-end application private.
TR
Trina
1 year ago
Definitely, those options seem like the best choice for securing the back-end.
SA
Salena
1 year ago
I think you're right, A and B sound like the way to go.
VI
Vincent
2 years 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!
RO
Rose
1 year ago
Let's not overcomplicate things, keeping it simple with Private Spaces is the most secure choice.
MY
Myrtie
1 year ago
Private Space VPN Connections and DNS Service Discovery are the best options for preventing public access.
WA
Walker
1 year ago
I agree, Private Spaces are definitely the way to go for securing the back-end.
DU
Dulce
2 years 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.
FR
Fredric
1 year ago
Private Spaces DNS Service Discovery could also be a good option to restrict access to the back-end application.
HO
Hortencia
1 year ago
I think Private Space VPN Connections would be a good choice to prevent public access.
HE
Helga
1 year ago
I agree, private spaces would definitely help secure the back-end application.
DO
Domitila
2 years 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.
VI
Victor
2 years 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.
DA
Dallas
1 year ago
Yes, those options would provide the necessary security measures to prevent public access to the back-end application.
FE
Felix
1 year ago
I agree, using Private Space VPN Connections and Private Spaces DNS Service Discovery would definitely help secure the back-end app.
TE
Temeka
2 years ago
I'm not sure about option B) Private Spaces DNS Service Discovery. Can someone explain how it would help prevent public access?
MA
Marylin
2 years ago
I agree with Wei. Private Space VPN Connections will ensure our back-end application is secure.
WE
Wei
2 years ago
I think we should go with option A) Private Space VPN Connections to prevent public access.