You must test a new version on 10% of traffic in Container Apps. What do you use?
Why B is the answer
Revisions with traffic splitting
Revisions are immutable snapshots of a version, and traffic can be split between them.
In detail
- Traffic splitting sends a share of requests to a new revision.
- Watch error rates during the split.
Use case
An illustrative scenario, not a real incident.
A team sends 10% of traffic to a new revision. Errors stay low, so it raises the share, and rollback is one change away.
See it in different ways
flowchart LR A["Ingress"] -->|"90%"| B["Revision 1"] A -->|"10%"| C["Revision 2"]
sequenceDiagram participant U as Users participant I as Ingress participant A as Revision 1 participant B as Revision 2 U->>I: Requests I->>A: 90 percent I->>B: 10 percent
flowchart LR S0["Create revision"] --> S1["Send 10%"] --> S2["Watch metrics"] --> S3["Send 100%"]
Key point: Revisions with traffic splitting test safely.
Why the other options are wrong
- A. A longer health probe on the existing container in the same revision
- A health probe checks health, and does not route traffic.
- C. Two separate Azure subscriptions, with a manual switch between them
- Separate subscriptions cannot split traffic.
- D. A second registry that holds the same image under another name
- A second registry changes nothing about traffic.