UNIT V

• Introduction to DevOps
DevOps • DevOps Application & Business Scenarios

• Business Drivers for Big Data • Planning the DevOps Strategy

• Benefits of DevOps • DevOps Process (13 Steps)

• DevOps Best Practices • DevOps Framework

• Agile Framework for DevOps • Benefits of Agile Development

Complete Study Guide with 15-Mark Answers

Covers All Exam Questions | Detailed Explanations | Key Points Highlighted
 CHAPTER 1: Introduction to DevOps

Q1. What is DevOps? Explain the traditional approach

15 Marks
and the emergence of DevOps in detail.

1. Definition of DevOps

DevOps is a software development methodology that combines Development (Dev) and IT

Operations (Ops). It integrates people, processes, and technology to continuously deliver
value to customers. The term DevOps was coined from 'Development' + 'Operations'.

Key aspects of DevOps:

Communication
1 All teams — dev, test, ops — communicate openly and continuously.

Collaboration
2 Teams work together throughout the entire software lifecycle.

Integration
3 Tools, processes, and pipelines are integrated end-to-end.

Automation
4 Manual, repetitive tasks are replaced with automated scripts and pipelines.

Key Outcomes:
✓ Rapid evolution of products and services
✓ Cost reduction — less rework and manual overhead
✓ Improved software quality through continuous testing
✓ Reduced project risk — early detection of issues

2. The Traditional Approach (Pre-DevOps)

Traditional SDLC involved multiple separate stakeholders — Business Analysts, Developers, QA
Teams, IT Operations, and Maintenance Teams — each working independently in silos.

Silo-Based Management
1 Development, testing, deployment, and maintenance were handled by completely separate
teams with no collaboration.
 Fragmented Process
2 Differences in techniques, frameworks, tools, and people caused a highly fragmented
workflow.

Impact on Product
3 Fragmentation directly affected features, cost, schedule, quality, performance, and
administrative overhead.

Maintenance Overlooked
4 Traditional methods ignored long-term maintenance costs and the skills required for support.

Risky Deployments
5 Releases were infrequent, large, and error-prone due to lack of automation and testing.

3. Pre-DevOps Challenges
• Resistance to change in systems and processes
• Risky, unpredictable deployments
• Lack of environment consistency — 'It works on my machine' problem
• Silo-based teams tossing problems across departments
• Duplication of effort and skill redundancy
• Conflicts between development and operations teams
• No single version of truth for source code

4. Emergence of DevOps
DevOps emerged as a response to the growing inefficiencies in traditional software development.
Several technological innovations drove this shift:
• Adoption of Agile methodology demanding faster delivery cycles
• Increase in production release frequency demanded by business stakeholders
• Wide availability of cloud computing infrastructure
• Rise of data center automation and configuration management tools
• Need to manage Big Data, machine learning, and microservices at scale

5. Role of DevOps

DevOps integrates all phases of the application lifecycle — Development, Testing,

Deployment, and Support — ensuring teams work as a cohesive unit. It aligns and
automates processes using open-source tools such as Git, Jenkins, Docker, Kubernetes,
and Ansible.

6. DevOps Best Practices (Overview)

• Code repositories (Git, GitHub)
• Build automation (Maven, Ant)
• Continuous Integration (CI) — Jenkins
• Continuous Deployment (CD)
• Container-based environments (Docker, Kubernetes)
• Configuration management (Ansible, Chef, Puppet)
• Application performance monitoring

Key Point for Exam: DevOps = Dev + Ops. It is NOT just about writing code — it is about
automating everything that happens after coding. DevOps adoption represents a cultural
change from traditional development.
 CHAPTER 2: DevOps Application &
Business Scenarios

Q2. Explain the business applications of DevOps with

15 Marks
suitable scenarios.

DevOps is applied across various stages of the software development lifecycle to solve real-world
business problems. The following are the major business application areas:

Application 1: Automation of Development Cycle

DevOps automates the entire software development process with minimal manual intervention.
Developers push code to repositories; open-source tools automatically build, test, and deploy the
application. This eliminates the manual hand-offs between development and operations teams.

