MENU
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?
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
37 comments · newest first
LA
Laurel
11 months ago
Adding a logging add-on could help identify the real issue too!
MA
Madalyn
12 months ago
Autoscaling might not be the best option here, manual scaling could work better.
MA
Marci
12 months ago
Wait, why are they still getting H12 errors with performance-m dynos?
JE
Jerilyn
1 year ago
I think upgrading to performance-L dynos could really help!
CA
Carman
1 year ago
Moving long-running tasks to worker dynos sounds smart.
SH
Shayne
1 year ago
I practiced a similar question where autoscaling was ineffective. I wonder if switching to manual scaling could stabilize the app, but I'm not convinced that's the best approach here.
BU
Buck
1 year ago
Adding a logging add-on might help us understand the root cause of the timeouts, but I don't think it directly addresses the H12 errors.
DE
Dewitt
1 year ago
I'm not entirely sure, but I think upgrading to performance-L dynos could help with the memory issue. However, it seems like a more expensive solution.
RE
Reiko
1 year ago
I remember studying H12 errors and how they relate to request timeouts. Moving long-running tasks to worker dynos seems like a solid option to reduce the load on web dynos.
UL
Ulysses
1 year ago
Okay, I think I've got a strategy here. Since autoscaling isn't working, I'd recommend trying a manual scaling option of 2 dynos. That way, they can ensure they have enough resources without potentially over-provisioning. Seems like the most straightforward solution.
LI
Linette
1 year ago
Hmm, I'm not sure if adding a logging add-on would really solve the timeout issue. That seems more like a troubleshooting step rather than a direct remediation. I'd focus on the scaling and task management aspects first.
SA
Samuel
1 year ago
I'm a bit confused by this question. The app is not consuming more than 800 MB of RAM, so I'm not sure why they're still encountering timeout errors. Upgrading to larger dynos might be overkill in this case.
JO
Josefa
1 year ago
This looks like a classic performance issue with the Heroku app. I think moving long-running tasks to worker dynos could be a good first step to try and alleviate the problem.
LA
Lawrence
1 year ago
Hmm, I'm not sure. IaaS might also work well since you have more control over the infrastructure and can customize it for your testing needs.
KA
Katheryn
1 year ago
Hmm, I'm a bit unsure about the difference between SMTP, IMAP, and Outlook. I'll need to review my notes on email protocols to make sure I select the right options.
DW
Dwight
1 year ago
I'm a bit confused by this question. The options seem to cover a range of different topics related to software testing and XML. I'll have to review my notes on XML and querying before I can confidently answer this.
CH
Chaya
1 year ago
I'm a bit torn between options A and C. They both seem to involve a similar process of identifying gaps, solutions, and dependencies, and then grouping them into work packages. I'll need to carefully compare the details of each approach to decide which one is truly the best.
LA
Laurel
1 year ago
I'm trying to recall if Elastic IP addresses are only for NAT instances. I should double-check whether they need to be attached to the EC2 directly or something else.
BE
Becky
1 year ago
I've always mixed up Tcrway and GA; I think GA is connected to ACK networks, but I need to double-check that!
FR
Freeman
1 year 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!
HE
Helene
1 year 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.
JU
Julio
1 year ago
D) Replace autoscaling with a manual scaling option of 2.
KA
Kati
1 year ago
Autoscaling is definitely the way to go, but maybe upgrading to performance-L dynos could also help.
LI
Lilli
1 year ago
C) Upgrade to performance-L dynos with 14 GB RAM.
JE
Jennie
1 year ago
A) Move long-running tasks to worker dynos.
TA
Tamekia
1 year 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.
BE
Becky
2 years ago
Adding a logging add-on might help diagnose the issue, but it doesn't really address the underlying problem of timeouts.
MA
Magda
1 year ago
C) Upgrade to performance-L dynos with 14 GB RAM.
VA
Val
1 year ago
B) Add a logging add-on from the Elements marketplace.
JO
Josephine
1 year ago
A) Move long-running tasks to worker dynos.
LA
Latonia
2 years 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.
DA
Dahlia
2 years ago
I'm not sure, maybe upgrading to performance-L dynos with more RAM could also solve the issue.
LO
Loreen
2 years ago
I agree with Tasia, that could help alleviate the H12 errors.
TA
Tasia
2 years ago
I think we should move long-running tasks to worker dynos.
SH
Shantell
2 years ago
But wouldn't upgrading to performance-L dynos with more RAM also be a good solution?
CH
Charisse
2 years ago
I agree with Billye, that could help alleviate the H12 errors.
BI
Billye
2 years ago
I think we should move long-running tasks to worker dynos.