What is true of a Container Apps revision once it exists?
Why A is the answer
It is immutable
Microsoft says a revision remains unchangeable once established.
In detail
- A revision is immutable.
- A change creates a new revision.
- Immutability makes rollback simple.
Use case
An illustrative scenario, not a real incident.
A developer changes an environment variable, and Container Apps creates a new revision. The old one stays as it was.
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
stateDiagram-v2 state "Revision 1" as s0 state "Revision 2" as s1 state "Traffic moves" as s2 [*] --> s0 s0 --> s1: configuration change s1 --> s2 s2 --> [*]
Key point: Revisions are immutable.
Why the other options are wrong
- B. It only exists in the registry and never runs in an environment
- A revision runs in an environment.
- C. It can be edited in place, without creating anything new
- It cannot be edited in place.
- D. It is deleted as soon as the first request has been served
- It is not deleted after a request.