MENU
A customer needs to test a database schema migration. Which approach should an Architect recommend?
Suggested Answer: 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
39 comments · newest first
SH
Shawana
11 months ago
B seems like a solid choice if you're using Heroku.
RE
Reynalda
11 months ago
Wait, can you really fork a production database? Sounds complicated.
AR
Ardella
12 months ago
Definitely not D! Maintenance mode is a hassle.
ED
Edelmira
12 months ago
I think A could work too, but it might be risky.
EL
Elenora
1 year ago
Option C is the safest way to test migrations without affecting production.
RU
Rusty
1 year 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.
MI
Minna
1 year ago
Detaching the Heroku Postgres add-on sounds familiar, but I can't recall if that would allow for proper testing without downtime.
RE
Rebeca
1 year 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.
BR
Broderick
1 year 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.
AN
Annelle
1 year 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.
NO
Norah
1 year 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.
HE
Herminia
1 year 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.
CI
Ciara
1 year 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.
ES
Estrella
1 year 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.
CH
Chantay
1 year ago
Fork the production database? That's like trying to defuse a bomb while it's still ticking!
JO
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.
TW
Twanna
1 year ago
Detaching the Heroku Postgres add-on seems like a risky move, I'd stick with the follower database.
NE
Nelida
1 year ago
I think forking the production database is also a good option to test without affecting the live data.
WA
Walton
1 year ago
I agree, it's a safe approach to ensure the migration works smoothly.
ST
Stevie
1 year ago
A follower database? Sounds like a great way to test without disrupting the live system.
DE
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.
DO
Dortha
1 year ago
I agree, keeping the app running while testing the migration is important
JU
Julianna
1 year ago
C) Create a follower database, and run the migration and test against the follower database
PE
Percy
1 year ago
I agree, keeping the app running while testing the migration is important
CO
Cory
1 year ago
C) Create a follower database, and run the migration and test against the follower database
JO
Jonelle
1 year ago
A) Fork the production database, and run the migration and tests against the fork
SH
Shelia
1 year ago
A) Fork the production database, and run the migration and tests against the fork
LU
Luisa
2 years 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.
RY
Ryan
1 year ago
I think option C is the way to go for testing database schema migration.
FR
Franchesca
1 year ago
Yeah, creating a follower database for testing seems like a good approach.
RI
Richelle
1 year ago
I agree, forking the production database sounds risky. Option C seems like a safer choice.
SA
Salome
2 years 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.
DE
Desmond
1 year ago
Creating a follower database is a smart move for testing database schema migrations.
KA
Kallie
1 year ago
It's important to make sure the migration won't cause any issues in production.
NO
Noah
1 year ago
I agree, testing against a follower database is a good practice.
KI
Kirby
1 year ago
Option C is definitely the safest choice.
FE
Felicitas
2 years ago
That's a good point, but I still think option A is more practical in terms of isolating the testing environment.
HU
Hubert
2 years ago
I disagree, I believe option C is better as it ensures the testing is done on a replica of the production database.
FE
Felicitas
2 years ago
I think option A is the best approach because it allows for testing without affecting the production database.