In serverless computing, how is pricing determined?

In serverless computing, how is pricing determined?

• A. Based on monthly fixed fee
• B. Based on actual functions performed
• C. Based on data transfer
• D. Based on provisioned capacity

Answer: (B)

Pricing in serverless computing is driven by usage. You aren’t charged a fixed monthly fee or for reserved capacity; you pay for what actually happens when your code runs. That typically means paying per function invocation and for the time the function executes (often tied to the memory it uses), with any additional data transfer charged separately in some setups. This pay-per-use model is why the best description is that pricing is based on actual functions performed—the amount of work your code does determines the cost. The other ideas don’t fit the serverless model. A fixed monthly fee implies paying regardless of usage, which erodes the elasticity serverless aims to provide. Data transfer charges can occur, but they’re not the primary basis for serverless pricing. Provisioned capacity charges you for reserved resources whether you use them or not, which contrasts with the on-demand nature of serverless where resources scale with demand and you’re billed for actual execution.

Pricing in serverless computing is driven by usage. You aren’t charged a fixed monthly fee or for reserved capacity; you pay for what actually happens when your code runs. That typically means paying per function invocation and for the time the function executes (often tied to the memory it uses), with any additional data transfer charged separately in some setups. This pay-per-use model is why the best description is that pricing is based on actual functions performed—the amount of work your code does determines the cost.

The other ideas don’t fit the serverless model. A fixed monthly fee implies paying regardless of usage, which erodes the elasticity serverless aims to provide. Data transfer charges can occur, but they’re not the primary basis for serverless pricing. Provisioned capacity charges you for reserved resources whether you use them or not, which contrasts with the on-demand nature of serverless where resources scale with demand and you’re billed for actual execution.