AZ-304 Exam QuestionsBrowse all questions from this exam

AZ-304 Exam - Question 187


You need to recommend a solution to deploy containers that run an application. The application has two tiers. Each tier is implemented as a separate Docker

Linux-based image. The solution must meet the following requirements:

✑ The front-end tier must be accessible by using a public IP address on port 80.

✑ The backend tier must be accessible by using port 8080 from the front-end tier only.

✑ Both containers must be able to access the same Azure file share.

✑ If a container fails, the application must restart automatically.

✑ Costs must be minimized.

What should you recommend using to host the application?

Show Answer
Correct Answer: C

Azure Container Instances (ACI) is the appropriate solution for deploying the given application with two Docker Linux-based images. ACI allows for the creation of container groups, enabling both containers to be managed together and share the same Azure file share, which satisfies the requirement for both containers to access the same storage. Additionally, ACI supports networking controls that allow the front-end container to be accessible via a public IP on port 80 and the backend container to be accessible on port 8080 from the front-end. ACI also includes restart policies such as 'OnFailure', ensuring the application restarts automatically if a container fails. Importantly, ACI is a cost-effective solution compared to other options like AKS or Azure Service Fabric, aligning with the requirement to minimize costs.

Discussion

14 comments
Sign in to comment
arseyam
Nov 28, 2020

Azure Container Instances is the correct answer. It has networking controls (public, private) and supports Restart policies set to "OnFailure" by default.

nicksu
Jul 20, 2021

I would say that when microsoft tells to use two containers - it would nearly always be the ACI, when there should be more containers or kind of orchestration, then it would be the AKS

gcpjay
Dec 13, 2020

The given answer is correct, but the reasoning is inadequate. We can have group both the container in an Azure Container Instance group and both can access the same Azure File share. https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groups

syu31svc
Oct 5, 2021

"two tiers" so 2 containers would do C is the answer

MaoLi
Sep 16, 2020

“Azure Container Service will be retired on January 31, 2020, and is no longer recommended for new resources." go with AKS

Florent44
Sep 18, 2020

Azure Container Instance is not the same thing as Azure Container Service so in this case the answer is ACI with container group : https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groups

StressiOlli
Nov 3, 2020

You have no clue.

jhoomtv
Dec 27, 2020

Given Answer is correct: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview Persistent storage; To retrieve and persist state with Azure Container Instances, we offer direct mounting of Azure Files shares backed by Azure Storage. Secondly has restart policy; https://docs.microsoft.com/en-us/azure/container-instances/container-instances-restart-policy

ArifUK
Dec 30, 2020

if anyone is interested, here's a comparison between ACI And AKS.

MumbaiIndians
Jan 4, 2021

bhai link toh dalta ??

milind8451
Jan 24, 2021

https://tutorialsdojo.com/azure-container-instances-aci-vs-azure-kubernetes-service-aks/

VincentZhang
Oct 8, 2021

You should use AKS if you need full container orchestration, such as service discovery across multiple containers, automatic scaling, and coordinated application upgrades.

Az_Sasi
Sep 20, 2020

Why not AKS? https://docs.microsoft.com/en-us/azure/container-instances/container-instances-overview For scenarios where you need full container orchestration, including service discovery across multiple containers, automatic scaling, and coordinated application upgrades, we recommend Azure Kubernetes Service (AKS).

Ragdoll
Sep 21, 2020

ACI is cheaper than AKS. In this case, both solutions can be used technically, but cost efficiency has to be considered as well.

ArifUK
Dec 30, 2020

says 'Cost must be minimized'. besides, the bells and whistles that come with AKS is not a requirement in the given scenario. ACI is just fine.

tmurfet
Oct 29, 2020

Example points the way: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groups

leo_az300
Sep 24, 2021

answer is correct. 2 containers in one Azure container group. xpose port 80. port 8080 is only for internal use. Both container can access Azure File Share in Azure container Group. Set up Restart Policy to OnFailure. Cost is less than other 2 options.

