<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps interview questions on DevOps &amp; SRE interview questions</title><link>https://ewry.net/devops-sre-interview-questions/docs/devops-interview-questions/</link><description>Recent content in DevOps interview questions on DevOps &amp; SRE interview questions</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://ewry.net/devops-sre-interview-questions/docs/devops-interview-questions/index.xml" rel="self" type="application/rss+xml"/><item><title>Senior DevOps Interview Questions — System Design, K8s at Scale, SLOs</title><link>https://ewry.net/devops-sre-interview-questions/devops-middle-senior-interview-questions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ewry.net/devops-sre-interview-questions/devops-middle-senior-interview-questions/</guid><description>&lt;h1 id="devops-middle-senior-interview-questions"&gt;DevOps middle+, senior interview questions&lt;a class="anchor" href="#devops-middle-senior-interview-questions"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h3 id="1-design--architecture--strategy"&gt;1. Design / Architecture / Strategy&lt;a class="anchor" href="#1-design--architecture--strategy"&gt;#&lt;/a&gt;&lt;/h3&gt;
&lt;h4 id="1-how-would-you-design-a-scalable-fault-tolerant-multi-region-architecture-for-a-microservices-application-so-as-to-minimize-latency-and-downtime"&gt;1. How would you design a scalable, fault-tolerant, multi-region architecture for a microservices application so as to minimize latency and downtime?&lt;a class="anchor" href="#1-how-would-you-design-a-scalable-fault-tolerant-multi-region-architecture-for-a-microservices-application-so-as-to-minimize-latency-and-downtime"&gt;#&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;strong&gt;Goal&lt;/strong&gt;: Deploy microservices across multiple regions (e.g., AWS us-east-1, eu-west-1) for global low-latency access (&amp;lt;100ms), auto-scaling to handle traffic spikes, and 99.99% uptime via redundancy.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Infrastructure Layer (Scalability &amp;amp; Fault Tolerance)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use managed Kubernetes (EKS/GKE) clusters per region, with auto-scaling node groups (e.g., scale from 3-50 nodes based on CPU &amp;gt;70%).&lt;/li&gt;
&lt;li&gt;Deploy via IaC (Terraform) for consistent, reproducible setups.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example&lt;/strong&gt;: Horizontal Pod Autoscaler (HPA) in K8s scales pods from 5-100 replicas during peak loads.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2. Networking Layer (Minimize Latency)&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>