Scenario Based Azure DevOps Interview Questions and Answers
1. Azure VM is not reachable. What will you check?
Check NSG rules, public IP, VM state, route table and firewall settings.
2. Azure DevOps pipeline suddenly fails.
Check recent code changes, pipeline logs, agent status and service connections.
3. Application is slow in Azure.
Check Azure Monitor metrics, CPU, memory, disk I/O and database performance.
4. Azure DevOps repo access given to wrong user.
Review project permissions, remove access and audit activity logs.
5. Pipeline triggered multiple times.
Check CI triggers, branch filters and webhook configuration.
6. Azure App Service deployment failed.
Check deployment logs, app settings, runtime version and rollback if required.
7. AKS pods are not starting.
Check pod logs, node resources, image pull secrets and events.
8. Storage account is publicly accessible.
Disable public access, configure firewall rules and use private endpoints.
9. Secrets leaked in pipeline logs.
Use Azure Key Vault, secret variables and mask values.
10. Build is very slow.
Enable caching, parallel jobs and optimize build steps.
11. Azure SQL Database is down.
Check service health, failover group and restore from backup if needed.
12. Load balancer shows unhealthy backend.
Check health probe path, NSG rules and application status.
13. User complains of high latency.
Use Azure Front Door or CDN and optimize backend services.
14. Azure cost increased suddenly.
Check Cost Management, identify unused resources and apply autoscaling.
15. Azure Function timing out.
Increase timeout, optimize code and check downstream services.
16. AKS cluster upgrade failed.
Rollback upgrade and perform node-by-node upgrade after testing in staging.
17. Infrastructure drift detected.
Reapply ARM/Bicep/Terraform templates to restore desired state.
18. Pipeline deployed wrong version.
Rollback release and enforce artifact versioning.
19. Application configuration not updated.
Restart service and validate app configuration or Key Vault reference.
20. API returns 403 error.
Check Azure AD authentication, role assignments and API permissions.
21. VM disk is full.
Resize disk, clean logs and enable log rotation.
22. Backup strategy needed.
Use Azure Backup and Recovery Services vault.
23. Multi-region disaster recovery required.
Use Traffic Manager, geo-replication and regular DR testing.
24. AKS service not accessible externally.
Check service type, ingress controller and NSG rules.
25. DevOps pipeline stuck in queue.
Add more agents and optimize job concurrency.
26. Unauthorized login detected.
Block user, rotate credentials and review Azure AD logs.
27. App crashes during traffic spike.
Enable autoscaling and tune resource limits.
28. Storage replication needed.
Use GRS or RA-GRS for disaster recovery.
29. DNS not resolving correctly.
Check Azure DNS records and TTL propagation.
30. How do you ensure Azure reliability?
Use multi-zone deployment, autoscaling, monitoring and backups.
Source: sureshtechlabs.com