aCI runs standalone container groups without maintaining an orchestration cluster. In this case, a one-off data conversion must be launched from a known image with environment variables. “Azure Container Instances (ACI)” would not satisfy that requirement; the supported action is “An Azure Container Instance with the required environment configuration”. ACI provides direct container execution with environment variable and image settings.

containers in one ACI group share the group lifecycle and associated network environment. In this case, a one-off data conversion must be launched from a known image with environment variables. “A multi-container container group” would not satisfy that requirement; the supported action is “An Azure Container Instance with the required environment configuration”. ACI provides direct container execution with environment variable and image settings.

runtime diagnostics reveal startup failures, image issues and container exit codes. In this case, a one-off data conversion must be launched from a known image with environment variables. “ACI container state, events and logs” would not satisfy that requirement; the supported action is “An Azure Container Instance with the required environment configuration”. ACI provides direct container execution with environment variable and image settings.

aCI runs standalone container groups without maintaining an orchestration cluster. In this case, a container team needs to inspect why a standalone instance exits immediately. “Azure Container Instances (ACI)” would not satisfy that requirement; the supported action is “ACI container state, events and logs”. Runtime diagnostics reveal startup failures, image issues and container exit codes.

removing a completed group cleans up the managed instance and its allocated resource definition. In this case, a container team needs to inspect why a standalone instance exits immediately. “The completed ACI container group” would not satisfy that requirement; the supported action is “ACI container state, events and logs”. Runtime diagnostics reveal startup failures, image issues and container exit codes.

containers in one ACI group share the group lifecycle and associated network environment. In this case, a container team needs to inspect why a standalone instance exits immediately. “A multi-container container group” would not satisfy that requirement; the supported action is “ACI container state, events and logs”. Runtime diagnostics reveal startup failures, image issues and container exit codes.

aCI runs standalone container groups without maintaining an orchestration cluster. In this case, a script must delete a finished short-lived container workload. “Azure Container Instances (ACI)” would not satisfy that requirement; the supported action is “The completed ACI container group”. Removing a completed group cleans up the managed instance and its allocated resource definition.

containers in one ACI group share the group lifecycle and associated network environment. In this case, a script must delete a finished short-lived container workload. “A multi-container container group” would not satisfy that requirement; the supported action is “The completed ACI container group”. Removing a completed group cleans up the managed instance and its allocated resource definition.

aCI provides direct container execution with environment variable and image settings. In this case, a script must delete a finished short-lived container workload. “An Azure Container Instance with the required environment configuration” would not satisfy that requirement; the supported action is “The completed ACI container group”. Removing a completed group cleans up the managed instance and its allocated resource definition.

ACI lacks the Container Apps revision and event-driven scaling feature set in the scenario. In this case, a microservice needs a managed Azure runtime with event-driven scale to zero, ingress and deployable revisions. “Azure Container Instances without a managed revision service” would not satisfy that requirement; the supported action is “Azure Container Apps”. Container Apps supports managed app revisions and scaling based on configured triggers.

Static hosting does not run a scalable long-lived microservice container. In this case, a microservice needs a managed Azure runtime with event-driven scale to zero, ingress and deployable revisions. “Azure Blob Storage static website hosting” would not satisfy that requirement; the supported action is “Azure Container Apps”. Container Apps supports managed app revisions and scaling based on configured triggers.

A standalone VM does not offer managed container revision and scale-to-zero capabilities. In this case, a microservice needs a managed Azure runtime with event-driven scale to zero, ingress and deployable revisions. “An ordinary Azure VM without autoscaling configuration” would not satisfy that requirement; the supported action is “Azure Container Apps”. Container Apps supports managed app revisions and scaling based on configured triggers.

A Layer-4 load balancer alone does not provision or manage the containerized API. In this case, a containerized public API needs managed HTTPS ingress from its Container Apps hosting platform. “A public Standard Load Balancer without a container hosting service” would not satisfy that requirement; the supported action is “Azure Container Apps HTTP ingress”. Managed ingress exposes eligible container apps over the configured endpoint and port.

ACR stores images but does not publish an HTTP API runtime endpoint. In this case, a containerized public API needs managed HTTPS ingress from its Container Apps hosting platform. “Azure Container Registry alone” would not satisfy that requirement; the supported action is “Azure Container Apps HTTP ingress”. Managed ingress exposes eligible container apps over the configured endpoint and port.

File shares provide storage, not container HTTP ingress. In this case, a containerized public API needs managed HTTPS ingress from its Container Apps hosting platform. “An Azure Files NFS share” would not satisfy that requirement; the supported action is “Azure Container Apps HTTP ingress”. Managed ingress exposes eligible container apps over the configured endpoint and port.

container Apps supports managed app revisions and scaling based on configured triggers. In this case, an event-processing service must add replicas when a supported queue workload grows. “Azure Container Apps” would not satisfy that requirement; the supported action is “Container Apps scaling rules for the event source”. Scale rules tie replica count to workload or event metrics, depending on the scaler.

