Explanation
The recommended path to override /libs standard functionality is /apps. The /apps folder contains application-specific code and configuration that can extend or override the default functionality provided by
/libs. The /apps folder has precedence over the /libs folder, meaning that if there are two resources with the same path under both folders, the one under /apps will be used. References:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-proje

Explanation
The ui.config project, (/config/.../config.<runmode>) folder is the location where the OSGi configuration should be created for a runmode-specific configuration for an AEM as a Cloud Service implementation. The ui.config project contains OSGi configurations that are deployed to /apps in the repository. The config.<runmode> folder specifies the runmode for which the configuration is applicable, such as author or publish.
References:https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying

Explanation
The WorkflowProcess interface is the interface to be used for automatic workflow steps implemented in Java.
Classes implementing this interface define Java based processes that can be attached to a WorkflowNode and executed by the workflow engine. The method execute takes a WorkItem, a WorkflowSession and a MetaDataMap as parameters and performs the logic of the custom process step. References:
https://developer.adobe.com/experience-manager/reference-materials/6-5/javadoc/com/adobe/granite/workflow/e

Explanation
The Apache Sling Logging Logger Configuration and Apache Sling Logging Writer Configuration are the OSGi configurations that the developer should use to create a Logger and Writer pair for the company's application logging. The Logger Configuration defines the log level and the log file name for a given logger name or category. The Writer Configuration defines the file size, number of files, and file location for a given log file name.
References:https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configure-lo

Explanation
The /enableTTL "1" configuration must be applied to enable re-fetching of cached items based on Cache Headers sent by AEM. This configuration enables the Time To Live (TTL) feature of dispatcher, which allows dispatcher to check the Cache-Control and Expires headers of the cached files and re-fetch them from AEM if they are expired.
References:https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/page-inv