poplovic
Sep 27, 2021

ACI is correct. 1. Linux so we can use container group 2. Azure file share is very simple in ACI there is an example in MS doc https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groups

Tos_123
Oct 2, 2020

A Based on Microsoft AKS is the recommended solution for Linux containers https://docs.microsoft.com/en-us/dotnet/architecture/modernize-with-azure-containers/modernize-existing-apps-to-cloud-optimized/choosing-azure-compute-options-for-container-based-applications

Remco
Oct 3, 2020

I think Azur Container Instances is the better choice here. Also based on the article you are referring to. The deciding factor is costs. If there was some kind of elasticity in the question then I would agree with you. The article states that AKS is recommended for LINUX in case of micro services and that means having elasticity.

SHABS78
Oct 25, 2020

I believe it could be ACI

SHABS78
Oct 25, 2020

I believe it could be ACI

manderda
Oct 7, 2020

Why is Azure Service Fabric not possible?

ForYEO
Nov 19, 2020

pricy, same as AKS

BoxMan
Nov 10, 2020

Pretty certain it is correct with C. The item about "restart automatically" is what AKS/Orchestrators do and ACI doesn't. "Azure Container Instances enables a layered approach to orchestration, providing all of the scheduling and management capabilities required to run a single container, while allowing orchestrator platforms to manage multi-container tasks on top of it." from: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-orchestrator-relationship

BoxMan
Nov 10, 2020

A not C, my bad. AKS.

RandomUser
Nov 22, 2020

The documentation likes to contradict: https://docs.microsoft.com/de-de/azure/container-instances/container-instances-restart-policy "When you create a container group in Azure Container Instances, you can specify one of three restart policy settings." Always , Never, OnFailure

RandomUser
Nov 22, 2020

"If a container fails, the application must restart automatically." Not sure this requirement makes sense when taken literally, but in that case we'd reach a scenario that ACI can't handle. (Not sure AKS can but I see more chances over there.)

arseyam
Nov 28, 2020

ACI supports restart policy (by default is set to "OnFailure"). https://docs.microsoft.com/en-us/azure/container-instances/container-instances-restart-policy

levo017
Feb 18, 2021

AKS support container auto restart. Actually anything that 'orchestrate' container support container auto restart. But the answer is ACI for cost reason.

arseyam
Nov 28, 2020

ACI supports restart policy (by default is set to "OnFailure"). https://docs.microsoft.com/en-us/azure/container-instances/container-instances-restart-policy

levo017
Feb 18, 2021

AKS support container auto restart. Actually anything that 'orchestrate' container support container auto restart. But the answer is ACI for cost reason.

RandomUser
Nov 22, 2020

The documentation likes to contradict: https://docs.microsoft.com/de-de/azure/container-instances/container-instances-restart-policy "When you create a container group in Azure Container Instances, you can specify one of three restart policy settings." Always , Never, OnFailure

RandomUser
Nov 22, 2020

"If a container fails, the application must restart automatically." Not sure this requirement makes sense when taken literally, but in that case we'd reach a scenario that ACI can't handle. (Not sure AKS can but I see more chances over there.)

arseyam
Nov 28, 2020

ACI supports restart policy (by default is set to "OnFailure"). https://docs.microsoft.com/en-us/azure/container-instances/container-instances-restart-policy

levo017
Feb 18, 2021

AKS support container auto restart. Actually anything that 'orchestrate' container support container auto restart. But the answer is ACI for cost reason.

arseyam
Nov 28, 2020

ACI supports restart policy (by default is set to "OnFailure"). https://docs.microsoft.com/en-us/azure/container-instances/container-instances-restart-policy

levo017
Feb 18, 2021

AKS support container auto restart. Actually anything that 'orchestrate' container support container auto restart. But the answer is ACI for cost reason.