DevOps & Cloud Interview Prep: Real Scenarios & Answers

Deploying EKS clusters across AWS accounts with CDK is a common senior interview scenario — here's how to handle VPC peering, Transit Gateway attachments, and IAM trust policies correctly.You'll learn:How to structure a multi-account CDK app using Stacks across environments with explicit env account/region targetsWhen to use VPC peering vs Transit Gateway for cross-account EKS network connectivity, and the trade-offs at scaleHow to wire up Transit Gateway attachments and route table propagation so worker nodes can reach shared servicesCross-account IAM role assumptions and EKS RBAC config required for cluster access from a management accountCommon CDK gotchas: bootstrap trust policies, asset S3 bucket permissions, and cross-account CFN execution rolesKeywords: cross-account EKS CDK, AWS Transit Gateway EKS, VPC peering Kubernetes, multi-account EKS architecture, AWS CDK EKS interview🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Correlating OpenTelemetry traces with CloudWatch Logs Insights across Lambda and Step Functions is a common senior interview scenario — here's exactly how to answer it.You'll learn:How to propagate trace context (W3C TraceContext headers) across Lambda invocations and Step Functions state transitions so trace IDs land in your structured logsConfiguring the AWS Distro for OpenTelemetry (ADOT) Lambda layer to auto-instrument functions without cold-start penaltiesWriting CloudWatch Logs Insights queries that join on trace_id to reconstruct an end-to-end execution timeline across servicesWhere correlation breaks — async Step Functions callbacks, missing X-Amzn-Trace-Id propagation, and log sampling mismatchesTrade-offs between ADOT, X-Ray native SDK, and a third-party collector like the OpenTelemetry Collector on FargateKeywords: OpenTelemetry Lambda tracing, CloudWatch Logs Insights trace correlation, ADOT Step Functions, serverless observability interview questions🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Splitting a monolithic 4GB Terraform state file into scoped microstates is one of the nastiest live-infrastructure challenges you'll face — here's how to do it without downtime using terraform state rm and moved blocks.You'll learn:Why state files balloon past 4GB and why that breaks plan/apply performanceHow to use terraform state rm to surgically extract resources without destroying themUsing moved blocks to re-home resources into child state backends cleanlySequencing the migration to avoid drift, lock contention, and accidental deletesHow to validate microstate integrity with terraform state list and targeted plans before cutting overKeywords: terraform state splitting, terraform state rm, moved blocks terraform, monorepo to microstate migration, terraform refactor interview🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Designing a monorepo CI pipeline that doesn't collapse under 1,000 microservices means getting Bazel remote caching and selective test execution right from the start.You'll learn:How to structure a monorepo CI pipeline so only affected services trigger builds — using Bazel's dependency graph to compute the minimal affected setConfiguring Bazel remote caching (local cache, shared remote cache via gRPC or HTTP) to avoid rebuilding unchanged targets across parallel CI workersSelective testing strategies: combining bazel query with --build_event_stream to identify and run only impacted test targetsCommon failure modes at scale — cache poisoning, overly broad BUILD file dependencies, and flaky remote executor connectionsHow to structure the CI orchestration layer (GitHub Actions, Buildkite, or Tekton) to fan out Bazel shards without thrashing the remote cacheKeywords: monorepo CI pipeline, Bazel remote caching, selective testing microservices, CI at scale DevOps interview, platform engineering build systems🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Learn how to generate dynamic Azure RBAC role assignments using Pulumi with YAML-driven definitions — including tag-scoped conditions like restricting storage access to env:prod resources only.You'll learn:How to define custom Azure RBAC roles in YAML and hydrate them through Pulumi's automation layerUsing condition and conditionVersion fields in role assignments to enforce attribute-based access control (ABAC)Scoping storage permissions to resources matching specific tag key/value pairs at assignment timeStructuring Pulumi component resources so YAML definitions stay DRY across multiple environmentsCommon gotchas: condition syntax errors, propagation delays, and principal vs. scope mismatchesKeywords: Azure RBAC Pulumi, dynamic role assignments Azure, Pulumi YAML infrastructure, Azure ABAC tag conditions, custom RBAC roles interview🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Taming Prometheus cardinality explosion in an Istio service mesh — dropping from 10 million to 500K active series using relabel_configs and recording rules — is exactly the kind of production war story senior SRE interviews dig into.You'll learn:Why Istio telemetry generates cardinality explosions and which high-cardinality labels (source_workload, destination_service, pod IPs) are the usual culpritsHow to use metric_relabel_configs to drop or rewrite labels before series are ingested into TSDB storageWriting recording rules to pre-aggregate high-resolution Istio metrics into lower-cardinality rollupsUsing topk and cardinality analysis queries to identify which metrics are burning your series budgetTrade-offs between dropping labels at scrape time versus aggregating at query time — and why interviewers care about the differenceKeywords: Prometheus cardinality, Istio metrics, relabel_configs, recording rules, TSDB series limit🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