Application 2: Single Version of Truth (Source Code Management)

Multiple code versions create confusion about which version is correct. Feedback from code
reviews through email is not properly recorded, leading to miscommunication and rework. DevOps
provides centralized SCM systems (e.g., Git) ensuring a single reliable version of code that all team
members can access and collaborate on.

Application 3: Consistent Configuration Management

Code may work in development but fail in production due to differences in dependency versions,
tools, and compilers. DevOps ensures consistent configurations across all environments
(development, testing, staging, production) using tools like Ansible, Chef, and Puppet.

Application 4: Product Readiness for the Market

Traditional development involves many manual checks causing delays. DevOps enables
continuous monitoring and gives organizations visibility into product readiness and quality at each
stage, enabling faster delivery planning and reducing time-to-market.

Application 5: Automation of Manual Processes

Manual processes are error-prone and inefficient. DevOps automates testing cycles, incremental
testing, and integration with build cycles. Infrastructure tasks such as creating VMs,
starting/stopping systems, and restarting machines are also automated, improving product quality
and release velocity.
Application 6: Containers for Portability
Code may work in development/QA but fail in production due to dependency issues. Containers
(Docker) provide platform-independent environments, improving portability and eliminating
compatibility issues across different operating systems and infrastructure.

Application 7: On-Premise System Challenges

Organizations managing on-premise infrastructure face capacity planning difficulties, slow
turnaround time, and unpredictable CAPEX/OPEX. Cloud migration with DevOps strategies
provides scalable, cost-efficient alternatives with better operational flexibility.

DevOps Suitable For DevOps Not Suitable For

• E-commerce platforms • Banking (with caution)

• SaaS applications • Power grid systems (avoid)

• Cloud-native projects • Mission-critical platforms (avoid)

• Website development • Medical life-support (avoid)

• Big Data pipelines

 CHAPTER 3: Business Drivers for DevOps
in Big Data

Q3. Discuss the business drivers and market trends for

15 Marks
DevOps application to Big Data.

Several powerful technological and business forces are driving the adoption of DevOps, especially
in the context of Big Data systems. These drivers are rapid, profound, and interconnected.

Driver 1: Agile Methodology

The widespread adoption of Agile development practices requires faster, iterative delivery cycles.
Agile demands continuous feedback and quick releases — goals that align perfectly with DevOps
automation. Together, Agile + DevOps ensure speed, flexibility, and automation.

Driver 2: Increase in Production Releases

Business stakeholders now demand more frequent production releases to stay competitive.
Manual release processes cannot support this frequency. DevOps CI/CD pipelines automate the
build-test-deploy cycle, making multiple daily releases feasible.

Driver 3: Wide Availability of Cloud Infrastructure

Cloud platforms (AWS, Azure, GCP) provide on-demand, scalable infrastructure. This enables
DevOps teams to provision environments instantly, run parallel tests, and deploy to production
without physical infrastructure constraints.

Driver 4: Data Center Automation & Configuration Management

Modern data centers — especially those handling Big Data workloads — require automated
configuration management. Tools like Ansible, Chef, and Puppet automate server provisioning,
application deployment, and infrastructure-as-code, which is essential for managing large-scale Big
Data clusters.

Driver 5: Big Data & Cloud Computing Convergence

Big Data systems (Hadoop, Spark, Kafka) require rapid deployment, horizontal scaling, and
continuous monitoring. DevOps provides the automation and tooling needed to manage these
complex, distributed systems reliably.
Driver 6: In-Memory Technologies & Data Science
Real-time analytics and data science workflows require fast iteration cycles. DevOps enables data
engineers and data scientists to deploy models and pipelines quickly with automated testing and
rollback capabilities.

Key Areas Where DevOps is Applied in Big Data:

Continuous Integration / Continuous Deployment (CI/CD)

1 Automating build, test, and deploy pipelines for Big Data applications

Virtualization & Containerization

2 Docker containers for data processing microservices; load balancing for high availability

Big Data & Social Media Projects

3 Managing Hadoop/Spark cluster deployments and social analytics pipelines

Machine Learning Projects

