Functions with HTTP triggers in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

HTTP Trigger Function Response Behavior

You have an Azure Function with an HTTP trigger that returns a JSON response. What will be the HTTP status code if the function completes successfully and returns a valid JSON object?

A 500 Internal Server Error

B 404 Not Found

C 302 Found

D 200 OK

💡 Hint

Think about the standard HTTP status code for a successful request.

When an Azure Function with an HTTP trigger completes successfully and returns a valid JSON response, it sends back a 200 OK status code indicating success.

❓ Configuration

intermediate

Configuring Authorization Level for HTTP Trigger

Which authorization level setting allows an Azure Function with an HTTP trigger to be called without any API key or authentication?

A Anonymous

B Admin

C Function

D User

💡 Hint

Consider which setting allows open access without keys.

The 'Anonymous' authorization level allows anyone to call the HTTP-triggered function without providing any API key or authentication.

❓ Architecture

advanced

Scaling Behavior of HTTP Triggered Functions

When an Azure Function with an HTTP trigger experiences a sudden spike in requests, how does the platform handle scaling to meet demand?

A It automatically creates more instances of the function app to handle the load.

B It queues the requests and processes them one by one on a single instance.

C It rejects new requests until the load decreases.

D It requires manual intervention to add more instances.

💡 Hint

Think about how serverless platforms handle sudden traffic increases.

Azure Functions automatically scale out by creating more instances of the function app to handle increased HTTP request load without manual intervention.

❓ security

advanced

Securing HTTP Triggered Azure Functions

Which of the following is the most secure way to restrict access to an HTTP-triggered Azure Function?

A Set authorization level to 'Anonymous' and rely on IP filtering.

B Set authorization level to 'Function' and share the function key only with trusted clients.

C Set authorization level to 'Admin' and expose the admin key publicly.

D Disable authorization and use HTTPS only.

💡 Hint

Consider how function keys control access.

Setting authorization level to 'Function' requires callers to provide a function key, which should be shared only with trusted clients, providing secure access control.

✅ Best Practice

expert

Optimizing Cold Start for HTTP Triggered Functions

You want to minimize cold start latency for your HTTP-triggered Azure Functions in a consumption plan. Which approach is the best practice?

A Increase the function timeout setting to allow longer execution.

B Disable HTTP triggers and use timer triggers instead.

C Use the Premium plan or Dedicated (App Service) plan to keep instances warm.

D Deploy multiple functions in the same app to share cold start time.

💡 Hint

Think about how Azure Functions plans affect cold start behavior.

The Premium or Dedicated plans keep function instances warm, reducing cold start latency compared to the Consumption plan which spins up instances on demand.