Functions with queue triggers in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the queue name for the Azure Function trigger.

Azure

public static void Run([QueueTrigger("[1]", Connection = "AzureWebJobsStorage")] string myQueueItem, ILogger log) {
    log.LogInformation($"C# Queue trigger function processed: {myQueueItem}");
}

Drag options to blanks, or click blank then click option'

Amyqueue-items

Bmyqueueitem

CqueueTrigger

Dstoragequeue

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase or incorrect queue names that don't match the actual queue.

Forgetting to put the queue name as a string.

The queue name must match the actual Azure Storage Queue name. Here, "myqueue-items" is the correct queue name used in the trigger attribute.

2fill in blank

medium

Complete the code to specify the connection string setting name for the Azure Storage account.

Azure

public static void Run([QueueTrigger("myqueue-items", Connection = "[1]")] string myQueueItem, ILogger log) {
    log.LogInformation($"Processed: {myQueueItem}");
}

Drag options to blanks, or click blank then click option'

AAzureWebJobsStorage

BStorageConnection

CQueueConnectionString

DStorageAccountKey

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect or custom connection string names without configuring them.

Confusing connection string names with storage account keys.

The default connection string setting for Azure Functions queue triggers is "AzureWebJobsStorage" which points to the storage account connection string.

3fill in blank

hard

Fix the error in the function signature to correctly bind the queue message as a string.

Azure

public static void Run([QueueTrigger("myqueue-items", Connection = "AzureWebJobsStorage")] [1] myQueueItem, ILogger log) {
    log.LogInformation($"Message: {myQueueItem}");
}

Drag options to blanks, or click blank then click option'

AQueueMessage

BCloudQueueMessage

Cstring

Dbyte[]

Attempts:

3 left

💡 Hint

Common Mistakes

Using CloudQueueMessage which requires extra parsing.

Using byte[] which is for binary data.

The queue trigger parameter should be of type string to receive the message content directly as text.

4fill in blank

hard

Fill both blanks to correctly bind the queue trigger and log the message length.

Azure

public static void Run([[1]("myqueue-items", Connection = "AzureWebJobsStorage")] string myQueueItem, ILogger [2]) {
    log.LogInformation($"Message length: {myQueueItem.Length}");
}

Drag options to blanks, or click blank then click option'

AQueueTrigger

Blogger

Clog

DQueueListener

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect attribute names like QueueListener.

Naming the logger parameter incorrectly causing errors.

The attribute to bind the queue trigger is [QueueTrigger]. The logger parameter is commonly named 'log' to write logs.

5fill in blank

hard

Fill all three blanks to create a function that triggers on a queue message, logs the message, and outputs a new message to another queue.

Azure

public static void Run(
    [[1]("input-queue", Connection = "AzureWebJobsStorage")] string inputMessage,
    [Queue("[2]", Connection = "AzureWebJobsStorage")] out string outputMessage,
    ILogger [3]) {
    log.LogInformation($"Received: {inputMessage}");
    outputMessage = inputMessage.ToUpper();
}

Drag options to blanks, or click blank then click option'

AQueueTrigger

Boutput-queue

Clog

DQueueOutput

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up input and output queue names.

Using wrong attribute names for output binding.

Incorrect logger parameter name.

The function triggers on 'input-queue' using [QueueTrigger]. It outputs to 'output-queue' using [Queue]. The logger parameter is named 'log'.

Practice

1. What does an Azure Function with a queue trigger do when a new message arrives in the queue?

easy

A. It automatically starts and processes the message.

B. It waits for manual activation to process the message.

C. It deletes the message without processing.

D. It sends an email notification only.

Solution

1. Step 1: Understand queue trigger behavior

   Queue triggers start the function automatically when a new message arrives in the queue.

2. Step 2: Identify the function's action

   The function processes the message as soon as it triggers without manual intervention.

3. Final Answer:

   It automatically starts and processes the message. -> Option A

4. Quick Check:

   Queue trigger = automatic start [OK]

Hint: Queue triggers start functions automatically on new messages [OK]