4 Automating ML model training, validation, and deployment pipelines (MLOps)

Important: Organizations adopting a comprehensive and integrated DevOps approach can

achieve greater value, efficiency, and competitive advantage. Many institutions have already
moved toward modern software development practices by adopting these technologies
together.
 CHAPTER 4: Planning the DevOps
Strategy

Q4. Explain the DevOps strategy in detail. What

15 Marks
questions must a DevOps strategy answer?

1. Purpose of a DevOps Strategy

A DevOps strategy is a comprehensive plan that helps organizations gain a deeper understanding
of DevOps concepts and their practical application. It integrates multiple technologies, tools, and
interfaces across the organization and provides focus, clarity, and a common view of existing
problems.

2. Key Questions a DevOps Strategy Must Answer

1. What are the organization's business goals and objectives?
2. How should the DevOps roadmap be planned and structured?
3. Where should the implementation begin (which team/project)?
4. How should resources and efforts be directed efficiently?
5. What outcomes are expected from DevOps adoption?
6. What is the implementation timeline or schedule?
7. What impact will DevOps have on the business and employees?
8. How will stakeholders perceive and measure the value delivered?
9. What are the costs and benefits of implementing DevOps?

3. Importance of a Holistic DevOps Strategy

A well-planned DevOps strategy accomplishes the following:

Identifies Current Issues

1 Maps out existing problems in the development and operations workflow.

Develops a Roadmap
2 Creates a clear path for future improvements and technology adoption.

Reveals Growth Opportunities

3 Identifies areas where automation or collaboration can unlock business value.

Improves Business Performance

4 Leads to measurable improvements in delivery speed, quality, and cost.
 Delivers Better Results
5 Aligns technology investments with strategic business outcomes.

4. DevOps Platform Strategy

A DevOps platform strategy is a comprehensive program covering the entire Software
Development Life Cycle (SDLC). It integrates multiple technologies, platforms, and tools.
Implementation requires skill, precision, and experience because of its complexity.

5. Areas Where DevOps Can Be Introduced

• Automation of infrastructure and workflow configuration management
• Automation of code repositories (Git, GitHub)
• Automating builds and testing (Jenkins, Maven)
• Automating development workflows (CI/CD pipelines)
• Containerization and microservices management (Docker, Kubernetes)

6. Popular DevOps Platforms

Platform Description

Red Hat OpenShift Enterprise Kubernetes platform with pre-integrated DevOps tools

Microsoft Azure DevOps Cloud-based CI/CD, boards, repos, and artifact management

AWS Container Services ECS/EKS for container orchestration with DevOps integration

GitHub Actions Built-in CI/CD workflows directly within GitHub repositories

 CHAPTER 5: Benefits of DevOps

Q5. What are the benefits of DevOps? Explain with

15 Marks
challenges faced without DevOps.

1. Challenges Without DevOps

If an organization does not follow DevOps practices, it may face:
• High deployment effort for development, QA, and production environments
• Complex manual installation procedures — time-consuming and costly
• Lack of a proper operations manual, making system operation difficult
• Insufficient logs or trace files, making troubleshooting incomplete
• Performance issues in one application may affect other applications
• Difficulty in meeting Service Level Agreements (SLAs)
• Monitoring systems separately (servers, databases, apps) leads to gaps
• Building redundancy and failover systems individually becomes expensive

2. Key Benefits of DevOps Adoption

CI/CD Pipeline
1 Continuous Integration and Continuous Delivery reduce human errors, minimize downtime
during upgrades, and improve productivity. Code is automatically built, tested, and deployed.

Automation Frameworks
2 Automation frameworks improve business efficiency and productivity. Repetitive manual tasks
are replaced with scripts, reducing errors and accelerating release cycles.

High Availability & Disaster Recovery

3 DevOps planning includes High Availability (HA) and Disaster Recovery (DR) technologies.
Resilience is built directly into the application code to handle failures effectively.

Operations Manual (Runbook)

DevOps creates an operations manual (runbook) during development itself. Runbook-driven
4 development in mature DevOps environments ensures teams know how to operate and
troubleshoot systems before they go live.

