Microsoft AZ-204

Incorrect. Although HTTP ingress is required for session affinity, multiple revision mode is not the correct revision setting for this requirement. Multiple revision mode is primarily used for traffic splitting and side-by-side revision deployments such as canary releases. The question asks specifically for support of session affinity, and the expected Azure Container Apps configuration is HTTP ingress with single revision mode.

Correct. Azure Container Apps session affinity is supported through HTTP ingress, because the platform uses HTTP-layer routing behavior to keep a client associated with the same backend replica. Single revision mode is the appropriate revision setting for this feature in the exam context. Even with a single active revision, the app can scale out to multiple replicas, and session affinity ensures repeat requests from the same client are routed consistently.

Incorrect. TCP ingress does not provide the HTTP-layer features needed for session affinity in Azure Container Apps. Sticky sessions rely on HTTP request handling rather than raw TCP forwarding. Multiple revision mode also does not compensate for the wrong ingress type, so this option fails because the protocol support is incorrect.

Incorrect. TCP ingress cannot be used for Azure Container Apps session affinity because the feature depends on HTTP ingress behavior. While single revision mode is the correct revision choice, the ingress type is still wrong. Since both parts of the configuration must be correct, this option is not valid.