DevOps Basics and Practices

Q: What is the core philosophy of DevOps, and how does it help improve software delivery?
A: DevOps is about breaking down barriers between development and operations teams. The goal is to work together to deliver better software faster. This involves automating tasks like testing and deployment, so there’s less manual work and fewer mistakes. 🚀

Q: Explain the difference between Continuous Integration, Continuous Delivery, and Continuous Deployment.
A:

• Continuous Integration (CI): Developers merge their code changes frequently, and automated tests verify these changes.

• Continuous Delivery (CD): Code is ready to be deployed at any time, but deployment happens manually.

• Continuous Deployment: Every successful code change is automatically deployed to production.

Q: How do you approach troubleshooting in a CI/CD pipeline?
A: First, check where the pipeline is failing (e.g., build, test, or deployment stage). Then, look at logs or error messages for clues. Start small—test locally if possible—and fix one issue at a time.

Infrastructure as Code (IaC)

Q: What is Terraform, and how does it differ from AWS CloudFormation?
A: Terraform is a tool to manage infrastructure across multiple cloud platforms, not just AWS. AWS CloudFormation, however, is specific to AWS. Terraform also uses its own language (HCL), while CloudFormation uses JSON or YAML.

Q: Can you explain Terraform state files and how to handle conflicts?
A: Terraform uses state files to keep track of your infrastructure. If multiple people change the state at the same time, conflicts happen. To avoid this, use remote state storage with locking, like AWS S3 with DynamoDB.

Q: How do you use terraform plan and terraform apply to manage resources?
A:

• terraform plan shows you what changes Terraform will make to your infrastructure before applying them.

• terraform apply makes those changes happen.

Q: Share an example of using Ansible for infrastructure automation.
A: You can use Ansible to install and configure software on multiple servers. For example, automating the setup of a web server with Nginx, including copying files and setting permissions.

AWS-Specific Questions

Q: What are the differences between AWS EC2, AWS Lambda, and AWS ECS? When would you use each?
A:

• EC2: Virtual servers—good for applications that need full control.

• Lambda: Serverless functions—great for running small tasks without managing servers.

• ECS: Containers—useful when deploying applications in Docker containers.

Q: How do you secure an S3 bucket for public access while ensuring necessary resources have access?
A: Block public access settings in S3, and then use bucket policies or IAM roles to allow only specific users or services to access the bucket.

Q: How does AWS IAM manage user roles and policies for secure access control?
A: IAM lets you create users and roles, and you assign them policies (JSON rules) to control what they can and can’t do. For example, a policy might allow access to S3 but block access to EC2.

Kubernetes and Containerization

Q: How does Kubernetes manage scaling and high availability?
A: Kubernetes automatically adds or removes pods based on traffic (horizontal scaling). It also ensures there’s always the desired number of healthy pods running for high availability.

Q: How do you troubleshoot a failing pod in Kubernetes?
A: Use kubectl describe pod <pod-name> to check events for errors and kubectl logs <pod-name> to see logs. This helps you identify if it’s a configuration or application issue.

Monitoring and Logging

Q: How would you set up monitoring for a production environment on AWS?
A: Use AWS CloudWatch to track metrics like CPU, memory, and application logs. You can set up alarms to notify you when something goes wrong.

Q: How do you analyze application logs for debugging and root cause analysis?
A: Centralize logs using tools like CloudWatch Logs or ELK Stack (Elasticsearch, Logstash, Kibana). Search for patterns, errors, or specific timestamps to find the issue.

CI/CD Pipelines

Q: Explain the key steps to setting up a CI/CD pipeline using AWS CodePipeline.
A:

1. Source: Connect your code repository (e.g., GitHub).

2. Build: Use AWS CodeBuild to compile and test the code.

3. Deploy: Deploy to services like EC2 or ECS using AWS CodeDeploy.

Q: How do you handle rollback scenarios during deployment failures?
A: Keep the last stable version ready. Automate rollbacks in CodeDeploy by monitoring health checks and reverting if something fails.

Linux Fundamentals

Q: How do you configure cron jobs to automate tasks?
A: Use crontab -e to create a schedule. For example, 0 2 * * * /path/to/script.sh runs a script at 2 AM daily.

Q: Can you explain the significance of file permissions and how to modify them?
A: Permissions control who can read, write, or execute files. Use chmod to change permissions, e.g., chmod 755 file allows the owner full access and others to read and execute.

Real-World Scenario

Q: How would you migrate an on-premises application to the AWS cloud using a lift-and-shift approach?
A:

1. Assess the application dependencies and configurations.

2. Create similar resources on AWS (e.g., EC2, RDS).

3. Use tools like AWS Application Migration Service to move the data.

4. Test the application thoroughly before switching traffic.

Q: Describe a challenging troubleshooting experience in a CI/CD pipeline.
A: Once, a build kept failing due to dependency conflicts. I checked the logs, updated the dependencies in the codebase, and re-ran the build. The issue was resolved, and I documented the fix for future reference.

Real-World Scenario: Troubleshooting Deployment Issues

Q: A deployment in AWS Elastic Beanstalk failed, and the application is down. How would you troubleshoot the issue?
A:

1. Check Elastic Beanstalk’s logs for errors (e.g., permissions, missing dependencies, etc.).

2. Verify the health of EC2 instances in the Elastic Beanstalk environment.

