Sample question 1 — Develop Azure Compute Solutions
A marketing site is written in PHP and hosted on an App Service plan shared with several internal tools. The pipeline creates a single release file for each commit, and operators want the same file to move from test to production unchanged. They also want a failed upload to leave the running site untouched rather than half replaced. Which release mechanism should the operators adopt?
- A. Publish the release archive with zip deployment to each
- B. Push individual changes with an FTP client after approval.
- C. Mount the site directory on a file share and edit files in place.
- D. Run a Git pull on the host through the Kudu command shell.
Answer: A. Option A is correct because publishing the release archive through zip deployment replaces each site atomically, so test and production receive identical bytes and a failed transfer leaves the previous build serving traffic. Option B sends separate parts over FTP, which can leave a partially updated site when the connection drops. Option C changes the content inside storage directly, so the live copy can drift before approval. Option D pulls the latest branch commit, which is not the archive the pipeline certified.
