Challenge: Applying a Queue Trigger

Apply your knowledge by redirecting the output from an HTTP trigger function to a storage queue.

We'll cover the following


In this challenge, you’ll be applying a queue trigger in a function app. You’ll be placing a message on the queue from an HTTP trigger so it can invoke a separate function method.


Below, we have a function app with two function methods. One method has an HTTP trigger. It returns either an OK (200) status code or a NoContent (204) status code, depending on whether the jobName query string parameter was set when the request to this function endpoint was made. Another method has a storage queue trigger and it emulates the process of starting a job with the name that corresponds to the value retrieved from the queue.

Currently, these methods are independent of each other. You need to make a change so that the method with the HTTP trigger acts as an entry point for the method with the storage queue trigger. The message that is placed on the queue must come from the data sent to the URL of the HTTP-triggered method.

Get hands-on with 1200+ tech skills courses.