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.)

AProviding long-term data warehousing

BAdding jobs to a queue

CProviding a data cache layer

DQuerying relational data

Show Suggested Answer

Suggested Answer: D

by Reena at Sep 14, 2024, 09:19 PM

Limited Time Offer

25%

Off

Get Premium Heroku Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Long

2 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

Martina

2 days ago

C) Providing a data cache layer

upvoted 0 times

...

Rima

24 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

Erinn

2 days ago

Maybe a quick Redis tutorial would help solidify your understanding of its capabilities.

upvoted 0 times

...

Kayleigh

7 days ago

I agree, those are the two main reasons an Architect would recommend using Heroku Redis.

upvoted 0 times

...

Elfrieda

24 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