Container Apps scaling rules in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does CPU-based scaling work in Azure Container Apps?

Azure Container Apps can scale based on CPU usage. What happens when the CPU usage exceeds the configured threshold?

A The platform ignores CPU usage and scales only based on memory.

B The platform decreases the number of container instances to save resources.

C The platform restarts the container instances to clear CPU usage.

D The platform increases the number of container instances to reduce CPU load.

💡 Hint

Think about how scaling helps manage load.

When CPU usage goes above the threshold, Azure Container Apps adds more container instances to handle the load and reduce CPU pressure.

❓ Configuration

intermediate

What is the effect of setting a minimum replica count in Container Apps scaling?

If you configure a minimum replica count of 2 in your Container App's scaling rules, what is the expected behavior?

A The Container App will run exactly 2 instances and never scale beyond that.

B The Container App will scale down to zero instances when idle.

C The Container App will always run at least 2 container instances, even if there is no traffic.

D The Container App will ignore the minimum and scale based only on CPU.

💡 Hint

Minimum replicas prevent scaling below a certain number.

Setting a minimum replica count ensures the app always has that many instances running, even with no traffic, to reduce cold start delays.

❓ Architecture

advanced

Which scaling rule best supports burst traffic in Azure Container Apps?

You expect sudden spikes in traffic to your Container App. Which scaling rule configuration will best handle this scenario?

A Set minimum replicas equal to maximum replicas to keep a fixed number of instances.

B Set a low CPU threshold with a high maximum replica count to quickly add instances during spikes.

C Disable scaling and manually add instances during spikes.

D Set a high CPU threshold with a low maximum replica count to limit resource use.

💡 Hint

Think about responsiveness and capacity during traffic bursts.

A low CPU threshold triggers scaling early, and a high max replica count allows many instances to handle bursts smoothly.

❓ security

advanced

What security risk can arise from improper scaling rule configuration in Container Apps?

If scaling rules allow unlimited scaling without limits, what security risk might occur?

A Potential denial of service due to resource exhaustion and increased attack surface.

B Automatic encryption of data at rest is disabled.

C Container images become publicly accessible.

D Scaling rules have no impact on security risks.

💡 Hint

Consider resource limits and attack vectors.

Unlimited scaling can cause resource exhaustion, leading to denial of service and exposing more instances to attacks.

✅ Best Practice

expert

What is the recommended approach to configure scaling rules for cost efficiency and performance in Azure Container Apps?

To balance cost and performance, which scaling rule setup is best?

A Set a moderate CPU threshold, define minimum replicas to avoid cold starts, and set a reasonable maximum replica count.

B Set minimum replicas to zero, maximum replicas to unlimited, and no CPU threshold.

C Set CPU threshold very low and maximum replicas very high to always scale out.

D Set maximum replicas to one and disable scaling to save costs.

💡 Hint

Think about avoiding cold starts and controlling costs.

Moderate CPU threshold triggers scaling when needed, minimum replicas avoid cold starts, and max replicas limit cost.