Lesson 3 Flashcards

1
Q

is the process of delivering software applications and updates to end users.

A

Software deployment

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

Software deployment is the process of delivering software
applications and updates to end users. Includes various activities
such as:
o Installation
o Configuration
o Running, and;
o Testing the software in a target environment.

A

true

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

Proper software deployment ensures that applications function
correctly, are scalable, and are secure.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  • A well-executed deployment also contributes to system reliability,
    security, and overall user satisfaction
A

True

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

Ensuring the software is packaged and ready for
deployment.

A

Preparation

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

Creating installation packages, scripts, or images.

A

Packaging

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

Testing to confirm proper deployment and
functionality.

A

verification

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

Continuous monitoring and providing updates
and patches.

A

Maintenance

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

is the broader process that includes release activities.

A

Deployment

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

Installing and configuring the software on
production servers.

A

Deployment

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

involves the entire process of making the software available for use, including installation and
configuration.

A

Software Deployment

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

specifically refers to the distribution of a new version or update to users.

A

Software Release

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

Best Practices for Software Deployment
* Use automated deployment tools to streamline the process.
* Conduct thorough before and after deployment.
* Implement rollback mechanisms in case of failures.
* Maintain clear documentation of the deployment process.
* Continuously monitor performance post-deployment

A

true

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

Training users and addressing their concerns post-deployment.

A

User Adaptation -

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

Keeping track of software settings and dependencies.

A

Configuration Management -

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

Need for secure deployment to avoid breaches.

A

Security Vulnerabilities

15
Q

Unexpected failures during deployment.

A

Downtime & Service Interruptions

16
Q

Software must work across different environments.

A

Compatibility Issues

17
Q

Uses two environments, one live and one
idle, for seamless updates.

A

Blue-Green Deployment

18
Q

Deploys new features to a subset of users
before full release.

A
  • Canary Deployment -
18
Q
  • Enables/disables features dynamically without redeploying
A
  • Feature Toggles
18
Q
  • Gradual software rollout to minimize downtime.
A
  • Rolling Deployment
18
Q
  • For this to work, both environments must have the same database schema to share data seamlessly, or a system to synchronize different schema versions.
A

Blue-Green Deployment

18
Q

Deploys the entire system at once, often riskier

A
  • Big Bang Deployment
18
Q

The stable, or older version of the application is always referred to as blue (or red), while the newer version is green (or black).

A

Blue-Green Deployment

19
Q

The new version is set up and production traffic is slowly shifted from the older version to the new one. For instance, during the deployment process, the older version might still handle 75% of all traffic while the newer version handles the
remaining 25%.

A
  • Canary Deployment -
19
Q
  • Updates servers one at a time in a round-robin fashion. This means each server can be tested before moving on to the next, making the deployment process more controlled
    and predictable.
A
  • Rolling Deployment -
19
Q

The software may not always be available to end users even after deployment, which is a possible step in the release process. It can be carried either as part of standard maintenance procedures or in advance of a release.

A

Timing - Software Deployment

19
Q

Enables or disables features dynamically without redeploying the entire system. It
provides flexibility in managing feature releases and allows for A/B testing. But, can lead
to complex code management and technical debt if not handled properly.

A
  • Feature Toggles -
19
Q

Requires a significant amount of coordination and testing to ensure that all the changes
work together as intended. Also requires a larger amount of testing and validation in a
short period of time. The risk is often also increased since all the changes are deployed
in one go and if something goes wrong it’s harder to rollback

A

Big Bang Deployment -

20
Q

When software is released, it becomes accessible to end users. Choosing when to release the program to the public requires considerations that are frequently in line with marketing plans or user expectations

A

Timing - Software Release

21
Q

The technical side of delivering and installing software is the main emphasis of deployment.

A

Scope Software Deployment

22
Q

Ensuring that the program is deployed accurately and effectively in the target environment is the main objective of deployment

A

Goals Software Deployment

22
Q

Release covers more ground than just deployment. It also includes documentation, marketing, and user communication.

A

Scope Software Release

23
Q

Delivering a software version that satisfies quality criteria and offers users value is the main objective of a release

A

Goals Software Release