MENU
According to the Twelve-Factor methodology, which best practice helps minimizethe gap between development and production?
Suggested Answer: A, C, E
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
33 comments · newest first
VA
Valentin
12 months ago
Wait, are we really sure A is the best? Seems too simple.
ED
Edison
12 months ago
D is crucial too, but I agree with A overall.
PO
Portia
12 months ago
C sounds good, but isn't it a bit risky?
JU
Jutta
1 year ago
I think B is more important for debugging.
ER
Erasmo
1 year ago
A is definitely the right choice! Same services make life easier.
TH
Theodora
1 year ago
I keep mixing up A and C. I know backing services are important, but long-running tasks also seem relevant to production.
OR
Oretha
1 year ago
I practiced a question similar to this, and I feel like D was emphasized a lot in our discussions. Fast startup times are crucial.
TE
Tennie
1 year ago
I'm not entirely sure, but I remember something about logging being important. Maybe it's B?
DE
Desirae
1 year ago
I think it's A, using the same backing services. It makes sense to keep things consistent across environments.
HA
Harrison
1 year ago
Hmm, I'm a bit unsure about this one. Linear programming seems like it could be related to a few different project selection criteria. I'll have to think it through carefully.
GW
Gwen
1 year ago
This looks like a straightforward alphabetical sorting question. I'll just compare the first letters of each name and select the one that would come first in descending order.
SH
Shanda
1 year ago
Hmm, I'm a bit unsure about this one. I'll have to think it through carefully before answering.
ST
Stanton
1 year ago
Option A, all the way! Using the same backing services? That's like wearing the same clothes to work and home - it just makes sense!
SA
Sanda
1 year ago
B is the way to go. Configuring logging to write to stdout is a no-brainer. Who needs fancy logging setups when you can just pipe everything to the terminal?
GW
Gwen
1 year ago
Haha, option C is my pick! Executing long-running tasks as background processes? That's just asking for trouble. Imagine a production issue caused by a runaway process!
ME
Merissa
1 year ago
D) Writing processes that are fast to start up and gracefully shut down
PE
Percy
1 year ago
B) Configuring application logging to write stdout.
PA
Paul
1 year ago
A) Using the same backing services in all of an application's environments.
BR
Brandon
2 years ago
Option D seems like the right choice to me. Processes that start up and shut down quickly can help with reliability and ease of deployment.
DE
Devon
1 year ago
That's true, consistency in backing services can make it easier to ensure that the application behaves the same way in different environments.
CH
Charolette
1 year ago
Using the same backing services in all environments can also help minimize the gap between development and production.
ZI
Zita
1 year ago
I agree, having fast startup and shutdown processes can definitely streamline the deployment process.
IS
Isadora
1 year ago
Option D seems like the right choice to me. Processes that start up and shut down quickly can help with reliability and ease of deployment.
GE
Genevive
1 year ago
Executing long-running tasks as background processes can help improve performance and scalability.
RO
Rosita
1 year ago
Configuring application logging to write stdout can make it easier to monitor and troubleshoot.
DE
Della
1 year ago
Using the same backing services in all environments is also important for consistency.
EL
Eloisa
1 year ago
I agree, having processes that start up and shut down quickly can definitely help with deployment.
SH
Shonda
2 years ago
I think option A is the best practice to minimize the gap between development and production. Using the same backing services across all environments ensures consistency and reduces potential issues.
CH
Charisse
1 year ago
I think option D is also important, having processes that start up and shut down gracefully can help with deployment.
ST
Stefany
1 year ago
I agree, using the same backing services in all environments is key for consistency.
TR
Trevor
2 years ago
I'm not sure, but I think D) Writing processes that are fast to start up and gracefully shut down could also be a good practice.
LA
Lakeesha
2 years ago
I agree with Terrilyn, using the same backing services can definitely help minimize the gap between development and production.
TE
Terrilyn
2 years ago
I think the answer is A) Using the same backing services in all of an application's environments.