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:

Long
1 months ago
I'm just gonna go ahead and say it: if you choose A or D, you might as well be using a carrier pigeon instead of Heroku Redis. B and C all the way, folks!
upvoted 0 times
Rima
21 days ago
B) Adding jobs to a queue
upvoted 0 times
...
Leontine
1 months ago
A) Providing long-term data warehousing
upvoted 0 times
...
...
Cathrine
2 months 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
Kayleigh
4 days ago
I agree, those are the two main reasons an Architect would recommend using Heroku Redis.
upvoted 0 times
...
Elfrieda
21 days ago
Yeah, adding jobs to a queue and providing a data cache layer are common use cases for Heroku Redis.
upvoted 0 times
...
Howard
1 months ago
I think B and C are the right choices for using Heroku Redis.
upvoted 0 times
...
...
Anisha
2 months 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
2 months ago
I'm not sure about that, I think D could also be a valid use case for Heroku Redis.
upvoted 0 times
...
Isabella
2 months 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
Henriette
29 days ago
Definitely, those are the two main use cases for it.
upvoted 0 times
...
Leah
1 months ago
I think you're right, B and C make sense for Heroku Redis.
upvoted 0 times
...
...
Chantay
2 months 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
Levi
1 months ago
D) Querying relational data
upvoted 0 times
...
Erasmo
2 months ago
I agree, Heroku Redis is definitely used for caching and queuing.
upvoted 0 times
...
Berry
2 months ago
C) Providing a data cache layer
upvoted 0 times
...
Sabrina
2 months ago
B) Adding jobs to a queue
upvoted 0 times
...
...
Monte
2 months 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
3 months ago
I think the answer is B and C.
upvoted 0 times
...

Save Cancel