Fully Automated Deployment

5 Full scripted installation enables completely automated deployment. DevOps teams are
familiar with logging frameworks for better monitoring and troubleshooting.
 Non-Functional Requirements
6 DevOps ensures proper attention to system operability, maintenance, and monitoring
alongside normal functional system development requirements.

SLA Compliance
7 Operational requirements such as SLAs are incorporated directly into the development
process, ensuring the delivered software meets business performance guarantees.

Application Resilience
8 DevOps frameworks help build resilience in application code. DevOps processes can work
independently or integrate with other existing processes.

3. Business Benefits Summary

✓ Increased service quality and reliability of delivery
✓ Increased customer value through faster responsiveness to change
✓ Better usability increases customer satisfaction
✓ Efficient operations reduce overhead
✓ Value creation increases employee satisfaction
✓ Collaboration improves team attitude and culture
✓ Constant learning and continuous improvement

Remember: DevOps means: don't do repetitive work manually — let tools do it

automatically. DevOps is NOT about writing application code; it is about automating what
happens AFTER coding.
 CHAPTER 6: DevOps Process

Q6. Explain the DevOps process in detail with all

15 Marks
standard processes.

DevOps consists of a set of standard processes widely adopted by organizations to automate and
streamline software development, testing, and deployment.

Process 1: Source Code Management (SCM)

Manages and stores code in a central repository. Enables version tracking and team collaboration.
Tracks who changed what and when. Tool: Git / GitHub.

Process 2: Source Code Review

Code is reviewed for quality and errors before integration into the main codebase. Helps maintain
coding standards, reduces bugs, and enforces best practices.

Process 3: Configuration Management

Manages system settings and environments. Ensures consistency across development, testing,
and production. Tools: Ansible, Chef, Puppet.

Process 4: Build Management

Converts source code into executable form (JAR/WAR files). Automates compilation, dependency
resolution, and packaging. Tool: Apache Maven.

Process 5: Repository Management

Stores build artifacts (JAR, WAR files) in a binary repository. Helps in version control of compiled
binaries and ensures traceable releases.

Process 6: Release Management

Plans, schedules, and controls software releases. Understands risks, dependencies, and issues.
Ensures smooth and predictable delivery to end users.

Process 7: Test Automation

Runs test cases automatically without manual intervention. Detects errors early in the development
cycle, reducing the cost of fixing bugs.
Process 8: Continuous Integration (CI)
Automatically integrates code changes from multiple developers into a shared repository. Runs
builds and tests frequently (multiple times per day). Tool: Jenkins.

Process 9: Continuous Delivery (CD)

Ensures code is always in a deployable state. Deployment to production is possible at any time.
Automates the release pipeline up to the point of deployment.

Process 10: Continuous Deployment

Automatically deploys code to production without any manual intervention once all tests pass.
Every code commit that passes the pipeline is automatically released.

Process 11: Infrastructure as Code (IaC)

Manages and provisions infrastructure using code/scripts instead of manual setup. Servers,
networks, and databases are defined using configuration files (e.g., Terraform, Ansible).

Process 12: Application Performance Monitoring

Continuously monitors application health, performance, and availability. Helps detect issues in
real-time and provides data for capacity planning.

Process 13: Routine Automation / Continuous Improvement

Automates repetitive operational tasks. Continuously improves processes based on feedback,
metrics, and post-incident reviews.

DevOps Lifecycle Overview:

Stage Activity Tool

Code Developer writes and commits code Git

Build Code compiled into executable artifact Maven, Gradle

Test Automated tests run against the build JUnit, Selenium

Release Build promoted to release candidate Jenkins, GitLab CI

Deploy Application deployed to environment Ansible, Docker

Operate System monitored and maintained Kubernetes, Nagios

Monitor Performance data collected and analysed Prometheus, Grafana

 CHAPTER 7: DevOps Best Practices

Q7. Explain DevOps Best Practices and the Enterprise

15 Marks
DevOps Adoption Model.

DevOps best practices are organized into three pillars: Principles, Management Framework, and
Practices. Together, they form the Enterprise DevOps Adoption Model.

