MENU
An existing app is experiencing performance degradation because of multiple executions of multiple, expensive SQL read queries. This SQL code cannot be optimized any further and the frequency of the execution of the queries cannot be reduced. Which two options should an Architect recommend in this scenario?
Suggested Answer: B, C
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
- https://devcenter.heroku.com/articles/using-sso-services-with-heroku#end-user-account-creation-and-removal
14 comments · newest first
JE
Jenise
3 days ago
Caching is a must in this case, no doubt about it!
JU
Judy
8 days ago
Wait, restarting the server? Is that really a solution?
MI
Micheline
13 days ago
Hardcoding results? That sounds risky!
JU
Judy
19 days ago
I think B could work too, but not as effective as caching.
SY
Sylvia
24 days ago
Option C is definitely the way to go! Caching helps a lot.
IS
Isaiah
29 days ago
Caching is a must, but I wonder if it’ll really solve the problem long-term.
BI
Billi
1 month ago
Wait, restarting the server? That seems like a temporary fix, right?
JA
Janessa
1 month ago
Hardcoding results? That sounds risky, not a fan of option A.
JO
Johnetta
1 month ago
I think option B could help too, more read capacity is always good.
VI
Vilma
2 months ago
Definitely go with option C, caching is key!
LI
Lilli
2 months ago
Restarting the server to reclaim cache seems like a temporary fix, but I doubt it's a long-term solution for performance degradation.
KA
Karl
2 months ago
Adding a read-only HerokuPostgres follower sounds familiar, but I can't recall if it really helps with performance issues like this.
MA
Martha
2 months ago
I'm not entirely sure, but hardcoding query results seems risky. What if the data changes?
LE
Leonardo
2 months ago
I remember discussing caching strategies in class, so I think creating a database caching layer could be a solid option.