Devops and aws interview preparation Hyderabad
رفتن به کانال در Telegram
Who interested to learn Linux AWS and devops I will explain and I will give my support until you got job and no need to go for proxy after training. For traning call me 9154078579 For serious learners I will share my entire knowledge
نمایش بیشتر5 144
مشترکین
-124 ساعت
+87 روز
+6130 روز
در حال بارگذاری داده‌ها
کانال‌های مشابه
ابر برچسب‌ها
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
نوامبر '26نوامبر '26
نوامبر '26
+45
در 0 کانال‌ها
اکتبر '26
+100
در 0 کانال‌ها
Get PRO
سپتامبر '26
+107
در 0 کانال‌ها
Get PRO
اوت '26
+127
در 0 کانال‌ها
Get PRO
ژوئیه '26
+169
در 0 کانال‌ها
Get PRO
ژوئن '26
+140
در 0 کانال‌ها
Get PRO
مه '26
+145
در 0 کانال‌ها
Get PRO
آوریل '26
+163
در 0 کانال‌ها
Get PRO
مارس '26
+133
در 0 کانال‌ها
Get PRO
فوریه '26
+106
در 0 کانال‌ها
Get PRO
ژانویه '26
+111
در 0 کانال‌ها
Get PRO
دسامبر '25
+108
در 0 کانال‌ها
Get PRO
نوامبر '25
+112
در 0 کانال‌ها
Get PRO
اکتبر '25
+106
در 0 کانال‌ها
Get PRO
سپتامبر '25
+5
در 0 کانال‌ها
Get PRO
اوت '25
+1
در 0 کانال‌ها
Get PRO
ژوئیه '25
+3
در 0 کانال‌ها
Get PRO
ژوئن '25
+7
در 0 کانال‌ها
Get PRO
مه '25
+5
در 0 کانال‌ها
Get PRO
آوریل '25
+5
در 0 کانال‌ها
Get PRO
مارس '25
+4
در 0 کانال‌ها
Get PRO
فوریه '250
در 0 کانال‌ها
Get PRO
ژانویه '25
+8
در 0 کانال‌ها
Get PRO
دسامبر '24
+89
در 0 کانال‌ها
Get PRO
نوامبر '24
+305
در 0 کانال‌ها
Get PRO
اکتبر '24
+356
در 0 کانال‌ها
Get PRO
سپتامبر '24
+265
در 0 کانال‌ها
Get PRO
اوت '24
+227
در 0 کانال‌ها
Get PRO
ژوئیه '24
+155
در 0 کانال‌ها
Get PRO
ژوئن '24
+131
در 0 کانال‌ها
Get PRO
مه '24
+184
در 0 کانال‌ها
Get PRO
آوریل '24
+141
در 0 کانال‌ها
Get PRO
مارس '24
+178
در 0 کانال‌ها
Get PRO
فوریه '24
+187
در 0 کانال‌ها
Get PRO
ژانویه '24
+317
در 0 کانال‌ها
Get PRO
دسامبر '23
+113
در 0 کانال‌ها
Get PRO
نوامبر '23
+23
در 0 کانال‌ها
Get PRO
اکتبر '23
+48
در 0 کانال‌ها
Get PRO
سپتامبر '23
+54
در 0 کانال‌ها
Get PRO
اوت '23
+104
در 0 کانال‌ها
Get PRO
ژوئیه '23
+75
در 0 کانال‌ها
Get PRO
ژوئن '23
+72
در 0 کانال‌ها
Get PRO
مه '23
+49
در 0 کانال‌ها
Get PRO
آوریل '23
+94
در 0 کانال‌ها
Get PRO
مارس '23
+71
در 0 کانال‌ها
Get PRO
فوریه '23
+80
در 0 کانال‌ها
Get PRO
ژانویه '23
+180
در 0 کانال‌ها
Get PRO
دسامبر '22
+104
در 0 کانال‌ها
Get PRO
نوامبر '22
+116
در 0 کانال‌ها
Get PRO
اکتبر '22
+44
در 0 کانال‌ها
Get PRO
سپتامبر '22
+58
در 0 کانال‌ها
Get PRO
اوت '22
+52
در 0 کانال‌ها
Get PRO
ژوئیه '22
+53
در 0 کانال‌ها
Get PRO
ژوئن '22
+252
در 0 کانال‌ها
Get PRO
مه '22
+55
در 0 کانال‌ها
Get PRO
آوریل '22
+52
در 0 کانال‌ها
Get PRO
مارس '22
+80
در 0 کانال‌ها
Get PRO
فوریه '22
+24
در 0 کانال‌ها
Get PRO
ژانویه '22
+34
در 0 کانال‌ها
Get PRO
دسامبر '21
+45
در 0 کانال‌ها
Get PRO
نوامبر '21
+1 040
در 0 کانال‌ها
| تاریخ | رشد مشترکین | اشارات | کانال‌ها | |
| 10 نوامبر | +2 | |||
| 09 نوامبر | +3 | |||
| 08 نوامبر | +1 | |||
| 07 نوامبر | +4 | |||
| 06 نوامبر | +3 | |||
| 05 نوامبر | +3 | |||
| 04 نوامبر | +1 | |||
| 03 نوامبر | +5 | |||
| 02 نوامبر | +12 | |||
| 01 نوامبر | +11 |
پست‌های کانال
Hi i am going to start new aws&Devops session on 09-11-2026 @ 8 Am IST The training main intention is to clear the interview yourself ping me who are interested to join the session 9154078579
| 2 | Question:-118 How does Docker layer caching work?
1.Docker layer caching speeds up image build times by reusing unchanged intermediate layers from previous builds rather than executing every instruction in a Dockerfile from scratch
2.Docker uses different criteria to check if a layer can be reused based on the instruction type
--->If the text of the command (RUN, ENV, WORKDIR) has changed (even a simple argument change), the cache is invalidated.
---> Docker (COPY, ADD) calculates a unique checksum for every file and directory being added. It compares this checksum against the files in the cached layer. If any contents, permissions, or modifications have changed, the cache is invalidated.
---->For a command like RUN apt-get update, Docker only checks the command string. It does not know if the remote software repositories have new updates. It will pull from the cache anyway unless forced otherwise.
To learn aws&Devops from scratch ping me 9154078579 | 595 |
| 3 | Question:-117 How we can do helm upgrade to latest version of Ingress NGINX?
1.Before upgrading, we must fetch the latest chart metadata from our repository provider.
----->helm repo update ingress-nginx
2.To upgrade the release to the latest version, we can execute helm upgrade followed by our release name and the repository path
----->helm upgrade <RELEASE_NAME> ingress-nginx/ingress-nginx
? what is RELEASE_NAME
--->If our Application is named my-app, the Helm release will also be named my-app.
### The release name is the handle we use to track, manage, upgrade, or uninstall that specific deployment
3.If the latest version causes issues or application downtime, immediately revert to our last stable revision
----->helm rollback <release-name> <revision-number> --namespace <namespace>
To learn aws&Devops from scratch ping me 9154078579 | 690 |
| 4 | Question-116:- Your company wants to migrate manually managed infrastructure to Terraform. How would you approach the migration without disrupting production?
To migrate manually managed infrastructure to Terraform without disrupting production terraform apply must yield zero changes (0 to add, 0 to change, 0 to destroy)
1.Always plan to migrate foundational components first (VPCs, IAM roles, Subnets) followed by downstream consumer resources (Databases, VMs).
2.we need to run terraform plan -generate-config-out=generated.tf. This instructs Terraform to analyze the live state and generate the exact HCL syntax matching to our infrastructure.
3.Inject lifecycle policies dynamically to protect resources while performing state alignment. Need to use prevent_destroy = true to guarantee nothing is accidentally deleted, and ignore_changes to bypass fast-moving live values like tags or metrics during the import phase.
4. Continuously run terraform plan. Compare live realities against our drafted configurations and fix formatting, attributes, or variable discrepancies.
5.Update identity policies (IAM) to change engineers' permissions to read-only for managed assets for Revoke Manual Write Access
To learn aws&Devops from scratch ping me 9154078579 | 775 |
| 5 | Question:-115-- > Can you explain terraform lifecylce ?
Terraform Lifecycle" refers to two distinct related concepts
1.The Core Workflow Lifecycle
[Write] ➔ [Init] ➔ [Plan] ➔ [Apply] ➔ [State Management] ➔ [Destroy]
Write:--->we can write our .tf files according our requirements
Initialize (terraform init)----->Prepares the directory by downloading the necessary cloud provider plugins (like AWS, Azure, or GCP) and setting up our state backend.
Plan (terraform plan): ----->Compares our code against the current reality of our cloud environment. It prints a preview showing exactly what will be added, changed, or deleted.
Apply (terraform apply):----> Executes the changes outlined in the plan. It calls the cloud provider APIs to spin up or modify our physical resources
State Management: ---->Terraform updates a file (terraform.tfstate) that serves as a single source of truth, mapping our code definitions to the actual IDs of real-world resources
Destroy (terraform destroy): ----->Cleans up our infrastructure by safely deleting all
resources tracked by that state file
2. The lifecycle Configuration Block
when we update an attribute that forces a resource to be recreated, Terraform deletes the old resource first and then creates the new one.To override this default behavior, we can insert a nested lifecycle block inside any resource configuration
create_before_destroy = true---->Forces Terraform to stand up a new replacement resource before tearing down the old one.
prevent_destroy = true--->Rejects any terraform apply or destroy command that attempts to delete this resource.
ignore_changes = [attr]------>Tells Terraform to look away if specific attributes change outside of the code---->Resources modified by external tools (e.g., cloud auto-scaling groups modifying instance counts or replica tags).
Example:
resource "aws_instance" "web_server" {
ami = "ami-123456"
instance_type = "t2.micro"
lifecycle {
create_before_destroy = true
prevent_destroy = false
}
}
To learn aws&Devops from scratch ping me 9154078579 | 984 |
| 6 | 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), and we can configure it with sessionAffinityConfig.clientIP.timeoutSeconds; the maximum is 86,400 seconds (24 hours).
4.There are two common places where sticky sessions can be configured
Kubernetes Service-------->sessionAffinity: ClientIP
Ingress / external Load Balancer--------->Cookie-based or LB-specific stickiness
5.Sticky sessions are often used for applications that store session state locally in the Pod
To learn aws&Devops from scratch ping me 9154078579 | 1 107 |
| 7 | 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 malicious traffic at the edge before it consumes backend bandwidth.
3.ALBs scale automatically, but a sudden instantaneous 10x burst can outpace its scaling algorithm. If the spike is predictable (e.g., a flash sale), we must pre-warm the ALB via AWS Support to ensure it handles the immediate wall of traffic.
4.Applications must be stateless so instances can be created or destroyed dynamically without losing user sessions
5.A 10x traffic surge creates a massive flood of database connection requests, which can exhaust DB memory. RDS Proxy pools and shares these connections to keep the database from buckling under the overhead.
To learn aws&Devops from scratch ping me 9154078579 | 1 094 |
| 8 | 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 keep-alive mismatch where our backend closes an idle connection before the load b
alancer expects it to
3.Need to check locked database tables, or memory pressure that temporarily stops the app from responding to new requests.
4. specific queries or slow database calls cause rare spikes that exceed timeout limits, even though average response times look fine.
5.we need to check VPC flow logs or network interfaces for high TCP retransmissions or packet drops.
To learn aws&Devops practically from scratch ping me 9154078579 | 928 |
| 9 | Hi i am going to start Generative artificial intelligence (GenAI) session on 5-10-2026 Monday@8AM IST
Generative AI & Foundation Models
Prompt Engineering
RAG & Knowledge Bases
AI Agents & Agentic AI
ping me who are interested to jion in my session 9154078579 | 976 |
| 10 |  +2Implemented RAG on AWS by Building an AI-powered Knowledge Base, with Amazon Bedrock and S3 Vectors
what is RAG?
RAG = Retrieval-Augmented Generation
RAG is an AI technique where a Large Language Model (LLM) retrieves relevant information from an external knowledge source and then uses that information to generate an answer.
What is Knowledge Base in RAG?
A Knowledge Base (KB) in RAG is a collection of information that an AI system can search and retrieve from when answering a user's question.
what is Amazon Bedrock?
Amazon Bedrock is an AWS fully managed service for building generative AI applications using foundation models (FMs) from Amazon and other AI providers. It provides APIs and tools so we can use these models without managing the underlying model infrastructure
To learn Generative artificial intelligence (GenAI) from scratch ping me 9154078579 | 996 |
| 11 | Question-110:-Two applications are running in different VPCs and need secure communication. How would you design the connectivity?
1.VPC Peering connects two VPCs using the cloud providers internal, private backbone network. Traffic remains entirely private and never traverses the public internet.
2.AWS PrivateLink is the ideal solution for Application B acts strictly as a "service" or API provider to Application A—or if both VPCs have overlapping IP address blocks
3.If we require strict, fine-grained HTTP/HTTPS request-level authentication without managing complex routing tables, Amazon VPC Lattice provides a managed service mesh layer.
To learn aws&Devops from scratch ping me 9154078579 | 742 |
| 12 | Question-109:- You have a Java application running inside a Docker container on a VM. If the process has one PID inside the container and another PID on the host, which PiD is greater and why?
1.The host PID is always greater than the container PID
2.Inside the container, the namespace creates a isolated environment where our Java application thinks it is the only major process running, assigning it PID 1 (or a very low number).
3.On the host, the process is viewed as part of the entire system's global process tree. Since the host has been running many system processes, daemons, and services.
4.The host tracks every process across the entire virtual machine consecutively, the global counter will almost always be much higher than the isolated, freshly initialized counter inside the container.
To learn aws&Devops from scratch ping me 9154078579 | 886 |
| 13 |  How to use driftctl for aws terraform ?
1. driftctl is used to find differences between our AWS live infrastructure and our Terraform state files
2. driftctl needs read-only permissions to scan our AWS environment. It automatically picks up standard AWS environment variables
3.By default, running driftctl scan looks for a local terraform.tfstate file in our current working directory.
driftctl scan --from tfstate://terraform.tfstate
4.If our AWS infrastructure is split across multiple state files, pass multiple --from flags
driftctl scan --from tfstate+s3://my-bucket/vpc.tfstate --from tfstate+s3://my-bucket/apps.tfstate
To learn aws&Devops from scratch ping me 9154078579 | 1 125 |
| 14 | Question:-108 Explain what a Helm release is, and how it is different from a chart.
In Helm a release is a running, deployed instance of a Helm chart inside a Kubernetes cluster
1.Helm release it consists of actual running Kubernetes resources (Pods, Services, etc.). Helm chart is a compressed file (.tgz), or a repository.
2.we can deploy the same chart multiple times to create separate releases (e.g., frontend-dev and frontend-prod). we only need one chart for an application.
3. Helm stores release information dynamically as Kubernetes Secrets within the cluster itself. It doesn't need an external database to track what is currently running.
4. Every time we update a release (e.g., changing an environment variable or upgrading the image version via helm upgrade), Helm increments the revision number (Revision 1, Revision 2, etc.). If an upgrade fails, we can instantly rollback the specific release to a previous stable revision using helm rollback.
To learn aws&Devops practically ping me 9154078579 | 1 028 |
| 15 |  بدون متن... | 954 |
| 16 |  بدون متن... | 1 110 |
| 17 | Question:-106 Suppose your EKS cluster is experiencing pod CrashLoopBackOff issues. Walk me through your debugging process.
When an Amazon EKS cluster experiences a CrashLoopBackOff issue, it means the container image was pulled successfully, but the application inside the container is starting, crashing, and restarting repeatedly
1. we can describe pod and check initially
kubectl describe pod <pod-name> -n <namespace>
we can check events section and the container status
A. If a liveness probe is misconfigured or too aggressive, it will kill a healthy application before it finishes booting up.
B. Issues mounting AWS EBS volumes, EFS, or missing ConfigMaps/Secrets keys.
2.If the platform infrastructure looks healthy, the bug is almost certainly inside the application
kubectl logs <pod-name> -n <namespace> --previous
Missing database connection strings, unhandled exceptions, database migration failures, or filesystem permission errors.
3.If the app crashes because it cannot connect to an Amazon RDS database, I verify that the EKS cluster security group is allowed on the RDS instance security group
To learn aws&Devops from scratch ping me 9154078579 | 1 195 |
| 18 | Hi I am going to start new aws&Devops session on 16-09-2026 Wednesday @7 Am IST The training main intention is to clear the interview on your own
Ping me who are interested to Jion the session 9154078579 | 1 108 |
| 19 | How To Get the Pod IP in Kubernetes ?
1.Each Pod is assigned a unique IP address upon initialization, which facilitates communication.
2.containers in a Pod share the same network namespace, IP address, and resources and can all reach each other's ports on localhost.
3.The Container Network Interface (CNI) plugin assigns IP addresses to pods by communicating with the container runtime when a pod is created and releasing them when the pod is deleted.
4.The CNI plugin is configured with a large CIDR range (e.g., 10.10.0.0/16)
5.When a new pod is created, Kubernetes asks the CNI plugin for an IP
6.The CNI plugin has an IPAM (IP Address Management) component that tracks all IPs
7.The CNI configures the network interfaces and routing for the pod
To learn aws&Devopd from scratch ping me 9154078579 | 1 261 |
| 20 | what is dns resolution in pod?
1. It is the process where an application inside a pod translates domain or service names into IP addresses using the cluster's internal DNS server
2. Kubernetes automatically injects an /etc/resolv.conf file into every container inside a pod.
3. Pod IPs in Kubernetes are ephemeral and change constantly when pods crash or scale, applications rely on stable Service names to talk to one another.
To solve pod DNS resolution issues, we must check CoreDNS status
example : Need to check if CoreDNS pods are running using kubectl get pods -n kube-system -l k8s-app=kube-dns
Inspect CoreDNS logs for errors using kubectl logs -n kube-system -l k8s-app=kube-dns
To learn aws&Devops from scratch ping me 9154078579 | 1 124 |
