Function execution model in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Azure Functions cold start behavior

What happens when an Azure Function app receives a request after being idle for a long time?

A The function experiences a delay as the platform initializes the environment (cold start).

B The function executes immediately with no delay.

C The function request is rejected with an error due to inactivity.

D The function runs on a dedicated VM that is always warm.

💡 Hint

Think about what happens when a serverless function has not been used recently.

Azure Functions on consumption plan may experience a cold start delay because the platform needs to allocate resources and initialize the runtime environment before executing the function.

❓ Architecture

intermediate

Scaling behavior of Azure Functions

How does Azure Functions scale when multiple events trigger the function simultaneously?

A Azure Functions rejects events if the current instance is busy.

B Azure Functions queues the events and processes them one by one on a single instance.

C Azure Functions requires manual scaling to handle multiple events.

D Azure Functions scales out automatically by creating multiple instances to handle concurrent events.

💡 Hint

Consider how serverless platforms handle load.

Azure Functions automatically scales out by creating new instances to process multiple events concurrently, ensuring responsiveness without manual intervention.

❓ security

advanced

Function app identity and access

Which method allows an Azure Function to securely access other Azure resources without storing credentials in code?

A Embed credentials directly in the function code for quick access.

B Store credentials in environment variables inside the function code.

C Use Managed Identity assigned to the Function app to authenticate to Azure resources.

D Use anonymous access to Azure resources without authentication.

💡 Hint

Think about secure ways to authenticate without hardcoding secrets.

Managed Identity provides a secure way for Azure Functions to access other Azure services without embedding credentials, improving security and manageability.

❓ Configuration

advanced

Timeout configuration in Azure Functions

What is the maximum execution timeout for an Azure Function running on the Consumption plan, and how can it be configured?

A Maximum timeout is 10 minutes, configured via <code>functionTimeout</code> in <code>host.json</code>.

B Maximum timeout is 30 seconds, configured in Azure Portal settings.

C Maximum timeout is unlimited and cannot be configured.

D Maximum timeout is 60 minutes, configured via environment variables.

💡 Hint

Check the official limits for Consumption plan functions.

On the Consumption plan, Azure Functions have a default timeout of 5 minutes and a maximum configurable timeout of 10 minutes set in host.json using the functionTimeout property.

✅ Best Practice

expert

Designing Azure Functions for high throughput and low latency

You need to design an Azure Function that processes thousands of events per second with minimal delay. Which approach best achieves this?

A Use Consumption plan with default settings and rely on automatic scaling only.

B Use Premium plan with pre-warmed instances and enable Always On to reduce cold starts.

C Deploy the function on a single dedicated VM to control resources manually.

D Use Consumption plan and increase the function timeout to handle longer processing.

💡 Hint

Consider how to reduce cold start delays and ensure capacity.

The Premium plan allows pre-warmed instances and Always On, which reduces cold start latency and supports high throughput better than Consumption plan.

Practice

1. What triggers an Azure Function to run?

easy

A. Only when the server restarts

B. Manual start from the Azure portal only

C. An event like an HTTP request or timer

D. When a user logs into Azure

Solution

1. Step 1: Understand Azure Function triggers

   Azure Functions start running when an event happens, such as an HTTP request or a timer firing.

2. Step 2: Eliminate incorrect options

   Manual starts, server restarts, or user logins are not triggers for Azure Functions.

3. Final Answer:

   An event like an HTTP request or timer -> Option C

4. Quick Check:

   Azure Functions run on events = A [OK]

Hint: Azure Functions run on events, not manual or login actions [OK]

Common Mistakes:

• Thinking functions run only manually
• Confusing server restart with trigger
• Assuming user login triggers function

2. Which of the following is the correct way to define an HTTP trigger in an Azure Function's function.json file?

easy

A. {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]}

B. {"bindings": [{"type": "timerTrigger", "direction": "out", "schedule": "0 */5 * * * *"}]}

C. {"bindings": [{"type": "queueTrigger", "direction": "in", "queueName": "myqueue"}]}

D. {"bindings": [{"type": "httpOutput", "direction": "in"}]}

Solution

1. Step 1: Identify HTTP trigger binding

   The correct binding for an HTTP trigger uses "type": "httpTrigger", "direction": "in", and specifies methods like "get".

2. Step 2: Check other options for errors

   {"bindings": [{"type": "timerTrigger", "direction": "out", "schedule": "0 */5 * * * *"}]} is a timer trigger with wrong direction; {"bindings": [{"type": "queueTrigger", "direction": "in", "queueName": "myqueue"}]} is a queue trigger; {"bindings": [{"type": "httpOutput", "direction": "in"}]} uses invalid "httpOutput" type with wrong direction.

3. Final Answer:

   {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]} -> Option A

4. Quick Check:

   HTTP trigger binding = {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]} [OK]

Hint: HTTP triggers use "httpTrigger" type with "in" direction [OK]

Common Mistakes:

• Confusing trigger type with output binding
• Using wrong direction for triggers
• Mixing trigger types like queue or timer

3. Given this Azure Function code snippet triggered by an HTTP request:

module.exports = async function (context, req) {
  context.log('Function started');
  context.res = { status: 200, body: 'Hello ' + (req.query.name || 'world') };
};

What will be the HTTP response body if the request URL is http://example.com/api?name=Alice?

medium

A. "Error: name not found"

B. "Hello world"

C. "Hello undefined"

D. "Hello Alice"

Solution

1. Step 1: Understand the code logic

   The function reads the query parameter "name" from the request. If "name" exists, it uses it; otherwise, it defaults to "world".

2. Step 2: Apply the input URL query

   The URL has "name=Alice", so the response body becomes "Hello Alice".

3. Final Answer:

   "Hello Alice" -> Option D

4. Quick Check:

   Query name present = "Hello Alice" [OK]

Hint: Check if query parameter exists; else use default [OK]

Common Mistakes:

• Ignoring query parameters
• Assuming default always used
• Confusing response body with error

4. You deployed an Azure Function with a timer trigger but it never runs. Which of these is the most likely cause?

medium

A. The schedule expression in function.json is incorrect

B. The function app is running and healthy

C. The HTTP trigger is missing

D. The function code has no output binding

Solution

1. Step 1: Check timer trigger configuration

   If the schedule expression is wrong, the timer never fires, so the function won't run.

2. Step 2: Evaluate other options

   Running app is good; missing HTTP trigger is irrelevant for timer trigger; output binding absence doesn't stop trigger execution.

3. Final Answer:

   The schedule expression in function.json is incorrect -> Option A

4. Quick Check:

   Wrong schedule = no timer run [OK]

Hint: Check cron schedule syntax for timer triggers [OK]

Common Mistakes:

• Confusing trigger types
• Ignoring schedule format errors
• Assuming output binding affects trigger

5. You want an Azure Function to process messages from a queue and then send results to a database without writing extra code to connect to the database. Which feature should you use to achieve this?

hard

A. Manually call the database API from the function

B. Use an output binding for the database

C. Use a timer trigger to poll the database

D. Write database connection code inside the function

Solution

1. Step 1: Understand output bindings

   Output bindings let functions send data to other services automatically without extra connection code.

2. Step 2: Match requirement to feature

   Using an output binding for the database allows sending results directly after processing queue messages.

3. Final Answer:

   Use an output binding for the database -> Option B

4. Quick Check:

   Output binding sends data without extra code [OK]

Hint: Output bindings connect services without manual code [OK]

Common Mistakes:

• Thinking manual code is always needed
• Confusing triggers with output bindings
• Using timer triggers incorrectly