DevOps and Agile Flashcards

1
Q

Provides Mechanisms

A

Perform software development, testing, and deployment in an automated and synchronized fashion

Quick time to market

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Provides Mechanisms and benefits 1

A

Perform deployments with great quality and stability in short duration of time

Reliable and stable applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Provides Mechanisms and benefits 2

A

Ensure support teams are enabled

Maintain service level agreements(SLA) for support related activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Continuous integration

A
  1. Code Analysis
  2. Unit testing
  3. Code coverage
  4. Build
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Continuous Delivery

A
  1. Environment provisioning for testing
  2. Testing (QA)
  3. Deployment to pre-production
  4. Release management
  5. Env. provisioning for production
  6. Deployment and release to production
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Need for DevOps

A
  1. Quick time to market - delay of promised new features although agility is being adopted
  2. Issues in code quality & application stability - code comes back at the same speed
  3. Drop in SLAs for support and operations - steady drop in SLA’s for resolving queries
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

DevOps definition

A

Business, Devs/QA, and Ops work together with common goal process and metrics to achieve speed, quality for early and continuous delivery for valuable software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Benefits of DevOps

A

Quick to market
Reliable and stable
Maintenance of service levels for support and ops

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Involves a collaborative working

A

Development
Testing
Infrastructure
Ops Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

DevOps maturity is measured by..

A

The speed, frequency, stability and quality of releases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

DevOps is driven by…

A

Automation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

DevOps is not…

A

Conglomeration of tools and their synchronization

Jenkins tools for orchestration of some build activities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Managed by..

A

Stakeholders and Vendors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

People and process dimensions are…

A

Very critical in DevOps adoption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

People transformation

A

Stage 1 - Dev & Ops separate
Stage 2 - Progressive Dev + Ops
Stage 3 - Integrated DevOps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Process adoption

A

Stage 1 - a separate dev and ops processes with interventions
Stage 2 - enhanced process to accommodate dev and ops tasks
Stage 3 - unified process with unified metrics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Technology innovation

A

Stage 1 - Continuous Integration
Stage 2 - Continuous delivery
Stage 3 - Monitoring and support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Challenges in DevOps Adoption 1

A
People
Conflict in goals
Little collaboration 
Ops teams not sensitized on the requirements & urgency of deployments 
Geographically distributed teams
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Challenges in DevOps Adoption 2

A

Process
Delays due to formal knowledge transfer
Tedious change management process
Complex release management process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Challenges in DevOps Adoption 3

A

Technology
Lack of automation
Defects generated due to inconsistent environments
Delays due to infrastructure unavailability

21
Q

Stakeholders involved for successful DevOps adoption

A
Business
Dev teams 
Test teams
Infrastructure teams
Ops teams
22
Q

Capabilities to be built for DevOps: Business

A
Agile approach
Automated acceptance test
Rapid prototyping 
Lean processes
Big room planning
23
Q

Capabilities to be built for DevOps: Dev team

A
Continuous integration 
Build automation 
Agile approach
Micro services
Feature toggle
Version control
Code quality analysis 
Code coverage
Unit test automation 
Artifact repository 
Incremental design
24
Q

Capabilities to be built for DevOps: Test team

A
Functional test automation 
Test management 
Test Data management 
Service virtualization 
Performance test automation 
Security test automation
Progressive test automation
25
Q

Capabilities to be built for DevOps: Infra team

A
Database deploy
Infrastructure layer 
Environment management 
CD automation 
Release management 
Containerization
On demand infra 
Infra-as-code 
Just enough infra
26
Q

Capabilities to be built for DevOps: Ops team

A
Incident management tools
Support analytics 
Monitoring and dashboard 
Predictive monitoring 
Self healing
27
Q

Technology stacks

A

Depends on the project, tech, and customers desire for automation

28
Q

SDLC

A

Planning stage
Construct stage
Validate/Test
Deploy and Release

29
Q

Application life cycle management tools

A

Tool used in Planning stage

Ex: Jira

30
Q

Scrum Design phase tool

A

Rapid prototyping tool

Ex: Infosys rapid prototyping tool

31
Q

Scrum Construct build phase

A

Version control tool
Ex: GIT

Static code quality analysis tool
Ex: Sonarcube

Dynamic code quality
Ex: probe

Unit testing
Ex: JUnit

Code coverage, check the quality of tests written
Ex: JaCoCo, Cobertura

Code review
Ex: Jupiter

Build automation, code built
Ex: Maven, Grunt

32
Q

Baseline in Artifact repository

A

Where the word file with the code goes so that the next stages can pick up from the right folder. Ensures the same version of the binary file undergoes testing, deployment to pre production, release to production

Construct stage
Ex: Nexus, Artifactory

33
Q

Continuous Integration

A

Where all the build activities from static code analysis to construction of the word file to baselining in artifact repository are sequenced and orchestrated

Construct stage and beginning of validation

Ex: Jenkins, Bamboo

34
Q

Validation is also orchestrated through..

A

Continuous Integration engine

35
Q

Deployment and Database Deployment

A

Automated deployment of application/database, next step of SDLC

Ex: liquibase

36
Q

Functional/Acceptance testing, Performance testing, and Security testing

A

Testing done in validation step of SDLC

Tool Ex:
functional testing, selenium

Performance testing, JMeter

Security testing, AppScan

37
Q

Test and defect management and Test Data management

A

Tool Ex:

Zephyr
Jira

38
Q

Continuous validation + deployment to pre-production environment =…

A

Continuous delivery

39
Q

Environment management tool

A

Used for the Environment for deployment in the pre-production environment

Used in tandem with a virtual environment using a cloud or

Environment for testing and also be configured using these tools
Ex: Chef, puppet

40
Q

Release management tools

A

Used for approvals for release

Ex: XL Release

41
Q

Incident management/Support analytics/Monitor Dashboard

A

Used to keep support and operations teams up to speed in the activities associated with SDLC

Ex: Nagios, splunk

42
Q

Developer role in DevOps set up

A

Collaborative planning for dev (+test) and ops activities
Resolving recurring Ops issues
Understanding and developing as per Ops requirements
Build automation and continuous integration

43
Q

Tester role in DevOps

A

Test automation (all phases including service virtualization)
Test data deploy management
Understanding Ops scope of work needs
Performing Ops-like testing for Ops-like metrics (e.g security)

44
Q

Ops role in DevOps

A

Providing Ops insights to Dev
Understanding Dev stories/configuration
Proactive planning for releases
Continuous integration for continuous KT

45
Q

Automation experts

A
End to end pipeline automation for build progression
Infra and release automation
Infra testing
Database deploy automation
Dynamic test data management
46
Q

Process Models

Model 1: Dev & Ops separate

A

Two separate teams
Teams follow their own processes
Teams brought together through common points of intervention
Teams discuss issues and dependencies

47
Q

Process models

Model 2: Dev & Ops separate but following similar process

A

Teams separate
Representatives of ops and testing in Dev teams
Teams start to follow the same processes

48
Q

Process models

Model 3: Unified process

A

Single DevOps team

Scrumban model