AZ-104 · Question #513
You create the following resources in an subscription: - An Azure Container Registry instance named Registry1 - An Azure Kubernetes Service (AKS) cluster named Cluster1 You create a container image…
The correct answer is C. Upload App1 to Registry1. To deploy a locally created container image to an Azure Kubernetes Service (AKS) cluster, the image must first be stored in a container registry.
Question
Options
- ARun the aa aks create command.
- BCreate a host pool on Cluster1
- CUpload App1 to Registry1.
- DRun the kubect1 apply command.
How the community answered
(24 responses)- A17% (4)
- B8% (2)
- C71% (17)
- D4% (1)
Why each option
To deploy a locally created container image to an Azure Kubernetes Service (AKS) cluster, the image must first be stored in a container registry.
The `az aks create` command is used to provision a new Azure Kubernetes Service cluster, not to deploy an application to an existing one.
A 'host pool' is a component of Azure Virtual Desktop, not directly relevant to deploying containerized applications to an Azure Kubernetes Service (AKS) cluster.
Before an Azure Kubernetes Service (AKS) cluster can deploy a container image, that image must be accessible from a container registry. Uploading `App1` to `Registry1` (an Azure Container Registry) makes the image available for `Cluster1` to pull and deploy.
The `kubectl apply` command is used to deploy a Kubernetes manifest to a cluster, but it requires the container image to already be available in a registry for the cluster to pull from; it's not the initial step if the image is only local.
Concept tested: Deploying container images to AKS using Azure Container Registry
Source: https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-docker-cli
Community Discussion
No community discussion yet for this question.