1.

1 Definition and Significance

1.1.1 Defining DevOps

DevOps as “a software development method that stresses communication, collaboration and

integration between software developers and information technology (IT) professionals.”

● Core principles encapsulated by the DevOps philosophy

DevOps is the philosophy of unifying Development and Operations at the culture, practice, and
tool levels, to achieve accelerated and more frequent deployment of changes to Production.

Culture=behaviour, teamwork, responsibility/accountability, trust...

Practice=policy, roles, processes/procedures, metrics/reporting...
Tools=shared skills, toolmaking for each other, common technology platforms...

1.1.2 Significance in Modern Software Development

● The role of DevOps in contemporary software engineering practices

● Impact on collaboration between development and operations teams
● Addressing challenges in traditional software development lifecycles

1.1.3 Integration with IT Operations

● Understanding the relationship between DevOps and IT operations

● Achieving synergy between development and operational tasks
● Real-world examples of successful DevOps integration

1.2 Evolution of DevOps

1.2.1 Historical Perspective

Year Event Key Figures

2007 DevOps Movement Patrick Debois

2008 Birds of a Feather Meeting Andrew Clay Shafer, Patrick Debois

2009 J Velocity Conference Talk John Allspaw

2009 First DevOpsDays Conference Patrick Debois

2010 "Continuous Delivery" Jez Humble, David Farley

2013 "The Phoenix Project" Gene Kim, Kevin Behr, George Spafford

2015 DORA (DevOps Research and Nicole Forsgren, Gene Kim, Jez Humble
Assessment) State of DevOps Report

2016 "The DevOps Handbook" Gene Kim, Jez Humble, Patrick Debois,
John Willis

Ongoing DevOpsDays and Ongoing Growth Patrick Debois, Global DevOps

Community

# Authors Year Title

1 Abdelkebir et al. [65] 2017 An agile framework for ITS management In organizations: A case
study based on DevOps

2 Akbar et al. [60] 2020 Identification and prioritization of DevOps success factors using
fuzzy-AHP approach

3 Alnamlah et al. [66] 2021 The necessity of a lead person to monitor development stages of
the DevOps pipeline
4 Ben Mesmia et al. 2021 DevOps workflow verification and duration prediction using
[67] non-Markovian stochastic Petri nets

5 Bezemer et al. [68] 2019 How is performance addressed in DevOps?

6 Callanan and Spillane 2016 DevOps: Making it easy to do the right thing
[32]

7 Chen [69] 2019 Improving the software logging practices in DevOps

8 Chen [70] 2020 Performance regression detection in DevOps

9 Claps et al. [44] 2015 On the journey to continuous deployment: Technical and social
challenges along the way

10 Díaz et al. [71] 2018 DevOps in practice: An exploratory case study

11 Díaz et al. [72] 2019 DevOps in practice — A preliminary analysis of two

multinational companies

12 Díaz et al. [73] 2021 Why are many businesses instilling a DevOps culture into their
organization?

13 Azad [74] 2022 Understanding DevOps critical success factors and organizational
practices

14 Erich et al. [2] 2017 A qualitative study of DevOps usage in practice

15 Rafi et al. [75] 2022 Decision-making taxonomy of DevOps success factors using
preference ranking organization method of enrichment evaluation

16 Karamitsos et al. [76] 2020 Applying DevOps practices of continuous automation for
machine learning

17 Hüttermann and 2019 DevOps: Walking the shadowy bridge from development success
Rosenkranz [77] to information systems success

18 Luz et al. [78] 2018 Building a collaborative culture: A grounded theory of well
succeeded DevOps adoption in practice

19 Lwakatare et al. [4] 2016 An exploratory study of DevOps extending the dimensions of
DevOps with practices

20 Marnewick and 2020 DevOps and organizational performance: The fallacy of chasing
Langerman [79] maturity
21 Maroukian and 2020 Leading DevOps practice and principle adoption
Gulliver [80]

22 Mohan and Othmane 2016 SecDevOps: Is it a marketing buzzword? — Mapping research on

[81] security in devops

23 Nybom et al. [30] 2016 On the impact of mixing responsibilities between devs and ops

24 Olszewska and 2015 DevOps meets formal modeling in high-criticality complex

Waldén [82] systems

25 Perera et al. [83] 2016 Evaluating the impact of DevOps practice in Sri Lankan software
development organizations

