DevOps Flashcards

1
Q

What is the role of Site Reliability Engineering (SRE)?

A

SRE implements the interface DevOps.

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

Why is DevOps considered to be in a state of flux?

A

Many see DevOps as a concrete concept rather than an abstract one.

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

What does the phrase ‘You Build It You Run It’ mean?

A

“Giving developers operational responsibilities enhances service quality by bringing them into direct contact with day-to-day operations and customer feedback.”

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

What are the five principles of DevOps as described by the CALMS acronym?

A
  1. Culture
  2. Automation
  3. Lean
  4. Measurement
  5. Sharing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the Culture principle in DevOps?

A

The Culture principle in DevOps is that everyone should work together with shared values, helping to prevent or resolve conflicts between team members.

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

Why is a blameless culture important in DevOps?

A

A blameless culture focuses on organizational learning, where human errors are addressed by learning lessons, growing, and sharing knowledge.

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

What did Toyota’s NUMMI plant teach us about culture?

A

Toyota retrained GM workers with a high-trust continuous improvement culture, which helped produce the highest quality cars in America within three months.

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

What is the Automation principle in DevOps?

A

The Automation principle in DevOps is that everyone should strive to automate as many manual tasks as possible to reduce the likelihood of deployment failures.

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

Why is automation important in DevOps?

A

Automation leads to repeatable, documented processes, increasing both velocity and transparency, while freeing up time for other tasks.

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

What does Jidoka mean in Toyota’s approach?

A

Jidoka, or ‘automation with a human touch,’ allows a machine to stop the production line when an abnormality is detected, or an operator can stop it by pulling the andon cord.

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

What is the Lean principle in DevOps?

A

The Lean principle in DevOps is that everyone seeks to eliminate waste, which delays product delivery without improving it.

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

How does limiting work in progress eliminate waste in DevOps?

A

Limiting work in progress helps avoid interrupt-driven tasks and ensures that the team remains focused on completing tasks before taking on new ones.

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

What is the importance of reducing handoffs in DevOps?

A

Reducing handoffs minimizes communication and coordination issues, which reduces waste and speeds up product delivery.

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

What is Kanban used for at Toyota?

A

Kanban boards are used to eliminate waste by visualizing workflows and identifying delays in areas like waiting, transporting, and overproduction.

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

What is the Measurement principle in DevOps?

A

The Measurement principle in DevOps is that metrics and logs are monitored obsessively to quickly detect problems and fix them.

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

Why are metrics important in DevOps?

A

Metrics provide valuable insight into system performance and can indicate problems quickly, allowing for timely interventions.

17
Q

What is the role of metrics at Toyota’s production line?

A

Toyota uses metrics to discover when a team or individual is struggling, helping to guide a gemba walk to provide support and improvement.

18
Q

What is the Sharing principle in DevOps?

A

The Sharing principle in DevOps is that everyone shares information, fostering collaboration and enhancing communication between development and operations teams.

19
Q

How can development and operations teams build relationships in DevOps?

A

Development teams can invite operations members to meetings, lunches, and informal outings, which fosters better communication and collaboration.

20
Q

How does better communication between teams benefit DevOps?

A

It enables quick detection of problems and ensures that lessons are shared, preventing the recurrence of issues.

21
Q

What is genchi genbutsu in Toyota’s approach?

A

Genchi genbutsu, meaning ‘go and see,’ encourages managers to observe conditions firsthand, engage with employees, and understand the issues in the production environment.

22
Q

What is DevOps in its purest form according to Vargo?

A

DevOps is about breaking down the (metaphorical) wall between developers and operators.

23
Q

Why should organizations reduce silos according to Vargo?

A

Success comes from cooperation between cross-functional teams, which requires reducing organizational silos.

24
Q

Why should failure be accepted as normal in DevOps?

A

Failure is normal because any system built by humans is inherently unreliable, and it must be addressed as part of continuous improvement.

25
Why is gradual change important in DevOps?
Large, million-line changes are harder to debug, so gradual change allows for more manageable, iterative improvements.
26
Why should tooling and automation be leveraged in DevOps?
Tooling and automation turn work into repeatable patterns, improving efficiency and reducing the chances of human error.
27
Why should everything be measured in DevOps?
Measuring everything provides the data necessary to justify the investment in DevOps and to track progress through clear metrics of success.
28
How does SRE reduce organizational silos?
SRE reduces silos by sharing ownership with developers, using the same shared tooling, and setting availability measures that force conversations between SRE and development.
29
How does SRE accept failure as normal?
SRE uses Service Level Objectives (SLOs) to acknowledge system unreliability and conducts blameless post-mortems to learn from failures.
30
How does SRE implement gradual change?
SRE implements gradual change through small, iterative deployments, reducing the cost of failure while maintaining reliability.
31
How does SRE leverage tooling and automation?
SRE ensures that tasks done manually this year should be automated next year, eliminating toil and improving system reliability.
32
How does SRE measure everything?
SRE measures both system metrics (e.g., reliability) and human metrics (e.g., toil), ensuring that both technical and human aspects are optimized.