AZ-204 Develop Azure compute solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use environment variables in the container group

  Why it's wrong here

  Azure Container Instances (ACI) allows you to define environment variables directly within the container group definition. These variables are injected into the container at startup and are accessible by the application running inside. To update the configuration, you simply modify the environment variable values in the ACI container group definition and then restart the container group. This approach provides a straightforward and effective method for runtime configuration changes without altering the container image itself.

• ✓

  Mount an Azure Files share and update the configuration file

  Why this is correct

  While Azure Container Instances supports mounting Azure Files shares as volumes, simply updating a configuration file on the mounted share does not automatically trigger a configuration refresh within the running container. The application inside the container would need to implement specific logic to continuously monitor the file for changes or be restarted to re-read the updated configuration. This method introduces additional complexity and does not provide a truly dynamic, out-of-the-box configuration update mechanism for ACI.

• ✗

  Use Application Settings in the container

  Why it's wrong here

  Application Settings are a specific feature primarily associated with Azure App Service, providing a managed way to inject configuration into web applications. Azure Container Instances, however, does not natively support "Application Settings" in the same manner as App Service. ACI is a more fundamental container hosting service, and its configuration mechanisms are typically handled through environment variables, command-line arguments, or mounted volumes, rather than App Service-specific settings.

• ✗

  Modify the container image to include new configuration

  Why it's wrong here

  Modifying the container image to embed new configuration values necessitates a complete rebuild of the Docker image. After rebuilding, the new image must then be pushed to a container registry and the Azure Container Instance must be updated to pull and run this new image. This process is time-consuming and resource-intensive, making it unsuitable for dynamic or frequent configuration updates at runtime, as it fundamentally changes the deployed artifact rather than just its operational parameters.