VALUE PURPOSE (The Goal):

Continuously deliver customer value in a sustainable way with improved lead time,
resilience, and quality.

Pillar 1: Principles

Self-Directed Teams over Command & Control

1 Teams are empowered to make decisions. Cross-functional teams own their delivery pipeline
end-to-end without micromanagement.

Course Correction over Perfection

2 Small, frequent improvements are preferred over waiting for a perfect solution. Fail fast, learn
fast, improve continuously.

Automated over Manual

3 Every manual, repetitive task should be automated. Automation is the foundation of DevOps
— it reduces errors and accelerates delivery.

Pillar 2: Management Framework

• People First — invest in team culture and skills
• Organizational Structure — align teams around value streams
• Capability Development — continuous learning and training
• Budget Management — fund DevOps toolchain and infrastructure
• Risk Management — identify and mitigate delivery risks
• Assets Management — manage code, artifacts, and dependencies
• Change Management — controlled, automated change processes
• Security Management — shift security left (DevSecOps)

Pillar 3: Practices
 Infrastructure as Code (IaC)
1 Define and manage all infrastructure (servers, networks, databases) using version-controlled
code.

Dashboard & Visibility

2 Real-time dashboards showing build status, deployment health, and application performance.

Working Backwards
3 Start from the customer outcome and design the development and delivery process
backwards.

Open Source Tooling

4 Leverage open-source tools (Git, Jenkins, Docker) to reduce costs and gain community
support.

DevOps Skill Matrix

5 Track team competencies across development, operations, and automation skills.

Audit Automation
6 Automate compliance checks and security audits within the CI/CD pipeline.

Self-Service
7 Enable developers to provision their own environments and run deployments without waiting
for ops.

Environment (Foundation):

All DevOps practices operate within the environment of: People, Organization, Laws,
Regulations, Culture, and Competitors. The environment shapes how DevOps is adopted
and what practices are prioritized.
 CHAPTER 8: DevOps Framework & Tools

Q8. Describe the DevOps framework. Explain popular

15 Marks
open-source DevOps tools.

1. DevOps Framework
The DevOps framework is a comprehensive structure covering the entire SDLC. It integrates
continuous integration, continuous delivery, configuration management, containerization,
monitoring, and feedback loops.

2. Popular Open-Source DevOps Tools

Tool 1: Docker
Docker is a container platform that packages an application and all its dependencies together into
an isolated container. It runs as an isolated process on the host OS and shares the OS kernel with
other containers. Key benefits: portability, consistency across environments, faster startup
compared to VMs, and efficient resource utilization.

Tool 2: Kubernetes
Kubernetes (K8s) is an open-source container orchestration system that manages Docker
containers at scale. Key functions include: grouping containers into logical units, scheduling
containers on nodes, managing workloads, auto-scaling, self-healing (restarting failed containers),
and ensuring the desired system state is always maintained.

Tool 3: Jenkins
Jenkins is a web-based CI/CD automation tool used for continuous integration, continuous build,
testing, and deployment. It works with a master-slave architecture and integrates with tools like Git,
Maven, and Ant. Jenkins monitors the repository for changes and automatically triggers
build-test-deploy pipelines.

Tool 4: Ansible
Ansible is an agentless automation tool used for software provisioning, configuration management,
and application deployment. It uses SSH for communication and defines tasks using YAML-based
Playbooks. Key components: Playbooks, Inventory, Ansible Tower, and YUM scripts.
Tool 5: Chef and Puppet
Chef and Puppet are agent-based configuration management tools that use a pull mechanism.
They are mainly used for automating the deployment and configuration of systems at scale. Unlike
Ansible, they require an agent installed on managed nodes.

Tool 6: GitHub
GitHub is a web-based platform for hosting Git repositories. Git is a distributed version control
system that tracks code changes. GitHub provides remote repository hosting, collaborative
development features (pull requests, issues, actions), and is widely used for both open-source and
private projects.

3. DevOps Tool Categories

Category Tools Purpose

Source Control Git, GitHub, GitLab Version control & code collaboration

