Public works wants short event-driven jobs that resize citizen photo uploads on demand without provisioning or patching servers. Which model best fits?
Select an answer to reveal the explanation.
Short Explanation
Those photo resizes are like pop-up food trucks that appear when a crowd shows up and leave when it is quiet. FaaS runs short event jobs without you standing up permanent servers. Keeping always-on VMs or bare metal for occasional uploads is renting a full restaurant for snack orders.
Full Explanation
Function as a Service executes short-lived, event-triggered code without requiring the customer to provision or patch underlying servers. Image resize after upload is a classic serverless pattern because work is bursty and brief. Persistent IaaS fleets or bare metal increase operational overhead when the workload does not need continuous capacity.