Adobe AD0-E134 Exam - 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?

ACreate a custom oak index for the custom page property.

BSet the reindex flag to true for node ''oakindex/cqPageLicen'

CUse the index Manager to validate the 'cqPageLicence index is enabled.

Show Suggested 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

by An at Jan 14, 2025, 10:13 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Vanda

4 months ago

I disagree, I don't think a custom index is necessary here.

upvoted 0 times

...

Annabelle

4 months ago

Wow, over 100,000 nodes? That's a lot to sift through!

upvoted 0 times

...

Geraldine

4 months ago

Setting the reindex flag seems risky, not sure if that's the right move.

upvoted 0 times

...

Cecily

4 months ago

I think validating the index is a good first step too.

upvoted 0 times

...

Pilar

4 months ago

Definitely need to create a custom oak index for better performance.

upvoted 0 times

...

Allene

5 months ago

The warning about traversing 1000 nodes suggests a performance issue. I think creating a custom oak index, like in option A, would definitely help optimize those search queries.

upvoted 0 times

...

Viki

5 months ago

I feel like we practiced a similar question where validating an index was crucial. Option C sounds familiar, but I’m not confident it’s the main solution here.

upvoted 0 times

...

Katina

5 months ago

I'm not entirely sure, but I think setting the reindex flag in option B might help if the index is not functioning properly.

upvoted 0 times

...

Matilda

5 months ago

I remember we discussed the importance of creating custom indexes for specific properties in AEM. It seems like option A could be the right choice here.

upvoted 0 times

...

Jade

5 months ago

This seems like a pretty straightforward indexing problem. I'd start by going with option A and creating a custom oak index. That should help speed up the search queries and resolve the client's issue. If that doesn't work, I might consider the other options, but A seems like the best place to start.

upvoted 0 times

...

Nobuko

5 months ago

Based on the information provided, I think option A is the way to go. Creating a custom oak index for the custom page property should help optimize the search performance and address the traversal issue. I'll make sure to thoroughly test this solution before implementing it.

upvoted 0 times

...

Patti

5 months ago

I'm a bit confused by the options here. Is option B about reindexing the existing 'oakindex/cqPageLicen' index? And what does option C mean by "validating" the index? I'll need to do some more research on these index-related concepts.

upvoted 0 times

...

Glory

5 months ago

Okay, let's see. The warning about traversing 1000 nodes suggests an indexing issue, and the large number of stored pages could be contributing to the problem. I think I'll go with option A and create a custom oak index for the custom page property.

upvoted 0 times

...

Kenneth

5 months ago

Hmm, this seems like a tricky one. I'll need to carefully review the information provided and think through the potential solutions.

upvoted 0 times

...

Beckie

1 year ago

Ugh, I hate it when clients have more than 100,000 things stored in their AEM instance. That's just asking for trouble. But hey, at least this question is giving us some options to try and fix it!

upvoted 0 times

Mary

12 months ago

C) Use the index Manager to validate the 'cqPageLicence index is enabled.

upvoted 0 times

...

Jackie

12 months ago

B) Set the reindex flag to true for node ''oakindex/cqPageLicen'

upvoted 0 times

...

Leota

1 year ago

A) Create a custom oak index for the custom page property.

upvoted 0 times

...

Goldie

1 year 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

Misty

1 year ago

User 2: Yeah, that seems like the best solution for the client's issue.

upvoted 0 times

...

Marci

1 year ago

User 1: I agree, let's go with the custom oak index.

upvoted 0 times

...

Onita

1 year 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

Jeffrey

1 year ago

B) Set the reindex flag to true for node ''oakindex/cqPageLicen'

upvoted 0 times

...

Ligia

1 year ago

A) Create a custom oak index for the custom page property.

upvoted 0 times

...

Natalya

1 year ago

I believe setting the reindex flag to true for node 'oakindex/cqPageLicen' could also be a good solution.

upvoted 0 times

...

Shantell

1 year 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