Build Maven, Gradle, Ant Compile & package source code

CI/CD Jenkins, GitLab CI, CircleCI Automated integration & deployment

Configuration Ansible, Chef, Puppet Environment & config management

Containers Docker, Podman Application containerization

Orchestration Kubernetes, Docker Swarm Container management at scale

Monitoring Nagios, Prometheus, Grafana Performance & health monitoring

Cloud AWS, Azure, Red Hat OpenShift Cloud infrastructure & services
 CHAPTER 9: Agile Framework for DevOps
Projects

Q9. Explain the Agile framework for DevOps process

15 Marks
projects. Compare Agile and DevOps.

1. Introduction
DevOps projects are typically based on Agile frameworks. Agile enables faster development,
continuous feedback, and quick delivery. Traditional models like the Waterfall model are
considered outdated because they are rigid and cannot handle frequent requirement changes.
Agile + DevOps together ensure speed, flexibility, and automation.

2. Core Principles of Agile Methodology (Agile Manifesto)

✓ Individuals and interactions over processes and tools
✓ Working software over comprehensive documentation
✓ Customer collaboration over contract negotiation
✓ Responding to change over following a fixed plan

3. Agile vs. DevOps Comparison

Agile DevOps

• Addresses gap between customer • Addresses gap between dev+testing and IT

requirements and dev+testing Operations

• Teams design, develop, and test features • Automated release management and
prioritized by customer deployment processes

• Focus: Functional + Non-functional • Focus: Functional + Non-functional +

requirements Operational + Business

• Short sprint cycles (2-4 weeks) for • Continuous delivery and continuous
iterative delivery deployment pipelines

• Scrum/Kanban frameworks for team • Automated toolchains for end-to-end

management delivery

• Customer satisfaction through frequent • Operational stability through monitoring

software delivery and resilience

4. Scrum Framework (Most Popular Agile Method)

Scrum is a popular Agile methodology that focuses on feature-based, incremental development.
Scrum Roles:

Scrum Master
1 Facilitates the Scrum team, conducts sprint planning and retrospective meetings, and removes
obstacles that block the team's progress.

Product Owner
2 Creates and prioritizes the product backlog. Ensures features are delivered in each sprint and
represents the voice of the customer/business.

Scrum Team
3 Cross-functional team of Developers and Testers responsible for completing the work
committed in each sprint.

5. Agile Development Process

Incremental & Iterative

1 Software is built in small pieces (increments) delivered repeatedly in cycles (iterations).

Sprint Cycle
2 Each sprint lasts 2 to 4 weeks. Each sprint delivers a working software feature.

Workflow
3 To Do → In Progress → Testing → Done

Key Sprint Activities

4 Feature development (user stories), bug fixing, regression testing, UAT.

6. Advantages of Agile in DevOps

✓ Faster delivery of working software
✓ Early feedback from customers allows course correction
✓ Easy to handle requirement changes at any stage
✓ Continuous testing and improvement within each sprint
✓ Better collaboration between development and operations teams
 CHAPTER 10: Benefits of Agile Software
Development

Q10. What are the benefits of Agile software

15 Marks
development methodology?

Adopting best practices of Agile methodology helps organizations deliver high-quality software
quickly and efficiently while adapting to changing requirements.

Lean and Productive Teams

Agile teams are small, focused, and efficient. The methodology minimizes unnecessary work
1 (waste) and maximizes productivity by focusing only on valuable features. Team sizes typically
range from 5 to 9 members.

Highly Skilled Sprint Teams

2 Teams work in short sprint cycles of 2 to 4 weeks. Continuous practice and repetition improve
skills, speed of delivery, and technical excellence over time.

Customer Satisfaction
Working software is delivered frequently at the end of each sprint. Customers can view
3 features early, provide feedback, and steer the product in the right direction before too much
effort is invested.

Early Bug Fixing

Developers and testers work together within the same sprint. Bugs are identified and fixed
4 early, reducing the cost of defect remediation significantly compared to finding them in
production.

Fast and Continuous Delivery

