A company has a containerized data-validation application packaged as a Docker image. The application processes batch files exported from a database once per day, taking approximately 10 minutes to complete. The application must write its output directly to a shared directory that is accessible by other systems, and it must exit immediately after finishing. If the application terminates with an error code, it must attempt to rerun.
You need to deploy the application using Azure Container Instances (ACI).
Which configuration settings should you apply to the container group?
- Set the restart policy to OnFailure and mount an Azure File share as a volume inside the container group.Cevap
- BSet the restart policy to Always and mount an Azure File share as a volume inside the container group.
- CSet the restart policy to OnFailure and configure the container to authenticate to the storage account using only the Subscription Owner RBAC role.
- DSet the restart policy to OnFailure and install the Azure File Sync agent inside the container to synchronize output files.
Cevap
Set the restart policy to OnFailure and mount an Azure File share as a volume inside the container group.
The correct option specifies setting the restart policy to OnFailure, ensuring the container group only restarts if it terminates with a non-zero exit code. It also correctly specifies mounting an Azure File share as a volume, which provides a shared, persistent storage directory accessible by other systems.
Adım Adım Çözüm
Anahtar Kavram
Configuring ACI restart policies and persistent volume mounts.