Azure DevOps Flashcards

1
Q

This is a collection of files or packages published by a run.

A

Artifact

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

A process by which code is built, tested, and deployed to one or more test and production stages.

A

Continuous delivery

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

The practice used by development teams to simplify the testing and building of code.
Helps catch bugs or problems early in the development cycle.

A

Continuous integration

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

Automated tests and builds are run as a part of this process.

A

Continuous integration

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

What is an environment?

A

A collection of resources, where you deploy your application.

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

This is a way to store files and share them across pipelines.

A

Secure files

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

Use this to store values and secrets that you might want to be passed into a YAML pipeline or make available across multiple pipelines.

A

Variable group

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

At what level can the number of parallel jobs be configured?

A

Organizational level

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

All feature development should take place in a dedicated branch and not the main branch. Makes it easier for developers to work on a particular feature without disturbing the main codebase. Means the main branch should never have broken code. This describes what type of development workflow

A

Trunk-based development

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

In a forking workflow how many and what types of repos do developers have?

A
  1. One private local and one public server-side one.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Github workflows support a maximum of how many secrets?

A

100

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

Use this type of process when your team wants the simplest model that uses Issues, Tasks, and Epics to track work. Tasks support tracking Remaining Work

A

Basic

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

This process works great if you want to track user stories and (optionally) bugs on the Kanban board, or track bugs and tasks on the taskboard. Tasks support tracking Original Estimate, Remaining Work, and Completed Work.

A

Agile

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

This process works great for tracking product backlog items (PBIs) and bugs on the Kanban board. Also, break down PBIs and bugs into tasks on the taskboard. Tasks support tracking remaining work only.

A

Scrum

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

Choose this when your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. With this process, track requirements, change requests, risks, and reviews. asks support tracking Original Estimate, Remaining Work, and Completed Work.

A

CMMI - Capability maturity model integration

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

Measurement of how long it takes your team to complete work once they have began to actively work on them.

A

Cycle time

17
Q

Determination of how much work can be done sprint-over-sprint

A

Velocity

18
Q

The time taken to close a work item after it was created

A

Lead time

19
Q

How much work remains in a given time period (i.e., sprint)

A

Burndown

20
Q
A