Build fluency in the core concepts of Azure Container Apps.
0 / 5 completed
1 / 5
At standup, a dev asks where multiple Container Apps share networking and logging. What is that boundary?
An Azure Container Apps environment is the secure boundary that groups apps sharing a virtual network and Log Analytics workspace. Apps in the same environment can communicate internally. It is the foundational deployment unit you create first.
2 / 5
During a PR review, a teammate deploys a new version while keeping the old one for rollback. What concept is this?
A revision is an immutable snapshot of a Container App version. You can run multiple revisions and split traffic for blue-green or canary releases. Keeping an old revision active enables instant rollback.
3 / 5
In a design review, the team wants the app to scale to zero based on queue length. Which component drives this?
Container Apps uses KEDA (Kubernetes Event-Driven Autoscaling) to scale on custom metrics like queue depth, including scaling to zero. You declare scale rules referencing the event source. This is how event-driven workloads stay cost-efficient.
4 / 5
During a code review, a service uses pub/sub and service invocation abstractions. Which Container Apps feature provides these?
Dapr (Distributed Application Runtime) is built into Container Apps and provides building blocks like pub/sub, state, and service invocation via a sidecar. You enable it per app and configure components. It decouples app code from specific infrastructure SDKs.
5 / 5
An incident report shows credentials hardcoded to reach a database. What Azure feature removes the secret?
A managed identity lets the Container App authenticate to Azure resources without storing credentials. Azure AD issues tokens for the identity, which you grant access via role assignments. This eliminates hardcoded secrets entirely.