MENU
A client has a web application that persists data to a local JSON file. They are migrating the application to Heroku. In order for the application to conform to the Twelve-Factor methodology, what changes 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
29 comments · newest first
MA
Margo
11 months ago
Yeah, JSON files aren't reliable for production.
TA
Tarra
11 months ago
I thought Heroku apps should be stateless? Confused!
SH
Shawn
12 months ago
Wait, why not just use SQLite? Seems easier.
VI
Viva
12 months ago
Agreed, local files just won't cut it in the cloud.
ME
Melissa
12 months ago
Definitely need to switch to a database add-on for Heroku.
LO
Lonna
1 year ago
I recall something about using add-ons for persistence, so option A seems right, but I wonder if there are other considerations we missed.
FR
Francesco
1 year ago
I feel like we practiced a question about statelessness, and option D sounds familiar, but I don't think it’s practical for this scenario.
DE
Delila
1 year ago
I'm not entirely sure, but I think using SQLite might still keep some state, which goes against the Twelve-Factor principles.
SH
Shayne
1 year ago
I remember we discussed how Heroku apps should use a database instead of local files, so I think option A makes the most sense.
VE
Venita
1 year ago
This question seems straightforward. I think the answer is C - fewer replacement parts and long-life consumables.
KA
Katheryn
1 year ago
I'm a bit unsure on the best approach here. Should I use a parametric test like a t-test or a non-parametric test like the Wilcoxon rank-sum? I'll need to look at the data distribution first to decide.
BE
Bettyann
1 year ago
This looks like a straightforward array question. I'll carefully examine the image and options to determine the correct output.
CA
Carry
1 year ago
Option B? SQLite? In the cloud? That's like trying to fit a square peg in a round hole. Not a good idea at all.
KI
Kindra
1 year ago
C) The application should use at least 2 dynos to ensure that the JSON file is highly available.
TE
Tennie
1 year ago
A) The application should persist the data to a database add-on.
PA
Page
1 year ago
Haha, option C is classic 'overcomplicate everything' syndrome. Using multiple dynos to ensure availability of a local JSON file? That's overkill, my dude.
CA
Caprice
1 year ago
User 2
ME
Meghann
1 year ago
User 1
TO
Tom
2 years ago
I'm torn between A and D. Persisting data to a database makes sense, but a truly stateless app might be the most Twelve-Factor-y approach. I guess it depends on the specific requirements.
GA
Gayla
1 year ago
A) The application should persist the data to a database add-on.
MA
Matilda
1 year ago
It really depends on the specific requirements of the application.
LI
Lino
1 year ago
D) The application should be stateless and therefore not persist data at all.
HI
Hildegarde
1 year ago
A) The application should persist the data to a database add-on.
KR
Kris
2 years ago
Option A seems like the way to go. Persisting data to a local file isn't really cloud-friendly, and the Twelve-Factor methodology emphasizes using external services for things like data storage.
PR
Providencia
1 year ago
B) I agree, using a database add-on is the recommended approach for cloud environments.
SA
Santos
1 year ago
A) The application should persist the data to a database add-on.
JA
Janae
2 years ago
I'm not sure, but I think option D could also be a valid choice to conform to the Twelve-Factor methodology.
HA
Hannah
2 years ago
I agree with Mignon, persisting data to a database add-on is the best choice for scalability.
MI
Mignon
2 years ago
I think the Architect should recommend option A.