A 311 mobile backend keeps open case drafts and uploaded photos only in process memory and local container disk so responses stay fast. What risk does that create on a cloud platform that may stop or multiply the process at any time?
Select an answer to reveal the explanation.
Short Explanation
Treat the process like a taxi that can be swapped mid-shift: anything left only on the seat disappears with the car. Session tables and uploads need a backing store. Local memory and disk are fine for scratch, not for business truth.
Full Explanation
Cloud platforms freely stop, relocate, or scale process instances. State that exists only in memory or on local disk disappears with that instance. Durable business data must live in an attached backing store the next instance can reach. Claiming automatic regional replication of local disk, a ban on ephemeral scratch, or automatic memory snapshots misses the design rule.