Explanation
AEM Assets HTTP API is a RESTful API that allows access to content fragments in JSON format without any customization. The API supports CRUD operations on content fragments and their variations, as well as querying and searching for content fragments based on metadata or full-text search.
References:https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/assets-api-content

Option B and Option D are two implementations that will support the HTL snippet. Option B uses the
@Model annotation with the adaptables parameter set to Resource.class. This allows the Sling Model to adapt from a resource object and access its properties using the ValueMap interface. Option B also uses the @Inject annotation with the name parameter set to "./text" to inject the value of the text property into the text field.
Option D uses the @Model annotation with the defaultInjectionStrategy parameter set to OPTIONAL. This allows the Sling Model to use optional injection for all fields and avoid null pointer exceptions if a property is missing. Option D also uses the @Inject annotation without any parameters to inject the value of the text property into the text field, using the field name as the default property name. References:
https://sling.apache.org/documentation/bundles/models.htmlhttps://experienceleague.adobe.com/docs/experience

Explanation
The IMS Lookup Tool is a tool that allows looking up Adobe Identity Management System (IMS) users by email and returning their IMS IDs. The IMS Lookup Tool is available in the Cloud Manager UI under the Tools menu. The IMS Lookup Tool can be used to find the IMS IDs of users who need to be added to Cloud Manager programs or environments. References:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager

Explanation
The recommended way to make the secret key available in the AEM application is to use an environment variable which is then consumed by an OSGi configuration. This way, the secret key is not stored in the code base or in the repository, but rather in a secure and encrypted way in the Cloud Manager environment variables. The OSGi configuration can use a placeholder to reference the environment variable and inject its value at runtime. References:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configurin

The Apache Jackrabbit Oak External Login Module and Apache Jackrabbit Oak Default Sync Handler are the two OSGi configurations that are required for LDAP integration in AEM. The External Login Module defines how AEM connects to the LDAP server and authenticates users against it. The Default Sync Handler defines how AEM synchronizes users and groups from the LDAP server to the repository.
References:https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/ldap-config.