Deployment methods (Git, ZIP, CI/CD) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Azure CLI Git deployment command

What is the output of the following Azure CLI command when deploying code via Git to an Azure Web App?

Azure

az webapp deployment source config-local-git --name MyWebApp --resource-group MyResourceGroup

A Deployment successful: Code pushed to Azure Web App

B Error: Resource group 'MyResourceGroup' not found

C Git URL for deployment: https://<username>@mywebapp.scm.azurewebsites.net/MyWebApp.git

D Warning: Git deployment not supported for this app service plan

💡 Hint

This command configures local Git deployment and returns the Git URL to push code.

The command sets up local Git deployment and outputs the Git URL to use for pushing code. It does not deploy code immediately or show deployment success.

🧠 Conceptual

intermediate

Understanding ZIP deployment behavior

When deploying an application to Azure App Service using ZIP deployment, what happens to the existing files in the wwwroot folder?

A Deployment fails if wwwroot folder is not empty

B New files are added, but existing files remain unchanged

C Existing files are backed up and merged with new files

D Existing files are completely replaced by the contents of the ZIP file

💡 Hint

Think about how ZIP deployment updates the app content folder.

ZIP deployment replaces the entire content of the wwwroot folder with the contents of the ZIP file, effectively overwriting existing files.

🔀 Workflow

advanced

Correct order of steps in a CI/CD pipeline for Azure Web App deployment

Arrange the following steps in the correct order for a CI/CD pipeline deploying code to an Azure Web App:

A 4, 2, 1, 3

B 4, 1, 2, 3

C 2, 4, 1, 3

D 4, 2, 3, 1

💡 Hint

Think about what happens first when code changes, then building, testing, and deploying.

The pipeline triggers on code commit (4), then builds artifacts (2), runs tests (1), and finally deploys to Azure (3).

❓ Troubleshoot

advanced

Identifying cause of deployment failure in Azure DevOps pipeline

An Azure DevOps pipeline deploying to an Azure Web App fails with the error: '403 Forbidden - Access Denied'. Which is the most likely cause?

A ZIP deployment package is corrupted

B Incorrect service connection permissions for Azure subscription

C Build agent does not have enough memory

D App Service plan is stopped

💡 Hint

403 Forbidden usually relates to permission issues.

A 403 Forbidden error during deployment typically means the service connection used by the pipeline lacks permission to deploy to the Azure subscription or resource.

✅ Best Practice

expert

Best practice for secure CI/CD deployment to Azure Web Apps

Which practice best improves security when deploying to Azure Web Apps using CI/CD pipelines?

A Use managed identities and Azure Key Vault to handle secrets

B Store deployment credentials directly in pipeline YAML files

C Disable HTTPS to simplify deployment

D Allow anonymous access to the deployment endpoint

💡 Hint

Think about secure secret management and identity in Azure.

Using managed identities with Azure Key Vault avoids storing secrets in code or pipeline files, enhancing security by managing credentials safely.

Practice

1. Which deployment method in Azure allows you to push your app code directly from your source code repository?

easy

A. Manual file upload

B. ZIP deployment

C. FTP deployment

D. Git deployment

Solution

1. Step 1: Understand Git deployment

   Git deployment connects your Azure app directly to your Git repository, pushing code changes automatically.

2. Step 2: Compare with other methods

   ZIP deployment uploads a packaged file, manual upload and FTP are manual and not direct from repo.

3. Final Answer:

   Git deployment -> Option D

4. Quick Check:

   Direct repo push = Git deployment [OK]

Hint: Git deployment means pushing code from your repo directly [OK]

Common Mistakes:

• Confusing ZIP deployment with Git deployment
• Thinking FTP is automated from repo
• Assuming manual upload is Git-based

2. Which of the following is the correct Azure CLI command to deploy a ZIP package to an Azure Web App named myapp in resource group mygroup?

easy

A. az webapp deploy zip --resource-group mygroup --app-name myapp --file app.zip

B. az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip

C. az deployment zip --resource-group mygroup --webapp myapp --package app.zip

D. az webapp deployment upload-zip --resource-group mygroup --name myapp --zip-file app.zip

Solution

