Scribd
Upload
2 views7 pages

devops interview

The document outlines key concepts in DevOps, including the DevOps lifecycle, CI/CD pipeline, and various tools and roles involved in the process. It provides detailed instructions on configuring Git, Jenkins, Docker, AWS services, and troubleshooting techniques. Additionally, it explains branching strategies, webhooks, and the differences between public and private subnets in AWS.

Uploaded by

poojanandish1993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views7 pages

devops interview

The document outlines key concepts in DevOps, including the DevOps lifecycle, CI/CD pipeline, and various tools and roles involved in the process. It provides detailed instructions on configuring Git, Jenkins, Docker, AWS services, and troubleshooting techniques. Additionally, it explains branching strategies, webhooks, and the differences between public and private subnets in AWS.

Uploaded by

poojanandish1993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Here are the answers to your next set of questions:

1. What is the lifecycle of DevOps?


The DevOps lifecycle includes several stages aimed at enhancing
collaboration between development and operations teams to deliver
software efficiently. The typical DevOps lifecycle includes:
1. Plan: Define project requirements and features.

2. Develop: Write and develop the application code.

3. Build: Compile code and package it for deployment.

4. Test: Automatically test the application to detect bugs and issues.

5. Release: Deploy the application to a staging or production


environment.

6. Deploy: Roll out the application to production.

7. Operate: Monitor the application and infrastructure for issues.

8. Monitor: Continuous monitoring for performance, security, and logs to


ensure health.

2. Command to add username and mail in git


To set your Git username and email:
bashCopyEditgit config --global user.name "Your Name"
git config --global user.email "your.email@example.com"

This will set the global username and email for all repositories. If you want to
set them for a specific repository, omit --global.

3. Explain end-to-end CI/CD pipeline


An end-to-end CI/CD pipeline automates the entire process of software
delivery, from code development to production deployment:
1. Code Commit: Developers commit code to the version control system
(e.g., Git).

2. Build: The CI server (e.g., Jenkins) builds the code and produces
artifacts (e.g., .jar, .war files).

3. Automated Testing: Tests (unit, integration, etc.) are run on the code
to ensure quality.

4. Deployment: The code is deployed to staging and then to production.


5. Monitoring: After deployment, the system is monitored for
performance and errors.

6. Rollback: If a failure occurs, a rollback can be initiated to revert to the


previous stable version.

4. Which tools are you using for CI/CD?


Some common CI/CD tools include:
 Jenkins: Automation server for building, testing, and deploying code.

 GitLab CI/CD: GitLab’s built-in CI/CD pipeline.

 CircleCI: Cloud-based CI/CD tool.

 Travis CI: Hosted CI service, especially for open-source projects.

 AWS CodePipeline: AWS’s CI/CD service for automating build, test,


and deploy phases.

5. Types of jobs created in Jenkins


In Jenkins, you can create different types of jobs:
1. Freestyle Project: A simple build job for one-time or ad-hoc builds.

2. Pipeline: A job defined by a Jenkinsfile with stages like Build, Test, and
Deploy.

3. Multibranch Pipeline: A type of pipeline job that works with multiple


Git branches.

4. GitHub Organization: Automatically creates a job for each repository


in a GitHub organization.

6. Write a Dockerfile using Python & explain


Here’s an example of a Dockerfile for a Python application:
dockerfileCopyEdit# Use the official Python base image
FROM python:3.8-slim

# Set the working directory in the container


WORKDIR /app

# Copy the requirements file into the container


COPY requirements.txt .

# Install the dependencies


RUN pip install --no-cache-dir -r requirements.txt

# Copy the rest of the application into the container


COPY . .

# Expose the application on port 5000


EXPOSE 5000

# Define the command to run the application


CMD ["python", "app.py"]

 FROM python:3.8-slim: Specifies the base image (Python 3.8).

 WORKDIR /app: Sets /app as the working directory in the container.

 COPY requirements.txt .: Copies requirements.txt into the container.

 RUN pip install: Installs the required Python dependencies.

 COPY . .: Copies the application code into the container.

 EXPOSE 5000: Exposes port 5000 for the application to be accessible.

 CMD ["python", "app.py"]: Specifies the command to run the


application when the container starts.

7. Difference between CMD & ENTRYPOINT


 CMD: Specifies the default command to run when a container is
started, but it can be overridden when running the container.

 ENTRYPOINT: Specifies the command that is always executed when


the container starts. It cannot be easily overridden.

You can use both together:


dockerfileCopyEditENTRYPOINT ["python"]
CMD ["app.py"]

This would run python app.py when the container starts, but you can
override CMD if needed.

8. Current Jenkins version & Kubernetes version


