The correct answer includes Service Invocation, State Management, and Pub/Sub as the three essential Dapr building blocks for service-to-service communication and state management in Azure Container Apps. Service Invocation enables direct, secure calls between microservices using gRPC or HTTP with built-in mTLS, retries, and observability, while State Management provides a pluggable key-value store abstraction—supporting Redis, Cosmos DB, or SQL Server—to manage shared state across services. Pub/Sub rounds out the trio by allowing asynchronous, event-driven communication that decouples producers and consumers through message brokers like Azure Service Bus. On the AZ-204 exam, this question tests your ability to distinguish Dapr’s core building blocks from its more specialized ones, such as Bindings or Actors; a common trap is to overlook Pub/Sub because the prompt emphasizes “service-to-service invocation,” but remember that Dapr treats asynchronous messaging as a first-class communication pattern. A useful memory tip: think of the three S’s—Service Invocation for synchronous calls, State for data, and Subscriptions for events.
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your Azure Container Apps solution uses Dapr for microservices communication. Which THREE Dapr building blocks are essential for service-to-service invocation and state management?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Service Invocation
Service Invocation (A) is correct because Dapr's service invocation building block enables direct, secure service-to-service communication using gRPC or HTTP, with built-in mTLS, retries, and observability. State Management (E) is correct because it provides a key-value store abstraction for managing state across microservices, supporting pluggable state stores like Redis, Cosmos DB, or SQL Server. Pub/Sub (C) is correct because it enables asynchronous event-driven communication between services, decoupling producers and consumers via message brokers like Kafka, RabbitMQ, or Azure Service Bus.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Service Invocation
Why this is correct
Service Invocation is the building block for direct service-to-service calls.
Related concept
Read the scenario before looking for a memorised answer.
✗
Bindings
Why it's wrong here
Bindings integrate with external systems, not for internal service communication.
✓
Pub/Sub
Why this is correct
Pub/Sub enables asynchronous messaging between services, often used alongside invocation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Actors
Why it's wrong here
Actors implement the virtual actor pattern, not essential for basic invocation and state.
✓
State Management
Why this is correct
State Management provides a key-value store for stateful services.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Bindings with service invocation (both involve external communication) or assume Actors are required for state management, but Dapr separates these concerns into distinct building blocks with specific use cases.
Detailed technical explanation
How to think about this question
Dapr's service invocation uses a sidecar proxy that intercepts outbound calls and applies service discovery, load balancing, and mTLS encryption automatically via the Dapr API (e.g., http://localhost:3500/v1.0/invoke/{appId}/method/{method}). State management uses pluggable state stores with configurable consistency (strong or eventual) and concurrency control (optimistic locking via ETags). In a real-world scenario, combining service invocation with state management allows a service to call another service and persist the result atomically, while Pub/Sub enables event-driven workflows like order processing.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Service Invocation — Service Invocation (A) is correct because Dapr's service invocation building block enables direct, secure service-to-service communication using gRPC or HTTP, with built-in mTLS, retries, and observability. State Management (E) is correct because it provides a key-value store abstraction for managing state across microservices, supporting pluggable state stores like Redis, Cosmos DB, or SQL Server. Pub/Sub (C) is correct because it enables asynchronous event-driven communication between services, decoupling producers and consumers via message brokers like Kafka, RabbitMQ, or Azure Service Bus.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.