Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Heroku Architect Topic 1 Question 43 Discussion

Actual exam question for Salesforce's Heroku Architect exam
Question #: 43
Topic #: 1
[All Heroku Architect Questions]

A customer needs to test a database schema migration. Which approach should an Architect recommend?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Beth at Aug 08, 2024, 10:20 PM

Limited Time Offer

25%

Off

Get Premium Heroku Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Chantay
28 days ago
Fork the production database? That's like trying to defuse a bomb while it's still ticking!
upvoted 0 times
...
Jolene
30 days ago
A follower database? Sounds like a great way to test without disrupting the live system. I'm with Salome and Luisa on this one.
upvoted 0 times
Walton
21 hours ago
I agree, it's a safe approach to ensure the migration works smoothly.
upvoted 0 times
...
Stevie
4 days ago
A follower database? Sounds like a great way to test without disrupting the live system.
upvoted 0 times
...
...
Desmond
1 months ago
Option D is an interesting idea, but I'm not sure putting the app into maintenance mode is the best approach. I'd prefer to keep the app up and running if possible.
upvoted 0 times
Dortha
7 days ago
I agree, keeping the app running while testing the migration is important
upvoted 0 times
...
Julianna
10 days ago
C) Create a follower database, and run the migration and test against the follower database
upvoted 0 times
...
Percy
12 days ago
I agree, keeping the app running while testing the migration is important
upvoted 0 times
...
Cory
14 days ago
C) Create a follower database, and run the migration and test against the follower database
upvoted 0 times
...
Jonelle
17 days ago
A) Fork the production database, and run the migration and tests against the fork
upvoted 0 times
...
Shelia
22 days ago
A) Fork the production database, and run the migration and tests against the fork
upvoted 0 times
...
...
Luisa
2 months ago
Hmm, I'm not sure about forking the production database. That seems a bit risky to me. I'd go with option C as well.
upvoted 0 times
Ryan
17 days ago
I think option C is the way to go for testing database schema migration.
upvoted 0 times
...
Franchesca
22 days ago
Yeah, creating a follower database for testing seems like a good approach.
upvoted 0 times
...
Richelle
1 months ago
I agree, forking the production database sounds risky. Option C seems like a safer choice.
upvoted 0 times
...
...
Salome
2 months ago
I think option C is the way to go - creating a follower database and testing against that is a great way to ensure the migration won't break the production environment.
upvoted 0 times
Desmond
14 days ago
Creating a follower database is a smart move for testing database schema migrations.
upvoted 0 times
...
Kallie
15 days ago
It's important to make sure the migration won't cause any issues in production.
upvoted 0 times
...
Noah
27 days ago
I agree, testing against a follower database is a good practice.
upvoted 0 times
...
Kirby
1 months ago
Option C is definitely the safest choice.
upvoted 0 times
...
...
Felicitas
2 months ago
That's a good point, but I still think option A is more practical in terms of isolating the testing environment.
upvoted 0 times
...
Hubert
2 months ago
I disagree, I believe option C is better as it ensures the testing is done on a replica of the production database.
upvoted 0 times
...
Felicitas
2 months ago
I think option A is the best approach because it allows for testing without affecting the production database.
upvoted 0 times
...

Save Cancel