Examkin

Question

Difficulty: HardImplement Azure Service Bus Solutions

You are developing a veterinary clinic management system that synchronizes patient health records. The system uses an Azure Service Bus queue named patient-sync to distribute updates (with an average payload size of 80 KB80\text{ KB}) to a clinic database. You are implementing a .NET console application that processes these messages.

The solution must meet the following requirements:
- Synchronize messages with at-least-once delivery guarantees. If the console application crashes during processing, the message must remain in the queue for subsequent processing.
- Configure client authentication using a Shared Access Signature (SAS) token that restricts the console application to only receiving and processing messages from the patient-sync queue, with no permissions to send messages or manage the queue.

Which two configuration settings should you apply? (Select two.)

  1. Set the ReceiveMode of ServiceBusProcessorOptions to ServiceBusReceiveMode.PeekLock.Answer
  2. Generate a SAS token with only the Listen permission scoped to the patient-sync queue.Answer
  3. C
    Set the ReceiveMode of ServiceBusProcessorOptions to ServiceBusReceiveMode.ReceiveAndDelete.
  4. D
    Generate a SAS token with Manage, Send, and Listen permissions scoped to the Service Bus namespace.

Answer

To meet the requirements, set the ReceiveMode of ServiceBusProcessorOptions to PeekLock and generate a SAS token with only the Listen permission scoped to the patient-sync queue.
The correct choices are setting the receive mode to PeekLock and generating a SAS token restricted to the Listen permission scoped to the queue. PeekLock ensures that messages are locked rather than deleted immediately upon receipt, allowing for automatic or manual completion only after successful processing. Scoping the SAS token to the queue with only Listen permission limits access to reading messages from that specific queue, adhering to the principle of least privilege.

Step-by-Step Solution

1
Determine the receive mode required for at-least-once delivery.
PeekLock mode must be configured.
PeekLock ensures the message is locked rather than deleted upon receipt, which allows the message to be processed and settled; if processing fails or the client crashes, the lock expires and the message becomes available again.
2
Determine the SAS token scope and permissions.
A queue-scoped SAS token with only Listen claims is required.
This satisfies the requirement to restrict the console application to only receiving and processing messages from the patient-sync queue without permission to send or manage.

Key Concept

Implement Azure Service Bus Solutions
Rate this question

Topics

Implement Azure Service Bus Solutions