You must run a short-lived data processing job using two tightly coupled containers: a worker and a log-forwarding sidecar. Both containers need to share files and securely connect to a private Redis cache hosted in an Azure virtual network. You want the simplest compute option with minimal management. What should you do? Choose two.

Running both containers in a single Azure Container Instances (ACI) container group with a shared Azure Files volume is correct because ACI is ideal for short-lived, tightly coupled container jobs requiring shared storage, and it offers minimal management. Deploying ACI into a delegated subnet for virtual network integration and assigning a private IP to the container group is correct because it allows secure access to the private Redis cache within the Azure virtual network. Deploying as a multi-container App Service Web App is incorrect as App Service is typically for longer-running web applications, not short-lived data processing jobs, and exposing Redis over a public IP is insecure. Provisioning an AKS cluster is incorrect because it introduces significant management overhead, which contradicts the requirement for the simplest compute option. Assigning a public IP with open ports on ACI is incorrect as it exposes the container group to the internet unnecessarily and does not provide secure access to a private Redis endpoint.