New Year Sale 2026! 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 Certified Heroku Architect (Plat-Arch-206) Exam - Topic 4 Question 39 Discussion

Actual exam question for Salesforce's Salesforce Certified Heroku Architect (Plat-Arch-206) exam
Question #: 39
Topic #: 4
[All Salesforce Certified Heroku Architect (Plat-Arch-206) 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 Salesforce Certified Heroku Architect (Plat-Arch-206) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Refugia
3 months ago
Definitely need to declare it as a separate process type!
upvoted 0 times
...
France
3 months ago
Replicating to local disk sounds like overkill.
upvoted 0 times
...
Thurman
3 months ago
Wait, are we really sharing a single cache across dynos?
upvoted 0 times
...
Gilbert
4 months ago
Totally agree, that's a big risk on Heroku!
upvoted 0 times
...
Margart
4 months ago
The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
Mozelle
4 months ago
I vaguely recall that declaring the cache as a separate process type could help, but I'm not confident if that's the best approach for Heroku.
upvoted 0 times
...
Lavonda
4 months ago
I think it's important to note that in-memory caches can be cleared unexpectedly on Heroku, which could impact performance.
upvoted 0 times
...
Coletta
4 months ago
I feel like I saw a practice question about caching on Heroku, and it mentioned that all dynos share the same cache, but I'm not entirely sure.
upvoted 0 times
...
Magnolia
5 months ago
I remember discussing how Heroku's dynos can be ephemeral, so I think the in-memory cache might not persist across deploys.
upvoted 0 times
...
Leah
5 months ago
I'm pretty confident I know the right approach for this. Heroku's stateless nature means the in-memory cache will likely need to be externalized.
upvoted 0 times
...
Chery
5 months ago
Okay, I think I have a strategy here. I'll need to consider how the application's cache can be made persistent across Heroku's ephemeral environment.
upvoted 0 times
...
Cordelia
5 months ago
Hmm, I'm a bit confused about the implications of running an in-memory cache on Heroku. I'll need to review the platform's architecture.
upvoted 0 times
...
Domonique
5 months ago
This seems like a tricky one. I'll need to think carefully about how Heroku handles in-memory caches.
upvoted 0 times
...
Stefany
5 months ago
This seems like a tricky question. I'll need to think through the expected behavior carefully.
upvoted 0 times
...
Claudio
5 months ago
I'm pretty confident on this one. Conservative label retention is the mode that saves all the label mappings received from peer LSRs. That's the best option here.
upvoted 0 times
...
Tomoko
5 months ago
Okay, let me see. I know that personas are used to represent user archetypes, not analyze competitors. And user profiles are more about understanding user backgrounds, not business knowledge levels. I'm leaning towards option D, since environmental factors like lighting would be important to consider in a requirements analysis.
upvoted 0 times
...
Cordell
10 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
9 months ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
Cyndy
9 months ago
B) All of the application's web dynos will share a single in-memory cache.
upvoted 0 times
...
Hermila
10 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
10 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
9 months ago
A) The application should declare its in-memory cache as a separate process type to preserve it across deploys.
upvoted 0 times
...
Hollis
9 months ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
...
Lachelle
10 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
11 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
11 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
9 months ago
Definitely, we need to ensure the application can handle the potential clearing of the cache.
upvoted 0 times
...
Solange
9 months ago
That's a good point. It's important to design a robust caching solution for Heroku.
upvoted 0 times
...
Candra
9 months ago
A) The application should declare its in-memory cache as a separate process type to preserve it across deploys.
upvoted 0 times
...
Quiana
10 months ago
D) The application's in-memory cache might be cleared at any time.
upvoted 0 times
...
...
Audry
11 months ago
But what if the cache gets cleared at any time? Wouldn't that affect the application's performance?
upvoted 0 times
...
Ivette
11 months ago
I agree with Dorian. It's important to preserve the in-memory cache across deploys for performance.
upvoted 0 times
...
Dorian
11 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