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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Heroku Architect Topic 4 Question 39 Discussion

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

A client wants to migrate their on-premise application to Heroku. The application maintains a local, in-memory cache for its datastore to improve performance.

What should an Architect advise the client about running the application on Heroku?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Sherill at Jun 21, 2024, 06:47 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Cordell
2 months ago
Wait, you mean I can't just dump my entire database into the in-memory cache and call it a day? Heroku is really cramping my style here.
upvoted 0 times
Paulina
13 days ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
Cyndy
1 months ago
B) All of the application's web dynos will share a single in-memory cache.
upvoted 0 times
...
Hermila
1 months ago
A) The application should declare its in-memory cache as a separate process type to preserve it across deploys.
upvoted 0 times
...
...
Lorita
2 months ago
C? Replicating the cache to disk? What is this, the Stone Age? Clearly, D is the way to go. Heroku will take care of my caching needs. I'm the king of cloud migration!
upvoted 0 times
Hannah
22 days ago
A) The application should declare its in-memory cache as a separate process type to preserve it across deploys.
upvoted 0 times
...
Hollis
28 days ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
...
Lachelle
2 months ago
Option A seems tempting, but declaring a separate process type just for the cache? That's a bit overkill, don't you think?
upvoted 0 times
...
Elouise
2 months ago
B? Really? Sharing a single in-memory cache across all web dynos? That sounds like a recipe for disaster. I'm glad I caught that one!
upvoted 0 times
...
Telma
2 months ago
Option D is the correct answer. Heroku's ephemeral file system means the application's in-memory cache might be cleared at any time. I'll make sure to design a more robust caching solution for Heroku.
upvoted 0 times
Helaine
16 days ago
Definitely, we need to ensure the application can handle the potential clearing of the cache.
upvoted 0 times
...
Solange
17 days ago
That's a good point. It's important to design a robust caching solution for Heroku.
upvoted 0 times
...
Candra
26 days ago
A) The application should declare its in-memory cache as a separate process type to preserve it across deploys.
upvoted 0 times
...
Quiana
1 months ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
...
Audry
2 months ago
But what if the cache gets cleared at any time? Wouldn't that affect the application's performance?
upvoted 0 times
...
Ivette
2 months ago
I agree with Dorian. It's important to preserve the in-memory cache across deploys for performance.
upvoted 0 times
...
Dorian
3 months ago
I think the Architect should advise the client to declare the in-memory cache as a separate process type.
upvoted 0 times
...

Save Cancel