A developer pushes a Terraform module with a public S3 bucket — here's exactly how to catch and block it in your Argo CD pipeline using Conftest policy-as-code before it ever reaches production.You'll learn:How Conftest integrates with Argo CD as a pre-sync hook to enforce OPA policies on Terraform plansWriting a Rego rule that flags acl = public-read or block_public_acls = false on aws_s3_bucket resourcesWhere in the GitOps workflow the gate fires — and why admission controllers alone aren't enough for IaC driftHow to surface policy failures as Argo CD sync errors so engineers see the violation before merge, not after deployCommon gotchas: Terraform plan JSON output format, conftest namespace mismatches, and false positives on legacy modulesKeywords: Conftest Argo CD policy, OPA Terraform GitOps, block public S3 bucket IaC, GitOps security controls, Rego policy Terraform plan🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Managing a Terragrunt dependency graph across 500+ modules without hitting circular dependencies or version drift is one of the hardest scaling problems in platform engineering.You'll learn:How to map and audit a large Terragrunt dependency graph using terragrunt graph-dependencies and DAG visualisation toolsPatterns for structuring module hierarchies to prevent circular dependencies before they reach CIEnforcing module versioning with OCI registries — why OCI beats Git tags at this scaleHow to segment a 500+ module monorepo into dependency tiers so targeted runs stay fastCommon failure modes: implicit dependencies, missing mock_outputs, and run-all ordering bugsKeywords: Terragrunt dependency graph, Terragrunt at scale, OCI module registry, circular dependencies Terraform, platform engineering IaC🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

External Secrets Operator lets you sync HashiCorp Vault dynamic secrets directly into Kubernetes Secrets — no Vault Agent sidecars, no annotation sprawl.You'll learn:How ESO's ExternalSecret and SecretStore CRDs map Vault paths to Kubernetes SecretsWhy dynamic secrets (short-lived, auto-rotated) are preferable to static tokens and how ESO handles lease renewalThe auth methods ESO supports for talking to Vault — Kubernetes auth vs. AppRole and when to use eachCommon failure modes: stale secrets after Vault seal, RBAC misconfigs, and refresh interval gotchasHow to scope a ClusterSecretStore safely across namespaces without over-permissioningKeywords: External Secrets Operator, HashiCorp Vault Kubernetes integration, dynamic secrets management, Vault sidecar alternative, Kubernetes secrets sync🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud

Parallel Jenkins jobs deploying Helm charts can deadlock silently — here's how to catch and fix mutex contention before it kills your pipeline.You'll learn:Why concurrent Helm deploys compete for the same release lock and how that surfaces as a deadlock in JenkinsHow to run jstack against the Jenkins JVM to capture thread dumps and identify which threads are waiting on a monitor lockReading mutex lock output to pinpoint the blocked executor and the thread holding itHelm-side mitigations: namespace isolation, --atomic flag behaviour, and serialising releases with lockfiles or pipeline lock() stepsWhen to escalate from a workaround to a structural fix — separate agents, dedicated namespaces, or a Helm operator patternKeywords: Jenkins parallel jobs deadlock, Helm chart deployment lock, jstack thread dump Jenkins, mutex lock CI/CD pipeline, Jenkins pipeline concurrency🎧 Listen, then go deeper — DevOps & Cloud interview-prep ebooks at DevOpsInterview.Cloud