Examkin

Question

Difficulty: HardConfigure Azure Container Instances (ACI)

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

Answer

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.

Step-by-Step Solution

1
Analyze the uptime and operational requirements of the telemetry dashboard workload.
Identify that the dashboard is a continuous, user-facing application that must be kept running indefinitely.
For continuous services, Azure Container Instances (ACI) requires a restart policy that restarts the container if it stops for any reason, which corresponds to the Always policy.
2
Determine the execution lifecycle and failure-handling requirements of the nightly ETL pipeline.
Identify that the ETL pipeline is a batch workload that runs until completion and must only retry in the event of an execution failure.
The OnFailure restart policy ensures that ACI does not restart the container group upon successful completion (exit code 0) but will automatically restart it if it exits with an error (non-zero exit code).
3
Evaluate the execution constraints of the network discovery scan utility.
Determine that the scan must execute a maximum of one time and must not attempt automatic retries, regardless of whether the execution succeeded or failed.
The Never restart policy guarantees that the container group is never restarted by Azure once it exits, preventing duplicate executions.

Key Concept

Selecting and configuring the appropriate restart policy (Always, Never, or OnFailure) in Azure Container Instances based on workload execution characteristics.
Estimated Time:2m 0s
Rate this question

Topics

Configure Azure Container Instances (ACI)

More questions from this topic