1. Step 1: Identify correct Azure CLI syntax for ZIP deployment

   The official command is az webapp deployment source config-zip with parameters for resource group, app name, and source ZIP file.

2. Step 2: Check options for syntax correctness

   az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip matches the correct command and parameters exactly; others use incorrect commands or flags.

3. Final Answer:

   az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip -> Option B

4. Quick Check:

   Correct CLI command for ZIP deploy = az webapp deployment source config-zip --resource-group mygroup --name myapp --src app.zip [OK]

Hint: Remember 'config-zip' is the key command for ZIP deploy [OK]

Common Mistakes:

• Using wrong command verbs like 'deploy' or 'upload-zip'
• Mixing parameter names like --app-name vs --name
• Forgetting to specify the source ZIP file with --src

3. Given this Azure DevOps pipeline snippet for CI/CD deployment:

trigger:
  branches:
    include:
      - main

steps:
- task: AzureWebApp@1
  inputs:
    azureSubscription: 'MyAzureSub'
    appName: 'myapp'
    package: '$(System.DefaultWorkingDirectory)/drop/app.zip'

What happens when you push code to the main branch?

medium

A. The pipeline triggers and deletes the Azure Web App

B. The pipeline triggers but does not deploy anything

C. The pipeline triggers and deploys the ZIP package to the Azure Web App

D. The pipeline does not trigger on main branch pushes

Solution

1. Step 1: Analyze the trigger section

   The pipeline triggers on pushes to the main branch as specified in the trigger include list.

2. Step 2: Understand the deployment task

   The AzureWebApp@1 task deploys the ZIP package located at the specified path to the Azure Web App named 'myapp'.

3. Final Answer:

   The pipeline triggers and deploys the ZIP package to the Azure Web App -> Option C

4. Quick Check:

   Push to main triggers deploy task = The pipeline triggers and deploys the ZIP package to the Azure Web App [OK]

Hint: Trigger on main means pipeline runs and deploys ZIP package [OK]

Common Mistakes:

• Assuming pipeline triggers on other branches
• Thinking deployment task does nothing
• Confusing deployment with deletion

4. You configured a CI/CD pipeline to deploy your app, but the deployment fails with an authentication error. What is the most likely cause?

medium

A. Incorrect Azure subscription service connection in the pipeline

B. ZIP package file is missing from the build artifacts

C. App name in the pipeline does not match the Azure Web App

D. Pipeline trigger is set to the wrong branch

Solution

1. Step 1: Identify cause of authentication error

   Authentication errors usually mean the pipeline cannot access Azure resources due to wrong or missing service connection credentials.

2. Step 2: Evaluate other options

   Missing ZIP or wrong app name cause deployment errors but not authentication errors; wrong trigger prevents pipeline start.

3. Final Answer:

   Incorrect Azure subscription service connection in the pipeline -> Option A

4. Quick Check:

   Auth error = service connection issue [OK]

Hint: Auth errors usually mean bad Azure service connection [OK]

Common Mistakes:

• Blaming missing ZIP for authentication errors
• Confusing app name mismatch with auth failure
• Assuming trigger issues cause auth errors

5. You want to automate deployment so that when code is pushed to GitHub, it builds, tests, and deploys your app to Azure automatically. Which combination of deployment methods should you use?

hard

A. CI/CD pipeline connected to GitHub with automated build and deploy steps

B. Manual ZIP deployment after pushing code to GitHub

C. FTP deployment triggered by GitHub webhook

D. Git deployment directly from GitHub without build or test

Solution

1. Step 1: Understand automation needs

   Automating build, test, and deploy requires a CI/CD pipeline connected to the source repository.

2. Step 2: Compare deployment methods

   Manual ZIP and FTP are manual or partial automation; Git deployment pushes code but lacks build/test automation.

3. Final Answer:

   CI/CD pipeline connected to GitHub with automated build and deploy steps -> Option A

4. Quick Check:

   Full automation = CI/CD pipeline [OK]

Hint: Full automation needs CI/CD pipeline linked to GitHub [OK]

Common Mistakes:

• Thinking Git deployment automates build and test
• Assuming FTP can automate deployment fully
• Using manual ZIP deploy for automation