MENU
After building a new website in AEMaaCS, it was discovered that the AEM-Managed CDN cache is not clearing hours after a page is published. What would be a way to resolve this issue?
Suggested Answer: D
Get Premium AD0-E117 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
CH
Chanel
7 months ago
I’m leaning towards B as well. It’s more reliable for cache issues.
FA
Fairy
7 months ago
Option D sounds interesting. SCD could streamline the process.
EM
Emmett
7 months ago
I feel like option C is a bit risky. Flushing the CDN might cause delays.
BE
Bernardo
8 months ago
Option A could work too, but it might not be a long-term fix.
MI
Ming
8 months ago
I agree, using the Replication API seems effective.
LO
Louvenia
8 months ago
Definitely agree with the Replication API approach!
KA
Kattie
8 months ago
Wait, can we really use SCD for CDN flush? Sounds odd.
JE
Jessenia
8 months ago
I think using the Replication API is the best option here.
CH
Chauncey
9 months ago
Lowering the CDN TTL could help.
MA
Marquetta
9 months ago
Hmm, I'd go with B. Replication API is the way to handle this kind of cache clearing issue. Easy peasy!
KE
Kerrie
9 months ago
A) Lower the CDN TTL? Nah, that's just a temporary fix. You want something more permanent.
CH
Charisse
9 months ago
D) Use Sling Content Distribution (SCD) from Author to flush CDN. Gotta love those fancy AEM tools!
AN
Antonio
9 months ago
C) Invoke the CDN flush replication agent. Seems like the most straightforward solution.
AL
Alline
9 months ago
B) Use the Replication API to invoke the publish Dispatcher flush replication agent. That's the way to go!
CA
Carlene
10 months ago
I think option B is the best choice. It directly addresses the replication issue.
RE
Rene
10 months ago
I'm feeling pretty confident about this one. I'd say the best solution is to use the Replication API to flush the CDN cache. That should do the trick.
MA
Maybelle
10 months ago
Haha, I bet the person who wrote this question has dealt with this problem a few times. Gotta love those AEM cache gremlins!
GI
Giuseppe
10 months ago
Isn’t invoking the CDN flush replication agent a bit overkill?
KA
Kate
11 months ago
Option C looks promising, but I'm not sure if invoking the CDN flush replication agent is the right approach here. I'll need to double-check the details.
MA
Martha
11 months ago
Okay, I think I've got this. I'd go with option B - using the Replication API to invoke the publish Dispatcher flush replication agent. That should clear the CDN cache.
AN
Andra
11 months ago
I'm a bit confused by the question. What's the difference between the Replication API and the CDN flush replication agent?
GL
Glynda
11 months ago
Hmm, this seems like a tricky one. I'll need to think through the different options carefully.
WI
Willard
6 months ago
I’d go with Sling Content Distribution for a more thorough flush.
CA
Catarina
6 months ago
The CDN flush replication agent sounds promising too.
GL
Glenna
6 months ago
But what about using the Replication API?
TA
Tayna
10 months ago
I think lowering the CDN TTL could help.
NO
Noelia
12 months ago
Sling Content Distribution sounds familiar, but I’m not confident if it's the right choice for clearing the CDN cache in this case.
AL
Alton
12 months ago
I feel like invoking the CDN flush replication agent could be a solution, but I can't recall if that's the standard method we discussed.
SH
Sheron
12 months ago
I remember practicing a question about using the Replication API, so I might lean towards option B for flushing the cache.
MU
Murray
1 year ago
I think lowering the CDN TTL could help, but I'm not entirely sure if that's the best approach for this situation.