Container Apps scaling rules in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the minimum number of container app replicas.

Azure

minReplicas: [1]

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

A1

B5

C10

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting minReplicas to a positive number prevents scaling down to zero.

Using a very high minReplicas wastes resources.

Setting minReplicas to 0 allows the container app to scale down to zero instances when idle.

2fill in blank

medium

Complete the code to set the maximum number of container app replicas.

Azure

maxReplicas: [1]

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

A1

B10

C0

D100

Attempts:

3 left

💡 Hint

Common Mistakes

Setting maxReplicas to 0 disables scaling up.

Setting maxReplicas too low limits app performance.

Setting maxReplicas to 10 limits the container app to scale up to 10 instances.

3fill in blank

hard

Fix the error in the CPU-based scaling rule threshold value.

Azure

cpu: [1]

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

A75

B1.5

C0.75

D-0.5

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0.75 instead of 75 (fraction instead of percentage) causes configuration errors.

Negative CPU values are invalid.

The CPU threshold should be a percentage between 0 and 100 representing % of CPU usage (e.g., 75).

4fill in blank

hard

Fill both blanks to configure HTTP request-based scaling with correct values.

Azure

http: {
  concurrency: [1],
  requestsPerSecond: [2]
}

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

A50

B100

C10

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping concurrency and requests per second values.

Setting concurrency too high causes overload.

Concurrency is set to 10 and requests per second to 100 for balanced scaling.

5fill in blank

hard

Fill all three blanks to define a scaling rule with CPU, memory, and HTTP triggers.

Azure

scalingRules: {
  cpuThreshold: [1],
  memoryThreshold: [2],
  httpRequests: [3]
}

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

A65

B80

C150

D90

Attempts:

3 left

💡 Hint

Common Mistakes

Using values greater than 100 for CPU or memory thresholds.

Confusing HTTP requests with CPU or memory thresholds.

CPU threshold is 65%, memory threshold 80%, and HTTP requests trigger at 150 requests per second.

Practice

1. What is the main purpose of scaling rules in Azure Container Apps?

easy

A. To automatically adjust the number of app instances based on demand

B. To manually restart the app when it crashes

C. To set the app's color theme

D. To limit the app's network bandwidth

Solution

1. Step 1: Understand scaling rules function

   Scaling rules help apps change the number of running instances automatically based on usage.

2. Step 2: Identify the correct purpose

   Among the options, only automatic adjustment of instances matches scaling rules' purpose.

3. Final Answer:

   To automatically adjust the number of app instances based on demand -> Option A

4. Quick Check:

   Scaling rules = auto adjust instances [OK]

Hint: Scaling rules control instance count automatically [OK]

Common Mistakes:

• Confusing scaling with manual restarts
• Thinking scaling changes app appearance
• Assuming scaling controls network limits

2. Which of the following is the correct JSON snippet to set a CPU-based scaling rule in Azure Container Apps?

easy

A. {"name":"cpu","type":"memory","metadata":{"value":"75"}}

B. {"name":"memory","type":"cpu","metadata":{"value":"75"}}

C. {"name":"cpu","type":"cpu","metadata":{"value":"75"}}

D. {"name":"requests","type":"http","metadata":{"value":"75"}}

Solution

1. Step 1: Identify correct metric type for CPU scaling

   The metric type must be "cpu" to scale based on CPU usage.

2. Step 2: Check JSON structure and metadata

   {"name":"cpu","type":"cpu","metadata":{"value":"75"}} correctly uses "cpu" type and sets a value of 75 for CPU percentage.

3. Final Answer:

   {"name":"cpu","type":"cpu","metadata":{"value":"75"}} -> Option C

4. Quick Check:

   CPU scaling JSON uses type "cpu" [OK]

Hint: CPU scaling uses type "cpu" in JSON metadata [OK]

Common Mistakes:

• Using wrong metric type like memory for CPU scaling
• Mixing HTTP request type with CPU
• Incorrect JSON key names

3. Given this scaling rule snippet:

{"name":"http","type":"http","metadata":{"concurrentRequests":"50"}}

What happens when the app receives 60 concurrent HTTP requests?

medium

A. The app scales out to add more instances

B. The app scales in to reduce instances

C. The app ignores the requests and crashes

D. The app blocks all requests above 50

Solution

1. Step 1: Understand the scaling trigger

   The rule triggers scaling when concurrent HTTP requests exceed 50.

2. Step 2: Analyze the scenario with 60 requests

   Since 60 > 50, the app will scale out by adding instances to handle load.

3. Final Answer:

   The app scales out to add more instances -> Option A

4. Quick Check:

   Requests > threshold triggers scale out [OK]

Hint: Requests above limit cause scale out [OK]

Common Mistakes:

• Thinking app scales in when load increases
• Assuming app crashes on overload
• Believing app blocks extra requests

4. You wrote this scaling rule JSON:

{"name":"cpu","type":"cpu","metadata":{"value":"abc"}}

What is the problem with this configuration?

medium

A. The JSON keys are misspelled

B. The type "cpu" is incorrect for CPU scaling

C. Scaling rules cannot use CPU metrics

D. The value for CPU threshold is not a valid number

Solution

1. Step 1: Check the value field in metadata

   The value should be a number representing CPU percentage, but "abc" is not numeric.

2. Step 2: Confirm type correctness

   The type "cpu" is correct, and keys are spelled properly.

3. Final Answer:

   The value for CPU threshold is not a valid number -> Option D

4. Quick Check:

   CPU value must be numeric [OK]

Hint: CPU threshold value must be a number [OK]

Common Mistakes:

• Using non-numeric strings for threshold values
• Changing correct type names
• Misspelling JSON keys

5. You want to configure an Azure Container App to scale between 2 and 10 instances based on CPU usage exceeding 70%. Which JSON snippet correctly sets the min and max replicas along with the CPU scaling rule?

hard

A. {"minReplicas": 10, "maxReplicas": 2, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]}

B. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]}

C. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "memory", "metadata": {"value": "70"}}]}

D. {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "http", "metadata": {"concurrentRequests": "70"}}]}

Solution

1. Step 1: Verify min and max replicas values

   Min replicas should be 2 and max replicas 10 as per requirement; {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} matches this correctly.

2. Step 2: Check scaling rule type and metadata

   The rule must be type "cpu" with value "70" for CPU usage threshold; {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} correctly sets this.

3. Final Answer:

   {"minReplicas": 2, "maxReplicas": 10, "rules": [{"name": "cpuRule", "type": "cpu", "metadata": {"value": "70"}}]} -> Option B

4. Quick Check:

   Min/max replicas correct and CPU rule set [OK]

Hint: Min < max replicas and type "cpu" for CPU scaling [OK]

Common Mistakes:

• Swapping min and max replica values
• Using wrong metric type like memory or http
• Incorrect metadata keys for CPU scaling