Container Apps scaling rules in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

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

Scaling rules automatically adjust the number of container instances based on demand to ensure performance and cost efficiency.

beginner

Name two types of triggers that can be used in Container Apps scaling rules.

CPU usage and HTTP request count are common triggers for scaling Container Apps.

intermediate

How does a 'minReplicas' setting affect Container Apps scaling?

It sets the minimum number of container instances to keep running, even when demand is low.

intermediate

What happens if the scaling rule threshold is not met in Azure Container Apps?

The number of container instances remains the same or scales down to the minimum replicas if demand decreases.

beginner

Explain the difference between 'scale out' and 'scale in' in Container Apps scaling rules.

'Scale out' means increasing container instances when demand rises; 'scale in' means decreasing instances when demand falls.

Which metric can trigger scaling in Azure Container Apps?

A Memory allocated

B Disk size

C Number of users logged in

D CPU usage

CPU usage is a common metric used to trigger scaling in Container Apps.

What does setting 'maxReplicas' control in Container Apps scaling?

A Maximum memory usage allowed

B Minimum number of container instances

C Maximum number of container instances

D Maximum CPU usage allowed

'maxReplicas' limits the maximum number of container instances that can be created.

If HTTP request count increases, what scaling action is expected?

A Scale out (increase instances)

B Scale in (decrease instances)

C No change

D Restart containers

An increase in HTTP requests usually triggers scaling out to handle more load.

What is the effect of setting 'minReplicas' to zero?

A Container Apps can scale down to zero instances

B Container Apps always run at least one instance

C Scaling is disabled

D Containers restart automatically

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

Which of these is NOT a valid scaling trigger in Azure Container Apps?

A CPU usage

B Disk I/O speed

C HTTP queue length

D Custom metrics

Disk I/O speed is not a standard scaling trigger in Azure Container Apps.

Describe how scaling rules help manage performance and cost in Azure Container Apps.

Think about how apps handle more or less traffic.

Explain the roles of 'minReplicas' and 'maxReplicas' in Container Apps scaling rules.

Consider limits on scaling up and down.