Examkin

Soru

Zorluk: ZorCreate and Configure Azure Functions

An organization is designing a serverless background processing solution using Azure Functions V4 to process large batches of files uploaded to an Azure Blob Storage container. The solution must satisfy the following constraints:
- Individual file processing operations are CPU-intensive and can take up to 15 minutes to complete.
- The function app must connect securely to an Azure SQL Database that is restricted to a private virtual network.
- The system must dynamically scale out the number of instances to handle sudden, unpredictable spikes in upload volume, and scale back down when idle.
- Cold start latency must be minimized for initial requests after periods of inactivity.

Which hosting plan should the organization choose to deploy the Azure Function app?

  1. Premium planCevap
  2. B
    Consumption plan
  3. C
    Dedicated (App Service) plan
  4. D
    Consumption plan with Azure App Service Environment (ASE)

Cevap

Premium plan
The Premium plan is the correct choice because it supports outbound virtual network integration, has a default execution timeout of 30 minutes (unbounded maximum), and provides event-based scaling via the Scale Controller to rapidly handle spikes while minimizing cold starts with pre-warmed instances.

Adım Adım Çözüm

1
Evaluate the runtime execution limit requirement.
The Consumption plan has a strict 10-minute maximum execution limit, which rules it out since processing can take up to 15 minutes.
Azure Functions hosting plans have different default and maximum execution timeouts.
2
Evaluate the network connectivity requirement.
The basic Consumption plan does not support virtual network integration, further ruling it out.
Securing database access behind a private virtual network requires a plan that supports outbound VNet integration.
3
Compare scaling behaviors of the Premium and Dedicated plans.
The Dedicated plan scales based on standard autoscale rules (e.g., CPU/Memory metrics), whereas the Premium plan scales rapidly based on events (e.g., number of blobs/messages) via the Scale Controller and provides pre-warmed instances to prevent cold starts.
Unpredictable spikes require the event-driven Scale Controller to add instances dynamically and proactively.

Anahtar Kavram

Azure Functions hosting plan features and limits, focusing on execution timeouts, network integration, and scaling behaviors.
Bu soruyu puanla

Konular

Create and Configure Azure Functions

Bu konudan daha fazla soru