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-E123 Exam - Topic 1 Question 12 Discussion

Actual exam question for Adobe's AD0-E123 exam
Question #: 12
Topic #: 1
[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.


Contribute your Thoughts:

0/2000 characters
Gracie
3 months ago
Totally agree with A, it's the simplest solution!
upvoted 0 times
...
Man
3 months ago
Wait, can we really do that with Cloud Manager? Surprised!
upvoted 0 times
...
Chan
3 months ago
C sounds a bit complicated for just clearing cache.
upvoted 0 times
...
Elenore
4 months ago
I think B is better, more control with the Replication API.
upvoted 0 times
...
Rachael
4 months ago
Option A is the way to go for cache invalidation!
upvoted 0 times
...
Chu
4 months ago
I feel like I’ve seen questions about cache invalidation before, but I can’t recall the details on which option is best.
upvoted 0 times
...
Chantay
4 months ago
Creating a servlet to clear the cache seems like a possible solution, but I’m not confident if that’s the preferred method.
upvoted 0 times
...
Daniela
4 months ago
I remember practicing with the Replication API in a similar question, so option B might be the right choice here.
upvoted 0 times
...
Kayleigh
5 months ago
I think option A sounds familiar, but I'm not entirely sure if it applies specifically to the Cloud Service environment.
upvoted 0 times
...
Kasandra
5 months ago
I'm a little confused by the different options here. I'll need to review the documentation on AEM as a Cloud Service and the available cache management features to determine the best approach. Hopefully, I can figure this out before the exam.
upvoted 0 times
...
Martha
5 months ago
Ah, I think I've seen this type of question before. The explicit cache invalidation feature in Cloud Manager sounds like the most straightforward and recommended approach. I'll make sure to double-check the details, but I feel confident about this one.
upvoted 0 times
...
Norah
5 months ago
The servlet option seems like it could work, but I'm not sure if that's the most efficient or preferred way to handle this. I'll need to review the details of each approach to decide which one is truly the best solution.
upvoted 0 times
...
Lamar
5 months ago
Hmm, I'm a bit unsure about this one. I'm not too familiar with the Replication API and replication flush agent, so I'm not sure if that would be the best approach. I'll have to think this through a bit more.
upvoted 0 times
...
Christa
5 months ago
This looks like a pretty straightforward question. I think the preferred approach would be to use the explicit cache invalidation feature in Cloud Manager.
upvoted 0 times
...
Providencia
5 months ago
Option D seems like a good long-term solution - creating a job to regularly hide unavailable products could help keep the catalog up-to-date and ensure a better customer experience.
upvoted 0 times
...
Luz
5 months ago
Hmm, I'm not totally sure about this one. I know mobile phones have sensors to detect movement, but I can't remember the exact name for that sensor.
upvoted 0 times
...
Amie
5 months ago
Okay, let me see. Minify is for reducing file size by removing whitespace, Compression is for reducing data transfer, and Inlining is for embedding resources directly in the HTML. That leaves Shrink to Attributes as the most likely answer here.
upvoted 0 times
...
Chandra
2 years ago
Ah, the age-old question of cache invalidation. I say we go with option D: just unplug the server and plug it back in. Works every time!
upvoted 0 times
...
Donte
2 years ago
Option A sounds interesting, but I'm not familiar with the explicit cache invalidation feature in Cloud Manager. I'd want to look into that a bit more before deciding.
upvoted 0 times
...
Grover
2 years ago
Hmm, I'm not sure. I think I'd need to do some more research to make a confident decision. All the options seem reasonable, but I'd want to understand the tradeoffs better.
upvoted 0 times
...
Marion
2 years ago
I'm leaning towards option C. Creating a custom servlet to clear the dispatcher cache seems more flexible and gives us more control over the process.
upvoted 0 times
Karan
2 years ago
I agree, creating a custom servlet gives us more control over clearing the dispatcher cache.
upvoted 0 times
...
Gearldine
2 years ago
Option C sounds like a good choice. It allows for more customization.
upvoted 0 times
...
...
Chantell
2 years ago
I think option B is the way to go. Using the Replication API with the replication flush agent seems like the most straightforward and reliable approach.
upvoted 0 times
Shalon
2 years ago
Yeah, that approach seems like it would be the most reliable way to clear the dispatcher cache.
upvoted 0 times
...
Cathern
2 years ago
I agree, option B using the Replication API with the replication flush agent is the best choice.
upvoted 0 times
...
...
Jerrod
2 years ago
I disagree, I believe option B with replication flush agent is more efficient.
upvoted 0 times
...
Ettie
2 years ago
I think option A is the best approach.
upvoted 0 times
...

Save Cancel