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 Deployment Manager is a role that can configure or run pipelines in Cloud Manager. The Deployment Manager can create and edit programs and environments, configure pipelines, start and cancel pipeline executions, and approve or reject deployments to production. The Deployment Manager role requires an IMS ID that is associated with the Adobe Experience Cloud product profile. References:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/using-cloud-manager

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
A mock framework is a tool that allows creating mock objects that simulate the behavior of real objects in a controlled way. A mock framework can be used in a unit test to inject the EmployeeService dependency into the CalculationService and verify its interactions. This way, the unit test can focus on testing the logic of the CalculationService without relying on the actual implementation of the EmployeeService. References:
https://sling.apache.org/documentation/development/sling-testing-tools.htmlhttps://wcm.io/testing/aem-mock/usa

Explanation
The embed property of the cq:ClientLibraryFolder node allows embedding code from a client library into another client library. At runtime, the generated JS and CSS files of the embedding library include the code of the embedded library. This reduces the number of network calls and improves performance. Embedding code is useful for providing access to libraries that arestored in secured areas of the repository. References:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/fu