You are deploying an Orders microservice to Azure Container Apps. You need to send 10% of external HTTP traffic to a new v2 revision while keeping 90% on v1. You also want your microservices to share the same VNet integration and Log Analytics workspace. What should you do?

The correct approach is to deploy both microservices into the same Container Apps environment, set the Orders app to multiple revisions mode, and configure a 90/10 traffic split between v1 and v2. Azure Container Apps natively supports traffic splitting across multiple revisions of a single container app, making it ideal for A/B testing or gradual rollouts. Placing them in the same environment ensures they share the same VNet integration and Log Analytics workspace, fulfilling the requirements. Creating separate environments is incorrect because it would prevent sharing VNet integration and Log Analytics. Single revision mode does not support traffic splitting between different versions. Deploying v2 as a separate Container App would also not allow for native traffic splitting within the same logical application and would complicate resource sharing.