⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All AWS & Cloud Architecture Interview Questions Scenario 122 of 179 in AWS & Cloud Architecture
Senior DevOps / SRE Azure & Cloud Azure DevOps & App Services Enterprise Azure

Q: Your Azure DevOps pipeline is green, but the application is down after deployment. How would you troubleshoot it?

Root cause isolation and troubleshooting procedure when an Azure DevOps CI/CD pipeline reports successful stage execution, but the deployed web application or API returns HTTP 500 or 503.

#Azure #Azure DevOps #App Service #Troubleshooting #CI/CD
🎙️ Candidate Opening & Architectural Context
"A green Azure DevOps pipeline only proves that build artifacts and ARM/Bicep deployments succeeded from the agent's perspective. It does not verify application runtime health unless automated post-deployment smoke tests are configured."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: A green Azure DevOps pipeline only proves that build artifacts and ARM/Bicep deployments succeeded from the agent's perspective. It does not verify application runtime health unless automated post-deployment smoke tests are configured.

1

Stream Azure App Service / Container Live Logs

Connect to the application container via Azure CLI or Kudu console to capture runtime crash logs that occurred after the pipeline detached.

az webapp log tail --name app-production-eus --resource-group rg-production-app
# For containerized apps:
az webapp log download --name app-production-eus --resource-group rg-production-app
2

Validate Key Vault References & App Settings

Check if App Service App Settings contain invalid Key Vault references (@Microsoft.KeyVault(...)). If the App Service Managed Identity lacks Get permissions or Key Vault networking blocks the App Service outbound IP, the app fails on boot.

Advertisement
3

Implement Pipeline Post-Deployment Health Probes

Update the azure-pipelines.yml with a post-deployment verification task using curl or PowerShell Invoke-RestMethod that validates the live health endpoint before marking the job green.

- task: AzureCLI@2
  inputs:
    scriptType: 'bash'
    scriptLocation: 'inlineScript'
    inlineScript: |
      STATUS=$(curl -s -o /dev/null -w "%{http_code}" https://$(webAppName).azurewebsites.net/healthz)
      if [ "$STATUS" -ne 200 ]; then
        echo "Health check failed with HTTP $STATUS"
        exit 1
      fi
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"A green pipeline without a verification stage only verifies artifact transfer. Stream az webapp log tail and check Key Vault managed identity permissions."
⚡ 60-Second Elevator Pitch Talking Points
  • Stream real-time runtime logs via az webapp log tail to view application boot crashes.
  • Verify Azure Key Vault references (@Microsoft.KeyVault) and App Service Managed Identity permissions.
  • Check port binding: ensure WEBSITES_PORT matches the container exposed port.
  • Add automated post-deployment health check tasks in azure-pipelines.yml to fail the pipeline on HTTP 5xx.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Treating architectural triage in isolation without establishing clear failure domains and circuit breaker boundaries when addressing troubleshoot Cascading failures in microservices occur when upstream services lack timeouts, retries with jitter, and circuit breakers.
  2. Applying disruptive configuration changes directly to live production environments without canary validation Skipping canary rollouts maximizes blast radius, turning minor configuration oversights into company-wide Sev-1 outages.
  3. Hardcoding environment dependencies and endpoint URLs instead of leveraging dynamic service discovery Hardcoded endpoints fail during failover migrations or dynamic pod rescheduling, requiring manual redeployments to recover.
  4. Omitting blameless postmortem analysis and actionable preventative action items following critical system incidents Blameless RCAs identify systemic organizational and architectural vulnerabilities, preventing recurring outages and fostering engineering trust.
Advertisement
Want more AWS & Cloud Architecture scenarios?
Explore our complete collection of scenario-based AWS & Cloud Architecture interview runbooks.
Browse All AWS & Cloud Architecture Questions →