Exam AZ-104 topic 5 question 150 discussion

I've just tried to create a new Windows container with private networking and was successfull. The notification about private networking not being available to Windows is gone as well.

Okay how is this supposed to determine that I can be a solutions architect?

For all saying B, check the link. Don't misguide before researching https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal Correct answer is D: OS type (Previous comment I said B is correct by mistake in the end. ignore it) :-)

For all saying B, check the link. Don't misguide before researching https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal Correct answer is B: OS type

B should be the correct answer

It might have been LInux only some time back, but not any more. Was able to create a Windows one in the lab. and saw the options and it says the following: Choose between three networking options for your container instance: 'Public' will create a public IP address for your container instance. 'Private' will allow you to choose a new or existing virtual network for your container instance. 'None' will not create either a public IP or virtual network. You will still be able to access your container logs using the command line.

it´s D Switching to private networking is not available for Windows containers. Private networking is only supported for Linux containers. Therefore, to enable private networking you need to change the OS type from Windows to Linux.

On this link: https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png it is mentioned: "'Private': (...) this is not yet available for windows containers"

I believe the main keyword was missing in the question. see the details below to enable private networking for Azure Container Instances (ACI), you need to select the Premium SKU instead of the Standard SKU! The Standard SKU does not support private networking.

answer is : B Networking type

https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png

Azure Container Instances (ACI) support private networking, but there are specific limitations based on the OS type: Linux Containers: ACI supports private networking for Linux containers, allowing them to be deployed within a virtual network. Windows Containers: As of the latest updates, private networking for Windows containers is not supported. Current Configuration: OS type: Windows Required Configuration for Private Networking: OS type: Linux Correct Setting to Change: D. OS type By changing the OS type from Windows to Linux, you enable the option to use private networking for your Azure Container Instance. The other settings (Memory, Networking type, Number of CPU cores, SKU) do not impact the availability of the private networking feature. Thus, to ensure that cont1 can be configured to use private networking, you should change the OS type from Windows to Linux.

Private networking for Azure Container Instances is not supported for Windows containers. It is only supported for Linux containers. Other Options: Networking type: While you might like to change the networking type, the "Private" option is unavailable for Windows containers. So OS type is the answer. Ref: https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal

OS type Private network is not supported https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal

B is correct

D or B ?

D, OS type https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png