26 Riungu-Kalliosaari et 2016 DevOps adoption benefits and challenges in practice: A case

al. [34] study

27 Rowse and Cohen 2021 A survey of DevOps in the South African software context
[84]

28 Salameh [85] 2019 The impact of DevOps automation, controls, and visibility
practices on software continuous deployment and delivery

29 Shahin et al. [86] 2016 The intersection of continuous deployment and architecting
process: Practitioners’ perspectives

30 Shahin et al. [7] 2017 Beyond continuous delivery: An empirical investigation of

continuous deployment challenges

31 Toh et al. [19] 2019 Adoption issues in DevOps from the perspective of continuous
delivery pipeline

32 Trihinas et al. [87] 2018 Devops as a service: Pushing the boundaries of microservice
adoption

33 Van Belzen et al. [88] 2019 Critical success factors of continuous practices in a DevOps
context

34 Wahaballa et al. [89] 2015 Toward unified DevOps model

35 Wettinger et al. [15] 2014 Devopslang–Bridging the gap between development and
operations

36 Wiedemann et al. [90] 2020 Understanding how DevOps aligns development and operations:
A tripartite model of intra-IT alignment
 37 Šmite et al. [91] 2021 Overcoming cultural barriers to being agile in distributed teams

38 Trigo et al. [92] 2022 DevOps adoption: Insights from a large European Telco

Unit 1 ref

https://aws.amazon.com/devops/what-is-devops/

DevOps Model Defined

DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s
ability to deliver applications and services at high velocity: evolving and improving products at a faster
pace than organizations using traditional software development and infrastructure management processes.
This speed enables organizations to better serve their customers and compete more effectively in the
market.
How DevOps Works
Under a DevOps model, development and operations teams are no longer “siloed.” Sometimes, these two
teams are merged into a single team where the engineers work across the entire application lifecycle, from
development and test to deployment to operations, and develop a range of skills not limited to a single
function.

In some DevOps models, quality assurance and security teams may also become more tightly integrated
with development and operations and throughout the application lifecycle. When security is the focus of
everyone on a DevOps team, this is sometimes referred to as DevSecOps.

These teams use practices to automate processes that historically have been manual and slow. They use a
technology stack and tooling which help them operate and evolve applications quickly and reliably. These
tools also help engineers independently accomplish tasks (for example, deploying code or provisioning
infrastructure) that normally would have required help from other teams, and this further increases a
team’s velocity.

Learn about AWS DevOps tooling and services »

Benefits of DevOps

Speed

Move at high velocity so you can innovate for customers faster, adapt to changing markets better, and
grow more efficient at driving business results. The DevOps model enables your developers and
operations teams to achieve these results. For example, microservices and continuous delivery let teams
take ownership of services and then release updates to them quicker.
Rapid Delivery

Increase the frequency and pace of releases so you can innovate and improve your product faster. The
quicker you can release new features and fix bugs, the faster you can respond to your customers’ needs
and build competitive advantage. Continuous integration and continuous delivery are practices that
automate the software release process, from build to deploy.

Reliability

Ensure the quality of application updates and infrastructure changes so you can reliably deliver at a more
rapid pace while maintaining a positive experience for end users. Use practices like continuous integration
and continuous delivery to test that each change is functional and safe. Monitoring and logging practices
help you stay informed of performance in real-time.

Scale

Operate and manage your infrastructure and development processes at scale. Automation and consistency
help you manage complex or changing systems efficiently and with reduced risk. For example,
infrastructure as code helps you manage your development, testing, and production environments in a
repeatable and more efficient manner.

Improved Collaboration

Build more effective teams under a DevOps cultural model, which emphasizes values such as ownership
and accountability. Developers and operations teams collaborate closely, share many responsibilities, and
combine their workflows. This reduces inefficiencies and saves time (e.g. reduced handover periods
between developers and operations, writing code that takes into account the environment in which it is
run).

Security

Move quickly while retaining control and preserving compliance. You can adopt a DevOps model without
sacrificing security by using automated compliance policies, fine-grained controls, and configuration
management techniques. For example, using infrastructure as code and policy as code, you can define and
then track compliance at scale.

Why DevOps Matters

Software and the Internet have transformed the world and its industries, from shopping to entertainment
to banking. Software no longer merely supports a business; rather it becomes an integral component of
every part of a business. Companies interact with their customers through software delivered as online
services or applications and on all sorts of devices. They also use software to increase operational
efficiencies by transforming every part of the value chain, such as logistics, communications, and
operations. In a similar way that physical goods companies transformed how they design, build, and
deliver products using industrial automation throughout the 20th century, companies in today’s world
must transform how they build and deliver software.

