A botanical-garden ticketing API on Azure Container Apps must send 10 percent of live HTTP traffic to a new build while 90 percent stays on the last good revision. Which approach meets the requirement?
Select an answer to reveal the explanation.
Short Explanation
Revisions are like labeled batches of tickets at the garden gate—you can let a few visitors try the new batch while most still use the proven one. Traffic weights on Container Apps revisions give you that split. ACI restarts and App Service slots are different hosts with different knobs.
Full Explanation
Azure Container Apps creates a revision for each versioned deployment snapshot of an app. You can keep multiple revisions active and assign HTTP traffic percentages for blue/green or canary rollouts. Restarting an ACI container or swapping an App Service slot does not configure Container Apps revision traffic, and revisions are not an Azure Container Registry feature.