You are planning the deployment of three separate enterprise workloads using Azure Container Instances (ACI). You need to configure the appropriate restart policy for each workload to ensure optimal behavior and cost efficiency. Match each workload requirement to the correct Container Instance restart policy configuration.
- A front-end dashboard application designed to display real-time telemetry metrics that must be highly available to administrators.Restart policy set to Always
- A nightly extract-transform-load (ETL) pipeline that processes a queue of log files and should only retry if it terminates with an error code.Restart policy set to OnFailure
- A custom diagnostic utility that runs a network discovery scan and must be prevented from executing again, even if it fails due to network timeouts, to avoid duplicate firewall alerts.Restart policy set to Never
Cevap
The telemetry dashboard matches the Always restart policy. The nightly ETL pipeline matches the OnFailure restart policy. The network discovery scan matches the Never restart policy.
The telemetry dashboard is a continuous application requiring Always to ensure high availability. The nightly ETL pipeline is a batch task that needs to run to completion and retry only on failure, matching OnFailure. The network discovery scan must run only once and never retry, matching Never.
Adım Adım Çözüm
Anahtar Kavram
Selecting and configuring the appropriate restart policy (Always, Never, or OnFailure) in Azure Container Instances based on workload execution characteristics.
Tahmini Süre:2m 0s