Azure Functions & Serverless Computing Flashcards
7 cards from real AZ-200 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Azure Functions & Serverless Computing flashcards as text
Which deployment method packages the function app into a ZIP file and mounts it read-only, improving startup performance?
Answer: Run-from-package (WEBSITE_RUN_FROM_PACKAGE=1)
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.
In Azure Durable Functions, how does the orchestrator function maintain state across awaits without using a database?
Answer: It uses the event sourcing pattern via a task hub in Azure Storage
Durable Functions replays the orchestrator's history from Azure Storage (queues, tables, blobs) using event sourcing to reconstruct state after each await.
Which HTTP authorization level requires callers to include a function-specific API key in the request?
Answer: Function
The Function authorization level requires a function key (or higher) to be passed with each request, limiting access to authorized callers.
When deploying Azure Functions in a container, which environment variable must be set to instruct the host not to install extensions?
Answer: FUNCTIONS_EXTENSION_VERSION
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.
What is the maximum number of instances the Consumption Plan will scale a single function app to by default?
Answer: 200 instances
On the Consumption Plan, Azure Functions scales out to a default maximum of 200 instances per function app.
Which Azure service should you configure to reliably trigger an Azure Function when a new blob is uploaded, even if the function app was offline?
Answer: Event Grid trigger using Azure Blob Storage events
Using an Event Grid trigger for Blob Storage events provides near-real-time, reliable delivery even if the function was unavailable, unlike the polling-based blob trigger.
In Azure Functions, which interface should an orchestrator function use when awaiting an activity in C#?
Answer: IDurableOrchestrationContext
IDurableOrchestrationContext provides the orchestrator with methods like CallActivityAsync to invoke activity functions and manage workflow state.