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.