Course File

The following attributes should be made available in each course file.

Department: CSD A.Y.: 2024-2025

Name of the Faculty: j.madhavi Subject Code: D85PC14 (R22)
Pre-Academic Session Review Title of the subject: DevOps
PART-A

S. No Attributes Yes/No
I Vision and Mission of institute
II Course handout& its contents
a) Vision and Mission of department

b) PEOs of the program

c) Program Outcomes (POs)

d) Program Specific Outcomes (PSOs)

e) Prerequisites

f) Course objectives

g) Course Outcomes (COs)

h) Detailed syllabus

i) Course Plan

j) Evaluation scheme

III Course material

a) PPT’s, Reference links of Material

b) Question bank prepared by faculty (unit wise)

c) Quiz question bank (unit wise)

 Devops-COURSE FILE
Class: III B.Tech ISem A.Y:2024-2025
Name of the Faculty:j. madhavi Email: jmadhavi@tkrcet.com
Phone Number: 9010945719 Contact Sessions: 50

Vision & Mission of the Institution

Vision: The institute endeavors towards imparting quality education with ethical values
and strives to make students technically competent to reach high level of achievements an
make our nation self-reliant and globally recognized.
Mission: The institute is committed and dedicated to mould the students into quality
engineers and technologists with aplomb by providing world class scientific and technical
education through:

Ensuring excellent branch wise infrastructure facilities, with eminent and qualified
faculty.
Making the institute a research/resource center to enhance scope for consultancy and
R&D.

a) Vision & Mission of the Department

Vision:
The Department endorses to inculcate academic practices that would transform nascent
students into Data Scientists with ethical values who could address technical and social
Challenges.
Mission:

1. To strengthen the students core competency with required rudimentary knowledge.

2. To inculcate academic practices by developing projects using technology.
3. To develop entrepreneurial skills, leadership qualities, ethical values and capability to work in a team
among the students.

b) Program Educational Objectives (PEOs)

The Program Educational Objectives of the program offered by the department are listed
below:

PEO 1

To create and sustain a community of learning in which students acquire knowledge and
apply in their concerned fields with due consideration for ethical, ecological and economic
issues.

PEO 2

To provide knowledge-based services so as to meet the needs of the society and industry.
 PEO 3

To make the students understand, design and implement the concepts in multiple arenas.

PEO 4

To educate the students in disseminating the research findings with good soft skills so as to
become successful entrepreneurs.

Program Outcomes (POs)

1. Engineering Knowledge: Apply the knowledge of mathematics, science, engineering fundamentals, and an
engineering specialization to the solution of complex engineering problems.
2. Problem Analysis: Identify, formulate, review research literature, and analyse complex engineering problems
reaching substantiated conclusions using first principles of mathematics, natural sciences, and engineering
sciences.
3. Design/Development of Solutions: Design solutions for complex engineering problems and design system
components or processes that meet the specified needs with appropriate consideration for the public health and
safety, and the cultural, societal, and environmental considerations
4. Conduct Investigations of Complex Problems: Use research-based knowledge and research methods including
design of experiments, analysis and interpretation of data, and synthesis of the information to provide valid
conclusions.
5. Modern Tool Usage: Create, select, and apply appropriate techniques, resources, and modern engineering and
IT tools including prediction and modelling to complex engineering activities with an understanding of the
limitations.
6. The Engineer and Society: Apply reasoning informed by the contextual knowledge to assess societal, health,
safety, legal and cultural issues and the consequent responsibilities relevant to the professional engineering
practice.
7. Environment and Sustain ability: Understand the impact of the professional engineering solutions in societal
and environmental contexts, and demonstrate the knowledge of, and need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and norms of the
engineering practice.
9. Individual and Team Work: Function effectively as an individual, and as a member or leader in diverse teams,
and in multi-disciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the engineering community
and with society at large, such as, being able to comprehend and write effective reports and design
documentation, make effective presentations, and give and receive clear instructions
11. Project Management and Finance: Demonstrate knowledge and understanding of the engineering and
management principles and apply these to one's own work, as a member and leader in a team, to manage projects
and in multi-disciplinary environments.
12. Life-long Learning: Recognize the need for, and have the preparation and ability to engage in independent and
life-long learning in the broadest context of technological change.

Program Specific Outcomes (PSOs)

PSO 1: Developing software applications with key focus on privacy, cost and utility.

PSO 2: Storing, processing, analyzing and learning from data for effective decision-making while finding
solutions for problems.

Prerequisites :
 A basic understanding of statistics, including concepts like probability, distributions, and descriptive
statistics, is necessary for data mining.
 This statistical foundation helps students interpret data and apply data mining techniques effectively.
Course Objectives:
Understand the skill sets and high-functioning teams involved in Agile, DevOps and

related methods to reach a continuous delivery capability.

Course Outcomes (COs)

Upon completion of the subject, students will be able to

1. Apply DevOps principles and methodologies to identify, analyze, and address

challenges in software development and delivery processes.L3

2. Apply DevOps principles, implement continuous testing practices, and shape resilient software
architecture to enhance business agility in software development models.L3
3. Apply source code control practices, understand the history and roles associated with

source code management, and effectively utilize Git-based tools and platforms in

project development.L3

4. Analyse complex built systems, demonstrate advanced proficiency in configuring and optimizing Jenkins
servers, critically strategize build dependency management, and design sophisticated pipelines for
effective system integration.L4
5. Analyze testing types, evaluate test automation, demonstrate proficiency in Selenium for frontend testing
and JavaScript for backend integration, apply test-driven development principles, and assess deployment
strategies using virtualization, configuration management, and container orchestration. L4
Syllabus

