An organization requires the deployment of three independent workloads using Azure Container Instances (ACI). Which container restart policy should be matched to each workload scenario to align with the specified operational requirements?
- A telemetry collector that continuously listens for incoming IoT device data and must automatically recover if the container agent experiences a fault.Restart policy set to Always
- A daily data validation utility that executes a check, reports status, and must restart only if the validation run terminates with an error code.Restart policy set to OnFailure
- A data migration script designed to perform a one-time database schema upgrade and must not run again under any circumstances after its execution completes.Restart policy set to Never
Cevap
Match the telemetry collector to 'Restart policy set to Always', the daily data validation utility to 'Restart policy set to OnFailure', and the data migration script to 'Restart policy set to Never'.
Matching the continuous telemetry collector with the Always restart policy ensures it recovers from faults. Matching the daily validation utility with the OnFailure policy ensures it completes once successfully but retries if it fails. Matching the database schema upgrade with the Never policy prevents unintended execution attempts.
Adım Adım Çözüm
Anahtar Kavram
Azure Container Instances (ACI) supports three restart policies: Always, OnFailure, and Never. Always is for continuous services, OnFailure is for run-to-completion tasks that need retry logic on error, and Never is for one-time tasks that must not run again.