What is DevOps?

To improve the efficiency and quality of software development, delivery, and deployment, a group of activities
and approaches called DevOps combines software development (Dev) with information technology operations
(Ops).

DevOps' primary objective is to foster teamwork between the development and operations teams so that they
may collaborate easily across the whole software development life cycle. In addition, automation, continuous
integration, delivery, and deployment are used to speed up and reduce mistakes in the software development
process.

Monitoring and feedback are also emphasized in DevOps, which enables the development and operations
teams to see problems early and proactively handle them. Using DevOps methods, businesses may improve
their agility, competitiveness, and overall productivity by achieving quicker release cycles, higher-quality
software, and enhanced team cooperation.

1. What do you know about DevOps?

Your answer must be simple and straightforward. Begin by explaining the growing importance of DevOps in
the IT industry. Discuss how such an approach aims to synergize the efforts of the development and operations
teams to accelerate the delivery of software products, with a minimal failure rate. Include how DevOps is a
value-added practice, where development and operations engineers join hands throughout the product or
service lifecycle, right from the design stage to the point of deployment.

2. How is DevOps different from agile methodology?

DevOps is a culture that allows the development and the operations team to work together. This results in
continuous development, testing, integration, deployment, and monitoring of the software throughout the
lifecycle.
Agile is a software development methodology that focuses on iterative, incremental, small, and rapid releases
of software, along with customer feedback. It addresses gaps and conflicts between the customer and
developers.

3. Which are some of the most popular DevOps tools?

The most popular DevOps tools include:

• Selenium
• Puppet
• Chef
• Git
• Jenkins
• Ansible
• Docker

4. What are the different phases in DevOps?

The various phases of the DevOps lifecycle are as follows:

Plan: Initially, there should be a plan for the type of application that needs to be developed. Getting a rough
picture of the development process is always a good idea.

Code: The application is coded as per the end-user requirements.

Build: Build the application by integrating various codes formed in the previous steps.

Test: This is the most crucial step of the application development. Test the application and rebuild, if necessary.

Integrate: Multiple codes from different programmers are integrated into one.

Deploy: Code is deployed into a cloud environment for further usage. It is ensured that any new changes do
not affect the functioning of a high traffic website.

Operate: Operations are performed on the code if required.

Monitor: Application performance is monitored. Changes are made to meet the end-user requirements.
5. Mention some of the core benefits of DevOps.
• The core benefits of DevOps are as follows:
• Technical benefits
• Continuous software delivery
• Less complex problems to manage
• Early detection and faster correction of defects
• Business benefits
• Faster delivery of features
• Stable operating environments
• Improved communication and collaboration between the teams

6. How will you approach a project that needs to implement DevOps?

The following standard approaches can be used to implement DevOps in a specific project:

1. Stage 1

An assessment of the existing process and implementation for about two to three weeks to identify areas of
improvement so that the team can create a road map for the implementation.

2. Stage 2

Create a proof of concept (PoC). Once it is accepted and approved, the team can start on the actual
implementation and roll-out of the project plan.

3. Stage 3

The project is now ready for implementing DevOps by using version

control/integration/testing/deployment/delivery and monitoring followed step by step.

By following the proper steps for version control, integration, testing, deployment, delivery, and monitoring,
the project is now ready for DevOps implementation.
7. What is the difference between continuous delivery and continuous
deployment?

Continuous Delivery Continuous Deployment

Every change that passes the

Ensures code can be safely deployed on to production automated tests is deployed to
production automatically

Makes software development and

Ensures business applications and services function as
the release process faster and
expected
more robust

There is no explicit approval from

Delivers every change to a production-like environment
a developer and requires a
through rigorous automated testing
developed culture of monitoring
8. What is the role of configuration management in DevOps?
Enables management of and changes to multiple systems.

Standardizes resource configurations, which in turn, manage IT infrastructure.

It helps with the administration and management of multiple servers and maintains the integrity of the
entire infrastructure.

9. How does continuous monitoring help you maintain the entire

architecture of the system?

Continuous monitoring in DevOps is a process of detecting, identifying, and reporting any faults or threats in
the entire infrastructure of the system.

Ensures that all services, applications, and resources are running on the servers properly.

Monitors the status of servers and determines if applications are working correctly or not.

Enables continuous audit, transaction inspection, and controlled monitoring.

10. What is the role of AWS in DevOps?

AWS has the following role in DevOps:

Flexible services: Provides ready-to-use, flexible services without the need to install or set up the software.
Built for scale: You can manage a single instance or scale to thousands using AWS services.

Automation: AWS lets you automate tasks and processes, giving you more time to innovate

Secure: Using AWS Identity and Access Management (IAM), you can set user permissions and policies.

Large partner ecosystem: AWS supports a large ecosystem of partners that integrate with and extend AWS
services.

11. Name three important DevOps KPIs.

The three important KPIs are as follows:

Meantime to failure recovery: This is the average time taken to recover from a failure.

Deployment frequency: The frequency in which the deployment occurs.

Percentage of failed deployments: The number of times the deployment fails.

12. What are the fundamental differences between DevOps & Agile?
The main differences between Agile and DevOps are summarized below:

Characteristics Agile DevOps

Automation needed along

Work Scope Only Agility
with Agility

Quality and Time

Main priority is Time and
Focus Area management are of equal
deadlines
priority

The main source of

The main source of feedback -
Feedback Source feedback - self (tools used
customers
for monitoring)
 Processes and practices like
Practices or
Practices like Agile Kanban, Continuous Development
Processes
Scrum, etc., are followed. (CD), Continuous Integration
followed
(CI), etc., are followed.

Development Release cycles are smaller,

Release cycles are usually
Sprints or Release along with immediate
smaller.
cycles feedback.

Both in operations and

Only development agility is
Agility development, agility is
present.
followed

13. What are the anti-patterns of DevOps?

Patterns are common practices that are usually followed by organizations. An anti-pattern is formed when an
organization continues to blindly follow a pattern adopted by others but does not work for them. Some of
the myths about DevOps include:

• Cannot perform DevOps → Have the wrong people

• DevOps ⇒ Production Management is done by developers
• The solution to all the organization’s problems ⇒ DevOps
• DevOps == Process
• DevOps == Agile
• Cannot perform DevOps → Organization is unique
• A separate group needs to be made for DevOps

THE END