How to Adopt a DevOps Model

DevOps Cultural Philosophy

Transitioning to DevOps requires a change in culture and mindset. At its simplest, DevOps is about
removing the barriers between two traditionally siloed teams, development and operations. In some
organizations, there may not even be separate development and operations teams; engineers may do both.
With DevOps, the two teams work together to optimize both the productivity of developers and the
reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the
quality of services they provide to customers. They take full ownership for their services, often beyond
where their stated roles or titles have traditionally been scoped by thinking about the end customer’s
needs and how they can contribute to solving those needs. Quality assurance and security teams may also
become tightly integrated with these teams. Organizations using a DevOps model, regardless of their
organizational structure, have teams that view the entire development and infrastructure lifecycle as part
of their responsibilities.

DevOps Practices Explained

There are a few key practices that help organizations innovate faster through automating and streamlining
the software development and infrastructure management processes. Most of these practices are
accomplished with proper tooling.

One fundamental practice is to perform very frequent but small updates. This is how organizations
innovate faster for their customers. These updates are usually more incremental in nature than the
occasional updates performed under traditional release practices. Frequent but small updates make each
deployment less risky. They help teams address bugs faster because teams can identify the last
deployment that caused the error. Although the cadence and size of updates will vary, organizations using
a DevOps model deploy updates much more often than organizations using traditional software
development practices.

Organizations might also use a microservices architecture to make their applications more flexible and
enable quicker innovation. The microservices architecture decouples large, complex systems into simple,
independent projects. Applications are broken into many individual components (services) with each
service scoped to a single purpose or function and operated independently of its peer services and the
application as a whole. This architecture reduces the coordination overhead of updating applications, and
when each service is paired with small, agile teams who take ownership of each service, organizations can
move more quickly.
However, the combination of microservices and increased release frequency leads to significantly more
deployments which can present operational challenges. Thus, DevOps practices like continuous
integration and continuous delivery solve these issues and let organizations deliver rapidly in a safe and
reliable manner. Infrastructure automation practices, like infrastructure as code and configuration
management, help to keep computing resources elastic and responsive to frequent changes. In addition,
the use of monitoring and logging helps engineers track the performance of applications and infrastructure
so they can react quickly to problems.

Together, these practices help organizations deliver faster, more reliable updates to their customers. Here
is an overview of important DevOps practices.

DevOps Practices
The following are DevOps best practices:

● Continuous Integration
● Continuous Delivery
● Microservices
● Infrastructure as Code
● Monitoring and Logging
● Communication and Collaboration

Below you can learn more about each particular practice.

Continuous Integration

Continuous integration is a software development practice where developers regularly merge their code
changes into a central repository, after which automated builds and tests are run. The key goals of
continuous integration are to find and address bugs quicker, improve software quality, and reduce the time
it takes to validate and release new software updates.

Learn more about continuous integration »

Continuous Delivery

Continuous delivery is a software development practice where code changes are automatically built,
tested, and prepared for a release to production. It expands upon continuous integration by deploying all
code changes to a testing environment and/or a production environment after the build stage. When
continuous delivery is implemented properly, developers will always have a deployment-ready build
artifact that has passed through a standardized test process.

Learn more about continuous delivery and AWS CodePipeline »

Microservices

The microservices architecture is a design approach to build a single application as a set of small services.
Each service runs in its own process and communicates with other services through a well-defined
interface using a lightweight mechanism, typically an HTTP-based application programming interface
(API). Microservices are built around business capabilities; each service is scoped to a single purpose.
You can use different frameworks or programming languages to write microservices and deploy them
independently, as a single service, or as a group of services.

Learn more about Amazon Container Service (Amazon ECS) »

Learn more about AWS Lambda »

Infrastructure as Code

Infrastructure as code is a practice in which infrastructure is provisioned and managed using code and
software development techniques, such as version control and continuous integration. The cloud’s
API-driven model enables developers and system administrators to interact with infrastructure
programmatically, and at scale, instead of needing to manually set up and configure resources. Thus,
engineers can interface with infrastructure using code-based tools and treat infrastructure in a manner
similar to how they treat application code. Because they are defined by code, infrastructure and servers
can quickly be deployed using standardized patterns, updated with the latest patches and versions, or
duplicated in repeatable ways.

