MENU
A client has a Heroku Postgres database add-on attached to a production application. The client now wants to access the database from another application that they use to perform administrative tasks. What should an Architect recommend in this scenario?
Suggested Answer: B, D
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
40 comments · newest first
RE
Rebeca
11 months ago
Option B could be a good alternative too, though.
JO
Johana
11 months ago
Isn't forking the database a bit risky?
AM
Amina
12 months ago
Wait, can you really attach the same add-on to multiple apps?
TO
Tomas
12 months ago
Agree, attaching the add-on makes it easier!
MO
Mose
1 year ago
I think option D is the best choice here.
FR
Frankie
1 year ago
I feel like attaching the same add-on to the admin app could be the simplest solution, but I wonder about the implications for access control.
HE
Hector
1 year ago
Creating a fork sounds familiar, but I feel like it might complicate things unnecessarily.
VI
Vince
1 year ago
I think attaching the database to a proxy could be a good option, but I can't recall the exact benefits of that approach.
CR
Crista
1 year ago
I remember something about connection URLs, but I'm not sure if just copying it is secure enough for admin tasks.
WI
Wilda
1 year ago
Attaching the same Heroku Postgres add-on to the administrative application seems like the most direct solution, but I want to make sure I understand the implications before recommending that.
SA
Santos
1 year ago
Creating a fork of the database and attaching it to the administrative app sounds like it could work, but I'm not sure if that's the best way to go about it.
VE
Velda
1 year ago
Hmm, I'm not sure about that. Wouldn't attaching the database to a separate application that acts as a proxy be more secure?
PE
Pearlene
1 year ago
I think copying the database connection URL and adding it to the administrative app as a config var is the simplest and most straightforward approach.
JE
Jerilyn
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions "cascaded mode" which makes me wonder if there's some nuance I'm missing. I'll have to think this through carefully.
LE
Lenna
1 year ago
Okay, I think I've got this. The key here is that the question is asking about what should be disclosed to senior management, not just the general results of the quality assessments. I'm leaning towards option D, as the qualifications and independence of the assessment team seem like important information to share with leadership.
TE
Teresita
1 year ago
Hmm, I'd say option C is the way to go. Developing a clear policy on machine learning use is crucial to set guidelines and ensure ethical practices from the start. That seems like the most proactive approach.
EM
Emmett
1 year ago
I bet the architect is going to recommend option A, because it's the most 'Ctrl+C, Ctrl+V' solution. Gotta love those easy fixes!
LA
Lasandra
1 year ago
Wait, why not just attach the same Heroku Postgres add-on to the administrative app? That way, they're using the same database, right? Option D is the way to go, in my opinion.
ME
Melissa
1 year ago
Creating a fork of the database and attaching it to the administrative application could also work, but it may require more maintenance in the long run.
ER
Ernestine
1 year ago
D) Attach the same Heroku Postgres add-on to the administrative application.
KA
Kassandra
1 year ago
Copying the database's connection URL and adding it as a config var to the administrative application would be a better approach to ensure data integrity.
JA
Jackie
1 year ago
C) Create a fork of the database and attach it to the administrative application.
JE
Jess
1 year ago
B) Attach the database to an application that acts as a database proxy.
DO
Dorian
1 year ago
A) Copy the database's connection URL and add it to the administrative application as a config var.
BE
Bernadine
1 year ago
Option D is not recommended because it could lead to data inconsistency between the production and administrative applications.
AN
Annelle
2 years ago
Oh, I like the idea of creating a fork! That way, the administrative app can have its own database without messing with the production one. Option C is my pick.
YV
Yvonne
1 year ago
Yes, creating a fork would definitely help in maintaining the integrity of the production database. Option C is a solid choice.
LE
Levi
1 year ago
I agree, it's important to keep the production database separate. Creating a fork seems like a safe option.
TA
Tayna
1 year ago
That's a good point! Having a separate database for the administrative app does sound like a good idea.
AR
Arminda
2 years ago
Hmm, I'm not sure about that. Wouldn't it be better to use a database proxy to keep things secure? Option B seems more robust to me.
YE
Yesenia
1 year ago
Yeah, I agree. Option B seems like the best choice in this scenario.
KA
Katlyn
1 year ago
I think using a database proxy is a good idea for security.
JO
Johana
2 years ago
I see both points. But I think option D could also work well, maintaining consistency.
BE
Bette
2 years ago
Option A is the way to go! It's the simplest and most straightforward solution. Just copy that connection URL and you're good to go.
CA
Carole
1 year ago
Yeah, copying the connection URL seems like the most practical solution in this scenario.
YO
Youlanda
1 year ago
I think I'll go with option A as well, seems like the most efficient choice.
KA
Katy
1 year ago
I agree, it's definitely the easiest way to access the database from another application.
DO
Donette
2 years ago
Option A is the way to go! It's the simplest and most straightforward solution. Just copy that connection URL and you're good to go.
MA
Marguerita
2 years ago
I disagree. I believe option B is better because it adds an extra layer of security.
ED
Edna
2 years ago
I think option A makes sense. It's simple and straightforward.