A developer wants to be able to execute the following query: SELECT * FROM [ntbase] AS s WHERE s.status ='STARTED' Which two options are mandatory…

When creating a custom query in AEM's JCR (Java Content Repository), the query's performance is

highly dependent on the indexing configuration. For the given query that selects all nodes with a

'status' property equal to 'STARTED' from the 'nt:base' node type, the index must be set up correctly:

Option A, "nt:base index rule", is correct. The index rule for 'nt:base' must be added to define which

properties of nodes of this type are indexed.

Option D, "status property with propertyIndex = true", is also correct. This index ensures that queries

filtering on the 'status' property are executed efficiently. The property index should be set to true,

which means that this property is indexed and the query will use this index to filter the results.

Option B is incorrect because setting the property index to false would mean that the property is not

indexed, making the query less efficient since the repository would need to scan each node to find

matches.

Option C, "nt:base aggregate", is not mandatory. Aggregates are used to include properties of related

nodes in the index, but they are not required for a simple property match like the one in the given

query.