Salesforce Certified Heroku Architect (Plat-Arch-206) Exam - Topic 3 Question 50 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect (Plat-Arch-206) exam

Question #: 50
Topic #: 3

[All Salesforce Certified Heroku Architect (Plat-Arch-206) 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 Salesforce Certified Heroku Architect (Plat-Arch-206) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lamar

3 months ago

I thought Redis was only for caching, but I guess it can handle queues too!

upvoted 0 times

...

Danica

3 months ago

D is a no-go for Redis, it’s not meant for that.

upvoted 0 times

...

Brent

3 months ago

Wait, long-term data warehousing? That’s not right, is it?

upvoted 0 times

...

Laila

4 months ago

I agree, B and C are spot on!

upvoted 0 times

...

Rasheeda

4 months ago

Definitely B and C! Perfect for queues and caching.

upvoted 0 times

...

Annabelle

4 months 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.

upvoted 0 times

...

Isreal

4 months ago

I feel like long-term data warehousing isn't a good fit for Redis, so I would lean towards B and C.

upvoted 0 times

...

Wendell

4 months ago

I'm not entirely sure, but I remember something about using Redis for job queues. Could that be option B?

upvoted 0 times

...

Quentin

5 months ago

I think Heroku Redis is great for caching, so maybe option C is one of the answers.

upvoted 0 times

...

Marguerita

5 months 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.

upvoted 0 times

...

Sheron

5 months 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.

upvoted 0 times

...

Shad

5 months 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.

upvoted 0 times

...

Rashad

5 months ago

This question seems straightforward. I'll focus on the use cases that are most relevant to Heroku Redis.

upvoted 0 times

...

Grover

5 months 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.

upvoted 0 times

...

Long

10 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

8 months ago

C) Providing a data cache layer

upvoted 0 times

...

Rima

9 months ago

B) Adding jobs to a queue

upvoted 0 times

...

Leontine

10 months ago

A) Providing long-term data warehousing

upvoted 0 times

...

Cathrine

10 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

8 months ago

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

upvoted 0 times

...

Kayleigh

9 months ago

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

upvoted 0 times

...

Elfrieda

9 months ago

Yeah, adding jobs to a queue and providing a data cache layer are common use cases for Heroku Redis.

upvoted 0 times

...

Howard

10 months ago

I think B and C are the right choices for using Heroku Redis.

upvoted 0 times

...

Anisha

10 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

10 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

11 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