UNIT-I:

Introduction to DevOps:

Introduction, Agile development model, DevOps and ITIL. DevOps process and Continuous

Delivery, Release management, Scrum, Kanban, delivery pipeline, identifying bottlenecks.

UNIT-II:

Software development models and DevOps:

DevOps Lifecycle for Business Agility, DevOps, and Continuous Testing.DevOps influence

on Architecture: Introducing software architecture, The monolithic scenario, Architecture

rules of thumb, The separation of concerns, Handling database migrations, Micro services and the data tier,
DevOps, architecture, and resilience.

UNIT-III:

Introduction to project management: The need for source code control, the history of source code management,
Roles and code, source code management system and migrations, shared authentication, Hosted Git servers,

Different Git server implementations, Docker intermission, Gerrit, The pull request model, GitLab.
UNIT-IV:

Integrating the system:

Build systems, Jenkins build server, Managing build dependencies, Jenkins plugins, and file

system layout, The host server, Buildslaves, Software on the host, Triggers, Job chaining and build pipelines,
Build servers and infrastructure as code, Building by dependency order, Build phases, Alternative build servers,
Collating quality measures

UNIT-V:

Testing Tools and Deployment:

Various types of testing, Automation of testing Pros and cons, Selenium - Introduction,

Selenium features, JavaScript testing, Testing backend integration points, Test-driven

development, REPL-driven development. Deployment of the system: Deployment systems,

Virtualization stacks, code execution at the client, Puppet master and agents, Ansible,

Deployment tools: Chef, Salt Stack and Docker

Text Books:

1.Data Mining-Concepts and Techniques-Jiawei Han, Micheline Kamber, Morgan Kaufmann Publishers,
Elsevier, 2 Edition,2006.

2.Introduction to Data Mining, Pang-Ning Tan, Vipin Kumar, Michael Steinbanch, Pearson Education.

Reference Books:

1.Data mining Techniques, Arun K Pujari, 3rd Edition, Universities Press.

2. Data Warehousing Fundamentals, Paulraj Ponnaiah, Wiley Student Edition.

3.The Data Warehousing Life Cycle Toolkit –Ralph Kimbal. Wiley Student Edition.

4. Data Mining, Vikaram Pudi, P Radha Krishna, Oxford University Press.

 Course Plan of Devops:

Topic(s) Expecte No. Time Teaching

No. d Date of in method
Ses Minu
sio tes
ns
1 COURSE OUTCOME 29/2/24 1 60M C&T
2 INTRODUCTION OF SDLC 30M
Software Development Life Cycle 1/3/24 1 C&T
SDLC Models 30M
3 Importance of subject and syllabus 5/3/24 1 60M C&T
4 Unit-1
Introduction to DevOps: 7/3/24 1 30 M C&T

Introduction, Agile development model 30M

5 DevOps and ITIL 1 60M PPT

9/3/24

6 Revision of previous session 1 10M

DevOps process and Continuous Delivery 12/3/24 50M C&T

7 Release management, Scrum, Kanban 14/3/24 1 60 PPT

Delivery pipeline, identifying bottlenecks. 15/3/24 1 40M C&T

9
Oral discussion on Unit-1 20M TA

Total Classes for Unit-1 14

10 UNIT-II: 60M GD
Software development models and DevOps 26/3/24 1

11 DevOps Lifecycle for Business Agility 28/3/24 1 60M PPT

12 DevOps, and Continuous Testing 1 60M C&T

13 DevOps influence on Architecture , 40M C&T
30/3/24 1
Introducing software architecture
The monolithic scenario 20M C&T

14 Oral discussion of previous topic 10M GD

2/4/24
Architecture rules of thumb , The separation of concerns, 30M C&T
1
Handling database migrations 20M
15 Micro services and the data tier 4/4/24 30M C&T
1
16 DevOps, architecture, and resilience. 60M C&T
16/4/24 1

17 Overall Discussion on UNIT-II 11 60M TA

Total Classes for Unit-2 8

18 UNIT-III: 30M C&T

Introduction to project management 18/4/24 1
The need for source code control 30 C&T
M
19 The History Of Source Code Management 60M C&T
19/4/24 1
26 Roles And Code, Source Overall Discussion on UNIT-III
Code Management System. 1 60 TA
M
20
21 Discussion on previous session
Total Classes for Unit-3 20/4/24 9 10M Interactive
1 session
Migrations, Shared Authentication 30M C&T
Hosted Git servers 20M TA

22 Different Git server implementations 50M C&T

Overview of the concept 23/4/24 1 10M Interactive
session
 UNIT-IV: 1 60M
Integrating the system: Build systems 4/5/24

28 Jenkins Build Server 1 30M C&T

7/5/24
Managing Build Dependencies 30M Case Study

29 Jenkins plugins, and file system layout 9/5/24 1 50M C&T

Overview of the concept 10M GD

30 Jenkins plugins, and file system layout 1 40M

10/5/24 C&T
The host server. 20M

31 Build slaves, Software on the host 1 40M C&T

11/5/24
Triggers. 20M C&T

32 Job Chaining And Build Pipelines 1 60M C&T

14/5/24
33 Build Servers And Infrastructure As Code 1 40M C&T
16/5/24
Building By Dependency Order 20M C&T

32 Build phases 1 40M C&T

34
Overview of the previous concepts 20M GD

35 Alternative build servers

