Question 1

A developer is using sling context-aware configuration trying to get the configuration resource using:

@ReferencePrivate configurationResourceResolver cfgResourceResolver;confResource = cfgResourceResolver.getResource(resource, Bucket_NAME, CONFIG_NAME);

Options :

A : Apply read permissions to anonymous user for /content directory

B : Apply write permissions to anonymous user for /conf directory

C : Apply read permissions to anonymous user for /conf directory

D : Apply read permissions to anonymous user for /etc directory

Answer: C

Question 2

Which URI should be used to configure a Flush Agent for a dispatcher listening on port 8080?

Options :

A : http://:8080/dispatcher/invalidate.cache

B : http://:8080/dispatcher/cache.invalidate

C : http://:8080/invalidate.cache

D : http://:8080/cache.invalidate

Answer: A

Question 3

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?

Options :

A : The Custom OAK Lucene index is missing evaluatePathRestrictions property and queryPaths property

B : The Custom Oak Lucene index must include boost property to rank it higher than default Lucene index

C : The custom OAK Lucene index must be replaced with OAK Lucene Property index

D : The Custom OAK lucene index is missing evaluatePathRestrictions property and includedPaths Property

Answer: C

Question 4

In an instance of AEM, queries with full-text conditions are not working as expected. A developer creates a new node under oak:index and names the node LucenedIndex. Which properties and values need to be added to this node to make the node a full text index? (Choose two answers.)

Options :

A : type: lucene

B : async: async

C : includePropertyNames: [full]

D : reindex: true

Answer: A,B

Question 5

A customer is having trouble with some search queries and provides the following information:The logs show the following warring occurs many times:

*WARN* Traversed 1000 nodes with filter Filter (query = SELECt ..)

The Client has more than 100000 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?

Options :

A : Advise the client to recognize their content by having nodes of no more than 10000 sub nodes.

B : Set the reindex flag to true for node 'oak:index/cqPageLucene'

C : Use the Index Manager to validate the 'cqPageLucene' index is enabled

D : Create a custom oak index for the custom page property

Answer: D