AZ-200 Azure Functions & Serverless Computing 3

Question 1

Which deployment method packages the function app into a ZIP file and mounts it read-only, improving startup performance?

Accepted Answer

Run-from-package (WEBSITE_RUN_FROM_PACKAGE=1)

Answer

Setting WEBSITE_RUN_FROM_PACKAGE=1 causes the host to mount the deployment ZIP read-only, reducing I/O overhead and improving cold start times.

Question 2

In Azure Durable Functions, how does the orchestrator function maintain state across awaits without using a database?

Accepted Answer

It uses the event sourcing pattern via a task hub in Azure Storage

Answer

Durable Functions replays the orchestrator's history from Azure Storage (queues, tables, blobs) using event sourcing to reconstruct state after each await.

Question 3

Which HTTP authorization level requires callers to include a function-specific API key in the request?

Accepted Answer

Function

Answer

The Function authorization level requires a function key (or higher) to be passed with each request, limiting access to authorized callers.

Question 4

When deploying Azure Functions in a container, which environment variable must be set to instruct the host not to install extensions?

Accepted Answer

FUNCTIONS_EXTENSION_VERSION

Answer

FUNCTIONS_EXTENSION_VERSION should be set to ~4 (or the appropriate major version) in containerized deployments so the host uses the bundled extensions rather than downloading them.

Question 5

What is the maximum number of instances the Consumption Plan will scale a single function app to by default?

Accepted Answer

200 instances

Answer

On the Consumption Plan, Azure Functions scales out to a default maximum of 200 instances per function app.

AZ-200 - Microsoft Azure Developer Practice Test

AZ-200 - Microsoft Azure Developer Practice Test

AZ-200 Azure Functions & Serverless Computing 3