Serverless Computing Questions and Answers

Answer: A

Correct answer: increases the processing power allocated to it

On the major platforms CPU is allocated in proportion to the memory setting, so raising memory raises processing power with it. That has a counter-intuitive consequence: a compute-bound function can be *cheaper* at a higher memory setting, because it finishes proportionally faster and the price is per gigabyte-second. The timeout and account concurrency limits are separate settings, and the unit price does not fall.

Answer: B

Both are true and the reason gives the mechanism, and the outcome depends on whether the work is actually processor bound. A function waiting on a network call gains nothing from the extra capacity and simply costs more.

Answer: C

Only the last stage repeats on a warm invocation, which is why the first three are collectively called the cold start. Work moved into the third stage is paid for once rather than on every call. That is why connection pools and loaded models are set up outside the handler.

Answer: D

Chaining functions by having each invoke the next leaves nowhere to keep progress and no sensible place to retry. An orchestrator holds the state of the workflow outside the functions and handles failure between steps.

Answer: A

The first two are correct and are the reasons orchestration services exist. The third is the practice those services were created to replace, and it becomes unmanageable beyond two or three steps. An orchestrator also gives a single place to see where a workflow actually stopped.

Answer: B

Correct answer: True

Event delivery is generally at-least-once, so retries after a timeout or a transient error can deliver the same event twice, and a function that is not idempotent will double-charge, double-post or corrupt its state. Writing with an idempotency key, or making the operation naturally repeatable, is therefore a requirement of the model rather than a refinement.

Answer: C

Both are true and the reason gives the cause, and the platform's own retry behaviour on failure adds to it. A handler that charges a card without a deduplication key will eventually charge it twice. Writing the deduplication key before doing the work is the usual guard against it.

Answer: D

Long lived stateful processes are the opposite of the model, which assumes short invocations in disposable environments. The other three are the properties that define it. A workload that needs any of them is telling you to choose a different service.