Connect to and consume Azure services and third-party services →mediumMultiple ChoiceObjective-mapped
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
You are developing a microservice that processes images. After processing, it needs to store the result in Azure Blob Storage and send a message to Azure Service Bus for further processing. Which Azure SDK client should you use to minimize overhead?
⚠ Common exam trap
It's easy for candidates to confuse a hosting option (Azure Functions) or a different service (SignalR) with the correct client library, or assume that raw REST calls are simpler when they actually introduce more overhead due to manual protocol handling.
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
✓
Use the Azure.Storage.Blobs and Azure.Messaging.ServiceBus NuGet packages
The Azure.Storage.Blobs and Azure.Messaging.ServiceBus NuGet packages are the official, high-level Azure SDK client libraries that provide optimized, asynchronous APIs for interacting with Azure Blob Storage and Azure Service Bus. These libraries handle connection pooling, retry policies, serialization, and authentication automatically, minimizing overhead compared to lower-level approaches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use the Azure.Storage.Blobs and Azure.Messaging.ServiceBus NuGet packages
Why this is correct
For a microservice processing images, Azure Blob Storage is the standard solution for storing the images, and the Azure.Storage.Blobs NuGet package provides a robust, idiomatic .NET client library for interacting with it. Similarly, Azure Service Bus is a highly reliable enterprise-grade messaging service ideal for asynchronous communication between microservices, and the Azure.Messaging.ServiceBus package offers a high-performance, feature-rich client for sending and receiving messages, enabling efficient decoupled processing workflows.
- ✗
Deploy the microservice as an Azure Function
Why it's wrong here
Deploying the microservice as an Azure Function describes a serverless compute environment for hosting the application logic, not a method for interacting with Azure storage or messaging services. While an Azure Function could internally utilize the correct NuGet packages for Blob Storage and Service Bus, the option itself proposes a deployment model rather than the specific client libraries required to perform the core tasks of storing images and sending messages.
- ✗
Call the Azure REST APIs directly using HttpClient
Why it's wrong here
Directly calling Azure REST APIs using HttpClient is technically possible but highly inefficient and generally discouraged for production applications. This approach necessitates manual handling of authentication (e.g., constructing SAS tokens or managing OAuth flows), request serialization, response deserialization, retry logic, and comprehensive error handling, all of which are robustly implemented and abstracted away by the official Azure SDKs, leading to significantly more complex and error-prone code.
- ✗
Use Azure SignalR Service for messaging
Why it's wrong here
Azure SignalR Service is designed for real-time, bidirectional communication between servers and clients, primarily for web applications requiring instant updates, chat functionality, or live dashboards. It is fundamentally different from a durable, asynchronous queueing service like Azure Service Bus, which is intended for reliable message delivery, load leveling, and decoupling microservices for background processing, not for direct client-to-server real-time notifications.
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
Go deeper
Related to this question
Learn chapter
Azure Functions Development
Key term
Blob Storage SDK
The Blob Storage SDK is a set of libraries and tools that lets developers write code to store, access, and manage unstructured data in Microsoft Azure's blob storage service.
Key term
Azure Relay
Azure Relay is a cloud service that securely exposes on-premises web services to the public internet or other cloud applications without opening firewall ports.
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.