An AEM Developer creates a custom OAK index for /content/mywebsite under /oak:index node. While testing the live site. It is found that the index is not being applied to any query within the website. Default Lucene indexes with high cost are being picked up by the AEM.What is the most likely of the issue?
A developer needs to create a new component called “Component A”. Component A must show a list of other components that all have a resource type of existing “Component B”. Component A must render this list of tiles for each Component B where the tile rendering is different from the default one. The list of rendered tiles must be reusable by future new components. How should the developer implement this functionality?