@swapnildesai26 Check this article about Hybrid approach  https://engineering.deptagency.com/achieving-agility-and-flexibility-with-aem-hybrid-implementation

@TapasMahalik  There isn't a built-in feature to download all schemas at once from UI, you need to use the Schema Registry API to retrieve schema https://experienceleague.adobe.com/en/docs/experience-platform/xdm/api/getting-started  

@RoyWalter I found this guide about creating asset reports which might help your use case.https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/administer/asset-reports

@AudreyBr2 Check this user guide about link tracking with Adobe analyticshttps://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/integration/adobeanalytics-link#sending-variable-data-with-link-clicks

@kchaura Got it. For that I see an example for selector deny in this guide, can you check that. This might be similar to what Anil has provided using "/selectors" filter https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration#example-filter...

@kchaura Can you check the order in which deny and allow are added? Did you add deny first and allow later? Also there is an earlier question related to this which Arun answered.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/disable-jcr-content-json-from-url-on-publisher-i...

There is "Computed attributes" which is in beta which might help you. "Computed attributes are functions used to aggregate event-level data into profile-level attributes. These functions are automatically computed so that they can be used across segmentation, activation, and personalization." Check ...

@TapasMahalik In order to receive alerts, the email address needs to be registered to an Adobe account. So, I don't think it is possible to receive alerts with DL. Check this endpoint guide for more clarificationhttps://experienceleague.adobe.com/en/docs/experience-platform/query/api/alert-subscript...

@IswarenSiman  This is expected as the profile update occurs in memory during the journey execution and is not persisted to the underlying dataset. Check the below excerpt from the documentation https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-bui...

@ribhubanerjee I see there is a API guide which might be useful https://experienceleague.adobe.com/en/docs/experience-platform/profile/api/overview