AZ-204 Develop Azure compute solutions Practice Question
Which FOUR features are supported by Azure Container Apps? (Select four.)
⚠ Common exam trap
The trap here is that candidates might confuse specific advanced networking features of AKS with Container Apps. While Container Apps abstracts much of the underlying Kubernetes complexity, it *does* support VNet integration for deploying the environment into an existing VNet. Azure NetApp Files, however, is not directly supported for volume mounting in Container Apps.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Virtual network (VNet) injection.
Option A is correct because Azure Container Apps supports VNet injection, allowing the environment to be deployed into a delegated subnet so apps can privately reach resources such as Azure SQL or Storage via private endpoints. Option C is correct because Azure Container Apps natively integrates KEDA scalers, enabling event-driven scaling based on sources like Service Bus queues, Event Hubs, or HTTP traffic. Option D is correct because Container Apps uses immutable revisions, which support blue-green (and canary) deployment patterns by splitting traffic between revisions and shifting weight after validation. Option E is correct because Container Apps has built-in Dapr integration, exposing sidecars for service invocation, pub/sub, state management, and bindings without extra infrastructure. Option B is not supported: Azure Container Apps does not natively mount Azure NetApp Files volumes; persistent storage is provided via Azure Files mounts or ephemeral storage, while Azure NetApp Files is used with services like Azure Kubernetes Service or Azure VMware Solution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Virtual network (VNet) injection.
Why this is correct
Azure Container Apps environments are deployed into a managed virtual network by default, or can be deployed into an existing VNet using custom VNet integration. However, "VNet injection" as a direct, granular control over individual container app network interfaces within a pre-existing VNet is not the operational model. Instead, the entire Container Apps environment is integrated into a subnet, providing network isolation and connectivity to other VNet resources, but not direct injection at the app level.
- ✗
Mounting Azure NetApp Files volumes.
Why it's wrong here
Azure Container Apps currently supports persistent storage through Azure Files shares and Azure Blob Storage, which can be mounted as volumes to container apps. Azure NetApp Files, while a high-performance, enterprise-grade file storage service for Azure, is not directly supported as a volume mount option within the Azure Container Apps environment. This limitation means developers cannot leverage its specific performance characteristics for their containerized applications in this platform.
- ✓
Event-driven scaling using KEDA.
Why this is correct
Azure Container Apps natively integrates KEDA (Kubernetes Event-driven Autoscaling) to enable dynamic scaling of container apps based on various event sources. This allows applications to scale out from zero instances to many based on metrics from message queues, databases, HTTP traffic, or custom scalers, and then scale back in when demand subsides. KEDA's integration provides efficient resource utilization by ensuring applications only consume resources when actively processing events.
- ✓
Blue-green deployment with revisions.
Why this is correct
Azure Container Apps supports blue-green deployments through its revisions feature, which allows multiple versions of a container app to run concurrently. Each revision represents an immutable snapshot of a container app's configuration and image. Traffic splitting can then be configured to route a percentage of requests to a new "green" revision while the existing "blue" revision handles the majority, enabling safe, gradual rollouts and easy rollback capabilities.
- ✓
Integration with Dapr (Distributed Application Runtime).
Why this is correct
Azure Container Apps has deep, native integration with Dapr (Distributed Application Runtime), providing a set of building blocks for developing resilient, portable, and event-driven microservices. Dapr sidecars can be easily enabled for container apps, offering capabilities like state management, service invocation, pub/sub messaging, and secret management without requiring developers to write boilerplate code. This simplifies the development of complex distributed applications by abstracting away common challenges.
Visual reference
Go deeper
Related to this question
Learn chapter
Azure Functions Workflows: Orchestration Patterns
Key term
Azure Files Shares
Azure Files Shares are fully managed cloud file shares that you can access from anywhere using standard industry protocols like SMB and NFS.
Key term
Azure Service Bus
Azure Service Bus is a cloud-based message broker that allows applications, services, and devices to send and receive messages reliably, even when they are not all running at the same time.
About these practice questions
One of 883 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.