36 Collating quality measures. 11 40M C&T

1
Discussion on servers 20M GD

37 Overall Discussion on UNIT-IV 1 60M TA

Total Classes for Unit-4 11

38 UNIT-V Testing Tools and Deployment 1 60M C&T

Various types of testing, 18/5/24
39 Automation of testing Pros and cons 1 60M C&T
21/5/24
40 Selenium - Introduction, Selenium features 1 60M C&T

41 JavaScript testing 1 40M C&T

25/5/24
Overview on testing 20M Interactive
session
42 Testing backend integration points 1 30M C&T
Test-driven development 28/5/24 30M C&T
43 REPL-driven development 30/5/24 1 40M C&T

Discussion concepts 1 20M Interactive

session
44 Deployment of the system: Deployment systems 31/5/24 1 60M C&T

45 Virtualization stacks, code execution at the client 1/6/24 1 60M C&T

46 Puppet master and agents Ansible 1 60M C&T

47 Deployment tools: Chef, Salt Stack and Docker. 1 60M C&T

48 Oral discussion on Unit V 4/6/24 1 60M Interactive

session
49 QUIZ 6/6/24 1 60M Interactive
session
Total Classes for Unit-5 12

Overall completion of syllabus 49

 C&T: Chalk &Talk

 PPT:Power point presentation
 GD: Group Discussion
 TA: Text book assignment
 Evaluation scheme:

Name of the Type of the Examination Marks

Exam

Minor-1 Assignment 10

Mid Term-1 Objective 10

Subjective 20

Mid Term-1 Total 30

Minor-2 Objective Paper 10

Mid Term-2 Objective 10

Subjective 20

Mid Term-2 Total 30

Average of Minor-1 and Minor-2 10

Average of Midterm-1 and Midterm-2 30

Average of Minor + Average of Midterm 10+30=40

End Part-A 10
Examination
10 Questions each Question Carries 1 Marks

Part-B 50
From Each Unit 2 Questions, attempt any one like 5
Questions has to answer, each Question carries 10
Marks

End Examination Total Marks 10+50=60

Total Marks 40+60=100

Course material
a) PPT’s, Reference links of Material

b) Question bank prepared by faculty (unit wise)

 UNIT-I

SHORT ANSWER:

1. Define DevOps.

2. What is the Agile development model?

3. Describe how DevOps complements ITIL practices.

4. What is Continuous Delivery in the DevOps process?

5. Explain the role of Release Management in DevOps.

6. What is the purpose of a Scrum sprint?

7. Define Kanban.

8. What is a delivery pipeline in DevOps?

9. What is a bottleneck in DevOps?

10. Assess the importance of a delivery pipeline in Continuous Integration/Continuous Delivery

LONG ANSWERS:
1. Discuss the evolution of software development practices leading to the adoption of DevOps.
Critically evaluate the principles of the Agile development model.
2. How do these principles impact the speed, quality, and collaboration in software development?
3. Analyze the role of Release Management in a DevOps environment. How does it contribute to risk
management, and what best practices ensure successful release cycles?
4. Explain the Scrum framework in detail. How does Scrum facilitate Agile practices, and what
challenges might teams face when implementing Scrum?
5. Discuss the Kanban method as an alternative to Scrum for managing workflows. Compare its
strengths and weaknesses in various types of projects
6. Design a delivery pipeline for a software development project using DevOps practices.
7. Examine the concept of bottlenecks in a DevOps pipeline. How can bottlenecks be identified and
mitigated to improve efficiency and speed of delivery?
8. Discuss the core principles of DevOps and how they address the challenges in traditional IT
operations and development
9. Describe the DevOps process, focusing on the role of Continuous Delivery. How does Continuous
Delivery contribute to the overall goals of DevOps?
10. Examine the role of Release Management in a DevOps environment. How does it differ from
traditional release management practices
UNIT-II
SHORT ANSWER:
1. Define business agility in the context of DevOps.
 2. Explain how the DevOps lifecycle supports business agility.
3. What is Continuous Testing in DevOps?
4. Describe the influence of DevOps on software architecture
5. Explain the role of software architecture in system design
6. Define a monolithic architecture
7. What is a key limitation of a monolithic architecture in a DevOps
8. environment?
9. Name one rule of thumb in software architecture design.
10. How does the separation of concerns benefit software development?
11. Explain how microservices architecture affects the data tier.

LONG ANSWER:
1. Analyze how DevOps enhances business agility.
2. Explain the role of Continuous Testing in DevOps.
3. Evaluate monolithic vs. microservices architecture in DevOps.
4. Examine the shift from monolithic to microservices.
5. Compare the benefits and drawbacks of monolithic and microservices architectures
6. Analyze the impact of separation of concerns on software maintainability.
7. Discuss the challenges of database migrations in a microservices environment.
8. Propose a strategy for maintaining data consistency in a microservices architecture.
9. Evaluate the effectiveness of DevOps in enhancing system resilience.
10. Analyze how DevOps practices contribute to building resilient architectures.
UNIT-III
SHORT ANSWER
1. Define source code control.
2. Explain the historical significance of source code management.
3. In a collaborative project, how can using hosted Git servers improve efficiency?
4. Analyze the pull request model. How does it facilitate code review in collaborative environments?
5. What is a source code management (SCM) system? Name two examples.
6. explain the historical significance of source code management.
7. Evaluate the role of Docker in modern software development.
8. Analyze the pull request model.
9. In a collaborative project, how can using hosted Git servers improve efficiency?
10. Provide an example of how GitLab’s CI/CD features can enhance project management.

