Container Apps for microservices in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a container app environment in Azure.

Azure

az containerapp env create --name myEnv --resource-group myResourceGroup --location [1]

Drag options to blanks, or click blank then click option'

AmyApp

BmyResourceGroup

Ccontainerapp

Deastus

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of a location.

Using the container app name instead of a location.

The --location parameter specifies the Azure region where the container app environment will be created. 'eastus' is a valid Azure region.

2fill in blank

medium

Complete the code to deploy a container app with a specified image.

Azure

az containerapp create --name myApp --resource-group myResourceGroup --environment myEnv --image [1]

Drag options to blanks, or click blank then click option'

AmyEnv

BmyResourceGroup

Cmcr.microsoft.com/azuredocs/containerapps-helloworld:latest

DmyApp

Attempts:

3 left

💡 Hint

Common Mistakes

Using the environment name instead of the image URL.

Using the resource group name instead of the image URL.

The --image parameter specifies the container image to deploy. It must be a valid container image URL, such as one from a container registry.

3fill in blank

hard

Fix the error in the command to scale the container app to 3 replicas.

Azure

az containerapp scale --name myApp --resource-group myResourceGroup --min-replicas [1]

Drag options to blanks, or click blank then click option'

A3

Bscale

Creplicas

DmyEnv

Attempts:

3 left

💡 Hint

Common Mistakes

Using the environment name instead of a number.

Using a command keyword instead of a number.

The --min-replicas parameter sets the minimum number of container app instances. To scale to 3 replicas, use '3'.

4fill in blank

hard

Fill both blanks to configure environment variables for the container app.

Azure

az containerapp update --name myApp --resource-group myResourceGroup --set configuration.[1][0].name=ENV_VAR configuration.[2][0].value=production

Drag options to blanks, or click blank then click option'

Asecrets

Benv

CenvironmentVariables

Dvariables

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'secrets' instead of 'environmentVariables'.

Using 'env' or 'variables' which are not valid properties here.

The environment variables are set under configuration.environmentVariables in the container app settings.

5fill in blank

hard

Fill all three blanks to create a container app with ingress enabled on port 80 and replicas set to 2.

Azure

az containerapp create --name myApp --resource-group myResourceGroup --environment myEnv --image myImage --ingress [1] --target-port [2] --min-replicas [3]

Drag options to blanks, or click blank then click option'

Aenabled

B80

C2

Ddisabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disabled' for ingress when enabling is needed.

Setting the wrong port number.

Setting replicas to 1 instead of 2.

To enable ingress, use 'enabled'. The target port is 80 for HTTP traffic. The minimum replicas set to 2 scales the app to two instances.

Practice

1. What is the main benefit of using Azure Container Apps for microservices?

easy

A. They let you run small parts of an app separately and scale them easily.

B. They require you to manage all the servers manually.

C. They combine all app parts into one big container.

D. They only work for apps without any updates.

Solution

1. Step 1: Understand microservices in Azure Container Apps

   Azure Container Apps allow running small, separate parts of an app independently.

2. Step 2: Identify the benefit of scaling and updating

   This setup lets you scale and update parts without affecting the whole app, and Azure manages the servers.

3. Final Answer:

   They let you run small parts of an app separately and scale them easily. -> Option A

4. Quick Check:

   Microservices = separate, scalable parts [OK]

Hint: Microservices run small parts separately for easy scaling [OK]

Common Mistakes:

• Thinking you must manage servers yourself
• Believing all parts run in one container
• Assuming no updates are possible

2. Which of the following is the correct way to define a container app in Azure CLI?

easy

A. az container create --name myapp --resource-group mygroup --image myimage:latest

B. az containerapp deploy --name myapp --resource-group mygroup --image myimage:latest

C. az appcontainer create --name myapp --resource-group mygroup --image myimage:latest

D. az containerapp create --name myapp --resource-group mygroup --image myimage:latest

Solution

1. Step 1: Identify the correct Azure CLI command for Container Apps

   The correct command to create a container app is az containerapp create.

2. Step 2: Check the command syntax

   The command includes the app name, resource group, and image, matching az containerapp create --name myapp --resource-group mygroup --image myimage:latest exactly.

3. Final Answer:

   az containerapp create --name myapp --resource-group mygroup --image myimage:latest -> Option D

4. Quick Check:

   Container Apps use 'az containerapp create' [OK]

Hint: Use 'az containerapp create' to define container apps [OK]

Common Mistakes:

• Using 'az container create' which is for regular containers
• Typing 'appcontainer' instead of 'containerapp'
• Using 'deploy' instead of 'create' command

3. Given this Azure CLI command:

az containerapp create --name orderservice --resource-group shoprg --image shop/orders:1.0 --cpu 0.5 --memory 1.0

What resource limits are set for this container app?

medium

A. 0.5 CPU cores and 1.0 GB memory

B. 1 CPU core and 0.5 GB memory

C. 0.5 CPU cores and 0.5 GB memory

D. 1 CPU core and 1.0 GB memory

Solution

1. Step 1: Read the CPU and memory flags in the command

   The command sets --cpu 0.5 and --memory 1.0.

2. Step 2: Interpret the values

   CPU is 0.5 cores, memory is 1.0 GB as per the flags.

3. Final Answer:

   0.5 CPU cores and 1.0 GB memory -> Option A

4. Quick Check:

   CPU=0.5, Memory=1.0 GB [OK]

Hint: Match --cpu and --memory values exactly [OK]

Common Mistakes:

• Swapping CPU and memory values
• Assuming units are in MB instead of GB
• Ignoring the flags and guessing defaults

4. You tried to deploy a container app with this command:

az containerapp create --name paymentapp --resource-group payrg --image pay/image:latest --cpu two --memory 1.5

What is the likely problem?

medium

A. The memory value 1.5 is too low; it must be at least 2 GB.

B. The CPU value 'two' is invalid; it should be a number like 2 or 0.5.

C. The image tag 'latest' is not allowed in Azure Container Apps.

D. The resource group name 'payrg' is invalid.

Solution

1. Step 1: Check the CPU parameter format

   The CPU value must be a number (like 0.5 or 2), not a word.

2. Step 2: Identify the error in the command

   Using 'two' instead of a numeric value causes a syntax error.

3. Final Answer:

   The CPU value 'two' is invalid; it should be a number like 2 or 0.5. -> Option B

4. Quick Check:

   CPU must be numeric [OK]

Hint: CPU must be a number, not a word [OK]

Common Mistakes:

• Using words instead of numbers for CPU
• Assuming 'latest' tag is invalid
• Thinking resource group name is the problem

5. You want to deploy a microservice architecture using Azure Container Apps with three services: frontend, backend, and database. You want each to scale independently and update without downtime. Which approach is best?

hard

A. Deploy only the frontend as a container app and run backend and database on VMs.

B. Combine all services into one container app to simplify management.

C. Deploy each service as a separate container app with its own scaling rules.

D. Use Azure Container Instances for all services instead of Container Apps.

Solution

1. Step 1: Understand microservice deployment goals

   Each service should scale independently and update without downtime.

2. Step 2: Evaluate deployment options

   Deploying each service as a separate container app allows independent scaling and updates.

3. Step 3: Rule out other options

   Combining services loses independent scaling; mixing VMs adds complexity; Container Instances lack built-in scaling features.

4. Final Answer:

   Deploy each service as a separate container app with its own scaling rules. -> Option C

5. Quick Check:

   Separate apps = independent scaling and updates [OK]

Hint: Separate container apps for each microservice [OK]

Common Mistakes:

• Combining all services in one container app
• Mixing container apps with VMs unnecessarily
• Using Container Instances which lack scaling