nerdexam
Linux_Foundation

KCNA · Question #108

In a serverless computing architecture:

The correct answer is A. Users of the cloud provider are charged based on the number of requests to a function. Serverless computing charges users based on actual resource consumption, typically the number of requests and compute time, rather than pre-provisioned capacity.

Submitted by viktor_hu· May 4, 2026Cloud Native Architecture

Question

In a serverless computing architecture:

Options

  • AUsers of the cloud provider are charged based on the number of requests to a function.
  • BServerless functions are incompatible with containerized functions.
  • CUsers should make a reservation to the cloud provider based on an estimation of usage.
  • DContainers serving requests are running in the background in idle status.

How the community answered

(41 responses)
  • A
    95% (39)
  • B
    2% (1)
  • C
    2% (1)

Why each option

Serverless computing charges users based on actual resource consumption, typically the number of requests and compute time, rather than pre-provisioned capacity.

AUsers of the cloud provider are charged based on the number of requests to a function.Correct

In a serverless computing architecture, cloud providers charge users only for the compute resources consumed while their code is executing, often measured by the number of requests and the duration of execution. This "pay-per-execution" model means users are not charged for idle time or underlying server infrastructure.

BServerless functions are incompatible with containerized functions.

Serverless functions are often implemented using containers, and many serverless platforms support deploying container images as functions, making them compatible.

CUsers should make a reservation to the cloud provider based on an estimation of usage.

Making a reservation based on estimation of usage is characteristic of traditional IaaS or PaaS models, where resources are pre-provisioned, not the pay-per-use model of serverless.

DContainers serving requests are running in the background in idle status.

In a true serverless model, containers or execution environments are typically scaled down to zero when idle, meaning there are no containers running in the background in idle status incurring cost.

Concept tested: Serverless computing billing model

Source: https://learn.microsoft.com/en-us/azure/architecture/guide/technology-choices/compute-decision-tree#serverless

Topics

#Serverless computing#FaaS#Cloud billing#Pay-per-use

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full KCNA Practice