As of my knowledge cutoff date (April 2024), the latest stable Jenkins version
was 2.375.x, and the latest stable Kubernetes version was 1.27.x. You can
always check the latest versions from their official websites:
 Jenkins latest version
 Kubernetes latest version

9. How to rollback to the previous version?


In most CI/CD systems:
1. Jenkins: You can roll back by redeploying the previous build artifact or
by restoring a previous version of the application from backups.

2. Docker/Kubernetes: Rollback by using the kubectl rollout undo


command to revert to a previous deployment in Kubernetes.

10. Explain roles and responsibilities in your project


In a typical DevOps project, roles and responsibilities can be divided as
follows:
 DevOps Engineer: Automates deployments, monitors infrastructure,
ensures system stability, and handles CI/CD pipelines.

 Software Developer: Writes the application code and ensures it is


testable and maintainable.

 System Administrator: Manages the infrastructure, including


servers, databases, and network configurations.

 QA Engineer: Ensures code quality through testing and works closely


with developers and operations.

 Product Manager: Coordinates the project and ensures the team


delivers according to business requirements.

11. Explain branching strategy


A common branching strategy is GitFlow, which involves:
 Master branch: Production-ready code.

 Develop branch: Latest development changes, merged into the


master after testing.

 Feature branches: Created for individual features.

 Release branches: Used to prepare for production release.

 Hotfix branches: Created to quickly address critical issues in


production.

12. Which type of trigger are you using in your company?


Common triggers used in CI/CD systems include:
 Push Trigger: Triggered when code is pushed to a repository.

 Pull Request Trigger: Triggered when a pull request is created or


updated.

 Scheduled Trigger: Triggered at a scheduled time (e.g., nightly


builds).

 Manual Trigger: Triggered by a user, often used for deploying to


production.

13. How to configure webhooks?


To configure webhooks:
1. In your repository, go to Settings > Webhooks.

2. Enter the URL of the service to notify (e.g., Jenkins, Slack).

3. Select the events to trigger the webhook (e.g., push events, pull
request events).

4. Save the webhook settings.

In Jenkins, you can configure webhooks under Manage Jenkins >


Configure System and enter the relevant GitHub or GitLab webhook URL.

14. Write any Groovy script


Here’s an example of a Groovy script to print "Hello, Jenkins!" in a Jenkins
pipeline:
groovyCopyEditnode {
echo 'Hello, Jenkins!'
}

This script runs within a Jenkins pipeline, and the node block indicates that it
will run on a Jenkins node.

15. How to integrate Kubernetes in Jenkins?


You can integrate Kubernetes with Jenkins using the Kubernetes plugin for
Jenkins:
1. Install the Kubernetes Plugin in Jenkins.

2. Configure a Kubernetes cloud under Manage Jenkins > Configure


System.

3. Define pod templates to run Jenkins jobs in Kubernetes pods.


4. In your Jenkins pipeline, specify the pod template to run the job in a
Kubernetes pod.

16. Which services are you using frequently in AWS?


Common AWS services used frequently in DevOps include:
 EC2: For running virtual machines.

 S3: For storage.

 EKS: For managing Kubernetes clusters.

 Lambda: For serverless functions.

 CloudWatch: For monitoring and logging.

 RDS: For managed relational databases.

 IAM: For identity and access management.

17. How many parameters do we have to configure while creating


EC2?
The essential parameters for creating an EC2 instance in AWS are:
1. AMI: Amazon Machine Image.

2. Instance Type: EC2 instance size (e.g., t2.micro).

3. Key Pair: For SSH access.

4. Security Group: Firewall settings.

5. VPC/Subnet: Network configurations.

6. IAM Role (optional): Permissions for accessing other AWS services.

7. Storage: Size and type of storage (e.g., EBS).

8. Tagging: Optional key-value pairs to label resources.

18. What is VPC? How to configure the subnets?


A VPC (Virtual Private Cloud) is a logically isolated section of the AWS
cloud where you can define your own network architecture.
 Subnets: Subnets are segments of a VPC’s IP address range that can
be used to launch resources. Subnets can be public (accessible from
the internet) or private (isolated from the internet).
To configure subnets:
1. Go to VPC > Subnets > Create subnet.

2. Choose the VPC, specify the CIDR block, and define the subnet’s type
(public or private).

19. Differences between private and public subnets


 Public Subnet: Has a route to the internet through an Internet
Gateway. Resources in this subnet can communicate with the outside
world.

 Private Subnet: Does not have direct access to the internet. It can
access the internet via a NAT Gateway or NAT instance.

20. I have 2 APIs in 2 different accounts, while connecting these 2,


I got a timeout issue. How to troubleshoot?
To troubleshoot timeout issues between APIs in different AWS accounts:
1. **Check Security

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy