How to Enable Continuous Deployment from GitHub to Azure App Service
You are deploying a web app to Azure App Service. You need to enable continuous deployment from a GitHub repository. Which TWO actions are required?
⚠ Common exam trap
A common mix-up: candidates think creating an App Service plan (Option A) is a required step for continuous deployment, but the plan is a separate prerequisite for hosting the web app, not for the deployment pipeline itself.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set up a build provider like GitHub Actions or Kudu
Option B is correct because continuous deployment from GitHub requires a build provider to detect commits and run the build/deploy pipeline — either GitHub Actions (workflow YAML in the repo) or the built-in Kudu (App Service build engine) that App Service uses to pull and build the source. Option C is correct because the Deployment Center in the App Service blade is where you authorize the GitHub connection, select the repository and branch, and choose the build provider, which wires up the deployment source. Option A is not required because an App Service plan is the underlying compute resource that is created or already exists when you create the web app; it is not part of configuring continuous deployment. Option D is not required because Application Insights is an APM/monitoring service and has nothing to do with source control deployment. Option E is not required because a custom domain is a DNS/hostname binding for user access, not a deployment mechanism.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a new App Service plan
Why it's wrong here
Creating a new App Service plan is incorrect because an App Service plan defines the underlying compute resources, such as VMs, CPU, and memory, that host your web app. Continuous deployment (CI/CD) is concerned with the process of automatically building and deploying code to an *existing* web app, not with provisioning new infrastructure. The App Service plan for the target web app is already in place and does not need to be re-created or modified specifically for setting up CI/CD.
- ✓
Set up a build provider like GitHub Actions or Kudu
Why this is correct
Setting up a build provider like GitHub Actions or Kudu is a correct step because a build provider is essential for automating the continuous integration and continuous deployment process. It is responsible for compiling source code, running tests, packaging the application, and then deploying the artifacts to the Azure App Service. GitHub Actions offers a robust external CI/CD platform, while Kudu is the built-in deployment engine for App Service, providing capabilities for source code synchronization, build automation, and deployment scripts directly within the service.
- ✓
Configure the Deployment Center in the App Service to connect to GitHub
Why this is correct
Configuring the Deployment Center in the App Service to connect to GitHub is a correct step as it provides the integrated Azure portal experience for setting up continuous deployment. The Deployment Center streamlines the process of linking your App Service to a source control repository like GitHub, automatically configuring the necessary pipeline components. This setup typically involves generating a GitHub Actions workflow or leveraging Kudu's capabilities to trigger builds and deployments whenever changes are pushed to the connected repository.
- ✗
Enable Application Insights
Why it's wrong here
Enabling Application Insights is incorrect because Application Insights is an Application Performance Management (APM) service used for monitoring the performance, availability, and usage of live web applications. While crucial for understanding an application's health and user experience *after* deployment, it plays no direct role in the actual process of building, packaging, or deploying the application code. Its functionality is entirely separate from the continuous integration and continuous deployment pipeline.
- ✗
Add a custom domain to the App Service
Why it's wrong here
Adding a custom domain to the App Service is incorrect because a custom domain allows users to access the web app using a personalized URL (e.g., `www.yourcompany.com`) instead of the default Azure-provided domain (e.g., `yourwebapp.azurewebsites.net`). This configuration is a post-deployment step focused on branding and accessibility for end-users, completely unrelated to the mechanisms or steps involved in setting up continuous integration or continuous deployment of the application code itself.
Go deeper
Related to this question
Learn chapter
Key Vault References in App Service and Functions
Key term
Application Insights
Application Insights is an Azure monitoring service that helps developers detect, diagnose, and understand issues in live web applications by collecting telemetry data like requests, exceptions, and performance counters.
Key term
Azure App Service Plans
An Azure App Service Plan defines the compute resources, pricing tier, scaling capabilities, and region for one or more web apps, API apps, mobile app backends, or Azure Functions hosted in Azure App Service.
About these practice questions
This AZ-204 question is part of Courseiva's 883-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.