container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks. In this case, an event-processing service must add replicas when a supported queue workload grows. “Azure Container Apps for managed revisions and scaling” would not satisfy that requirement; the supported action is “Container Apps scaling rules for the event source”. Scale rules tie replica count to workload or event metrics, depending on the scaler.

revisions preserve deployment versions so traffic can be redirected when supported. In this case, an event-processing service must add replicas when a supported queue workload grows. “An earlier Container Apps revision if retained and available” would not satisfy that requirement; the supported action is “Container Apps scaling rules for the event source”. Scale rules tie replica count to workload or event metrics, depending on the scaler.

container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks. In this case, a new container revision should receive a small traffic fraction before full promotion. “Azure Container Apps for managed revisions and scaling” would not satisfy that requirement; the supported action is “Container Apps multiple revisions with controlled traffic weights”. Revision traffic splitting supports staged delivery and rollback in supported revision modes.

revisions preserve deployment versions so traffic can be redirected when supported. In this case, a new container revision should receive a small traffic fraction before full promotion. “An earlier Container Apps revision if retained and available” would not satisfy that requirement; the supported action is “Container Apps multiple revisions with controlled traffic weights”. Revision traffic splitting supports staged delivery and rollback in supported revision modes.

container Apps supports managed app revisions and scaling based on configured triggers. In this case, a new container revision should receive a small traffic fraction before full promotion. “Azure Container Apps” would not satisfy that requirement; the supported action is “Container Apps multiple revisions with controlled traffic weights”. Revision traffic splitting supports staged delivery and rollback in supported revision modes.

container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks. In this case, two Container Apps should communicate privately within the same managed environment. “Azure Container Apps for managed revisions and scaling” would not satisfy that requirement; the supported action is “Environment networking and internal ingress settings”. Container Apps environments and ingress controls govern app-to-app access and public exposure.

managed ingress exposes eligible container apps over the configured endpoint and port. In this case, two Container Apps should communicate privately within the same managed environment. “Azure Container Apps HTTP ingress” would not satisfy that requirement; the supported action is “Environment networking and internal ingress settings”. Container Apps environments and ingress controls govern app-to-app access and public exposure.

when configured for zero minimum replicas, eligible services may suspend active replicas until triggered. In this case, two Container Apps should communicate privately within the same managed environment. “Autoscaling has scaled the app to zero after inactivity” would not satisfy that requirement; the supported action is “Environment networking and internal ingress settings”. Container Apps environments and ingress controls govern app-to-app access and public exposure.

container Apps supports managed app revisions and scaling based on configured triggers. In this case, a service needs to roll back quickly after a bad new container image. “Azure Container Apps” would not satisfy that requirement; the supported action is “An earlier Container Apps revision if retained and available”. Revisions preserve deployment versions so traffic can be redirected when supported.

revision traffic splitting supports staged delivery and rollback in supported revision modes. In this case, a service needs to roll back quickly after a bad new container image. “Container Apps multiple revisions with controlled traffic weights” would not satisfy that requirement; the supported action is “An earlier Container Apps revision if retained and available”. Revisions preserve deployment versions so traffic can be redirected when supported.

managed ingress exposes eligible container apps over the configured endpoint and port. In this case, a service needs to roll back quickly after a bad new container image. “Azure Container Apps HTTP ingress” would not satisfy that requirement; the supported action is “An earlier Container Apps revision if retained and available”. Revisions preserve deployment versions so traffic can be redirected when supported.

container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks. In this case, a Container Apps service has a minimum replica count of zero and appears idle. “Azure Container Apps for managed revisions and scaling” would not satisfy that requirement; the supported action is “Autoscaling has scaled the app to zero after inactivity”. When configured for zero minimum replicas, eligible services may suspend active replicas until triggered.

container Apps supports managed app revisions and scaling based on configured triggers. In this case, a Container Apps service has a minimum replica count of zero and appears idle. “Azure Container Apps” would not satisfy that requirement; the supported action is “Autoscaling has scaled the app to zero after inactivity”. When configured for zero minimum replicas, eligible services may suspend active replicas until triggered.

container Apps environments and ingress controls govern app-to-app access and public exposure. In this case, a Container Apps service has a minimum replica count of zero and appears idle. “Environment networking and internal ingress settings” would not satisfy that requirement; the supported action is “Autoscaling has scaled the app to zero after inactivity”. When configured for zero minimum replicas, eligible services may suspend active replicas until triggered.

ACI is suitable for short-lived groups but lacks the desired managed revision and HTTP autoscaling features. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “Azure Container Instances for one-off jobs” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.

Blob storage does not run a continuously managed HTTP microservice. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “A new Azure Storage blob container” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.

An individual VM does not provide managed Container Apps revision/scaling features. In this case, a continuously managed HTTP container service needs revisions and event-driven autoscaling. “An Azure VM with a manually restarted process” would not satisfy that requirement; the supported action is “Azure Container Apps for managed revisions and scaling”. Container Apps supplies application-oriented ingress, revisions and scale rules that standalone ACI lacks.