LONG ANSWER

1. Explain need for source code control.

2. What are essential devops roles.
3. Discuss Source code management system and migrations
4. What is Git and GitHub explain it? How it can be used in DevOps explain?
5. Write short notes on Hosted Git servers
6. Explain Different Git server implementations
7. Demonstrate the terminology of Docker intermission
 8. Explain terms A)Gerrit B)The pull request model
9. Briefly explain Shared authentication
10. Mention the steps to transfer the data from local repository to Central repository

UNIT-IV

SHORT ANSWER:

1. What is a build system?

2. How would you set up a simple Jenkins job to compile a Java application?
3. What are build dependencies?
4. Name two types of Jenkins plugins.
5. What is a build system?
6. Describe the concept of infrastructure as code.
7. What are build phases, and why are they important?
8. Provide an example of a trigger that can start a Jenkins job.
9. Evaluate the importance of collating quality measures in the build process.
10. Explain the importance of file system layout in managing Jenkins jobs and builds

LONG ANSWER:

1. Define Jenkins and its primary purpose in software development.

2. Explain the function of build slaves in a Jenkins environment.
3. What is job chaining, and how does it enhance build pipelines?
4. Examine how Jenkins plugins can be used to extend the capabilities of the build process.
5. Critically analyze the role of a host server in a Jenkins build system.
6. Discuss the implications of using infrastructure as code on system maintenance and deployment.
7. Evaluate the effectiveness of different build phases in achieving a successful build. Discuss how each
phase contributes to the overall process.
8. Examine how Jenkins plugins can be used to extend the capabilities of the build process.
9. Develop a strategy for managing build dependencies using a dependency management tool like Maven or
Gradle.
10. Describe the process of configuring a Jenkins server to build and deploy an application.

UNIT-V

SHORT ANSWER:

1. What are the main types of software testing?

2. Define test automation.
3. Explain the advantages of automating testing.
4. What are the disadvantages of test automation?
5. How would you implement a simple test using Selenium?
6. Illustrate a scenario where TDD can improve software quality.
7. Compare the advantages and disadvantages of TDD versus traditional testing methods.
8. Analyze the impact of automation on software testing efficiency.
9. Assess the effectiveness of different testing types (unit, integration, system) in the software development
lifecycle.
10. Evaluate the role of virtualization stacks in modern deployment strategies.

LONG ANSWER:

1. What are the fundamental concepts of different types of software testing? Provide examples.
 2. Outline the features and capabilities of Selenium as a testing tool.
3. Describe the process of implementing test automation in a software project. What steps should be taken?
4. Explain the significance of REPL-driven development in the context of modern programming practices.
5. Develop a comprehensive test automation strategy using Selenium for a web application. Include key
considerations.
6. Create a detailed deployment plan using Ansible that includes pre- deployment checks, deployment steps,
and post-deployment validations.
7. Evaluate the effectiveness of automated testing versus manual testing in different scenarios. When is one
preferable over the other?
8. critically assess the implications of using TDD on software design and development workflows.
9. Discuss the importance of testing backend integration points in ensuring software reliability.
10. Identify the key differences between Chef and Ansible for deployment.

Quiz question bank (unit wise)

1. What is the primary goal of DevOps?
A) Increase documentation
B) Reduce testing time
C) Bridge the gap between development and operations
D) Improve user interface design
Answer: C
2. Agile development emphasizes:
A) Long-term planning
B) Waterfall model principles
C) Iterative and incremental delivery
D) Complete code freezes before testing
Answer: C

### **3. Which of the following is NOT a core principle of Agile?**

A) Customer collaboration
B) Responding to change
C) Following a strict plan
D) Working software
Answer: C
4. ITIL stands for:
A) Information Technology Infrastructure Library
B) Information Tools in Lean
C) IT Infrastructure Lifecycle
D) Infrastructure and Technology in Linux
Answer: A
5. How does DevOps relate to ITIL?
A) They are competing frameworks
B) DevOps replaces ITIL entirely
C) DevOps complements ITIL practices
D) DevOps and ITIL have no relationship
Answer: C
6. Which of these best describes Continuous Delivery
A) Delivering software in one big release
B) Delivering software without automation
C) Software is always ready for release
D) Manual testing of software
Answer: C

---

