MENU
For which two use cases should an Architect recommend using Heroku Redis? (Choose two.)
Suggested Answer: D
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
35 comments · newest first
LA
Lamar
11 months ago
I thought Redis was only for caching, but I guess it can handle queues too!
DA
Danica
11 months ago
D is a no-go for Redis, it’s not meant for that.
BR
Brent
12 months ago
Wait, long-term data warehousing? That’s not right, is it?
LA
Laila
12 months ago
I agree, B and C are spot on!
RA
Rasheeda
1 year ago
Definitely B and C! Perfect for queues and caching.
AN
Annabelle
1 year ago
I practiced a similar question, and I think providing a data cache layer is definitely a use case, but I'm unsure about the second one.
IS
Isreal
1 year ago
I feel like long-term data warehousing isn't a good fit for Redis, so I would lean towards B and C.
WE
Wendell
1 year ago
I'm not entirely sure, but I remember something about using Redis for job queues. Could that be option B?
QU
Quentin
1 year ago
I think Heroku Redis is great for caching, so maybe option C is one of the answers.
MA
Marguerita
1 year ago
The key is to identify the use cases that play to Heroku Redis's strengths as an in-memory data store. I'll eliminate the less relevant options.
SH
Sheron
1 year ago
Okay, I think I've got it. Heroku Redis is great for caching and queuing, but not for long-term data storage or relational queries.
SH
Shad
1 year ago
Hmm, I'm a bit unsure about the differences between data warehousing and a data cache layer. I'll need to review those concepts before answering.
RA
Rashad
1 year ago
This question seems straightforward. I'll focus on the use cases that are most relevant to Heroku Redis.
GR
Grover
1 year ago
I think I know this one - the Deployment Report in VIOM shows the version of the InfoScale product installed on the host, and how discovered storage is being consumed by host.
LO
Long
2 years 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!
MA
Martina
1 year ago
C) Providing a data cache layer
RI
Rima
1 year ago
B) Adding jobs to a queue
LE
Leontine
1 year ago
A) Providing long-term data warehousing
CA
Cathrine
2 years 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...
ER
Erinn
1 year ago
Maybe a quick Redis tutorial would help solidify your understanding of its capabilities.
KA
Kayleigh
1 year ago
I agree, those are the two main reasons an Architect would recommend using Heroku Redis.
EL
Elfrieda
1 year ago
Yeah, adding jobs to a queue and providing a data cache layer are common use cases for Heroku Redis.
HO
Howard
1 year ago
I think B and C are the right choices for using Heroku Redis.
AN
Anisha
2 years 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.
CY
Cyril
2 years ago
I'm not sure about that, I think D could also be a valid use case for Heroku Redis.
IS
Isabella
2 years 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?
HE
Henriette
1 year ago
Definitely, those are the two main use cases for it.
LE
Leah
1 year ago
I think you're right, B and C make sense for Heroku Redis.
CH
Chantay
2 years 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.
LE
Levi
2 years ago
D) Querying relational data
ER
Erasmo
2 years ago
I agree, Heroku Redis is definitely used for caching and queuing.
BE
Berry
2 years ago
C) Providing a data cache layer
SA
Sabrina
2 years ago
B) Adding jobs to a queue
MO
Monte
2 years ago
I agree with Bernadine, using Heroku Redis for adding jobs to a queue and providing a data cache layer makes sense.
BE
Bernadine
2 years ago
I think the answer is B and C.