Content refresh for ACI module

JeffKoMS · JeffKoMS · commit 8a464164cff1 · 2026-01-17T16:26:34.000-08:00
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/1-introduction.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/1-introduction.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/2-azure-container-instances-overview.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/2-azure-container-instances-overview.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore Azure Container Instances
   description: "Explore Azure Container Instances"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/2-azure-container-instances-overview.md)]
+  [!include[](includes/2-azure-container-instances-overview.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/3-run-azure-container-instances-cloud-shell.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/3-run-azure-container-instances-cloud-shell.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Deploy a container to Azure Container Instances using Azure CLI commands
   description: "Exercise - Deploy a container to Azure Container Instances using Azure CLI commands"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 15
 content: |
-  [!include[](includes/3-run-azure-container-instances-cloud-shell.md)]
+  [!include[](includes/3-run-azure-container-instances-cloud-shell.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/4-run-containerized-tasks-restart-policies.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/4-run-containerized-tasks-restart-policies.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Run containerized tasks with restart policies
   description: "Run containerized tasks with restart policies"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/4-run-containerized-tasks-restart-policies.md)]
+  [!include[](includes/4-run-containerized-tasks-restart-policies.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/5-set-environment-variables-azure-container-instances.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/5-set-environment-variables-azure-container-instances.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Set environment variables in container instances
   description: "Set environment variables in container instances"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/5-set-environment-variables-azure-container-instances.md)]
+  [!include[](includes/5-set-environment-variables-azure-container-instances.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/6-mount-azure-file-share-azure-container-instances.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/6-mount-azure-file-share-azure-container-instances.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Mount an Azure file share in Azure Container Instances
   description: "Mount an Azure file share in Azure Container Instances"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/6-mount-azure-file-share-azure-container-instances.md)]
+  [!include[](includes/6-mount-azure-file-share-azure-container-instances.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/7-knowledge-check.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/7-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Module assessment
   description: "Knowledge check"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -17,36 +17,58 @@ durationInMinutes: 3
 quiz:
   title: "Check your knowledge"
   questions:
-  - content: "Which of the following methods is recommended when deploying a multi-container group that includes only containers?"
+  - content: "When your deployment includes only container instances, which approach is recommended for deploying a multi-container group?"
     choices:
-    - content: "Azure Resource Management template"
+    - content: "Azure Resource Manager template"
       isCorrect: false
       explanation: "Incorrect. Due to the YAML format's more concise nature, a YAML file is recommended when your deployment includes only container instances."
     - content: "YAML file"
       isCorrect: true
       explanation: "Correct. Due to the YAML format's more concise nature, a YAML file is recommended when your deployment includes only container instances."
-    - content: "`az container creates` command"
+    - content: "Azure portal"
       isCorrect: false
-      explanation: "Incorrect. This command isn't specific to this scenario."
+      explanation: "Incorrect. This module recommends using a YAML file (or a Resource Manager template) for multi-container group deployments."
   - content: "What is the purpose of a restart policy in Azure Container Instances?"
     choices:
     - content: "To charge customers more for compute resources used while the container is running."
       isCorrect: false
-      explanation: "Incorrect. The restart policy is not related to charging customers more for compute resources."
+      explanation: "Incorrect. The restart policy isn't related to charging customers more for compute resources."
     - content: "To ensure that containers are never restarted, even if the process fails."
       isCorrect: false
       explanation: "Incorrect. The `Never` restart policy ensures that containers are run at most once, but it doesn't allow for restarting on failure."
     - content: "To specify when and how containers should be restarted, based on the desired behavior."
       isCorrect: true
       explanation: "Correct. The restart policy allows you to specify when and how containers should be restarted, based on the desired behavior. This can help optimize resource usage and ensure that tasks are completed successfully."
-  - content: "If you want to mount multiple volumes, what options are at your disposal for deployment?"
+  - content: "If you want to mount multiple volumes, what options are available for deployment?"
     choices:
     - content: "YAML file only"
       isCorrect: false
       explanation: "While YAML file is a viable option, you can also use Azure Resource Manager templates."
     - content: "Azure Resource Manager template and YAML file"
       isCorrect: true
       explanation: "Correct. To mount multiple volumes in a container instance, you must deploy using an Azure Resource Manager template or a YAML file."
-    - content: "Azure Resource Manager template and PowerShell"
+    - content: "Azure portal only"
       isCorrect: false
-      explanation: "While Azure Resource Manager templates are a viable option, you can't use PowerShell commands to directly mount multiple volumes."
+      explanation: "Incorrect. The module explains that mounting multiple volumes requires a template-based approach such as a YAML file or an Azure Resource Manager template."
+  - content: "When you need to pass a secret as an environment variable in Azure Container Instances, which option is supported?"
+    choices:
+    - content: "Define the variable in a YAML file by using `secureValue`"
+      isCorrect: true
+      explanation: "Correct. Azure Container Instances supports secure environment variables in YAML by using the `secureValue` property."
+    - content: "Define the variable by using `--environment-variables` and expect the value to be visible in `az container show` output"
+      isCorrect: false
+      explanation: "Incorrect. Secure environment variable values aren't shown in container properties output. The secure value is accessible only from within the container."
+    - content: "Bake the secret into the container image and retrieve it from the file system at runtime"
+      isCorrect: false
+      explanation: "Incorrect. Baking secrets into an image isn't a recommended approach because it increases the chance of accidental disclosure and makes rotation harder."
+  - content: "Which statement about mounting an Azure Files share in Azure Container Instances is correct?"
+    choices:
+    - content: "You can mount Azure Files shares only to Linux containers"
+      isCorrect: true
+      explanation: "Correct. Azure Container Instances supports mounting Azure Files shares only for Linux containers."
+    - content: "You can mount Azure Files shares to Windows containers"
+      isCorrect: false
+      explanation: "Incorrect. This module notes that Azure Files share mounting in Azure Container Instances is supported only for Linux containers."
+    - content: "You can mount Azure Files over SMB by using managed identity"
+      isCorrect: false
+      explanation: "Incorrect. Azure Storage doesn't support SMB mounting of an Azure file share by using managed identity in this scenario."
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/8-summary.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/8-summary.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/8-summary.md)]
+  [!include[](includes/8-summary.md)]
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/2-azure-container-instances-overview.md b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/2-azure-container-instances-overview.md
@@ -35,7 +35,7 @@ There are two common ways to deploy a multi-container group: use a Resource Mana
 
 ## Resource allocation
 
-Azure Container Instances allocates resources such as CPUs, memory, and optionally GPUs (preview) to a container group by adding the resource requests of the instances in the group. If you create a container group with two instances, each requesting one CPU, then the container group is allocated two CPUs.
+Azure Container Instances allocates resources such as CPUs and memory to a container group by adding the resource requests of the instances in the group. If you create a container group with two instances, each requesting one CPU, then the container group is allocated two CPUs.
 
 ## Networking
 
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/4-run-containerized-tasks-restart-policies.md b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/4-run-containerized-tasks-restart-policies.md
@@ -6,7 +6,7 @@ With a configurable restart policy, you can specify that your containers are sto
 
 When you create a container group in Azure Container Instances, you can specify one of three restart policy settings.
 
-Restart policy | Description 
+Restart policy | Description
 - | -
 `Always` | Containers in the container group are always restarted. This is the **default** setting applied when no restart policy is specified at container creation.
 `Never` | Containers in the container group are never restarted. The containers run at most once.
@@ -26,4 +26,4 @@ az container create \
 
 ## Run to completion
 
-Azure Container Instances starts the container, and then stops it when its application, or script,  exits. When Azure Container Instances stops a container whose restart policy is `Never` or `OnFailure`, the container's status is set to **Terminated**.
+Azure Container Instances starts the container, and then stops it when its application, or script, exits. When Azure Container Instances stops a container whose restart policy is `Never` or `OnFailure`, the container's status is set to **Terminated**.
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/5-set-environment-variables-azure-container-instances.md b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/5-set-environment-variables-azure-container-instances.md
@@ -8,14 +8,14 @@ In the following example, two variables are passed to the container when it's cr
 az container create \
     --resource-group myResourceGroup \
     --name mycontainer2 \
-    --image mcr.microsoft.com/azuredocs/aci-wordcount:latest 
+    --image mcr.microsoft.com/azuredocs/aci-wordcount:latest \
     --restart-policy OnFailure \
-    --environment-variables 'NumWords'='5' 'MinLength'='8'\
+    --environment-variables 'NumWords'='5' 'MinLength'='8'
 ```
 
 ## Secure values
 
-Objects with secure values are intended to hold sensitive information like passwords or keys for your application. Using secure values for environment variables is both safer and more flexible than including it in your container's image. 
+Objects with secure values are intended to hold sensitive information like passwords or keys for your application. Using secure values for environment variables is both safer and more flexible than including it in your container's image.
 
 Environment variables with secure values aren't visible in your container's properties. Their values can be accessed only from within the container. For example, container properties viewed in the Azure portal or Azure CLI display only a secure variable's name, not its value.
 
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/6-mount-azure-file-share-azure-container-instances.md b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/includes/6-mount-azure-file-share-azure-container-instances.md
@@ -2,9 +2,9 @@ By default, Azure Container Instances are stateless. If the container crashes or
 
 ## Limitations
 
-* You can only mount Azure Files shares to Linux containers. 
+* You can only mount Azure Files shares to Linux containers.
 * Azure file share volume mount requires the Linux container run as *root*.
-* Azure File share volume mounts are limited to CIFS support.
+* Azure file share volume mounts are limited to CIFS support.
 
 ## Deploy container and mount volume
 
@@ -60,7 +60,7 @@ properties:
   volumes:
   - name: filesharevolume
     azureFile:
-      sharename: acishare
+      shareName: acishare
       storageAccountName: <Storage account name>
       storageAccountKey: <Storage account key>
 tags: {}
@@ -70,7 +70,7 @@ type: Microsoft.ContainerInstance/containerGroups
 
 To mount multiple volumes in a container instance, you must deploy using an Azure Resource Manager template or a YAML file. To use a template or YAML file, provide the share details and define the volumes by populating the `volumes` array in the `properties` section of the template.
 
-For example, if you created two Azure Files shares named *share1* and *share2* in storage account *myStorageAccount*, the `volumes` array in a Resource Manager template would appear similar to the following:
+For example, if you created two Azure Files shares named *share1* and *share2* in storage account *myStorageAccount*, the `volumes` array in a Resource Manager template would appear similar to the following example:
 
 ```json
 "volumes": [{
diff --git a/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/index.yml b/learn-pr/wwl-azure/create-run-container-images-azure-container-instances/index.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Run Container Images in Azure Container Instances
   description: "Run container images in Azure Container Instances"
-  ms.date: 06/17/2025
+  ms.date: 01/15/2024
   author: JeffKoMS
   ms.author: jeffko
   ms.topic: module-standard-task-based