7. What is the key difference between Continuous Delivery and Continuous Deployment?
A) Delivery includes testing
B) Deployment requires manual approval
C) Deployment always happens in a staging environment
D) Delivery skips performance testing
Answer: B
8. Which of the following is a benefit of DevOps
A) Longer development cycles
B) Decreased deployment frequency
C) Improved collaboration between teams
D) Reduced code quality
Answer: C
9. Scrum is a type of
A) Deployment tool
B) Agile framework
C) Programming language
D) Version control system
Answer: B
10. What is a "sprint" in Scrum?
A) A unit of time for completing tasks
B) A backup of the codebase
C) A brainstorming session
D) A testing method
Answer: A
11. In Scrum, the product owner is responsible for
A) Managing the team
B) Creating unit tests
C) Prioritizing the product backlog
D) Writing deployment scripts
answer: C
12. Which chart is commonly used in Scrum to track progress?
A) Bar chart
B) Burn-down chart
C) Pie chart
D) PERT chart
Answer: B
13. Kanban emphasizes:
A) Fixed iteration lengths
B) Limiting work in progress
C) Mandatory daily stand-ups
D) Long-term releases
Answer: B
14. The term "pull system" in Kanban refers to:
A) Pulling all tasks into a sprint
B) Tasks pulled as capacity allows
C) Pulling reports from the server
D) Pulling backups from production
Answer: B
15. What is a key visual feature of a Kanban board?
A) Flowchart design
B) Color-coded mind maps
C) Columns showing workflow stages
D) UML diagrams
Answer: C
16. What is the purpose of release management?
A) Writing application code
B) Managing software builds and deployment
C) Performing manual testing
D) Creating wireframes
Answer: B
17. Which of the following is part of a typical delivery pipeline?
A) Brainstorming sessions
B) Code reviews
C) Automated builds and tests
D) Marketing emails
Answer: C
18. What does CI in DevOps stand for?
A) Continuous Isolation
B) Continuous Integration
C) Controlled Implementation
D) Code Injection
Answer: B
19. Which tool is commonly used for CI/CD?
A) Photoshop
B) Jenkins
C) Excel
D) GIMP
Answer: B
20. What does identifying bottlenecks help with in DevOps?
A) Increase code duplication
B) Decrease productivity
C) Improve efficiency in the pipeline
D) Reduce testing coverage
Answer: C
21. What is a common cause of bottlenecks in a DevOps pipeline?
A) Too many coffee breaks
B) Automated testing
C) Manual approval steps
D) Unlimited work in progress
Answer: C
22. Which of the following best describes a “delivery pipeline”?
A) A marketing strategy
B) A sequence of manual operations
C) Automated steps to deliver software
D) A server upgrade plan
Answer: C
23. Which Agile framework uses roles such as Scrum Master and Product Owner?
A) Kanban
B) XP
C) Scrum
D) Lean
Answer: C
24. What is NOT a characteristic of DevOps?
A) Collaboration
B) Automation
C) Isolation of teams
D) Continuous feedback
Answer: C
25. What is the role of automation in DevOps?
A) Reduce human error and speed up processes
B) Eliminate the need for testing
C) Increase manual work
D) Replace developers
Answer: A
26. Which of these is a Continuous Integration practice?
A) Merging code once a month
B) Committing code only after testing
C) Regularly committing and testing code
D) Ignoring failed tests
Answer: C
27. What is a stand-up meeting in Scrum?
A) A performance review
B) A code review session
C) A short daily team meeting
D) A lunch meeting
Answer: C
28. Agile encourages
A) Strict contract negotiation
B) Comprehensive documentation
C) Face-to-face communication
D) Separate dev and ops teams
Answer: C
29. What is a DevOps culture built on?
A) Isolation
B) Trust and collaboration
C) Waterfall principles
D) Slow releases
Answer: B
30. Which phase typically follows code integration in a delivery pipeline?
A) Production deployment
B) Source control
C) Automated testing
D) Idea generation
Answer: C

Unit II

1. What is the main goal of the DevOps lifecycle?

A) Increase system downtime

B) Create complex architecture
C) Achieve faster and more reliable software delivery
D) Eliminate software testing
Answer: C
1. What is the main goal of the DevOps lifecycle?

A) Increase system downtime

B) Create complex architecture
C) Achieve faster and more reliable software delivery
D) Eliminate software testing
Answer: C

2. Which of the following phases is part of the DevOps lifecycle?

A) Ideation
B) Waterfall execution
C) Continuous Integration and Deployment
D) Requirement freezing
Answer: C

3. What does business agility in DevOps primarily aim to improve?

A) Server speed
B) Employee count
C) Time to market and adaptability
D) Company hierarchy
Answer: C

4. Continuous Testing in DevOps means:

A) Testing only after deployment

B) Manual testing during final release
C) Running automated tests throughout the lifecycle
D) Avoiding tests to increase speed
Answer: C

5. One of the key roles of continuous testing is to:

A) Delay deployment
B) Replace continuous integration
C) Provide rapid feedback on code quality
D) Run tests annually
Answer: C

6. Software architecture refers to:

A) Database optimization
B) The design and structure of software systems
C) Server provisioning
D) Coding standards
Answer: B

7. The monolithic architecture is characterized by:

A) Independent services
B) Loose coupling
C) A single codebase handling all functionalities
D) Serverless execution
Answer: C

8. What is a major drawback of monolithic architecture?

A) Better scalability
B) Easy debugging
C) Difficult to scale individual components
D) Low performance
Answer: C

9. In DevOps, a common recommendation is to design architecture with:

A) Minimal code reuse

B) High coupling
C) Separation of concerns
D) All-in-one class files
Answer: C

10. Separation of concerns in software architecture helps to:

A) Increase system complexity

B) Break the system into manageable modules
C) Make debugging harder
D) Reduce team collaboration
Answer: B

11. A benefit of separating concerns is:

A) Tighter integration
B) Easier maintenance and testing
C) Monolithic architecture adoption
D) Lower modularity
Answer: B

12. Which of these best describes microservices architecture?

A) One large, tightly coupled application

B) Application built as a suite of small, independent services
C) Single script that performs all operations
D) Client-server legacy setup
Answer: B

13. What makes microservices suitable for DevOps?

A) Centralized control
B) Ability to test and deploy services independently
C) Requires fewer servers
D) Large, unified team handling all services
Answer: B

14. One challenge of microservices is:

A) Lack of modularity
B) Scalability
C) Inter-service communication and orchestration
D) Tightly coupled code
Answer: C

15. In a microservices architecture, the data tier is often:

A) Centralized for all services
B) Shared across services without isolation
C) Owned and managed independently by each service
D) Stored in flat files
Answer: C

16. What is a recommended practice when handling database migrations in DevOps?

