A radio newsroom connects an App Service web app to a GitHub repository so each push publishes the site. How should the developer describe that capability on the exam?
Select an answer to reveal the explanation.
Short Explanation
Deployment Center is the “connect this repo and publish when we push” switch on the App Service side of the wire. You are not suddenly taking the AZ-400 release-architect exam. Stay on the App Service continuous deployment setting.
Full Explanation
Deployment Center continuous deployment is the App Service developer feature that attaches a source repository such as GitHub so each push publishes the radio-newsroom site. On AZ-204, describe that capability as App Service’s built-in publish-on-push setting—the switch on the App Service side of the wire—not as an AZ-400-only release-strategy design task and not as a Kubernetes migration.
It is incorrect that App Service has no built-in continuous deployment setting. Requiring migration of the web app to AKS and installing Flux before any GitHub push can deploy invents an unrelated GitOps platform. Claiming the capability exists only when the site runs as Azure Functions on a premium plan with KEDA confuses Functions scaling with App Service Deployment Center for web apps.
Exam caveat: AZ-204 still expects you to know how to wire the repository and that builds or publishes follow the Deployment Center flow for the web app. Deeper multi-stage enterprise release design and approval gates lean toward AZ-400, but recognizing the App Service continuous deployment setting itself remains in scope.
Operational check: in Deployment Center, connect the web app to the GitHub repository and branch, push a trivial README or content change, and confirm App Service detects the push and publishes without introducing AKS, Flux, or a Functions Premium plan.