The recommended approach to use AEM Core Components is by creating proxy components. Proxy components are essentially wrapper components within your own project that reference the core components. This practice allows developers to inherit functionality from the core components while being able to override and extend it as necessary. By using proxy components, developers can ensure that any custom styles and configurations are preserved even when the core components are updated in the future.

In Adobe Experience Manager (AEM), when dealing with live copies, a content author must be aware of various factors related to the synchronization of content between the source (blueprint) and the live copies. Option A is correct because when inheritance is re-enabled on a live copy page, synchronization with the blueprint page occurs, which may include automatic updates to the live copy page's content. Option D is also correct because local changes made to a component marked as a container are protected during rollouts, meaning that these local changes will not be overwritten by content from the blueprint. The container concept in AEM allows for more granular control over which parts of the page are updated during synchronization.

For Option B, the term 'paragraph system' seems incorrect. It should likely refer to 'paragraph systems' as in the ParSys (Paragraph System), a component that allows authors to add components to a page. There is no automatic restoration of the order of components from the blueprint upon re-enabling canceled inheritance; instead, components are managed according to the rules set in the rollout configurations.

Option C is incorrect because the cancel and suspend actions can be applied to individual child components within a container. When inheritance is canceled for a container, the inheritance status of child components within that container can be controlled individually.

In AEM, Lucene is often used for indexing due to its powerful full-text search capabilities, and it also supports asynchronous indexing. Asynchronous indexing allows the system to handle other tasks while indexing is being processed in the background, which can improve performance and scalability. This is especially useful when multiple properties need to be indexed without impacting the immediate response times of the system. Therefore, when a developer needs to enable the indexing of multiple properties asynchronously, a Lucene index is the most suitable choice.

In Sling Models, the @DefaultInjectionStrategy annotation is used to specify the strategy for injecting fields into the model. When setting it to DefaultInjectionStrategy.OPTIONAL , it indicates that all injected fields in the Sling Model are optional and the model will not fail to instantiate if a field cannot be injected. This is a class-level annotation that affects the default injection behavior of all fields within the Sling Model.

Option B is incorrect because requiredInjectionStrategy is not a valid annotation property in Sling Models.

Option C is incorrect because injectionStrategy is not specified at the class level; it is used on the field level with the @Inject annotation.

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.