04 Modernize Infrastructure and Applications with Google Cloud

Question 1

workload

Answer 1

a specific:
- application
- service or
- capability
that can be run on-prem or in the Cloud. it includes:
- containers
- databases
- virtual machines

Question 2

retiring a workload

Answer 2

removing it from a platform because its unnecessary, not secure, not cost-effective or not compatible with a specific platform.

Question 3

retaining a workload

Answer 3

retain: intentionally kept, typically on-prem or in a hybrid cloud environment, this means that it is managed by the business and will not be subject to the Cloud control.

Question 4

rehosting/Lift and Shift
perks and drawbacks

Answer 4

migration of a workload to the Cloud without changing the architecture.
Perks:
- the simplest way to migrate
Drawbacks:
- not using all the benefits of the Cloud
- making it difficult to change and scaling.

Question 5

replatform/ move and improve
perks and drawbacks

Answer 5

process of migrating while making some changes to the code and architecture.

 Perks
- reducing the cost of the workloads
- entering the Cloud’s benefits
- improving performance on workloads

Drawbacks
- making it complex and time-consuming
- difficult to make the necessary changes
- testing the changes can also be difficult.

Question 6

refactored a workload

Answer 6

changing the code of a workload. an org might refactor a workload to use a Cloud-based microservices architecture or a Cloud-based server-less architecture.

Perks
- more efficient, scalable and secure workloads
- a valuable investment for orgs intending to use the Cloud’s benefits

Drawbacks 
- it can be a complex and time-consuming process

Question 7

reimagined a workload

Answer 7

the process of rethinking of how an org uses the infrastructure to rewrite it and achieve business goals. including Cloud strategy, use of other technologies (AI, ML).

Perks 
- it can help improve their efficiency
- reduce costs
- increase agility
- meet their needs of customers and partners.