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

Salesforce CCM-101 Exam - Topic 8 Question 55 Discussion

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

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?

Suggested Answer: C

Get Premium CCM-101 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
34 comments · newest first
NA
Nan 11 months ago
I didn't know that about the cache duration! That's interesting.
HE
Heidy 11 months ago
Totally agree with B, caching can be tricky with multiple tags.
LO
Louann 12 months ago
Wait, are we sure the TTL only affects static content? Sounds off.
LA
Lashawnda 12 months ago
I think option B is spot on. Multiple tags can mess things up.
YU
Yuki 1 year ago
Don't forget to invalidate the cache after the hot fix!
LA
Laura 1 year 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.
LA
Laurel 1 year 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.
MI
Mignon 1 year 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.
ET
Ethan 1 year 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.
SH
Shenika 1 year 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.
TY
Ty 1 year 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.
DO
Donette 1 year 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.
LO
Louann 1 year 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.
LU
Luis 1 year 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.
JO
Joseph 2 years 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!
CH
Chi 2 years ago
↳ replying to Joseph
Let's make sure to follow the correct steps and invalidate the cache before deploying the hot fix.
EU
Eugene 2 years ago
↳ replying to Joseph
I agree, option A is the best choice to ensure the hot fix takes effect in production.
LE
Leonora 2 years ago
↳ replying to Joseph
Option C is incorrect, we definitely need to invalidate the cache for the hot fix.
AS
Ashlyn 2 years 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.
FI
Fidelia 2 years ago
↳ replying to Ashlyn
Good point. If that's the case, then B would be the better option to consider.
GE
Geraldine 2 years ago
↳ replying to Ashlyn
But what if the page has multiple tags with different cache durations? Would that affect the hot fix?
MA
Maile 2 years ago
↳ replying to Ashlyn
Yeah, I think A makes sense because we need to make sure the cache is invalidated after the hot fix.
JU
Julio 2 years ago
↳ replying to Ashlyn
I agree, option C does seem like a distraction. A or B would be safer choices.
KR
Krissy 2 years ago
I'm not sure about that. Option B sounds like it might be the safest bet, especially if there are multiple tags involved.
KI
King 2 years ago
↳ replying to Krissy
A: Definitely. It's important to be cautious when deploying hot fixes in production environments.
KA
Kati 2 years ago
↳ replying to Krissy
B: Yeah, that makes sense. It could help avoid any unexpected caching behavior.
DO
Doug 2 years ago
↳ replying to Krissy
A: Option B sounds like a good idea. It's better to consider the highest cache duration in production.
BR
Brynn 2 years ago
I agree with Leslie. Invalidating the cache for the hot fix is crucial to ensure the fix is applied correctly in production.
LE
Leslie 2 years ago
I think the developer should consider option A) It will be required to invalidate the cache for the hot fix.
NI
Nickolas 2 years ago
Hmm, I think option A is the way to go. Gotta clear that cache to see if the hot fix works!
BR
Bronwyn 2 years ago
↳ replying to Nickolas
User 4: Clearing the cache will ensure the fix is properly applied in production.
RE
Reita 2 years ago
↳ replying to Nickolas
User 3: Make sure to double check the cache settings before deploying the hot fix.
VI
Viva 2 years ago
↳ replying to Nickolas
User 2: Definitely, cache invalidation is key for testing the fix.
IZ
Izetta 2 years ago
↳ replying to Nickolas
I agree, clearing the cache is important for the hot fix.
0/2000 characters

Save Cancel