MENU
A client currently runs a Ruby script in aone-off dyno each time they deploy their Go application to Heroku. The development team wants the script to be executed before the application is deployed because it performs necessary database migrations. Which approach should an Architect recommend?
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
33 comments · newest first
NO
Norah
11 months ago
D could work too, but it feels a bit overcomplicated for this case.
GL
Gladys
11 months ago
Surprised that modifying the buildpack is even an option! Sounds risky.
PA
Paris
12 months ago
Why not just convert it to Go? Option B seems simpler.
MA
Marylin
12 months ago
Agree with C! Running the script in the release phase makes sense.
BL
Blondell
1 year ago
I think option C is the best choice. It keeps things clean.
LA
Lawana
1 year ago
Defining different process types sounds familiar, but I can't recall if that would actually help with running the migrations before deployment.
MA
Margart
1 year ago
I feel like using both buildpacks and running the Ruby script in the release phase is a solid approach, but I need to double-check how that works.
ET
Ettie
1 year ago
I think converting the Ruby script to Go could work, but it might be a lot of extra work if the script is complex.
KE
Kenneth
1 year ago
I remember we discussed using buildpacks in class, but I'm not sure if modifying the Go buildpack is the best option.
FR
Francoise
1 year ago
I'm a bit torn between the options, but I think using both the Go and Ruby buildpacks and running the script in the release phase could be a good solution.
MA
Magdalene
1 year ago
I feel pretty confident about this one. Converting the Ruby script to Go and running it on startup seems like the most straightforward approach.
DO
Dong
1 year ago
Okay, I think I've got a handle on this. I'll focus on options that integrate the Ruby script into the deployment process, rather than running it separately.
SA
Sarah
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to review the details of the Heroku buildpack and release process to determine the best solution.
MA
Marisha
1 year ago
This seems like a tricky one. I'll need to carefully consider the different options and think through the implications of each approach.
GA
Gaynell
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully examine the table layouts and the SQL statement to figure out the right answer.
BE
Bethanie
1 year ago
Hmm, I'm a bit unsure about this one. Azure has so many different services, it's hard to know which one would be the right choice for monitoring a virtual machine's availability. I'll have to think this through carefully.
TO
Tonja
1 year ago
Hmm, I'm a little unsure about this one. I'll need to carefully read through the answer choices and think about the key requirements for this type of referral fee.
GE
Gene
1 year ago
I'm leaning towards option C - catching the exceptions and retrying with exponential backoff. That way, we can keep trying to get the API data without impacting the rest of the UI. Plus, the question says the API data is less critical, so it's worth making a few extra attempts to get it.
NI
Nickolas
1 year ago
I'd just set the script to run on a cron job every minute. That way, it'll always be up-to-date, even if someone forgets to deploy!
JA
Jacki
1 year ago
Defining different process types for the script and the app in the Procfile sounds promising. That way, we can manage them separately without too much hassle.
LA
Laura
1 year ago
Using both buildpacks seems like the easiest way to go. That way, we can keep the Ruby script as-is and run it during the release phase.
SH
Sharen
1 year ago
That sounds like a good idea. We can make sure the script runs at the right time without too much hassle.
EV
Eveline
1 year ago
C) Use both Go and Ruby language buildpacks, and run the Ruby script with release phase
YO
Yolando
1 year ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
EL
Elli
2 years ago
Converting the Ruby script to Go makes sense, but that could be a lot of work. I'd prefer a simpler solution if possible.
LA
Lanie
1 year ago
C) Use both Go and Ruby language buildpacks, and run the Ruby script with release phase
AJ
Aja
1 year ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
MA
Maryann
1 year ago
Converting the Ruby script to Go would be a lot of work, but it might be the best long-term solution.
GE
Gerry
2 years ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
EM
Emelda
2 years ago
Option A looks like a good solution, but I'm not sure if modifying the Go buildpack is the best approach. It might be better to keep the languages separate.
JO
Johana
2 years ago
But option A allows for easier maintenance and management of dependencies.
RO
Rodney
2 years ago
I disagree, I believe option C is more efficient.
JO
Johana
2 years ago
I think option A is the best approach.