5 Software is delivered in weeks, not months. This enables quick releases, frequent updates,
and the ability to respond rapidly to market changes and customer demands.

Self-Organizing Teams
Agile teams manage their own work without micromanagement. They focus on better
6 architecture, clear requirements, and efficient design decisions, leading to higher ownership
and accountability.

Focus on Technical Excellence

Continuous improvement in code quality and design standards leads to robust, maintainable,
7 and extensible software. Regular refactoring and code reviews are integral parts of the Agile
process.
 Effective Communication
8 Regular meetings — daily stand-ups (15 min), sprint reviews, and retrospectives — improve
coordination, transparency, and product quality across the team.

Motivated and Trusted Teams

9 Projects are built around motivated individuals. Teams are given ownership and responsibility,
which increases performance, creativity, and innovation.

Flexibility for Changes

10 Customers can request changes at any stage of development. Agile easily adapts to new
requirements without disrupting the entire project, unlike Waterfall.

Summary Comparison — Waterfall vs Agile vs DevOps:

• Waterfall: Sequential phases, rigid, high risk, late delivery
• Agile: Iterative sprints, flexible, customer-focused, faster delivery
• DevOps: Continuous integration + deployment + operations, maximum automation
 QUICK REVISION: Key Terms &
Definitions

Term Definition
DevOps Combination of Development + Operations. Automates and integrates the entire SDLC

CI (Continuous Integration) Automatically integrating code changes into a shared repo; runs builds & tests frequent

CD (Continuous Delivery) Code is always in deployable state; deployment can happen at any time.

CD (Continuous Deployment) Every passing code change is automatically deployed to production without manual ste

IaC (Infrastructure as Code) Managing infrastructure using code/scripts instead of manual configuration.

Docker Container platform that packages app + dependencies as isolated, portable units.

Kubernetes Container orchestration system that manages, scales, and heals Docker containers.

Jenkins Web-based CI/CD automation tool for build-test-deploy pipelines.

Ansible Agentless automation tool for configuration management and deployment (uses SSH +

Git Distributed version control system for tracking code changes.

Sprint A fixed time period (2-4 weeks) in Scrum during which a working feature is delivered.

Scrum Master Agile facilitator who removes blockers and ensures the team follows Scrum practices.

Product Owner Represents the customer; creates and prioritizes the product backlog.

Runbook Operations manual created during development documenting how to run and troublesh

HA / DR High Availability / Disaster Recovery — ensuring system uptime and recovery from failu

SLA Service Level Agreement — performance and availability commitments made to custom

Silo A team or department that operates independently without sharing information with oth

IMPORTANT EXAM POINTS TO

REMEMBER
1. DevOps = Dev + Ops. It integrates Communication, Collaboration, Integration, and Automation.

2. Traditional SDLC problems: Silo-based teams, fragmentation, risky deployments, no

consistency.

3. DevOps best practices: Code repos, build automation, CI/CD, containers, config management.

4. DevOps process has 13 steps from SCM to Continuous Improvement.

5. Key DevOps tools: Git, Jenkins, Docker, Kubernetes, Ansible, Chef, Puppet, GitHub.

6. DevOps strategy answers 9 key questions about goals, roadmap, resources, costs, timeline.

7. CI = integrate + test frequently. CD = always deployable. Continuous Deployment =

auto-release.

8. Agile Manifesto: Individuals > Processes, Working SW > Documentation, Customer

Collaboration > Contract, Responding to Change > Fixed Plan.

9. Scrum roles: Scrum Master, Product Owner, Scrum Team. Sprint = 2–4 weeks.

10. Benefits of DevOps: CI/CD, HA/DR, Runbook, Automation, Non-functional requirements, SLA
compliance.

11. Benefits of Agile: Lean teams, early bug fix, customer satisfaction, fast delivery, flexibility.

12. DevOps SUITABLE FOR: e-commerce, websites, cloud. NOT SUITABLE FOR: banks, power
systems, mission-critical.

13. Enterprise DevOps Model = Value Purpose + Principles + Management Framework +

Practices + Environment.

14. DevOps is NOT about writing application code — it is about automating what happens AFTER
coding.