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 3 Question 50 Discussion

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

For which two use cases should an Architect recommend using Heroku Redis? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Cathrine
8 days ago
Heroku Redis, the ultimate solution for your caching and queueing needs! I'm feeling pretty confident about B and C on this one. Though maybe I should have a quick Redis tutorial just to be sure...
upvoted 0 times
...
Anisha
10 days ago
Well, well, well, look who's trying to trick us with that data warehousing nonsense. C'mon, everyone knows Heroku Redis is for caching and queuing. I'm gonna go with B and C and call it a day.
upvoted 0 times
...
Cyril
14 days ago
I'm not sure about that, I think D could also be a valid use case for Heroku Redis.
upvoted 0 times
...
Isabella
16 days ago
Ooh, this is a tricky one! I'm leaning towards B and C. Heroku Redis is all about that sweet, sweet in-memory caching and job queueing action, am I right?
upvoted 0 times
...
Chantay
20 days ago
I'm pretty sure Heroku Redis is for caching and queuing, not for data warehousing. A and D are definitely not the right answers here.
upvoted 0 times
Berry
1 days ago
C) Providing a data cache layer
upvoted 0 times
...
Sabrina
2 days ago
B) Adding jobs to a queue
upvoted 0 times
...
...
Monte
20 days ago
I agree with Bernadine, using Heroku Redis for adding jobs to a queue and providing a data cache layer makes sense.
upvoted 0 times
...
Bernadine
27 days ago
I think the answer is B and C.
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