Question-113:- How do you configure sticky sessions in Kubernetes? In Kubernetes, sticky sessions means the requests from the same client are repeatedly routed to the same Pod instead of being load-balanced across different Pods. 1.Sticky sessions or session affinity is a convenient strategy to keep subsequent requests always reaching the same pod. 2.The simplest Kubernetes-native approach is sessionAffinity: ClientIP. Kubernetes supports ClientIP and None; the default is None. # Enable sticky sessions sessionAffinity: ClientIP 3.The default sticky-session timeout is 10,800 seconds (3 hours),

Question-112:-your application suddenly receives 10x normal traffic. how would you design aws infrastructure to handle the traffic? To handle a sudden 10x traffic increase, we design an elastic, multi-layered AWS architecture that scales compute dynamically, caches data at the edge, and protects backend databases from saturation 1.Amazon Route 53 Routes traffic globally with latency-based or geoproximity routing to spread the load across multiple AWS Regions if necessary 2. A 10x spike might be a DDoS(Distributed Denial-of-Service) attack. AWS WAF implements rate-limiting rules to block malic

Question-111:-Your application is healthy, but users experience intermittent timeouts. How would you identify whether the issue is in the application, network, infrastructure, or load balancer? we need to check load balancer metrics and logs to see how it handles traffic 1.If loadbalancer showing 504 error means the load balancer timed out waiting for a response from our application. If our app takes 70 seconds to reply but our load balancer timeout is set to 60 seconds, the load balancer cuts the connection. 2.If loadbalancer is it showing 502 error means a bad gateway, often caused by a kee