Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Hands On DevOps > Final Part 1 > Flashcards

Final Part 1 Flashcards

1
Q

Blue/Green Deployment

A

Enables you to launch a new version of your application alongside the old version, and monitor and test the new version before you reroute traffic to it, rolling back on issue detection.

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

Canary Deployment

A

Releases software changes to select customers as a way of
testing functionality and reliability in production while limiting the number
of customers potentially impacted.

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

What to do after you’re satisfied that no customer is negatively impacted from the Canary Deployment?

A

You can slowly increase the number of customers who receive the new version of your application.

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

Rolling Deployment

A

Installation of software updates on one server or server subset at a time, rather than updating all servers or server subsets at the same time.

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

How often is a new version deployed at each instance in Rolling Deployment?

A

One at a time(in clusters)

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

Window Size

A

The size of your grouping

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

A window size of one will proceed______ machine at a time whereas a window size of four will deploy the new version to four servers at the same time.

A

one

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

What’s the advantage of Rolling Deployment?

A

The contrast between it and a traditional upgrade.

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

Feature flag or Feature toggle

A

Conditional feature that can be hidden from customers.

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

What does feature flags help solve?

A

Maintaining continuous delivery or continuous deployment while not releasing the functionality to customers until you’re ready.

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

What happens if you deploy partially completed work?

A

It reduces the number of feature branches and merging you have to manage throughout the process and alerts other developers of your work long before it’s finished.

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

What needs to be monitored after releasing software?

A

Performance, Availability, Security and More

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

Telemetry

A

Fancy word for collecting data on the behavior of your systems.

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

What does telemetry enable your system to do?

A

Regularly update you on how things are going, which keeps you from digging into logs only when something goes wrong.

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

How does telemetry create records on its own behavior?

A

Independently

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

What can you do to benefit from telemetry?

A

You must set your application and infrastructure up in such a way that data collection and reporting are possible

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

What are the two components that Telemetry requires?

A

Data collection and Metrics management

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

What three terms in site reliability engineering is important to keep in mind for monitoring systems.

A

Service-Level Agreement (SLA), Service-Level Objective (SLO), and Service-Level Indicator (SLI):

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

Service-Level Agreement(SLA)

A

Defines the level of service expected by a customer from a supplier - Availiability

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

Service-Level Objective (SLO)

A

Is the specific reliability, availability, or performance target that a vendor promises to meet within an SLA.

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

Service-Level Indicator (SLI)

A

Measures how well a company actually meets the SLO promises that it sets within SLAs

22
Q

Similarities and differences between SLAs, SLOs and SLIs

A

An SLA is a contract.
An SLO is a specific goal that is defined in a contract.
An SLI measures the extent to which teams comply with the SLO promises they make in SLA contracts.

23
Q

Release engineering

A

Relatively new and fast-growing discipline of software engineering that can be concisely described as building and delivering software.

24
Q

What do release engineers have a solid(if not expert) understanding of?

A

Source code management, compilers, build configuration languages, automated build tools, package managers, and installers.

Also development, configuration management, test integration, system administration, and customer support.

25
Q

What do running reliable services require?

A

A reliable release process

26
Q

What should SRE’s know about their binaries and configurations?

A

That they are built in a reproducible, automated way so that releases are repeatable and aren’t “unique snowflakes.”

27
Q

What kind of tools that Release Engineers mostly envision and develop?

A

Tools that report on a host of metrics, such as how much time it takes for a code change to be deployed into production (in other words, release velocity) and statistics on what features are being used in build configuration files.

28
Q

What does Google’s best practices cover?

A

All elements of the release process. Examples include compiler flags, formats for build identification tags, and
required steps during a build.

29
Q

What’s an incident or service outage?

A

Essentially, an incident is any technical disruption of your business. Incidents come in all shapes, sizes, and severities.

30
Q

Instead of focusing on preventing humans from making mistakes what does DevOps processes recommend?

A

Creating and implementing automated systems along the entire development process.

31
Q

What are four areas primed for automation?

A

– Code: Software developers design and build solutions via code. Developers
manage their source code and often work on the same portion of a codebase
simultaneously.
– Integration: Code changes must be merged from multiple developers into the
master branch of a code repository.
– Deployment: After being merged, the code must be deployed. This can often
mean releasing updates, changing configurations, and even deprecating
services.
– Infrastructure: An application must be run on hardware. Depending on the
updates to code, infrastructure may need to be instantiated, provisioned, or
terminated.

32
Q

What are some benefits of moving with a crowd for solutions for your team?

A

Popular tools often have the best documentation and answers on technical forums.

Popular tools are often open-source software(OSS)

33
Q

Empirically

A

By means of observation or experience rather than theory or pure logic. “empirically tested methods”

34
Q

Mean Time To Repair(MTTR)

A

The average time your business is impacted during incidents. Also sometimes used to describe the mean time to recovery, the amount of time your team takes to resolve an issue as well as mean time to respond, or the time an organization takes to acknowledge and initiate a response to a problem.

35
Q

What to include when collecting the MTTR?

A

Latency, the time from when the failure first occurred to when it was detected. This is likely calculated after the incident is resolved.

36
Q

MTTR formula

A

MTTR = total time of impact / number of incidents

37
Q

What steps can incidents be broken down into?

A

Discovery, Response, Restoration, Reflection, and Preparation.

38
Q

What is the purpose of breaking an incident into different phases?

A

To better understand each step of the unplanned work.

39
Q

Discovery

A

This phase starts when the issue is detected. Services can be
impacted for a period of time before you realize it.

40
Q

Response

A

This phase is the scramble of trying to determine the source of the issue.

41
Q

Restoration

A

At this point, you’ve identified the issue and are working on solving it. This phase is often one of the shortest ones of the incident. After you know what’s happening, you usually discover a straightforward fix, even if it means rolling back a deployment or reverting to the last issue-free build.

42
Q

Reflection

A

This phase is where a post-incident review takes place.

43
Q

Preparation

A

During the preparation phase, engineers complete the work determined necessary during the post-incident review.

44
Q

What two incident phases are often forgotten after the service is restored?

A

Reflection and Preparation.

45
Q

Distributed System

A

A collection of components networked across multiple computers.

46
Q

Are the components of a distributed system independent or dependent?

A

They are independent. They can fail without impacting other services and work concurrently.

47
Q

Why are companies moving to cloud hosting?

A

Running applications at scale requires efficient use of infrastructure and the cost of underutilizing hardware adds up quickly.

48
Q

What are two concepts that accompany the transition to distributed systems?

A

Microservices and Containers

49
Q

Microservices

A

Style of architecture that separates logic into loosely coupled services.

50
Q

Containers

A

Enable engineering teams to package applications with dependencies and provide an isolated, ephemeral environment(an environment meant to last for a limited amount of time).

Hands On DevOps (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions