Practice Test 2 | Designing And Implementing Microsoft DevOps Solutions | AZ-400 | Dumps | Mock Test
You did set up a service hook on the Azure DevOps for one of your applications. You want to insert a string representation of the event to an Azure Storages Queue whenever a comment is made on a work item.
You want to create an HTTP POST request to the subscription’s URL for the Azure DevOps Services organization with the event, consumer, and action for the subscription. Which one of the following data is not required in the request payload?
A. connectionString
B. ttl.
C. accountName
D. visiTimeout.
Answer: A
- Option A is correct. ConnectionString is not required to insert the event information into the Azure storage queue. The SAS (shared access signature) connection string is used to connect with Azure Service Bus.
- Option B is incorrect. The time-to-live takes interval for the queue message, in seconds. The maximum time-to-live allowed is seven days, or 604,800 seconds. This is a mandatory parameter to insert event information into the Azure storage queue.
- Option C is incorrect. AccountName is the storage account name associated with the Azure storage account (e.g., https://STORAGE_ACCOUNT_NAME.queue.core.windows.net). This is required to receive events in the storage queue.
- Option D is incorrect. VisiTimeOut Specifies the visibility timeout value, in seconds, for the enqueued message, relative to server time. The value must be larger than or equal to 0, and cannot be longer than seven days, or 604,800 seconds. The visibility timeout must be set to a value smaller than the message’s time-to-live value, and it is a mandatory data.
- Reference Link: For more information on service hooks, please refer to the below link from Microsoft- https://docs.microsoft.com/en-us/azure/devops/service-hooks/overview?view=azure-devops
Comments are closed, but trackbacks and pingbacks are open.