Senior AWS DevOps Engineering

Given an exchange-platform scenario, produce and prioritize measurable availability, latency, throughput, scalability, security and compliance, RTO, RPO, and cost requirements while stating assumptions and trade-offs.

Design a multi-AZ VPC with appropriate subnet tiers, routing, controlled egress, VPC endpoints, security groups, and network ACLs.

Select and justify Route 53, CloudFront, WAF, API Gateway, ALB, or NLB components for a specified traffic, latency, availability, and security profile.

Design and defend a highly available ECS service by selecting EC2 or Fargate and specifying multi-AZ placement, load balancing, autoscaling, health checks, task IAM, and secrets; identify requirements that would justify EKS instead.

Diagnose a failed or unstable EKS request path using workload status, events, probes, Services, Ingress, autoscaling, disruption controls, and node signals.

Design an RDS topology that meets availability and recovery targets using Multi-AZ deployment, read replicas, backups, failover, connection management, and encryption.

Structure reusable Terraform modules and isolated environments with explicit provider and module versions, inputs, outputs, state boundaries, and ownership boundaries.

Evaluate a Terraform plan for destructive replacement, dependency, drift, remote-state, locking, privilege, and sensitive-data risks before approving a production change.

Produce a zero-downtime ECS delivery and rollback runbook that uses immutable artifact promotion, test and security gates, approvals, health verification, rolling or blue-green deployment, and backward-compatible database migration.

Design least-privilege access for engineers, CI/CD systems, and workloads using IAM roles, short-lived credentials, permission boundaries, and managed secrets.

Define service SLIs and SLOs, then map them to actionable metrics, logs, traces, dashboards, burn-rate or symptom-based alerts, and error-budget decisions.

Design and defend a tested backup and disaster-recovery strategy that distinguishes Multi-AZ high availability from regional recovery and satisfies stated RTO and RPO targets.

Conduct and defend an end-to-end AWS production-readiness review under questioning about network and container choices, data and asynchronous messaging, failure modes, disaster recovery, security, performance, scaling, compliance, and cost.