Learn to manage your infrastructure as code with AWS CloudFormation »

Configuration Management

Developers and system administrators use code to automate operating system and host configuration,
operational tasks, and more. The use of code makes configuration changes repeatable and standardized. It
frees developers and systems administrators from manually configuring operating systems, system
applications, or server software.

Learn how you can configure and manage Amazon EC2 and on-premises systems with Amazon EC2
Systems Manager »

Learn to use configuration management with AWS OpsWorks »

Policy as Code

With infrastructure and its configuration codified with the cloud, organizations can monitor and enforce
compliance dynamically and at scale. Infrastructure that is described by code can thus be tracked,
validated, and reconfigured in an automated way. This makes it easier for organizations to govern changes
over resources and ensure that security measures are properly enforced in a distributed manner (e.g.
information security or compliance with PCI-DSS or HIPAA). This allows teams within an organization
to move at higher velocity since non-compliant resources can be automatically flagged for further
investigation or even automatically brought back into compliance.

Learn how you can use AWS Config and Config Rules to monitor and enforce compliance for your
infrastructure »
Monitoring and Logging

Organizations monitor metrics and logs to see how application and infrastructure performance impacts the
experience of their product’s end user. By capturing, categorizing, and then analyzing data and logs
generated by applications and infrastructure, organizations understand how changes or updates impact
users, shedding insights into the root causes of problems or unexpected changes. Active monitoring
becomes increasingly important as services must be available 24/7 and as application and infrastructure
update frequency increases. Creating alerts or performing real-time analysis of this data also helps
organizations more proactively monitor their services.

Learn how you can use Amazon CloudWatch to monitor your infrastructure metrics and logs »

Learn how you can use AWS CloudTrail to record and log AWS API calls »

Communication and Collaboration

Increased communication and collaboration in an organization is one of the key cultural aspects of
DevOps. The use of DevOps tooling and automation of the software delivery process establishes
collaboration by physically bringing together the workflows and responsibilities of development and
operations. Building on top of that, these teams set strong cultural norms around information sharing and
facilitating communication through the use of chat applications, issue or project tracking systems, and
wikis. This helps speed up communication across developers, operations, and even other teams like
marketing or sales, allowing all parts of the organization to align more closely on goals and projects.
DevOps Tools

The DevOps model relies on effective tooling to help teams rapidly and reliably deploy and innovate for
their customers. These tools automate manual tasks, help teams manage complex environments at scale,
and keep engineers in control of the high velocity that is enabled by DevOps. AWS provides services that
are designed for DevOps and that are built first for use with the AWS cloud. These services help you use
the DevOps practices described above.

Learn about AWS DevOps services »

Learn about AWS partner solutions »

DevOps Methodologies:

DevOps is not a specific methodology but rather a set of practices that aim to improve collaboration
between development (Dev) and operations (Ops) teams throughout the software development lifecycle.
However, several methodologies and practices are commonly associated with DevOps:
 1. Continuous Integration (CI):
○ Developers frequently integrate their code changes into a shared repository.
○ Automated builds and tests ensure early detection of integration issues.
2. Continuous Delivery (CD):
○ Code changes that pass automated tests are automatically deployed to a staging or
production environment.
○ Enables rapid and reliable software releases.
3. Infrastructure as Code (IaC):
○ Infrastructure is managed and provisioned through code, allowing for automated and
consistent deployment.
○ Improves scalability, repeatability, and version control of infrastructure.
4. Microservices Architecture:
○ Application is divided into small, independent, and loosely coupled services.
○ Facilitates rapid development, deployment, and scaling of individual services.
5. Automated Testing:
○ Automated testing practices, including unit tests, integration tests, and end-to-end tests,
ensure code quality and reliability.
6. Collaborative Development:
○ Promotes collaboration between development and operations teams to enhance
communication and understanding.

Goals of DevOps:

1. Accelerated Delivery:
○ Aim to deliver software changes quickly and efficiently to meet business demands.
2. Reliability:
○ Enhance the reliability and stability of software systems through automated testing and
continuous monitoring.
3. Collaboration:
○ Foster collaboration and communication between development and operations teams to
break down silos.
4. Efficiency:
○ Optimize and automate the software development lifecycle to improve efficiency and
reduce manual interventions.
5. Scalability:
○ Enable organizations to scale their software development and deployment processes
seamlessly.
6. Continuous Feedback:
○ Implement continuous feedback loops to gather insights for continuous improvement.

