Connect to and consume Azure services and third-party services
Free Microsoft Certified: Azure Developer Associate practice — 6 questions on Connect to and consume Azure services and third-party services, with explanations. No sign-up. Full 12-question mixed test →
An order-processing system uses an Azure Service Bus queue. Multiple concurrent worker instances read messages, but processing for a given customer must complete in strict FIFO order relative to other messages for that same customer, even though many customers are processed in parallel. Which configuration meets this requirement?
Sessions group related messages by SessionId; a session-aware receiver locks an entire session, guaranteeing FIFO delivery within that session even while other sessions (customers) are processed concurrently by other receivers.
A manufacturing company must ingest 2 million sensor readings per second from IoT devices. Three independent analytics services must each read the entire stream on their own schedule without affecting one another, and the team needs to replay the last 24 hours of readings on demand. Which service should they use?
Event Hubs is built for massive-throughput streaming ingestion, supports configurable retention (up to 90 days) enabling replay, and consumer groups let multiple independent readers consume the full stream at their own pace via offsets.
An application generates 50 million short status-update messages per day, each under 60 KB. There is no requirement for ordering, sessions, transactions, or dead-lettering, and the team wants the lowest-cost queue with at-least-once delivery. Which service should they choose?
Azure Queue Storage supports messages up to 64 KB, provides at-least-once delivery through visibility timeouts, and is billed per storage transaction/capacity, making it the cheapest option for high-volume, simple queuing with no advanced messaging needs.
You need to restrict a single API Management subscription key to no more than 10 calls per 60 seconds, independent of any other subscriber's usage. Which inbound policy should you configure?
rate-limit-by-key enforces the limit per an arbitrary counter key, such as the subscription ID, giving each caller its own independent throttle bucket.
A Service Bus queue uses default settings. A message repeatedly fails processing due to an unhandled exception and is abandoned each time. After how many unsuccessful delivery attempts will Service Bus automatically move the message to the dead-letter queue?
The default MaxDeliveryCount for a Service Bus queue or subscription is 10. Once a message has been delivered and abandoned (or its lock expires) 10 times, Service Bus automatically moves it to the dead-letter queue.
A company exposes an API to multiple external partners through Azure API Management. Each partner needs an independently revocable key, its own daily call quota of 1,000 requests, and the ability to change terms for one partner without impacting others. What should you configure?
APIM products group APIs with their own usage policies (such as quota) and access terms; creating one product per partner with an individual quota policy and subscription key lets each partner's access, quota, and revocation be managed completely independently.
Ready for the real thing?
The full course has two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed answer explanations.
Start my full course on Udemy →