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 22 Discussion

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?
D) The application should be stateless and therefore not persist data at all.
A) The application should persist the data to a database add-on.
B) The application should persist the data to a local SQLite database.
C) The application should use at least 2 dynos to ensure that the JSON file is highly available.

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

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Luisa at Aug 06, 2023, 11:42 AM

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
Margo
8 months ago
Yeah, JSON files aren't reliable for production.
upvoted 0 times
...
Tarra
8 months ago
I thought Heroku apps should be stateless? Confused!
upvoted 0 times
...
Shawn
8 months ago
Wait, why not just use SQLite? Seems easier.
upvoted 0 times
...
Viva
9 months ago
Agreed, local files just won't cut it in the cloud.
upvoted 0 times
...
Melissa
9 months ago
Definitely need to switch to a database add-on for Heroku.
upvoted 0 times
...
Lonna
9 months 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.
upvoted 0 times
...
Francesco
9 months 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.
upvoted 0 times
...
Delila
9 months ago
I'm not entirely sure, but I think using SQLite might still keep some state, which goes against the Twelve-Factor principles.
upvoted 0 times
...
Shayne
10 months 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.
upvoted 0 times
...
Venita
10 months ago
This question seems straightforward. I think the answer is C - fewer replacement parts and long-life consumables.
upvoted 0 times
...
Katheryn
10 months 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.
upvoted 0 times
...
Bettyann
10 months ago
This looks like a straightforward array question. I'll carefully examine the image and options to determine the correct output.
upvoted 0 times
...
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.
upvoted 0 times
Kindra
1 year ago
C) The application should use at least 2 dynos to ensure that the JSON file is highly available.
upvoted 0 times
...
Tennie
1 year ago
A) The application should persist the data to a database add-on.
upvoted 0 times
...
...
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.
upvoted 0 times
Caprice
1 year ago
User 2
upvoted 0 times
...
Meghann
1 year ago
User 1
upvoted 0 times
...
...
Tom
1 year 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.
upvoted 0 times
Gayla
1 year ago
A) The application should persist the data to a database add-on.
upvoted 0 times
...
Matilda
1 year ago
It really depends on the specific requirements of the application.
upvoted 0 times
...
Lino
1 year ago
D) The application should be stateless and therefore not persist data at all.
upvoted 0 times
...
Hildegarde
1 year ago
A) The application should persist the data to a database add-on.
upvoted 0 times
...
...
Kris
1 year 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.
upvoted 0 times
Providencia
1 year ago
B) I agree, using a database add-on is the recommended approach for cloud environments.
upvoted 0 times
...
Santos
1 year ago
A) The application should persist the data to a database add-on.
upvoted 0 times
...
...
Janae
1 year ago
I'm not sure, but I think option D could also be a valid choice to conform to the Twelve-Factor methodology.
upvoted 0 times
...
Hannah
1 year ago
I agree with Mignon, persisting data to a database add-on is the best choice for scalability.
upvoted 0 times
...
Mignon
1 year ago
I think the Architect should recommend option A.
upvoted 0 times
...

Save Cancel