Common Mistakes:

• Thinking the function needs manual start
• Assuming the message is deleted without processing
• Confusing triggers with notifications

2. Which of the following is the correct way to declare a queue trigger in an Azure Function using Python?

easy

A. @app.queue_trigger(arg_name='msg', queue_name='myqueue', connection='AzureWebJobsStorage')

B. @blob_trigger(container_name='mycontainer')

C. @http_trigger(methods=['GET'])

D. @timer_trigger(schedule='0 */5 * * * *')

Solution

1. Step 1: Identify the correct trigger decorator

   Queue triggers use @app.queue_trigger with queue_name, connection, and arg_name parameters.

2. Step 2: Check other options

   Blob, HTTP, and timer triggers use different decorators and parameters.

3. Final Answer:

   @app.queue_trigger(arg_name='msg', queue_name='myqueue', connection='AzureWebJobsStorage') -> Option A

4. Quick Check:

   Queue trigger decorator = @app.queue_trigger [OK]

Hint: Queue triggers use @app.queue_trigger decorator with queue_name [OK]

Common Mistakes:

• Using wrong trigger decorators like @blob_trigger
• Missing required parameters like queue_name
• Confusing connection string names

3. Given this Azure Function code snippet in Python, what will be printed when a message with content 'Hello' arrives in the queue?

import logging
import azure.functions as func

def main(msg: func.QueueMessage):
    message = msg.get_body().decode('utf-8')
    logging.info(f'Received message: {message}')

medium

A. Error: msg.get_body() is not a function

B. Received message: b'Hello'

C. No output because logging is disabled

D. Received message: Hello

Solution

1. Step 1: Decode the message body

   The message body is decoded from bytes to string using decode('utf-8'), so 'Hello' is a string.

2. Step 2: Logging output

   The logging.info call prints 'Received message: Hello' to the logs.

3. Final Answer:

   Received message: Hello -> Option D

4. Quick Check:

   Decoded message logged = 'Received message: Hello' [OK]

Hint: Decode bytes to string before logging message content [OK]

Common Mistakes:

• Logging raw bytes without decoding
• Assuming get_body() is not callable
• Thinking logging is off by default

4. You deployed an Azure Function with a queue trigger, but it never runs when messages arrive. Which of these is the most likely cause?

medium

A. The function code has a syntax error in the main function.

B. The connection string for the storage account is incorrect or missing.

C. The queue name is misspelled in the trigger configuration.

D. The function app is set to manual scale mode.

Solution

1. Step 1: Check connection string

   If the connection string to the storage account is wrong or missing, the function cannot listen to the queue.

2. Step 2: Consider other causes

   While syntax errors cause deployment failure, misspelled queue names cause no trigger, but connection issues are most common.

3. Final Answer:

   The connection string for the storage account is incorrect or missing. -> Option B

4. Quick Check:

   Connection string error = no trigger run [OK]

Hint: Verify storage connection string first if function doesn't trigger [OK]

Common Mistakes:

• Ignoring connection string errors
• Assuming scaling mode stops triggers
• Overlooking queue name spelling

5. You want to process messages from two different queues in the same Azure Function app. What is the best way to configure this?

hard

A. Use one function with two queue triggers on the same method.

B. Combine both queues into one and use a single queue trigger.

C. Create two separate functions within the app, each with its own queue trigger for each queue.

D. Use a timer trigger to poll both queues manually.

Solution

1. Step 1: Understand function triggers

   Each function can have one trigger. To listen to two queues, create two functions with separate queue triggers.

2. Step 2: Evaluate other options

   One function cannot have two queue triggers on the same method; combining queues may not be feasible; timer triggers require manual polling.

3. Final Answer:

   Create two separate functions within the app, each with its own queue trigger for each queue. -> Option C

4. Quick Check:

   One trigger per function = two functions for two queues [OK]

Hint: Use separate functions for each queue trigger [OK]

Common Mistakes:

• Trying multiple triggers on one function method
• Merging queues without control
• Using timer triggers instead of queue triggers