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 8 Question 25 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

0/2000 characters
Norah
3 months ago
D could work too, but it feels a bit overcomplicated for this case.
upvoted 0 times
...
Gladys
3 months ago
Surprised that modifying the buildpack is even an option! Sounds risky.
upvoted 0 times
...
Paris
3 months ago
Why not just convert it to Go? Option B seems simpler.
upvoted 0 times
...
Marylin
4 months ago
Agree with C! Running the script in the release phase makes sense.
upvoted 0 times
...
Blondell
4 months ago
I think option C is the best choice. It keeps things clean.
upvoted 0 times
...
Lawana
4 months ago
Defining different process types sounds familiar, but I can't recall if that would actually help with running the migrations before deployment.
upvoted 0 times
...
Margart
4 months 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.
upvoted 0 times
...
Ettie
4 months 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.
upvoted 0 times
...
Kenneth
5 months ago
I remember we discussed using buildpacks in class, but I'm not sure if modifying the Go buildpack is the best option.
upvoted 0 times
...
Francoise
5 months 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.
upvoted 0 times
...
Magdalene
5 months 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.
upvoted 0 times
...
Dong
5 months 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.
upvoted 0 times
...
Sarah
5 months 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.
upvoted 0 times
...
Marisha
5 months ago
This seems like a tricky one. I'll need to carefully consider the different options and think through the implications of each approach.
upvoted 0 times
...
Gaynell
5 months 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.
upvoted 0 times
...
Bethanie
5 months 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.
upvoted 0 times
...
Tonja
5 months 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.
upvoted 0 times
...
Gene
5 months 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.
upvoted 0 times
...
Nickolas
9 months 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!
upvoted 0 times
...
Jacki
9 months 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.
upvoted 0 times
...
Laura
10 months 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.
upvoted 0 times
Sharen
8 months ago
That sounds like a good idea. We can make sure the script runs at the right time without too much hassle.
upvoted 0 times
...
Eveline
8 months ago
C) Use both Go and Ruby language buildpacks, and run the Ruby script with release phase
upvoted 0 times
...
Yolando
9 months ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
upvoted 0 times
...
...
Elli
11 months 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.
upvoted 0 times
Lanie
9 months ago
C) Use both Go and Ruby language buildpacks, and run the Ruby script with release phase
upvoted 0 times
...
Aja
9 months ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
upvoted 0 times
...
Maryann
9 months ago
Converting the Ruby script to Go would be a lot of work, but it might be the best long-term solution.
upvoted 0 times
...
Gerry
10 months ago
A) Modify the Go buildpack to install Ruby, and run the script from the _profile
upvoted 0 times
...
...
Emelda
11 months 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.
upvoted 0 times
...
Johana
11 months ago
But option A allows for easier maintenance and management of dependencies.
upvoted 0 times
...
Rodney
11 months ago
I disagree, I believe option C is more efficient.
upvoted 0 times
...
Johana
11 months ago
I think option A is the best approach.
upvoted 0 times
...

Save Cancel