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

Adobe AD0-E117 Exam - Topic 4 Question 24 Discussion

Actual exam question for Adobe's AD0-E117 exam
Question #: 24
Topic #: 4
[All AD0-E117 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Bernardo
6 days ago
Option A could work too, but it might not be a long-term fix.
upvoted 0 times
...
Ming
11 days ago
I agree, using the Replication API seems effective.
upvoted 0 times
...
Louvenia
16 days ago
Definitely agree with the Replication API approach!
upvoted 0 times
...
Kattie
21 days ago
Wait, can we really use SCD for CDN flush? Sounds odd.
upvoted 0 times
...
Jessenia
27 days ago
I think using the Replication API is the best option here.
upvoted 0 times
...
Chauncey
1 month ago
Lowering the CDN TTL could help.
upvoted 0 times
...
Marquetta
1 month ago
Hmm, I'd go with B. Replication API is the way to handle this kind of cache clearing issue. Easy peasy!
upvoted 0 times
...
Kerrie
1 month ago
A) Lower the CDN TTL? Nah, that's just a temporary fix. You want something more permanent.
upvoted 0 times
...
Charisse
2 months ago
D) Use Sling Content Distribution (SCD) from Author to flush CDN. Gotta love those fancy AEM tools!
upvoted 0 times
...
Antonio
2 months ago
C) Invoke the CDN flush replication agent. Seems like the most straightforward solution.
upvoted 0 times
...
Alline
2 months ago
B) Use the Replication API to invoke the publish Dispatcher flush replication agent. That's the way to go!
upvoted 0 times
...
Carlene
2 months ago
I think option B is the best choice. It directly addresses the replication issue.
upvoted 0 times
...
Rene
2 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.
upvoted 0 times
...
Maybelle
3 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!
upvoted 0 times
...
Giuseppe
3 months ago
Isn’t invoking the CDN flush replication agent a bit overkill?
upvoted 0 times
...
Kate
3 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.
upvoted 0 times
...
Martha
3 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.
upvoted 0 times
...
Andra
4 months ago
I'm a bit confused by the question. What's the difference between the Replication API and the CDN flush replication agent?
upvoted 0 times
...
Glynda
4 months ago
Hmm, this seems like a tricky one. I'll need to think through the different options carefully.
upvoted 0 times
Tayna
2 months ago
I think lowering the CDN TTL could help.
upvoted 0 times
...
...
Noelia
4 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.
upvoted 0 times
...
Alton
4 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.
upvoted 0 times
...
Sheron
4 months ago
I remember practicing a question about using the Replication API, so I might lean towards option B for flushing the cache.
upvoted 0 times
...
Murray
5 months ago
I think lowering the CDN TTL could help, but I'm not entirely sure if that's the best approach for this situation.
upvoted 0 times
...

Save Cancel