Microsoft Azure Architect Design (AZ-304) Practice Test

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Microsoft Azure Architect Design Test with our comprehensive questions and detailed explanations. Get ready to ace your exam with tailored study materials!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


Which Azure service should be used to facilitate automatic restarts of failed containers while keeping costs low?

  1. Azure Kubernetes Service (AKS)

  2. Azure Container Instances

  3. Azure App Services

  4. Azure Service Fabric

The correct answer is: Azure Container Instances

Using Azure Container Instances is a suitable choice for facilitating automatic restarts of failed containers while maintaining a focus on cost-effectiveness. Azure Container Instances allows you to quickly and easily deploy containers without needing to manage complex infrastructure, making it a simple solution for running applications in containers without the overhead of orchestrating multiple services. This service automatically handles the lifecycle of your containers, including restarts, to ensure that they remain operational. It is particularly beneficial for scenarios where you need to run stateless applications or batch jobs without the need for a full-scale orchestration platform, which can often incur higher costs due to additional resource management. In contrast, other options may not align as well with the requirement to keep costs low. For instance, Azure Kubernetes Service is more suitable for managing complex containerized applications and provides greater scalability and features that come with added costs associated with managing the Kubernetes infrastructure. Azure App Services is designed for web applications with built-in support for scaling, but it may include features that are unnecessarily robust for straightforward container deployments. Azure Service Fabric, while powerful for microservices and stateful applications, adds complexity and can be more costly compared to a straightforward solution like Azure Container Instances, particularly when limited resources and simplicity are desired.