0
0
Azurecloud~10 mins

Container Apps scaling rules in Azure - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
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.
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.
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.
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.
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.