A) Avoid version control

B) Manual updates in production
C) Use migration scripts and version control
D) Do migrations only annually
Answer: C

17. Why are database migrations important in a DevOps pipeline?

A) They replace CI/CD

B) To ensure database changes are synchronized with application changes
C) They remove the need for testing
D) To centralize user access
Answer: B

18. Architecture rules of thumb in DevOps include:

A) Favor tight coupling

B) Build once, deploy everywhere
C) Avoid automation
D) Keep all logic in one file
Answer: B

19. What does resilience in software architecture mean?

A) A system with a nice user interface

B) Ability to recover from failures and continue functioning
C) Use of old technologies
D) Performing regular backups
Answer: B

20. Which approach improves system resilience in a microservices environment?

A) Hard-coding dependencies
B) Circuit breakers and retries
C) Synchronous service calls only
D) Ignoring failures
Answer: B

21. DevOps supports architectural resilience by encouraging:

A) Infrequent deployments
B) Manual server provisioning
C) Monitoring, alerts, and failover strategies
D) Hardcoded configurations
Answer: C

22. In a DevOps context, the architecture should support:

A) Rare releases
B) Static deployment
C) Frequent and automated deployment
D) Developer-only testing
Answer: C

23. What is a benefit of applying DevOps to architectural planning?

A) Increased time to market

B) Rigid development process
C) Early detection of architectural issues
D) Avoidance of testing
Answer: C

24. How does DevOps influence software architecture?

A) Promotes large, tightly coupled systems

B) Encourages modular, scalable, and deployable components
C) Removes the need for version control
D) Focuses only on UI/UX
Answer: B

25. Which of the following best describes DevOps' role in the evolution of development models?

A) Returning to waterfall practices

B) Encouraging manual builds
C) Driving automation, flexibility, and faster delivery
D) Avoiding continuous feedback
Answer: C

Unit III

1. Why is source code control important in project management?

A) To increase software size

B) To allow multiple developers to collaborate without overwriting code
C) To reduce application speed
D) To make code harder to understand
Answer: B

2. What is the primary function of a version control system (VCS)?

A) Reduce file storage

B) Maintain documentation
C) Track and manage changes to source code
D) Increase network traffic
Answer: C

3. Which of the following is a common issue without source code control?

A) Faster development
B) Improved teamwork
C) Code conflicts and loss of changes
D) Enhanced testing
Answer: C

4. One of the earliest version control systems was:

A) Git
B) SVN
C) RCS (Revision Control System)
D) Docker
Answer: C

5. Git was originally developed by:

A) Bill Gates
B) Linus Torvalds
C) Mark Zuckerberg
D) Dennis Ritchie
Answer: B

6. Which of the following best describes Git?

A) Centralized version control system

B) File compression software
C) Distributed version control system
D) Cloud storage provider
Answer: C

7. What is a common reason for migrating source code management systems?

A) To reduce team size

B) To move to a modern and more scalable tool
C) To delete source code
D) To make documentation harder
Answer: B

8. In source code management, a “role” typically defines:

A) Team size
B) File formats
C) Access levels and responsibilities
D) Code syntax
Answer: C

9. Which of these is a hosted Git server platform?

A) MySQL
B) GitHub
C) Apache
D) Oracle
Answer: B

10. GitLab is an example of a:

A) Web server
B) Hosted Git server with CI/CD capabilities
C) Desktop IDE
D) Data visualization tool
Answer: B

11. Which of the following supports self-hosting Git repositories?

A) GitHub (free plan)
B) Bitbucket Cloud
C) GitLab Community Edition
D) Notepad++
Answer: C

12. Gerrit is a:

A) Cloud storage provider

B) Git repository manager for code review
C) File sharing tool
D) Containerization engine
Answer: B

13. What is a key feature of Gerrit?

A) Pull-based backups
B) Automated hardware provisioning
C) Code review before merging changes
D) Manual file transfers
Answer: C

14. The pull request model allows developers to:

A) Pull random code from the internet

B) Avoid writing tests
C) Request that their changes be reviewed and merged
D) Bypass version control
Answer: C

15. In Git, a pull request is also referred to as a:

A) Push merge
B) Fork submission
C) Merge request
D) Commit update
Answer: C

16. Shared authentication in Git servers allows:

A) Each user to create their own security settings

B) Common user credentials across services
C) Anonymity for all contributors
D) Disabling access control
Answer: B

17. Which of the following is NOT a Git server implementation?

A) GitHub
B) GitLab
C) Dropbox
D) Bitbucket
Answer: C

18. Docker is primarily used for:

A) Hosting Git repositories
B) Managing physical servers
C) Creating and running containers
D) Writing code
Answer: C

19. A Docker container is:

A) A physical server
B) An IDE
C) A lightweight, standalone executable package
D) A shell script
Answer: C

20. What is the benefit of using Docker in a development workflow?

A) Increases memory usage

B) Ensures consistent environments across development and production
C) Reduces version control
D) Removes the need for source code
Answer: B

21. Which Git operation is used to upload local commits to a remote repository?

A) git clone
B) git init
C) git pull
D) git push
Answer: D

22. In Git, to fetch and merge changes from a remote repository into the current branch, you
use:

A) git fork
B) git push
C) git pull
D) git reset
Answer: C

23. GitLab CI/CD pipelines are configured using which file?

A) config.yaml
B) gitlab.json
C) .gitlab-ci.yml
D) docker-compose.yml
Answer: C

24. Which Git server supports both pull request and code review mechanisms?

