Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Heroku Architect Topic 4 Question 15 Discussion

Actual exam question for Salesforce's Heroku Architect exam
Question #: 15
Topic #: 4
[All Heroku Architect 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

Contribute your Thoughts:

Stanton
29 days 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 months 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 months 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
Percy
10 days ago
B) Configuring application logging to write stdout.
upvoted 0 times
...
Paul
19 days ago
A) Using the same backing services in all of an application's environments.
upvoted 0 times
...
...
Brandon
2 months 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
Charolette
3 days ago
Using the same backing services in all environments can also help minimize the gap between development and production.
upvoted 0 times
...
Zita
6 days ago
I agree, having fast startup and shutdown processes can definitely streamline the deployment process.
upvoted 0 times
...
Isadora
8 days 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
16 days ago
Executing long-running tasks as background processes can help improve performance and scalability.
upvoted 0 times
...
Rosita
21 days ago
Configuring application logging to write stdout can make it easier to monitor and troubleshoot.
upvoted 0 times
...
Della
1 months ago
Using the same backing services in all environments is also important for consistency.
upvoted 0 times
...
Eloisa
2 months ago
I agree, having processes that start up and shut down quickly can definitely help with deployment.
upvoted 0 times
...
...
Shonda
2 months 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 months 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 months ago
I agree, using the same backing services in all environments is key for consistency.
upvoted 0 times
...
...
Trevor
3 months 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
3 months ago
I agree with Terrilyn, using the same backing services can definitely help minimize the gap between development and production.
upvoted 0 times
...
Terrilyn
3 months ago
I think the answer is A) Using the same backing services in all of an application's environments.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77