DevOps Mühendisi - Senaryo Soruları

DevOps Mühendisi 10 soru 06.04.2026
Bu sorular ve cevaplar genel bilgilendirme ve mülakat hazırlık amaçlıdır. Gerçek mülakat sorularını yansıtmaz.
1

Senaryo: Production outage occurred, service down. Incident response plan?

1) Immediate assessment: Scope, impact, severity. 2) Communication: Stakeholders, status page. 3) Mitigation: Rollback, failover, hotfix. 4) Root cause analysis: Logs, metrics, traces. 5) Resolution ve verification. 6) Post-mortem: Document findings, action items. Priority: User impact minimization.
2

Senaryo: Deployment sonrası spike in error rate. Debugging approach?

1) Rollback decision: Business impact assessment. 2) Investigation: Logs (error patterns), metrics (correlation), traces (request flow). 3) Isolation: Pre-production testing, feature flags. 4) Fix ve validation. 5) Process improvement: Automated rollback, better testing.
3

Senaryo: Engineering team "daha hızlı deployment istiyor" diyor ama QA process bottleneck. Çözüm?

Shift-left testing: Unit tests, integration tests early. Automated testing: CI/CD pipeline integration. Feature flags: Progressive rollout, canary deployments. Monitoring: Real-time production validation. Balance: Speed vs quality, risk assessment.
4

Senaryo: Cloud bill %50 arttı, cost reduction gerek. Actions?

Audit: Resource utilization, unused services. Optimization: Right-sizing, reserved instances, auto-scaling. Architecture: Serverless migration, spot instances. Governance: Budget alerts, approval workflows. Education: Team awareness, cost optimization culture.
5

Senaryo: Security audit found vulnerabilities in production code. Response?

Risk assessment: Severity scoring (CVSS). Immediate mitigation: WAF rules, patches, disabling vulnerable features. Communication: Security team, management. Long-term: Secure SDLC, automated scanning, security training. Priority: Customer data protection.
6

Senaryo: Database performance degradation, slow queries. Approach?

1) Monitoring: Query performance metrics, slow query log. 2) Analysis: EXPLAIN plan, index usage. 3) Optimization: Index creation, query rewriting, schema changes. 4) Scaling: Read replicas, caching. 5) Capacity planning: Hardware upgrade, sharding.
7

Senaryo: Microservices architecture transition plan. Monolith'ten nasıl geçersiniz?

Strangler fig pattern: Incremental migration. Phases: 1) Identify boundaries, 2) API gateway setup, 3) Extract services incrementally, 4) Data decoupling. Challenges: Distributed transactions, data consistency. Tools: Service mesh, container orchestration.
8

Senaryo: New team member onboarding. DevOps practices nasıl teach edersiniz?

Documentation: Runbooks, architecture diagrams. Hands-on training: Sandbox environment, guided deployments. Shadowing: Pair programming, incident response participation. Continuous learning: Knowledge sharing sessions, documentation updates. Culture: Blameless post-mortems.
9

Senaryo: Multi-region deployment requirement. Architecture?

Active-active vs active-passive. Data replication: Multi-master, read replicas. DNS routing: Geo-based, latency-based. Failover: Automated, manual. Consistency models: Eventual consistency handling. Compliance: Data residency requirements.
10

Senaryo: Legacy application modernization. Strangler pattern uygulaması?

Pattern identification: Domain boundaries. API layer: Reverse proxy, BFF. Incremental extraction: Feature by feature. Data migration: Dual write, sync jobs. Testing: Parallel runs, A/B testing. Risk mitigation: Rollback capability, monitoring.