Connect to and consume Azure services and third-party services →mediumMultiple ChoiceObjective-mapped

AZ-204 Practice Question: Connect to and consume Azure services and third-party services

Exhibit

{
  "type": "Microsoft.Web/sites/sourcecontrols",
  "properties": {
    "repoUrl": "https://github.com/contoso/app.git",
    "branch": "main",
    "isManualIntegration": false,
    "gitHubActionConfiguration": {
      "codeConfiguration": {
        "runtimeStack": "dotnetcore|8.0",
        "runtimeVersion": "8.0"
      }
    }
  }
}

Refer to the exhibit. An Azure App Service deployment is configured using this ARM template snippet. The web app is built from a GitHub repository. However, when a pull request is merged to main, the app does not automatically deploy. What is the most likely cause?

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

✓

The GitHub Actions workflow file is missing from the repository.

The most likely cause is that the GitHub Actions workflow file is missing from the repository. The ARM template configures the web app to use GitHub Actions for deployment, but it does not create the workflow file. Without the workflow file in the repository at the path referenced (e.g., .github/workflows/), the deployment will not trigger on pull request merges. Option A is incorrect because isManualIntegration: false means automated deployment is expected. Option B is unlikely because the runtime stack is typically specified correctly in the ARM template. Option C is incorrect because the branch is set to main, which typically triggers deployments on merges to main.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The isManualIntegration property is set to false.
Why it's wrong here
False means automatic integration, not the issue.
✗
The runtime stack is incorrect for the application.
Why it's wrong here
dotnetcore|8.0 is a valid stack.
✗
The branch is set to main, but the deployments only trigger on a different branch.
Why it's wrong here
Main is typical for deployments.
✓
The GitHub Actions workflow file is missing from the repository.
Why this is correct
The ARM template only enables the integration; the actual workflow file must exist in the repo.

Go deeper

AZ-204 Practice Question: Connect to and consume Azure services and third-party services

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question