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.