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

Salesforce Exam Heroku Architect Topic 6 Question 28 Discussion

Actual exam question for Salesforce's Heroku Architect exam
Question #: 28
Topic #: 6
[All Heroku Architect Questions]

Universal Containers has recently experienced a higher volume of traffic on their mobile app hosted on Heroku. When Universal Containers was running 4 standard-2x dynos with 1 GB RAM each, they encountered multiple H12 ("request timeout") errors. The app never consumed more than 800 MB of RAM. They then switched to performance-m dynos, with 2.5 GB RAM, and set autoscaling to a maximum of 2 dynos. However, they still encountered H12 ("request timeout") errors.

What remediation should an Architect recommend to alleviate this problem?

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

Contribute your Thoughts:

Freeman
16 days ago
Wait, so they're getting timeout errors on an app that's not even using all the RAM it has? Someone call the IT Helpdesk, we've got a real brain teaser here!
upvoted 0 times
...
Helene
18 days ago
Replacing autoscaling with manual scaling? What is this, the Stone Age? Autoscaling is the way to go, even if it takes some trial and error to get it right.
upvoted 0 times
Jennie
1 days ago
A) Move long-running tasks to worker dynos.
upvoted 0 times
...
...
Tamekia
28 days ago
Upgrading to performance-L dynos with 14 GB RAM sounds like overkill. If the app never used more than 800 MB, that's a lot of extra resources.
upvoted 0 times
...
Becky
1 months ago
Adding a logging add-on might help diagnose the issue, but it doesn't really address the underlying problem of timeouts.
upvoted 0 times
Val
17 days ago
B) Add a logging add-on from the Elements marketplace.
upvoted 0 times
...
Josephine
21 days ago
A) Move long-running tasks to worker dynos.
upvoted 0 times
...
...
Latonia
1 months ago
Moving long-running tasks to worker dynos seems like the obvious choice here. That way, the main app can focus on handling incoming requests more efficiently.
upvoted 0 times
...
Dahlia
2 months ago
I'm not sure, maybe upgrading to performance-L dynos with more RAM could also solve the issue.
upvoted 0 times
...
Loreen
2 months ago
I agree with Tasia, that could help alleviate the H12 errors.
upvoted 0 times
...
Tasia
2 months ago
I think we should move long-running tasks to worker dynos.
upvoted 0 times
...
Shantell
2 months ago
But wouldn't upgrading to performance-L dynos with more RAM also be a good solution?
upvoted 0 times
...
Charisse
2 months ago
I agree with Billye, that could help alleviate the H12 errors.
upvoted 0 times
...
Billye
2 months ago
I think we should move long-running tasks to worker dynos.
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
a