Cloud Native Development Interview Questions and Answers (With Reasoning)

Key takeaways

• Cloud native is a way of building and running software for dynamic environments: containers, microservices, automation, declarative configuration.
• Kubernetes questions focus on Pods, Deployments, Services, probes and scaling, not on memorising YAML.
• Resilience patterns (timeouts, retries with backoff, circuit breakers) come up in nearly every senior interview.
• Say why. Interviewers hire people who explain trade-offs.

How to answer

For each question: give a one-line definition, the reason it exists and a concrete example. Where a command helps, show it. The Kubernetes documentation and Docker documentation are the places to confirm details.

Foundations

1. What does cloud native mean?

Building and running applications to take advantage of cloud platforms: packaged in containers, loosely coupled (often microservices), managed through automation and declarative configuration, and designed to scale and recover from failure. It is about how software is built and operated as well as where it runs.

2. How does cloud native differ from lift-and-shift?

Lift-and-shift moves an existing application to cloud servers largely unchanged. Cloud native redesigns it to use managed services, scale horizontally and tolerate instance failure.

3. What is the twelve-factor app?

A methodology for building services that are portable and easy to operate, published at 12factor.net. Key ideas: one codebase, explicit dependencies, configuration in the environment, backing services as attached resources, stateless processes, logs as event streams, and disposable processes.

4. Why should config live in the environment?

So the same build artefact runs in dev, test and production with different settings, and secrets are not committed to source control.

5. Monolith or microservices?

Microservices give independent deployment and scaling but add network calls, distributed failure and operational cost. A well-structured monolith is often right for small teams. Choose based on team size and need, not fashion.

Containers

6. What is a container and how is it different from a VM?

A container is an isolated process using the host kernel, with its own filesystem view through namespaces and resource limits through cgroups. A VM carries a full guest operating system. Containers start faster and are lighter, VMs isolate more strongly.

7. What is the difference between an image and a container?

An image is a read-only template of layers. A container is a running instance of an image with a writable layer.

8. How do you keep images small and safe?

Use a minimal base image, multi-stage builds, pin versions, run as a non-root user and scan images for known vulnerabilities.

docker build -t myapp:1.0.
docker run --rm -p 8080:8080 myapp:1.0

9. Why are containers considered ephemeral?

They can be stopped and replaced at any time. Anything that must survive goes in a volume or an external store, not the container's writable layer.

Kubernetes

10. What is a Pod?

The smallest deployable unit: one or more containers sharing network and storage. Most Pods have one main container.

11. What does a Deployment do?

It declares the desired number of Pod replicas and handles rolling updates and rollbacks through ReplicaSets.

kubectl create deployment web --image=nginx --replicas=3
kubectl rollout status deployment/web
kubectl rollout undo deployment/web

12. What is a Service?

A stable network endpoint that load-balances across a changing set of Pods selected by labels. Types include ClusterIP, NodePort and LoadBalancer.

13. Liveness, readiness and startup probes?

Liveness tells Kubernetes when to restart a stuck container. Readiness decides whether a Pod receives traffic. Startup protects slow-starting apps from being killed too early.

14. ConfigMap versus Secret?

Both inject configuration. Secrets are meant for sensitive values, but they are only base64-encoded by default, so enable encryption at rest and restrict access with RBAC.

15. How does Kubernetes scale?

The Horizontal Pod Autoscaler adjusts replica counts based on metrics such as CPU. The Cluster Autoscaler adds or removes nodes. Always set resource requests and limits.

16. A Pod is in CrashLoopBackOff. What do you check?

kubectl describe pod <name>
kubectl logs <name> --previous

Look for application errors, bad configuration, missing secrets, failing probes or out-of-memory kills.

Resilience

17. What is a circuit breaker?

A pattern that stops calling a failing dependency for a while, so failures do not cascade and the dependency can recover.

18. How should retries work?

Retry only idempotent operations, use exponential backoff with jitter, cap attempts and set timeouts. Blind retries can turn a small outage into a large one.

19. What is idempotency and why does it matter?

An operation that gives the same result if repeated. It makes retries safe, for example using a unique request key for payments.

20. What is graceful shutdown?

On SIGTERM the service stops accepting new work, finishes in-flight requests and exits before the grace period ends, so rolling updates do not drop requests.

Delivery

21. What is CI/CD?

Continuous integration builds and tests every change. Continuous delivery keeps the code always releasable, and continuous deployment releases automatically. See the CI/CD interview questions for more.

22. Explain blue-green and canary deployments.

Blue-green switches traffic between two full environments. Canary sends a small share of traffic to the new version first and widens it if metrics look healthy.

23. What is GitOps?

Using Git as the source of truth for desired state, with an agent that reconciles the cluster to match it, giving audit and easy rollback.

24. What is infrastructure as code?

Defining infrastructure in version-controlled files, so environments are reproducible and reviewed like code.

Observability

25. Monitoring versus observability?

Monitoring watches known signals and alerts on them. Observability lets you ask new questions of a system using metrics, logs and traces.

26. What are the three pillars of observability?

Metrics (numbers over time), logs (events) and traces (a request's path across services).

27. What are SLIs, SLOs and error budgets?

An SLI is a measurement, such as the share of successful requests. An SLO is the target for it. The error budget is how much failure the target allows, and it guides how fast to release.

Security

28. How do you secure a cloud native application?

Least-privilege identities, image scanning, non-root containers, network policies, secrets management, signed images and regular patching. The Certified Kubernetes Security Specialist path goes deep on this.

29. What is a service mesh?

A layer, often sidecar proxies, that handles service-to-service traffic: mutual TLS, retries, routing and telemetry, without changing application code. It adds complexity, so use it when needed.

30. Where does the shared responsibility model apply?

The cloud provider secures the underlying platform. You secure identity, configuration, data and your workloads.

Next steps

For hands-on preparation, the Certified Kubernetes Administrator (CKA) and DevOps courses give practice with the tools behind these questions. More interview prep: cloud DevOps practices questions and cloud development tools questions.