3. Review the application configuration settings (e.g., environment variables).

4. Ensure the application code has no errors by testing locally.

5. Roll back to the previous stable version using Elastic Beanstalk versioning.

Real-World Scenario: High Latency in Application

Q: Your web application hosted on AWS EC2 is experiencing high latency. How would you fix it?
A:

1. Check the server's CPU, memory, and disk utilization in CloudWatch.

2. Verify if the database (e.g., RDS) is the bottleneck (look for slow queries).

3. Use Elastic Load Balancer to distribute traffic across multiple EC2 instances.

4. Enable Auto Scaling to add more instances during peak times.

5. Use AWS CloudFront for caching static content closer to users.

Question: AWS IAM and Security

Q: How do you ensure secure access to an S3 bucket used for storing application logs?
A:

1. Create an IAM role with permissions to access the S3 bucket (e.g., s3:GetObject).

2. Attach the IAM role to the application server or Lambda function.

3. Apply an S3 bucket policy to restrict access to specific IP ranges or VPCs.

4. Enable S3 Server Access Logging to monitor access activities.

Real-World Scenario: Kubernetes Troubleshooting

Q: A Kubernetes pod is stuck in the "CrashLoopBackOff" state. What do you do?
A:

1. Run kubectl describe pod <pod-name> to check for error messages.

2. Check the container logs using kubectl logs <pod-name>.

3. Verify that the container image is valid and pulled correctly.

4. Ensure that the pod has the necessary resources (CPU, memory).

5. Check if any environment variables or secrets are misconfigured.

Question: Cost Optimization

Q: Your company is seeing high AWS bills every month. How would you optimize costs?
A:

1. Identify unused resources (e.g., idle EC2 instances) and terminate them.

2. Switch to Spot Instances or Savings Plans for workloads that are flexible.

3. Use AWS Trusted Advisor for recommendations on cost savings.

4. Right-size your resources (e.g., downscale oversized EC2 or RDS instances).

5. Enable S3 lifecycle rules to move infrequently accessed data to cheaper storage tiers (e.g., Glacier).

Real-World Scenario: CI/CD Pipeline Failure

Q: Your Jenkins pipeline fails at the deployment stage. What steps do you take?
A:

1. Check the error logs in Jenkins for detailed information.

2. Verify the credentials or keys used for accessing AWS (e.g., IAM roles).

3. Ensure the target environment (e.g., EC2, ECS) is up and reachable.

4. Test deployment scripts manually to pinpoint the issue.

5. Roll back to the previous stable release and notify the team.

VPC Configuration

Q: How do you set up a secure VPC with both public and private subnets?
A:

1. Create a VPC and divide it into public and private subnets.

2. Attach an Internet Gateway to the VPC for public internet access.

3. Assign public IPs to instances in the public subnet for internet-facing applications.

4. Use a NAT Gateway in the public subnet to allow private subnet instances to access the internet securely.

5. Add Security Groups and Network ACLs to control inbound/outbound traffic.

Real-World Scenario: Application Monitoring

Q: How do you monitor a production application for performance issues?
A:

1. Use CloudWatch Metrics to track CPU, memory, and disk utilization.

2. Set up CloudWatch Alarms to get notified of threshold breaches.

3. Enable AWS X-Ray for distributed tracing and identifying bottlenecks in requests.

4. Collect and analyze logs using CloudWatch Logs Insights or ELK stack (ElasticSearch, Logstash, Kibana).

5. Automate incident response using AWS Lambda for specific triggers.

Real-World Scenario: Database Migration

Q: How would you migrate an on-premises MySQL database to AWS RDS with minimal downtime?
A:

1. Use the AWS Database Migration Service (DMS) to migrate data.

2. Set up a replication instance in DMS for continuous data synchronization.

3. Perform schema conversion using the AWS Schema Conversion Tool (SCT) if needed.

4. Test the migrated database in RDS thoroughly before switching traffic.

5. Perform a final data sync and switch application connections to the RDS instance.

CI/CD for Containers

Q: How do you set up a CI/CD pipeline for containerized applications on AWS?
A:

1. Push your application code to a Git repository (e.g., CodeCommit, GitHub).

2. Build a Docker image using AWS CodeBuild or Jenkins.

3. Push the Docker image to Amazon ECR (Elastic Container Registry).

4. Deploy the container to AWS ECS using a task definition.

5. Automate the pipeline with AWS CodePipeline or a similar tool.

Real-World Scenario: Scaling Applications

Q: Your application experiences a sudden spike in traffic. How do you handle it?
A:

1. Enable Auto Scaling on your EC2 instances or ECS tasks to handle traffic spikes.

2. Use an Elastic Load Balancer to distribute traffic evenly.

3. Cache frequently accessed data using Amazon ElastiCache (Redis or Memcached).

4. Optimize database queries and enable read replicas for RDS.

5. Monitor the application using CloudWatch to prevent resource exhaustion.

Handling Failures

Q: What steps would you take to ensure high availability and disaster recovery for a web application?
A:

1. Use multi-AZ deployment for databases like RDS.

2. Set up an S3 bucket for storing static assets with versioning enabled.

3. Configure Route 53 for DNS failover between regions.

4. Create regular backups and use AWS Backup for automated recovery.

5. Implement Infrastructure as Code (IaC) tools like Terraform to recreate infrastructure in case of failure.