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 4 Question 15 Discussion

According to the Twelve-Factor methodology, which best practice helps minimizethe gap between development and production?
A) Using the same backing services in all of an application's environments. and C) Executing long-running tasks as background processes.
B) Configuring application logging to write stdout.
D) Writing processes that are fast to start up and gracefully shut down

Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 4 Question 15 Discussion

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

According to the Twelve-Factor methodology, which best practice helps minimizethe gap between development and production?

Show Suggested Answer Hide Answer
Suggested Answer: A, C, E

by Caprice at Feb 27, 2023, 12:18 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
Valentin
8 months ago
Wait, are we really sure A is the best? Seems too simple.
upvoted 0 times
...
Edison
9 months ago
D is crucial too, but I agree with A overall.
upvoted 0 times
...
Portia
9 months ago
C sounds good, but isn't it a bit risky?
upvoted 0 times
...
Jutta
9 months ago
I think B is more important for debugging.
upvoted 0 times
...
Erasmo
9 months ago
A is definitely the right choice! Same services make life easier.
upvoted 0 times
...
Theodora
9 months ago
I keep mixing up A and C. I know backing services are important, but long-running tasks also seem relevant to production.
upvoted 0 times
...
Oretha
9 months 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.
upvoted 0 times
...
Tennie
9 months ago
I'm not entirely sure, but I remember something about logging being important. Maybe it's B?
upvoted 0 times
...
Desirae
10 months ago
I think it's A, using the same backing services. It makes sense to keep things consistent across environments.
upvoted 0 times
...
Harrison
10 months 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.
upvoted 0 times
...
Gwen
10 months 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.
upvoted 0 times
...
Shanda
10 months ago
Hmm, I'm a bit unsure about this one. I'll have to think it through carefully before answering.
upvoted 0 times
...
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!
upvoted 0 times
...
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?
upvoted 0 times
...
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!
upvoted 0 times
Merissa
1 year ago
D) Writing processes that are fast to start up and gracefully shut down
upvoted 0 times
...
Percy
1 year ago
B) Configuring application logging to write stdout.
upvoted 0 times
...
Paul
1 year ago
A) Using the same backing services in all of an application's environments.
upvoted 0 times
...
...
Brandon
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.
upvoted 0 times
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.
upvoted 0 times
...
Charolette
1 year ago
Using the same backing services in all environments can also help minimize the gap between development and production.
upvoted 0 times
...
Zita
1 year ago
I agree, having fast startup and shutdown processes can definitely streamline the deployment process.
upvoted 0 times
...
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.
upvoted 0 times
...
Genevive
1 year ago
Executing long-running tasks as background processes can help improve performance and scalability.
upvoted 0 times
...
Rosita
1 year ago
Configuring application logging to write stdout can make it easier to monitor and troubleshoot.
upvoted 0 times
...
Della
1 year ago
Using the same backing services in all environments is also important for consistency.
upvoted 0 times
...
Eloisa
1 year ago
I agree, having processes that start up and shut down quickly can definitely help with deployment.
upvoted 0 times
...
...
Shonda
1 year 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.
upvoted 0 times
Charisse
1 year ago
I think option D is also important, having processes that start up and shut down gracefully can help with deployment.
upvoted 0 times
...
Stefany
1 year ago
I agree, using the same backing services in all environments is key for consistency.
upvoted 0 times
...
...
Trevor
1 year 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.
upvoted 0 times
...
Lakeesha
1 year ago
I agree with Terrilyn, using the same backing services can definitely help minimize the gap between development and production.
upvoted 0 times
...
Terrilyn
1 year ago
I think the answer is A) Using the same backing services in all of an application's environments.
upvoted 0 times
...

Save Cancel