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 CCM-101 Exam - Topic 8 Question 55 Discussion

Actual exam question for Salesforce's CCM-101 exam
Question #: 55
Topic #: 8
[All CCM-101 Questions]

A developer observed a specific issue in production, which they cannot reproduce in other environments. The developer wants to do a hot fix to one of the ISML pages, which uses tag, to see if that resolves while issue. Which consideration must the developer keep in mind while deploying the hot fix in production?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Latosha at Oct 21, 2024, 12:36 AM

Limited Time Offer

25%

Off

Get Premium CCM-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Nan
3 months ago
I didn't know that about the cache duration! That's interesting.
upvoted 0 times
...
Heidy
3 months ago
Totally agree with B, caching can be tricky with multiple tags.
upvoted 0 times
...
Louann
3 months ago
Wait, are we sure the TTL only affects static content? Sounds off.
upvoted 0 times
...
Lashawnda
4 months ago
I think option B is spot on. Multiple tags can mess things up.
upvoted 0 times
...
Yuki
4 months ago
Don't forget to invalidate the cache after the hot fix!
upvoted 0 times
...
Laura
4 months ago
I feel like option A makes the most sense since we’re making a change to the page. We definitely don’t want stale content in production.
upvoted 0 times
...
Laurel
4 months ago
I’m a bit confused about the TTL cache setting. Does it really only affect static content? That could change how we approach the issue.
upvoted 0 times
...
Mignon
4 months ago
I think I saw a similar question where the highest cache duration was mentioned. It might be important to consider that if there are multiple tags involved.
upvoted 0 times
...
Ethan
5 months ago
I remember something about needing to invalidate the cache after a hot fix, but I'm not entirely sure if that's always necessary.
upvoted 0 times
...
Shenika
5 months ago
The key thing to remember here is that the developer needs to invalidate the cache for the hot fix to take effect. That's the most important consideration they need to keep in mind.
upvoted 0 times
...
Ty
5 months ago
I'm not entirely sure about the TTL cache setting and how that relates to the page cache. I'll need to double-check the details on that part of the question.
upvoted 0 times
...
Donette
5 months ago
Okay, let me think this through step-by-step. The developer is using an tag, so they need to make sure the cache is properly invalidated. And they need to be aware that the highest cache duration will be used, even if there are multiple tags.
upvoted 0 times
...
Louann
5 months ago
Hmm, I'm a bit confused about the difference between the page cache and the static content cache. I'll need to review the details on how caching works in this context.
upvoted 0 times
...
Luis
5 months ago
I'm pretty confident I know the answer to this one. The key is that the developer needs to invalidate the cache for the hot fix to take effect in production.
upvoted 0 times
...
Joseph
1 year ago
Option C is just trying to confuse us. Obviously, we need to invalidate the cache for the hot fix to take effect. A all the way!
upvoted 0 times
Chi
1 year ago
Let's make sure to follow the correct steps and invalidate the cache before deploying the hot fix.
upvoted 0 times
...
Eugene
1 year ago
I agree, option A is the best choice to ensure the hot fix takes effect in production.
upvoted 0 times
...
Leonora
1 year ago
Option C is incorrect, we definitely need to invalidate the cache for the hot fix.
upvoted 0 times
...
...
Ashlyn
1 year ago
Hold up, is that C option talking about the TTL cache setting? That sounds like a red herring to me. I'd go with A or B.
upvoted 0 times
Fidelia
1 year ago
Good point. If that's the case, then B would be the better option to consider.
upvoted 0 times
...
Geraldine
1 year ago
But what if the page has multiple tags with different cache durations? Would that affect the hot fix?
upvoted 0 times
...
Maile
1 year ago
Yeah, I think A makes sense because we need to make sure the cache is invalidated after the hot fix.
upvoted 0 times
...
Julio
1 year ago
I agree, option C does seem like a distraction. A or B would be safer choices.
upvoted 0 times
...
...
Krissy
1 year ago
I'm not sure about that. Option B sounds like it might be the safest bet, especially if there are multiple tags involved.
upvoted 0 times
King
1 year ago
A: Definitely. It's important to be cautious when deploying hot fixes in production environments.
upvoted 0 times
...
Kati
1 year ago
B: Yeah, that makes sense. It could help avoid any unexpected caching behavior.
upvoted 0 times
...
Doug
1 year ago
A: Option B sounds like a good idea. It's better to consider the highest cache duration in production.
upvoted 0 times
...
...
Brynn
1 year ago
I agree with Leslie. Invalidating the cache for the hot fix is crucial to ensure the fix is applied correctly in production.
upvoted 0 times
...
Leslie
1 year ago
I think the developer should consider option A) It will be required to invalidate the cache for the hot fix.
upvoted 0 times
...
Nickolas
1 year ago
Hmm, I think option A is the way to go. Gotta clear that cache to see if the hot fix works!
upvoted 0 times
Bronwyn
1 year ago
User 4: Clearing the cache will ensure the fix is properly applied in production.
upvoted 0 times
...
Reita
1 year ago
User 3: Make sure to double check the cache settings before deploying the hot fix.
upvoted 0 times
...
Viva
1 year ago
User 2: Definitely, cache invalidation is key for testing the fix.
upvoted 0 times
...
Izetta
1 year ago
I agree, clearing the cache is important for the hot fix.
upvoted 0 times
...
...

Save Cancel