A) GitHub
B) GitLab
C) Gerrit
D) All of the above
Answer: D

25. In project management, version control contributes to:

A) Replacing team roles
B) Slowing down releases
C) Better collaboration and traceability
D) Disabling rollback options
Answer: C

Unit IV

1. What is the primary purpose of a build system?

A) Managing project budgets

B) Writing application logic
C) Automating code compilation, testing, and packaging
D) Encrypting source code
Answer: C

2. Jenkins is best described as a:

A) Programming language
B) Source code repository
C) Continuous Integration/Continuous Deployment (CI/CD) tool
D) Cloud storage service
Answer: C

3. Which of the following can Jenkins automate?

A) Writing user stories

B) Running tests and deploying code
C) Designing UIs
D) Scheduling meetings
Answer: B

4. What is a “build dependency”?

A) A type of bug
B) A financial resource
C) A module or library that a project relies on to build successfully
D) A backup system
Answer: C

5. Jenkins plugins allow:

A) Limiting Jenkins functionality

B) Adding new features and integrations
C) Encrypting the Jenkins server
D) Avoiding builds
Answer: B

6. The Jenkins file system layout helps in:

A) Managing memory leaks

B) Organizing jobs, builds, and configuration files
C) Sending emails
D) Generating passwords
Answer: B

7. The host server in Jenkins refers to:

A) The end-user machine

B) The server that runs Jenkins master and controls build execution
C) The database server
D) A remote git repository
Answer: B

8. Buildslaves (or agents) in Jenkins are used for:

A) User authentication
B) Building on distributed environments
C) Managing credentials
D) Saving passwords
Answer: B

9. One key benefit of using buildslaves is:

A) Decreased parallelism
B) Better memory management
C) Load distribution across multiple machines
D) Reduced logging
Answer: C

10. What is meant by “software on the host” in CI/CD contexts?

A) The software users install

B) Software installed on the build server to support jobs (e.g., Java, Maven)
C) Mobile apps only
D) Operating system files only
Answer: B

11. A trigger in Jenkins is used to:

A) Execute jobs manually

B) Log out users
C) Start a job based on specific conditions (e.g., commit, schedule)
D) Limit plugin use
Answer: C

12. Job chaining in Jenkins refers to:

A) Creating secure credentials

B) Sequential execution of dependent jobs
C) Combining branches
D) Enabling backups
Answer: B

13. A build pipeline is:

A) A user interface theme

B) A group of servers
C) A set of automated processes that execute from code commit to deployment
D) A GitHub repository
Answer: C

14. Infrastructure as Code (IaC) involves:

A) Manually setting up servers

B) Writing server configuration in code (e.g., YAML, Terraform)
C) Encrypting databases
D) Designing user interfaces
Answer: B

15. What is one key benefit of Infrastructure as Code?

A) Encourages manual setup

B) Reduces deployment repeatability
C) Improves consistency and automation in provisioning infrastructure
D) Slows down development
Answer: C

16. Building by dependency order ensures:

A) Random execution of builds

B) Builds fail quickly
C) All required modules are built in the correct sequence
D) Build history is deleted
Answer: C

17. A typical build process includes which of the following phases?

A) Design → Budgeting → Deployment

B) Compile → Test → Package → Deploy
C) Encrypt → Compress → Host
D) Debug → Refactor → Draw
Answer: B

18. An alternative to Jenkins for build automation is:

A) Excel
B) Git
C) Travis CI
D) WinRAR
Answer: C

19. Which of the following is a CI tool besides Jenkins?

A) Terraform
B) Docker
C) CircleCI
D) Adobe XD
Answer: C

20. What does “collating quality measures” involve in CI/CD?

A) Ignoring test reports

B) Combining results from testing, code coverage, and static analysis
C) Estimating file sizes
D) Optimizing Docker images
Answer: B

21. Which plugin in Jenkins can be used to visualize pipelines?

A) GitHub Plugin
B) Blue Ocean
C) Apache Plugin
D) Disk Usage Plugin
Answer: B

22. What file is often used to define Jenkins pipelines?

A) Jenkins.txt
B) Jenkinsfile
C) Pipeline.md
D) config.ini
Answer: B

23. Jenkins builds can be triggered using:

A) Git commits
B) Cron schedules
C) API calls
D) All of the above
Answer: D

24. What is a build artifact?

A) A build error
B) A test result
C) The output of the build process, like binaries or packaged files
D) An error log
Answer: C

25. A failed build step in a pipeline typically:

A) Is ignored
B) Triggers deployment
C) Stops subsequent steps unless handled
D) Deletes the codebase
Answer: C

Unit V

1. What is the purpose of software testing?

A) Increase code complexity

B) Verify that software behaves as expected
C) Remove features from applications
D) Replace source control
Answer: B
2. Which of the following is a type of functional testing?

A) Load testing
B) Unit testing
C) Penetration testing
D) Volume testing
Answer: B

3. What is non-functional testing focused on?

A) Business logic
B) Performance, scalability, and usability
C) Syntax correctness
D) Database design
Answer: B

4. A key advantage of test automation is:

A) Manual code changes

B) Faster and repeatable test execution
C) Elimination of test coverage
D) Avoiding documentation
Answer: B

5. A potential disadvantage of test automation is:

A) Consistent results
B) Initial time and effort to set up
C) Support for CI/CD
D) Less human error
Answer: B

6. Selenium is primarily used for:

A) Backend database testing

B) Server provisioning
C) Automating web browser testing
D) Mobile app testing
Answer: C

