Examkin

Soru

Zorluk: Çok zorServerless and Web Application Hosting

An organization is designing a serverless backend for an enterprise batch import system. The system must process files uploaded to an Azure Blob Storage container. The architectural design must satisfy the following technical constraints:

- Execution Time: The file processing logic is single-threaded and can take up to 15 minutes to complete for large payloads.
- Network Isolation: The compute resource must securely access an Azure SQL Database and storage accounts via private endpoints within an Azure Virtual Network (VNet).
- Cost Efficiency: The compute resource must automatically scale down to zero instances when there are no files to process, ensuring zero billing during idle periods.
- Operational Overhead: Minimize administrative overhead by avoiding the need to configure, build, or deploy custom Docker container images or manage container registries.

Which Azure compute hosting option should you recommend to meet these requirements?

  1. A
    Azure Functions on a Consumption plan
  2. B
    Azure Functions on an Elastic Premium plan
  3. Azure Functions on a Flex Consumption planCevap
  4. D
    Azure Kubernetes Service (AKS) with KEDA

Cevap

Azure Functions on a Flex Consumption plan
The correct option is the Azure Functions Flex Consumption plan. It supports fast virtual network integration through subnet delegation, scales to zero instances when idle to eliminate cold-start costs during inactive periods, allows configuring the execution duration timeout up to 30 minutes, and offers a code-first deployment path that avoids containerization overhead.

Adım Adım Çözüm

1
Evaluate the execution duration limit constraint.
The file processing tasks can take up to 15 minutes. This immediately rules out the standard Azure Functions Consumption plan, which has a hard maximum timeout of 10 minutes.
Choosing a plan that cannot support the maximum processing time will result in premature execution failures.
2
Evaluate the network isolation constraint.
The solution requires secure access to resources using private endpoints inside an Azure Virtual Network (VNet).
This rules out the standard Consumption plan as it lacks VNet integration support, but Elastic Premium, Flex Consumption, and AKS options remain viable.
3
Evaluate the cost constraint of scaling to zero billing during idle periods.
The compute hosting plan must scale to zero instances when idle to ensure no compute charges.
This rules out the Elastic Premium plan because it requires at least one active, pre-warmed instance, leading to continuous charges regardless of usage.
4
Evaluate the operational overhead and container management constraint.
The architecture must avoid container management, registry management, and custom Dockerfile creation.
This rules out Azure Kubernetes Service (AKS) with KEDA, as it introduces substantial containerization and cluster administration overhead.
5
Confirm the capabilities of the remaining option.
Azure Functions on a Flex Consumption plan natively supports up to 30-minute execution limits, fast subnet delegation VNet integration, scales down to zero instances when inactive, and allows code-first deployment without custom container images.
This matches all specific constraints of the scenario.

Anahtar Kavram

Selecting the optimal Azure Functions plan based on execution limits, virtual network integration, scale-to-zero capabilities, and administrative overhead.
Bu soruyu puanla

Konular

Serverless and Web Application Hosting

Bu konudan daha fazla soru