A clerk-office zip extract left a half-written wwwroot after a failed copy, and users saw mixed old and new DLLs. Which App Service deployment approach avoids that partial-update problem?
Select an answer to reveal the explanation.
Short Explanation
Extracting a zip onto a live wwwroot is like swapping pages in a binder while people are still reading—halfway through you get a mess of old and new sheets. Run From Package mounts one zip as the whole book. Atomic drop, no half-written binder.
Full Explanation
Run From Package configures App Service to use a single deployed package as the read-only content root, which avoids torn updates from extracting files onto the worker during a failed or interrupted copy. That atomic model is cleaner than piecemeal FTP or file copies into wwwroot. It is a supported code-deployment pattern and does not require switching the workload to ACI.