7. Which of the following is a feature of Selenium?

A) Native app testing

B) Command-line-only testing
C) Cross-browser testing automation
D) Virtualization support
Answer: C

8. Selenium WebDriver allows:

A) Testing only in Firefox

B) Programmatic control of browsers
C) Manual script execution
D) File encryption
Answer: B

9. Which language is NOT commonly used with Selenium?

A) Java
B) Python
C) C++
D) JavaScript
Answer: C

10. JavaScript testing frameworks are best suited for:

A) Backend testing only

B) Web browser UIs and front-end applications
C) Testing mobile apps
D) Testing networks
Answer: B

11. A popular JavaScript testing framework is:

A) Selenium
B) JUnit
C) Mocha
D) Postman
Answer: C

12. What is typically tested in backend integration testing?

A) HTML structure
B) Browser rendering
C) APIs and services connecting with other systems
D) CSS layout
Answer: C

13. Test-Driven Development (TDD) involves writing tests:

A) After the deployment

B) Alongside project documentation
C) Before writing actual code
D) Only in production
Answer: C

14. A benefit of TDD is:

A) Decreased test coverage

B) Reduced code modularity
C) Improved design and early bug detection
D) Slower development
Answer: C

15. REPL-driven development is most commonly associated with:

A) Compiled languages
B) Writing tests manually
C) Interactive coding in a Read-Eval-Print Loop environment
D) Static code generation
Answer: C

16. Which language is known for REPL-driven development?

A) Java
B) C
C) Clojure
D) HTML
Answer: C

17. What is the purpose of a deployment system?

A) Write backend APIs

B) Serve test reports
C) Automate application release and environment configuration
D) Compile binary files only
Answer: C

18. Virtualization stacks are used to:

A) Physically install software

B) Increase manual testing
C) Create isolated environments using virtual machines or containers
D) Avoid using servers
Answer: C

19. Code execution at the client side typically happens in:

A) JavaScript in a browser
B) Java server
C) Docker container
D) Bash scripts
Answer: A

20. Puppet follows which configuration management model?

A) Push model
B) Manual intervention
C) Pull model (agent polls master)
D) Fully serverless
Answer: C

21. The role of the Puppet agent is to:

A) Control the master

B) Fetch configurations from the Puppet master and apply them
C) Deploy Docker containers
D) Replace Ansible
Answer: B

22. Ansible differs from Puppet in that it:

A) Requires a central master server

B) Uses a push model with SSH
C) Has a GUI for configurations
D) Is Windows-only
Answer: B

23. Chef is a:
A) Deployment testing tool
B) Database software
C) Configuration management and automation tool
D) Code formatter
Answer: C

24. Salt Stack is known for:

A) Building containers
B) Peer-to-peer communication and fast remote execution
C) Running JavaScript tests
D) Providing IDE services
Answer: B

25. Docker is best described as:

A) An API testing tool

B) A virtualization platform using containers
C) A server monitoring system
D) A browser testing framework
Answer: B
 PART-B

Department: CSD Date:

Name of the Faculty: J MADHAVI Subject Code: D85PC14 (R22)
Title of the subject: DEVOPS

1 CO-PO & PSO’s mapping

2 Teaching Dairy (Faculty Activity Book)

3 Analysis of student performance

4 Answer book copies

a) Internal books (Excellent/Good/Fail) = 3 Nos

b) Assignment Copies (Excellent/Good/Fail) = 3 Nos

c) Quiz paper (Excellent/Good/Fail) = 3 Nos

d) Laboratory records (if any) (Excellent/Good/Fair) = 3 Nos.

5 Whether remedial measures were taken by faculty members after

completion of first module (with supporting documents)

6 IQAC review report of teaching notes (pre + post)

Progra
Program Outcomes m
Course Specific
Outcom Outcome
es s
PO 1 P P P P P P P P P P P PS PS
O O O O O O O O O O O O O
2 3 4 5 6 7 8 9 1 1 1 2
0 1 1
2
CO1 0 2 0 0 3 0 0 0 2 2 0 1 2 2
CO2 2 2 2 0 3 0 0 0 2 2 2 1 2 2
CO3 0 0 2 0 3 0 0 0 2 2 2 1 2 2
CO4 0 0 2 0 3 0 0 0 1 2 1 1 2 2
CO5 2 0 2 0 3 0 0 0 2 2 2 1 2 2

Average
*To be rated with 1- slightly, 2 – moderately, 3- substantial

Contribution of course to program outcomes& Program Specific outcomes

Type Course P PO 2 PO 3 PO 4 P P P P PO 9 PO 10 P PO PSO PS

Code, O O O O O O 12 1 O
Title 1 6 8 2
5 7 1
1
Theor DevOps
y
3 1.6 2.2 1.6 3 2 1.3 1.8 1. 2.8 1
6 .
4
 Delivery Methodology

Course Delivery Methods/Modes:

1. Class room lectures: 48
2. Presentations:5
3. Laboratory sessions:-
4. Demos: 0
5. Assignments:5
6. Case studies: 0
7. Seminars:3
8. Projects: 0
9. E-Learning Resources:5

Mapping between Course Delivery Methodology and Course Outcomes

Course Delivery Methods Course Outcomes

1 2 3 4 5

Class room lecture √ √ √ √ √

Presentations √ √ √ √ √

Laboratory sessions

Demo or simulations

Assignments √ √ √ √ √

Case studies √ √ √ √

Projects

Seminars √ √ √ √ √

E-Learning resources √ √ √ √ √

37