You have an Azure subscription.
You are creating a new Azure container instance that will have the following settings:
• Container name: cont1
• SKU: Standard
• OS type: Windows
• Networking type: Public
• Memory (GiB): 2.5
• Number of CPU cores: 2
You discover that the Private setting for Networking type is unavailable.
You need to ensure that cont1 can be configured to use private networking.
Which setting should you change?
To ensure that the Azure container instance can be configured to use private networking, you need to change the OS type. Private networking for Azure Container Instances is only supported for Linux containers and not for Windows containers. The restriction on private networking applies specifically to the OS type, making it necessary to switch from a Windows-based container to a Linux-based container.
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.
Yes, it's true. I checked and I confirm that the notification about the unavailability of the private network for Windows has disappeared.
Okay how is this supposed to determine that I can be a solutions architect?
OS type Private network is not supported https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal
chatgpt: To configure cont1 to use private networking, you need to change the Networking type. Specifically, switch from Public networking to Private networking. Here’s the adjustment you should make: Change the Networking type from Public to Private. By doing this, cont1 will be configured to use private networking, ensuring that it is accessible only within the specified private network.
This article is out of date probably, 07/28/2022. I've submitted the feedback. I created a container and " Windows not supported" is gone.
D OS TYPE Currently https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png
https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png
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.
D, OS type https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png
D: OS TYPE Private networking is Not supported yet for Windows containers In this link of the documentation we can see that in the networking section, there is a comment that says "Private: this is not yet available for windows containers" https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal
The page you shared doesn't mention what you just stated. Where is Mlantonis?
Correction: you are right. It's on the picture, so you can not search on the page. But you are correct. OS Type is the answer
are yyou sure?`
Yes bro, because private networking is not supported for Windows containers.
D, OS type https://learn.microsoft.com/en-us/azure/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png
Correct: B. Networking type choose option "Networking type:" Private https://learn.microsoft.com/en-us/azure/container-instances/container-instances-quickstart-portal
Incorrect. the page tells you "Private: this is not yet available for windows containers". Just the picture where they choose the tenant.
answer is : B Networking type
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.
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
B is correct
D or B ?
Answer: D Private networking is Not supported yet for Windows containers