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 Certified Heroku Architect (Plat-Arch-206) Exam - Topic 1 Question 43 Discussion

A customer needs to test a database schema migration. Which approach should an Architect recommend?
D) Place the app into maintenance mode, and then perform the tests
A) Fork the production database, and run the migration and tests against the fork
B) Detach the Heroku Postgres add-on. and run the migration and tests against the database.
C) Create a follower database, and run the migration and test against the follower database

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 1 Question 43 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect (Plat-Arch-206) exam
Question #: 43
Topic #: 1
[All Salesforce Certified Heroku Architect (Plat-Arch-206) 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 Salesforce Certified Heroku Architect (Plat-Arch-206) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Shawana
9 months ago
B seems like a solid choice if you're using Heroku.
upvoted 0 times
...
Reynalda
10 months ago
Wait, can you really fork a production database? Sounds complicated.
upvoted 0 times
...
Ardella
10 months ago
Definitely not D! Maintenance mode is a hassle.
upvoted 0 times
...
Edelmira
10 months ago
I think A could work too, but it might be risky.
upvoted 0 times
...
Elenora
10 months ago
Option C is the safest way to test migrations without affecting production.
upvoted 0 times
...
Rusty
10 months ago
Placing the app into maintenance mode seems risky; I feel like it could lead to user frustration if something goes wrong during the tests.
upvoted 0 times
...
Minna
11 months ago
Detaching the Heroku Postgres add-on sounds familiar, but I can't recall if that would allow for proper testing without downtime.
upvoted 0 times
...
Rebeca
11 months ago
I remember a practice question about using a follower database for testing migrations. It seems like a safer approach since it wouldn't impact the main database.
upvoted 0 times
...
Broderick
11 months ago
I think forking the production database could be a good option, but I'm not entirely sure how that would affect the data integrity during testing.
upvoted 0 times
...
Annelle
11 months ago
Option D is definitely not the way to go here. Putting the app into maintenance mode just to test a database migration seems like overkill. I'm leaning towards A or C as the best approaches.
upvoted 0 times
...
Norah
11 months ago
Hmm, I'm a bit unsure about this one. I'm trying to decide between A and C. Forking the production database or creating a follower database both seem like reasonable options. I'll need to think it through a bit more.
upvoted 0 times
...
Herminia
11 months ago
This seems like a straightforward question about database migration testing. I think I'll go with option C - creating a follower database and testing against that. It seems like the safest approach to avoid disrupting the production environment.
upvoted 0 times
...
Ciara
11 months ago
Ah, this is a good one. I think I'll go with option A - forking the production database. That way, I can test the migration without impacting the live system. It's a bit more work, but it's the safest option in my opinion.
upvoted 0 times
...
Estrella
11 months ago
I'm a little confused by the options here. Daemon Set, Replica Set, and Deployment all sound like they could potentially work. I'll have to review the differences between them to make sure I pick the right one.
upvoted 0 times
...
Chantay
1 year ago
Fork the production database? That's like trying to defuse a bomb while it's still ticking!
upvoted 0 times
...
Jolene
1 year 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
Twanna
1 year ago
Detaching the Heroku Postgres add-on seems like a risky move, I'd stick with the follower database.
upvoted 0 times
...
Nelida
1 year ago
I think forking the production database is also a good option to test without affecting the live data.
upvoted 0 times
...
Walton
1 year ago
I agree, it's a safe approach to ensure the migration works smoothly.
upvoted 0 times
...
Stevie
1 year ago
A follower database? Sounds like a great way to test without disrupting the live system.
upvoted 0 times
...
...
Desmond
1 year 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
1 year ago
I agree, keeping the app running while testing the migration is important
upvoted 0 times
...
Julianna
1 year ago
C) Create a follower database, and run the migration and test against the follower database
upvoted 0 times
...
Percy
1 year ago
I agree, keeping the app running while testing the migration is important
upvoted 0 times
...
Cory
1 year ago
C) Create a follower database, and run the migration and test against the follower database
upvoted 0 times
...
Jonelle
1 year ago
A) Fork the production database, and run the migration and tests against the fork
upvoted 0 times
...
Shelia
1 year ago
A) Fork the production database, and run the migration and tests against the fork
upvoted 0 times
...
...
Luisa
1 year 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
1 year ago
I think option C is the way to go for testing database schema migration.
upvoted 0 times
...
Franchesca
1 year ago
Yeah, creating a follower database for testing seems like a good approach.
upvoted 0 times
...
Richelle
1 year ago
I agree, forking the production database sounds risky. Option C seems like a safer choice.
upvoted 0 times
...
...
Salome
1 year 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
1 year ago
Creating a follower database is a smart move for testing database schema migrations.
upvoted 0 times
...
Kallie
1 year ago
It's important to make sure the migration won't cause any issues in production.
upvoted 0 times
...
Noah
1 year ago
I agree, testing against a follower database is a good practice.
upvoted 0 times
...
Kirby
1 year ago
Option C is definitely the safest choice.
upvoted 0 times
...
...
Felicitas
1 year 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
1 year 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
1 year ago
I think option A is the best approach because it allows for testing without affecting the production database.
upvoted 0 times
...

Save Cancel