Benefits of Implementing DevOps:

1. Faster Time-to-Market:
○ Accelerated development and deployment cycles result in quicker releases.
2. Increased Collaboration:
 ○ Improved communication and collaboration between teams lead to better productivity.
3. Reduced Failure Rate:
○ Early detection of issues through automated testing reduces the likelihood of failures in
production.
4. Improved Efficiency:
○ Automation of manual processes improves efficiency and reduces errors.
5. Scalability:
○ Scalable infrastructure and practices support business growth.
6. Continuous Improvement:
○ Continuous feedback loops enable organizations to continuously improve their processes.

Challenges of Implementing DevOps:

1. Cultural Resistance:
○ Resistance to cultural change and breaking down traditional silos.
2. Integration Complexity:
○ Integrating DevOps practices with existing processes and technologies can be complex.
3. Skillset Gaps:
○ Organizations may lack the necessary skills to implement and maintain DevOps
practices.
4. Security Concerns:
○ Balancing speed with security measures can be challenging.
5. Toolchain Selection:
○ Choosing and integrating the right set of tools for automation and collaboration.
6. Legacy Systems:
○ Legacy systems may pose challenges in adopting modern DevOps practices.
7. Monitoring and Visibility:
○ Ensuring effective monitoring and visibility across the entire pipeline.
Benefits and Challenges of Working as a DevOps Engineer Across Industries

As DevOps becomes a pervasive methodology, its application spans diverse industries, each presenting
unique benefits and challenges for DevOps engineers.

1. Software and Technology:

Benefits:

● Cutting-edge Technologies: Work with the latest and most advanced technologies.
● Agile Methodologies: Leverage agile methodologies for rapid development cycles.
● Innovative Solutions: Contribute to innovative solutions and automation workflows.

Challenges:

● High Expectations: Face high expectations and demands from customers and stakeholders.
● Fast-Paced Environment: Navigate a fast-paced and competitive market.
● Continuous Learning: Cope with the constant need to learn new skills and tools.

Contributor Insights: Navigating the rapid development of DevOps applies consistently across industries.

2. Finance and Banking:

Benefits:

● Improved Security: Enhance security, reliability, and performance of financial applications.

● Compliance Streamlining: Streamline compliance and auditing processes.
● High Salaries: Enjoy high salaries and incentives offered by finance and banking companies.

Challenges:

● Strict Regulations: Deal with strict regulations governing financial data and transactions.
● Legacy Systems: Modernize and integrate legacy and complex systems.
● Resistance: Overcome resistance and skepticism from traditional stakeholders.

Contributor Insights: Understand the shift towards "Digital Banking" and prioritize engineering for a
leading digital bank.

3. Healthcare and Medicine:

Benefits:
 ● Quality Enhancement: Enhance the quality, accessibility, and efficiency of healthcare services.
● Innovation Contribution: Contribute to innovation and collaboration in medical research.
● Fulfilling Impact: Enjoy satisfaction from contributing to the health and well-being of people.

Challenges:

● Sensitive Data: Handle sensitive and confidential medical data.

● Ethical Implications: Navigate ethical and legal implications of healthcare decisions.
● Diverse Needs: Address diverse and complex needs and preferences of patients and providers.

Contributor Insights: DevOps in healthcare is promising, driving collaboration, innovation, and positive
impacts.

4. Education and Learning:

Benefits:

● Delivery Improvement: Contribute to improving the delivery and effectiveness of education

solutions.
● Technology Adoption: Support the development and adoption of new and emerging technologies.
● Flexibility: Enjoy the flexibility and creativity of working in the education sector.

Challenges:

● Limited Budget: Cope with limited budgets and resources in education organizations.
● Diverse Needs: Address diverse and dynamic needs and expectations of learners and educators.
● Cultural Barriers: Navigate cultural and social barriers hindering DevOps adoption.

Contributor Insight: DevOps engineers have much to teach in real applications, contributing significantly
to the education sector.

5. Media and Entertainment:

Benefits:

● Content Optimization: Contribute to creating, distributing, and optimizing media and

entertainment content.
● Scalability Enablement: Enable scalability, availability, and performance of media applications.
● Diversity: Enjoy the variety and diversity of working in the media and entertainment sector.

Challenges:

