A tech company with multiple platform engineering teams needs to manage the different sandboxes within their Adobe Experience Platform (AEP). They…

Adobe Experience Platform (AEP) Sandboxes are the recommended feature for this scenario. Sandboxes are virtual partitions within a single AEP instance that isolate data, profiles, and other resources. This allows different platform engineering teams to develop and test applications, data models, and configurations independently without impacting the production environment or each other's work. Assigning different teams to different sandboxes provides the necessary segregation for development, testing, and production lifecycles, ensuring effective management and isolation of data and profiles across various services and teams.

A. The Data Lifecycle feature is used to manage data retention and schedule the deletion of datasets or records, not to segregate development environments.

C. The Data Governance Framework is used to manage how data can be used (e.g., for marketing), not to partition the platform for different teams.

D. Adobe Privacy Service is a tool for managing consumer data privacy requests (GDPR/CCPA), not for managing development sandboxes or team segregation.

1. Adobe Experience Platform Documentation, "Sandboxes: Sandboxes overview". The document states: "Sandboxes are virtual partitions within a single instance of Adobe Experience Platform, which allow for seamless integration with the development process of your digital experience applications... Sandboxes are used to isolate development environments and to help you manage the development lifecycle."

2. Adobe Experience Platform Documentation, "Sandboxes: Access control for sandboxes". This section explains how permissions and roles can be used to assign specific users (teams) to specific sandboxes, reinforcing their use for team segregation.