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

Adobe Exam AD0-E134 Topic 3 Question 41 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 41
Topic #: 3
[All AD0-E134 Questions]

A customer is having trouble with some search queries and provides the following information:

* The logs show the following warning occurs many time: WARN* Traversed 1000 nodes with filter Filter (query=select...)

* The client has more than 100,000 stored in their AEM instance

* The client uses a custom page property to help search for pages of a given type

What should the AEM Developer do to help resolve the client's issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

The warning WARN* Traversed 1000 nodes with filter Filter (query=select...) indicates that the query is performing a traversal instead of using an index. This results in poor performance, especially when the client has a large number of nodes (e.g., more than 100,000).

To resolve this issue, you should create a custom Oak index for the custom page property. This ensures that the queries can leverage the index for efficient data retrieval.

Steps to create a custom Oak index:

Define the Oak Index:

Navigate to the /oak:index node in CRXDE Lite (http://localhost:4502/crx/de).

Create a new node of type oak:QueryIndexDefinition.

Configure the Index:

Set the properties of the new index node to define the indexing rules for the custom page property.

{

'jcr:primaryType': 'oak:QueryIndexDefinition',

'type': 'property',

'propertyNames': ['customPageProperty'],

'reindex': true,

'async': 'async'

}

Deploy and Reindex:

Save the changes and initiate a reindexing process.

Ensure that the reindex flag is set to true for the newly created index.

Validate the Index:

Use the Index Manager or the AEM Web Console to validate that the new index is enabled and functioning correctly.

By creating a custom Oak index for the custom page property, the queries will be optimized to use the index, significantly improving the search performance and resolving the client's issue.


Adobe Experience Manager - Oak Indexing

Apache Jackrabbit Oak - Indexing

Contribute your Thoughts:

Goldie
3 days ago
Haha, the index manager? Really? I bet the developer who wrote that question has never actually used the index manager in their life. Let's go with the custom oak index, that's the way to go!
upvoted 0 times
...
Onita
10 days ago
Hmm, I'm not so sure about that. Reindexing the 'oakindex/cqPageLicen' node might be a better option. Seems like the index is the issue here, so we should make sure it's enabled and up-to-date.
upvoted 0 times
...
Natalya
11 days ago
I believe setting the reindex flag to true for node 'oakindex/cqPageLicen' could also be a good solution.
upvoted 0 times
...
Shantell
12 days ago
Okay, let's see. A custom oak index for the custom page property seems like the way to go. That should help with the performance issues, right? Gotta love those oak indexes!
upvoted 0 times
Talia
12 hours ago
B) Set the reindex flag to true for node ''oakindex/cqPageLicen'
upvoted 0 times
...
Gerald
4 days ago
A) Create a custom oak index for the custom page property.
upvoted 0 times
...
...
Adrianna
18 days ago
I agree with Evangelina, creating a custom oak index would definitely help improve search performance.
upvoted 0 times
...
Evangelina
26 days ago
I think the AEM Developer should create a custom oak index for the custom page property.
upvoted 0 times
...

Save Cancel