Examkin

Soru

Zorluk: Çok zorRun Containerized Solutions using Azure Container Instances

You are deploying a multi-container group to Azure Container Instances (ACI) using a YAML deployment file. The deployment consists of an application container and a logging sidecar container. The container images are hosted in a private Azure Container Registry (ACR). The application requires persistent storage provided by an Azure File share, and must authenticate to ACR using a user-assigned managed identity to avoid storing credentials in the YAML file. Which two of the following configuration blocks must you include in the YAML deployment definition to satisfy these requirements? (Select two.)

  1. An 'identity' block at the container group root level with type 'UserAssigned' containing the managed identity's resource ID, and an 'imageRegistryCredentials' block specifying the ACR server and the identity's resource ID.Cevap
  2. A 'volumes' block at the container group root level specifying the 'azureFile' details (shareName, storageAccountName, and storageAccountKey), and a 'volumeMounts' block inside the container definitions specifying the volume name and mountPath.Cevap
  3. C
    An 'imageRegistryCredentials' block specifying the ACR server with the 'username' set to the managed identity's client ID and the 'password' set to a token retrieved from Azure Key Vault.
  4. D
    A 'volumes' block at the container group root level specifying a 'managedIdentity' volume type that references the storage account URI, and assigning a Key Vault Access Policy to allow the container group to retrieve the share credentials.

Cevap

To deploy the multi-container group with secure registry authentication and persistent storage, the YAML definition must contain a root-level identity block with the user-assigned identity resource ID coupled with an image registry credentials block pointing to that identity. Additionally, the Azure File share must be declared in a volumes block at the root and mapped to a volumeMounts block within the containers.
To pull container images from a private ACR using a user-assigned managed identity, the container group must have the identity enabled at the root level and referenced in the registry credentials block. To mount an Azure File share, the volume must be defined at the container group root level with the required storage account credentials and referenced in the container definitions under volume mounts.

Adım Adım Çözüm

1
Define the user-assigned managed identity under the root-level 'identity' property of the container group.
The identity is successfully associated with the ACI deployment.
Enables ACI to use the managed identity for interactions with other Azure resources.
2
Configure the 'imageRegistryCredentials' section in the YAML to reference the ACR server and map the 'identity' field to the user-assigned managed identity's resource ID.
ACI can authenticate with ACR during the container creation phase.
Allows ACI to pull the private container images securely without embedding registry passwords in the YAML file.
3
Define the volume using the 'azureFile' driver under the root-level 'volumes' array of the container group.
The volume representing the Azure File share is defined for the container group.
Provides the backend storage credentials and share configuration necessary for mounting.
4
Add a 'volumeMounts' block to the containers that need access to the persistent storage, linking them to the defined volume name and directory path.
The container filesystem accesses the persistent share at the specified path.
Exposes the mounted volume to the container runtimes.

Anahtar Kavram

Multi-container group configuration in ACI involving secure registry authentication via managed identity and persistent volume mounts.
Bu soruyu puanla

Konular

Run Containerized Solutions using Azure Container Instances

Bu konudan daha fazla soru