Cyber Monday 2024! 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 PL
Mob_nav_barsMENU

Adobe Exam AD0-E123 Topic 2 Question 19 Discussion

Actual exam question for Adobe's AD0-E123 exam
Question #: 19
Topic #: 2
[All AD0-E123 Questions]

In an AEM as a Cloud Service environment, a client needs a feature to be able to explicitly clear a dispatcher cache of required resources.

Which approach is preferred to create this feature?

Show Suggested Answer Hide Answer
Suggested Answer: B

In an AEM as a Cloud Service environment, the preferred approach to clear dispatcher cache of required resources is to use the Replication API along with a replication flush agent. This method allows for programmatic clearing of the cache and is the standard way of invalidating cached content so that the dispatcher can retrieve fresh content from the publish instance.

Option A, 'Enable the explicit cache invalidation feature in cloud manager,' is not a standard feature available in Cloud Manager.

Option C, 'Create a servlet, which will make an HTTP request to the dispatcher,' is not advisable as it bypasses the recommended AEM replication and flushing mechanisms and could lead to inconsistencies.


by Lindsay at Sep 13, 2024, 03:31 AM

Limited Time Offer

25%

Off

Get Premium AD0-E123 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Jade
2 months ago
I'll have to go with option B. It's the most standard and well-documented way to handle cache invalidation in AEM as a Cloud Service.
upvoted 0 times
...
Tatum
2 months ago
Haha, option A sounds like a magic button that would be too good to be true. I doubt that would be the preferred approach here.
upvoted 0 times
...
Lelia
2 months ago
Hmm, I'm not sure. Option C with a custom servlet might be more flexible and give us more control over the cache invalidation process.
upvoted 0 times
Berry
24 days ago
Enabling the explicit cache invalidation feature in cloud manager might be the easiest option.
upvoted 0 times
...
Daren
25 days ago
I think using Replication API along with replication flush agent could also work well.
upvoted 0 times
...
Gail
26 days ago
Option C with a custom servlet sounds like a good idea.
upvoted 0 times
...
...
Kati
3 months ago
I think option B is the way to go. Using the Replication API and the replication flush agent seems like the most straightforward approach.
upvoted 0 times
Kathrine
1 months ago
Creating a servlet to make an HTTP request to the dispatcher could work too, but option B seems more direct.
upvoted 0 times
...
Latrice
2 months ago
I think option A might be easier to implement. Enabling explicit cache invalidation in cloud manager seems efficient.
upvoted 0 times
...
William
2 months ago
That sounds like a good plan. It's a reliable way to clear the dispatcher cache.
upvoted 0 times
...
Lisandra
2 months ago
I agree, option B using the Replication API and replication flush agent is the best choice.
upvoted 0 times
...
...
Lucina
3 months ago
I would go with option C, creating a servlet seems like a flexible solution.
upvoted 0 times
...
Felicitas
3 months ago
I disagree, I believe option B is better as it provides more control over the cache invalidation process.
upvoted 0 times
...
Javier
3 months ago
I think option A is preferred because it's the most straightforward.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77