● Data Volume: Manage high volumes of media and entertainment data and traffic.
● Trend Unpredictability: Adapt to unpredictable trends and preferences of audiences.
● Legal/Ethical Issues: Address legal and ethical issues arising from media production and
consumption.
 Contributor Insights: Challenges in media and entertainment can be addressed through continuous
learning, efficient testing, and scalability considerations.

6. Retail Industry:

Opportunities:

● E-commerce Growth: Contribute to the growing demand for e-commerce-based platforms.

● Problem Solving: Present opportunities for imaginative problem-solving and innovative solutions.
● Future Growth: Offer prospects for interesting work and future growth opportunities.

Challenges:

● Demand Variability: Address challenges associated with the ever-growing demand for retail
solutions.
● Consumer Expectations: Adapt to changing consumer preferences and expectations.
● Implementation: Implement solutions for retail enterprises, whether large or small.

Contributor Insight: Retail is a sector worth considering, offering challenges and opportunities in the
DevOps space.

Session Topics Questions BLoms CO

level

Session Overview of 1. What is the significance of DevOps in the context of modern software development and IT L1/L2 1
1 DevOps operations? 2. How have DevOps principles evolved, and what milestones mark the
progression of DevOps practices?

Session Key 3. Explain how collaboration, automation, and feedback are core principles of DevOps. L2 1
2 Principles Provide examples of how each principle is applied.
and Goals of
DevOps

Session Benefits and 4. Discuss the challenges commonly faced in adopting DevOps and propose strategies to L3 1
3 Challenges overcome resistance to change.
of
Implementin
g DevOps

Session Expectations 5. Analyze the skill set expected from a DevOps professional. How does proficiency in L4 1
4 from DevOps collaboration, automation, and scripting contribute to success?
Profile and
Challenges
 of DevOps
Engineer

Session Skill Set 6. Discuss specific skills expected from a DevOps engineer and how these skills contribute to L3 1
5 Expectations effective DevOps practices.

Session Challenges 7. Identify and elaborate on common challenges faced by DevOps engineers and potential L4 1
6 Faced by solutions.
DevOps
Engineers

Session DevOps 8. Provide an overview of commonly used DevOps tools and their roles in the development L4 1
7 Tools lifecycle.
Overview

Session Role of 9. How does organizational culture impact the successful adoption of DevOps practices? L4 1
8 Culture in Discuss strategies to foster a DevOps-friendly culture.
DevOps

Session DevOps Case 10. Analyze a real-world case study of a successful implementation of DevOps practices. L5 1
9 Study Highlight key takeaways and lessons learned.

1. What does "DevOps" stand for?

a. Development and Operations

b. Development over Operations

c. Developers and Operators

d. Deviation from Operations

2. Which of the following is a key goal of DevOps?

a. Slower Development Cycles

b. Increased Silos between Teams

c. Limited Collaboration

d. Continuous Integration and Delivery

3. What is the primary purpose of Continuous Integration in DevOps?

a. Minimizing Collaboration

b. Automating Testing

c. Delaying Software Releases

d. Siloing Development and Operations

4. Which practice emphasizes the collaboration and communication between development and operations
teams?

a. Agile

b. Waterfall

c. DevOps

d. Scrum

5. In DevOps, what does "CI/CD" stand for?

a. Continuous Implementation and Continuous Development

b. Continuous Integration and Continuous Deployment

c. Controlled Iteration and Continuous Deployment

d. Continuous Interaction and Continuous Delivery

6. What is the main goal of Continuous Deployment in DevOps?

a. Automating Code Review

b. Automatically Deploying Code to Production

c. Continuous Testing

d. Delaying Software Deployment

7. Which tool is commonly used for container orchestration in DevOps?

a. Jenkins

b. Docker

c. Puppet

d. Kubernetes

8. What is the purpose of "Infrastructure as Code" (IaC) in DevOps?

a. Manual Infrastructure Management

b. Automating Infrastructure Deployment using Code

c. Ignoring Infrastructure Configuration

d. Isolating Infrastructure from Code

9. Which phase of the DevOps lifecycle focuses on monitoring, feedback, and continuous improvement?

a. Development

b. Testing

c. Deployment

d. Operations

10. What does the "DevOps Culture" emphasize?

a. Maintaining Silos between Teams

b. Blaming Individuals for Failures

c. Collaboration, Communication, and Empathy

d. Strict Hierarchy in Teams

Answers:

a
d