Subdomain 1.1: Describe cloud computing
1.Which characteristics genuinely apply to serverless computing as offered through services like Azure Functions? (Choose 3.)(Select 3)
- A.Code execution is triggered by events, such as a file upload or an incoming HTTP request
- B.Billing is generally based on actual execution time rather than pre-allocated, always-on capacity
- C.The cloud provider handles the underlying server management, so the developer does not provision virtual machines
- D.The developer must manually configure and patch the operating system that hosts the running function
- E.A dedicated virtual machine must be reserved and kept running at all times so the function can execute instantly
- F.The developer must forecast peak load in advance and pre-purchase enough server capacity to cover it
Show answer & explanation
Correct answers: A, B, C — Code execution is triggered by events, such as a file upload or an incoming HTTP request; Billing is generally based on actual execution time rather than pre-allocated, always-on capacity; The cloud provider handles the underlying server management, so the developer does not provision virtual machines
- A. Correct: serverless functions are event-driven, executing in response to triggers like file uploads, queue messages, or HTTP requests rather than running continuously.
- B. Correct: serverless billing is typically pay-per-execution, charging for actual compute time consumed rather than for reserved, always-on capacity.
- C. Correct: the defining feature of serverless is that the provider manages the underlying infrastructure, so the developer never provisions or maintains a virtual machine.
- D. Manually configuring and patching the operating system is an IaaS responsibility; serverless computing specifically removes this burden from the developer entirely.
- E. Keeping a dedicated virtual machine running at all times describes traditional or IaaS hosting, which contradicts the on-demand, event-triggered nature of serverless execution.
- F. Forecasting peak load and pre-purchasing capacity is exactly the traditional capacity-planning burden that serverless computing's automatic scaling is designed to eliminate.