A credit-union team wants a public demo Container App to call Dapr building blocks used by the production card-dispute API. They propose placing the demo in the same Container Apps environment so both apps can “share Dapr.” What should the developer do?
Select an answer to reveal the explanation.
Short Explanation
Picture the Container Apps environment as one locked office floor: everyone on that floor can find each other and share the same wiring. Stick a public demo on that floor and you just invited strangers into the production hallway. Put untrusted apps in their own environment instead.
Full Explanation
An Azure Container Apps environment is the isolation boundary for networking, service discovery, and shared observability features such as Dapr. Apps in the same environment can resolve and invoke one another; that is intentional for trusted microservices, not for mixing a public demo with a card-dispute API. Separating the demo into another environment keeps the production boundary intact without requiring AKS or ACI as a workaround.