A containerized solution in Azure Container Instances includes a frontend container (App1) and a backend container (DB1). DB1 performs a lengthy data load on startup. You need to ensure DB1 is ready to handle requests before App1 accepts user traffic. Which container health mechanism should you configure?

A readiness probe is the correct choice because it determines if a container is ready to serve traffic. In this scenario, DB1 needs to complete its lengthy data load before App1 can successfully interact with it. A readiness probe on DB1 would prevent App1 from sending requests until DB1 signals it's ready, ensuring application stability. A liveness probe checks if a container is running and healthy, restarting it if it fails. It doesn't address the "ready to serve traffic" aspect. A performance log is for monitoring and analysis, not for controlling traffic flow based on container readiness. An Azure Load Balancer health probe checks the health of backend instances in a load balancer pool, but it operates at a higher network level and wouldn't directly manage the internal readiness of a specific container within an ACI container group.