• What is cloud computing?

• a) Delivery of computing services over the internet….

• b) Delivery of storage services over the internet
• c) Delivery of websites accessible via the internet

• Which cloud model uses some datacenters focused on providing cloud services to
anyone that wants them and some datacenters that are focused on a single
customer?

• a) Public cloud
• b) Hybrid cloud…
• c) Multi-cloud

• According to the shared responsibility model, which cloud service type places
the most responsibility on the customer?

• a) Infrastructure as a Service (IaaS)

• b) Platform as a Service (PaaS)
• c) Software as a Service (SaaS)

• Which cloud service type is most suited to a lift-and-shift migration from an on-
premises datacenter to a cloud deployment?

• a) Infrastructure as a Service (IaaS)

• b) Platform as a Service (PaaS)
• c) Software as a Service (SaaS)

• What type of cloud service is commonly used for email and messaging
applications?

• a) Infrastructure as a Service (IaaS)

• b) Platform as a Service (PaaS)
• c) Software as a Service (SaaS)

• What are the four common cloud deployment models?

• a) Private, public, hybrid, multi-cloud

• b) Internal, external, combined, public
• c) Global, local, mixed, distributed

• Which scenario is best suited for Platform as a Service (PaaS)?

• a) Development framework
• b) Lift-and-shift migration
• c) Database configuration
• Which of the following is an example of capital expenditure (CapEx)?

• a) Buying a new datacenter

• b) Paying for cloud services on demand
• c) Leasing a company vehicle

• In a cloud migration process, which phase typically comes first?

• a) Discover
• b) Optimize
• c) Migrate

• What does the “rehost” approach in cloud migration refer to?

• a) Moving a current asset to the cloud with minimal changes

• b) Creating a new cloud-native application
• c) Refactoring an application to fit a PaaS model

cloud migration process –

2. Types of Clouds (Cloud Models)

There are different ways to set up cloud computing, called cloud models:

• Private Cloud: This is like a private company that only you can use. It’s more
secure and gives you more control but is expensive to maintain.
• Public Cloud: Think of this as a public library where anyone can access and use
resources. A third-party provider (like Google or Amazon) owns and manages it.
• Hybrid Cloud: This mixes both private and public clouds, so you can use one
for certain tasks and another for more public resources. For example, a company
might keep sensitive data in a private cloud but store general data on a public
cloud.
• Multi-cloud: Here, a company uses multiple public cloud providers to get
different services. It's like choosing different stores for various products.

3. Cloud Service Models

There are three ways to provide cloud services:

• Infrastructure as a Service (IaaS): You rent physical hardware (like servers

and storage). You manage everything on top of that, like operating systems and
applications. It's like renting the raw materials to build whatever you want.
 • Platform as a Service (PaaS): In this model, you get a ready-to-use platform.
The provider gives you tools to build apps, but you don’t manage the underlying
hardware or operating systems. It's like renting a fully equipped workshop where
you can start working on your projects immediately.
• Software as a Service (SaaS): This is the simplest model. You use fully built
software through the internet, like email or Google Docs. The provider manages
everything, and you just use the service. It's like renting a car that's ready to
drive.

. Capital Expenditure (CapEx) vs. Operating Expenditure (OpEx)

Cloud computing falls under OpEx. This means you don’t need to spend a lot of money
upfront to build data centers or buy hardware. Instead, you pay for services as you use
them, which helps companies save money and only pay for what they need.

For example, in traditional IT, you would have to spend a lot of money buying servers
(CapEx). With cloud computing, you only pay for the resources you use each month
(OpEx), like a subscription.

Discovery: they first check all the software’s etc that needed to be moved. (cloud
service types – iaa..etc)

Assessment: Next, the company decides which parts of their system are ready to be
moved to the cloud. Even cost

Migration Planning:

• Rehost (Lift-and-Shift): Move things as they are, without changing much.

• Refactor: Make small changes to the software so it works better in the cloud. PAAS
to fit this model
• Rearchitect: Completely rebuild the software to make it perfect for the cloud.
Get old doesn’t support with cloud then rearchitect
• rebuild: In this approach, if an old application no longer meets the company’s needs
now, it is rebuilt from scratch as a cloud-native application.
• Replace: This strategy involves replacing existing applications with cloud-based
software solutions rather than migrating the old systems. Like getting 365 instead
having an old email server.

Optimization:
Once the migration is complete, organizations begin to optimize their cloud
environment.
Week4

The digital estate is everything that exists in your current system: apps, data, servers,
and virtual machines (VMs). Before moving to the cloud, you need a complete picture
of your digital estate

For each of these outcomes, the first step starts with a clear understanding of the assets
(applications, data, and VMs) you are responsible for today. Those assets collectively a

There are special tools like Azure Migrate that help with migration(Discovery and
Assessment Tools)

• Azure readiness: Checks if your current systems are ready for the cloud.
• Azure sizing: Estimates how big your cloud resources (like virtual machines)
need to be.
• Azure cost estimation: Calculates how much running your systems in the cloud
will cost.
• Dependency analysis: Helps identify which systems depend on each other so
nothing is left behind during the migration.

Identifying Workloads in Use – before moving to cloud.

• Machine configuration (disks, network cards, etc.), NIC metadata

• Installed applications and roles
• )Performance data, including CPU and memory utilization, disk IOPS, and
throughput

Dependencies are the connections between different systems. For example, one server
might depend on another to function. Before migration, it's important to analyze these
dependencies so that related systems are moved together and nothing breaks.

After analyzing, you can group systems into high-confidence groups for migration. This
prevents disruptions during the move.

10. Prioritizing Workloads for Migration

Not everything can be moved at once, so you’ll need to prioritize:
• Migrate simpler, less critical systems first.
• Make adjustments and learn from each migration before moving more complex
systems.
• Factors to consider include time-to-migrate, business urgency, compliance, and
security needs.

After Assessment:

• Ready for Azure: Can be moved to the cloud as-is.

• Conditionally ready: Can be moved with some minor changes.
 • Not ready for Azure: Needs more work before it can be moved.
• Readiness unknown: There’s not enough data to decide.

Basic Concept Questions:

1. What is the purpose of a digital estate in cloud migration?

o A) To store personal data
o B) To understand all the assets (applications, data, and VMs) you
manage
o C) To manage cloud billing
o D) To secure the cloud environment
Answer: B
2. What does the Discovery and Assessment tool in Azure Migrate do?
o A) Evaluates data storage size in the cloud
o B) Assesses readiness, sizing, and cost estimation for on-premises
machines
o C) Controls cloud security
o D) Tracks cloud resource usage
Answer: B
3. Why is it important to assess the on-premises infrastructure before
migrating to the cloud?
o A) To create new servers
o B) To ensure the environment is safe from cyberattacks
o C) To identify workloads, dependencies, and optimize cost for migration
o D) To delete unused applications
Answer: C
4. What is one goal of the discovery and assessment process?
o A) To create backups for all workloads
o B) To set up cloud cost management
o C) To assess machine readiness for cloud migration
o D) To shut down legacy systems
Answer: C
5. What kind of data is collected by the Azure Migrate appliance during
discovery?
o A) Machine disk, NIC metadata, performance data, and application data
o B) Only application data
o C) Cloud resource usage data
o D) User login history
Answer: A

Tool and Process Questions:

6. Which of the following is part of the Azure readiness assessment?

o A) Checking internet speed
o B) Estimating Azure costs for running on-premises servers
o C) Monitoring security breaches
 o D) Assessing available disk space
Answer: B
7. How does the server assessment tool help with Azure sizing
recommendations?
o A) It suggests the correct cloud regions to use
o B) It provides database security guidelines
o C) It suggests the appropriate VM SKU and disk type based on machine
performance or settings
o D) It reviews user access permissions
Answer: C
8. What is the main benefit of dependency analysis in cloud migration?
o A) To assess the financial cost of migration
o B) To ensure there are no cross-server dependencies left behind during
migration
o C) To prevent cybersecurity threats
o D) To create more virtual machines
Answer: B

Evaluation and Strategy Questions:

9. Which of the following describes machines that are conditionally ready for
Azure migration?
o A) Machines that need major architectural changes before migration
o B) Machines that cannot be migrated at all
o C) Machines that need minor changes as per the remediation guidance
before migration
o D) Machines that are ready to migrate without any changes
Answer: C
10. What factor should be considered when prioritizing workloads for
migration?
o A) Business urgency
o B) Internet bandwidth
o C) Number of cloud administrators
o D) Distance from the nearest data center
Answer: A
11. What does the evaluation of gaps and blockers help with in cloud
migration?
o A) Selecting the best cloud region
o B) Identifying downtime constraints and unsupported features that might
hinder migration
o C) Preventing user access to certain applications
o D) Optimizing disk space usage
Answer: B

Technical and Planning Questions:

12. How does Azure cost estimation assist with migration planning?
 o A) It provides performance data about cloud resources
o B) It estimates the costs for running on-premises servers in Azure
o C) It monitors migration activities
o D) It allocates cloud resources automatically
Answer: B
13. What is a key step when creating an effective cloud migration plan?
o A) Scheduling application backups
o B) Declaring a maintenance window for application migration with
minimal downtime
o C) Assigning user roles and permissions
o D) Reviewing network security policies
Answer: B
14. What should be included in a post-migration testing plan?
o A) Only security testing
o B) Application functionality, performance, and data relationship testing
o C) Cloud usage analysis
o D) Server decommissioning plans
Answer: B

Week5

What is Rehosting (Lift and Shift)? Rehosting, commonly called "lift and shift," is a
cloud migration strategy where you move applications or workloads from on-premise
systems (like your own servers or data centers) directly to the cloud without making any
major changes to the application's code. Essentially, you're moving everything as it is
but taking advantage of the cloud's storage and computing power.

• Why do this?
Sometimes, you need to move to the cloud quickly, and rewriting your software
for the cloud is too costly or time-consuming. Lift and shift allows you to keep
things running smoothly with minimal disruption, while benefiting from the
cloud's flexibility and scalability.

When to Use Rehosting

• Fast Migration Needs:

You should choose rehosting if you need to move your applications to the cloud
quickly without spending time on recoding.
• No Modifications Needed:
If your applications are stable and don’t require significant updates, and you
simply want the benefits of the cloud (e.g., cost savings, flexibility), rehosting is
the best option.
• Scalability:
If your applications were already designed to handle large amounts of data or
 users, you can take advantage of the cloud's ability to scale up or down based on
your needs after migration.(iaas)

- When apps are important to your business, but you don't need immediate
changes to the app capabilities

Rehosting Process

1. Prepare Azure for Migration:

Before you can move your VMs, Azure needs to be set up. This includes
configuring security settings and ensuring that the Azure environment is ready to
host your applications.
2. Prepare On-Premise VMs:
The virtual machines currently running on your own hardware need to be
prepared for the move, which includes ensuring they are stable and compatible
with Azure.
3. Replicate VMs:
The next step is to replicate your VMs in the cloud. This creates a copy of them
on the cloud without turning them off on-premise, ensuring no downtime during
the process.
4. Migrate VMs:
Once everything is ready, the VMs are migrated to the cloud, and your
applications are now running on cloud infrastructure.

1. What is rehosting (lift and shift) in cloud migration?

A. A strategy where applications are rewritten entirely for the cloud

B. A migration method that requires code changes and infrastructure reorganization
C. A migration strategy where applications are moved to the cloud without code
changes
D. A process where only databases are moved to the cloud

Answer: C

2. Why is rehosting often referred to as “lift and shift”?

A. Applications are lifted off their physical servers and rewritten

B. It involves lifting the code into a new programming language
C. The apps are moved (“lifted”) to the cloud and operated without significant changes
(“shift”)
D. It requires physical transportation of servers

Answer: C
3. What are the main benefits of rehosting in cloud migration?

A. Applications can be quickly moved to the cloud without significant downtime

B. It eliminates the need for re-coding and allows fast cloud adoption
C. It offers immediate scalability and cost savings in the cloud
D. All of the above

Answer: D

4. In which situation would you choose rehosting over other migration

strategies?

A. When you want to rewrite the application for cloud-native architectures

B. When you need to move applications quickly to the cloud without modifying them
C. When your application needs a complete infrastructure redesign
D. When the application is no longer needed and will be decommissioned

Answer: B

5. Which of the following environments is often migrated using

rehosting?

A. Applications running on mainframes only

B. Virtual Machines (VMs)
C. Physical servers only
D. Cloud-native applications

Answer: B

6. What is the first step in the rehosting process?

A. Replicate the on-premises VMs

B. Prepare Azure for the migration tool
C. Move the database to the cloud
D. Migrate the VMs to the cloud

Answer: B
7. What is a key feature of rehosting?

A. It requires substantial code changes

B. It moves the application to the cloud without modifying the underlying code
C. It improves application performance immediately after migration
D. It reduces the number of VMs needed for operation

Answer: B

8. Which of the following is an example of an application suitable for

rehosting?

A. A legacy accounting system running on bare metal servers

B. A cloud-native application built for serverless architecture
C. An outdated app requiring complete rewriting
D. A non-critical database that can be shut down

Answer: A

9. What is the role of VMware in the rehosting migration process?

A. It enables rewriting the applications for cloud compatibility

B. It helps move virtual machines to the cloud without needing hardware changes
C. It is used to monitor applications after migration
D. It automates code modification for cloud migration

Answer: B

10. Which case study is an example of a successful lift and shift

migration?

A. Moving a legacy app to microservices architecture

B. Data warehouse with SSIS/SQL Server migration to cloud VMs
C. Transforming a billing application to a cloud-native serverless app
D. Redesigning an entire eCommerce system for cloud architecture

Answer: B
11. When should you consider using rehosting as your migration
strategy?

A. When applications require substantial infrastructure updates

B. When applications need to be moved quickly without modifying their code
C. When you're designing a cloud-native application from scratch
D. When you want to decommission your data center entirely

Answer: B

12. What is the final step in the rehosting process?

A. Prepare the on-premises VMs

B. Migrate the VMs to the cloud
C. Replicate the on-premises VMs to the cloud
D. Perform code changes for the cloud

Answer: B

13. Which of the following is NOT a benefit of rehosting?

A. Quick migration to the cloud

B. No need for application code changes
C. Immediate reduction in cloud costs without optimization
D. Maintaining existing application functionality

Answer: C

14. How does rehosting help businesses with critical apps?

A. It allows them to re-architect the entire app for scalability

B. It ensures minimal downtime and quick cloud migration without app modification
C. It redesigns the app for improved cloud performance
D. It reduces app importance to the business

Answer: B
15. Which of the following is an example of software typically rehosted
during migration?

A. Commercial Off-the-Shelf Software (COTS)

B. Cloud-native microservices
C. Edge computing apps
D. Serverless apps

Answer: A

Week6

Refactoring in Cloud Migration

What is Refactoring? Refactoring, also called repackaging, involves making small

changes to your apps so they can use cloud services like Azure's Platform as a Service
(PaaS). The goal is to adjust your app just enough to take advantage of cloud features
without completely rebuilding it.

For example, you might move an existing app to services like:

• Azure App Service: A cloud service for hosting web apps.

• Azure Kubernetes Service (AKS): A managed service for running
containerized applications.

You can also move databases to cloud platforms like:

• Azure SQL Database Managed Instance

• Azure Database for MySQL
• Azure Database for PostgreSQL
• Azure Cosmos DB (for non-relational databases)

Example: Moving a Web App to Azure App Service(PAAS OPTION

VERY SIMILAR TO HEROKU)

• Azure App Service is a platform where you can host your web apps without
worrying about the underlying infrastructure (servers, operating systems, etc.).
• Microsoft manages everything, including updates, load balancing, and scaling
(adjusting the resources your app needs based on demand).
• This is a great option if you don’t want to manage your own servers but still
want to run web applications.

Key benefits:

• You only need to focus on your app, as Azure handles all the background setup.
 • You can scale up (add more power) or scale down (reduce power) based on
how many people are using your app.

Azure App Service Migration Assistant

This is a tool provided by Azure to help you move your web apps to Azure App
Service. It does two things:

1. Assessment: It checks if your web app can be moved to the cloud without
needing major changes. It looks at things like the app's dependencies (other
software the app relies on).

It performs an assessment of a specific web app installed on Windows Server. It

evaluates the dependencies of the web app to determine whether a migration to
Azure App Service is possible without modification to the web app.

2. Migration: If your app passes the assessment, it can be moved. The Migration
Assistant will move the app, create the necessary cloud resources, and configure
them in your Azure account.

If the assessment proves that the web app can be migrated, the Migration
Assistant performs the migration. You need to give the Migration Assistant access
to your Azure account, select which resource group you want to use, and select a
name for the web app, among other details.

Steps in the migration process:

by collecting key details from you about your Azure account and then performs the
migration

• The assistant asks for information like which resource group, region and any
other selection we have made.
• It then packages (zips) your app’s files and uses the App Service deployment
• API to deploy them
• Lastly, it helps set up additional options, such as a hybrid connection, which
lets your cloud app communicate with on-premises systems.

After a successful migration, you'll need to perform any post-migration tasks

1. What is refactoring in the context of cloud migration?

A. Moving applications to the cloud without any code changes

B. Making small changes to applications to use cloud services like PaaS
C. Rewriting the entire application for cloud compatibility
D. Only migrating databases to the cloud
Answer: B

2. Why is refactoring also referred to as repackaging?

A. It involves completely rewriting the application

B. It includes making minimal changes to an application so it can connect to cloud
services
C. It packages all app files into a new programming language
D. It involves only changing the underlying infrastructure, not the app code

Answer: B

3. Which of the following is an example of a service you can migrate to

during refactoring?

A. Azure App Service

B. Azure Kubernetes Service (AKS)
C. Azure SQL Database Managed Instance
D. All of the above

Answer: D

4. When should you consider refactoring an application for cloud

migration?

A. When you need to move an app quickly without code changes

B. When you want to use innovative DevOps practices, such as continuous integration
and containers
C. When the application is no longer needed
D. When the application is already cloud-native

Answer: B

5. Which type of database can be moved using refactoring?

A. Azure SQL Database Managed Instance

B. Azure Cosmos DB
C. Azure Database for MySQL
D. All of the above

Answer: D

6. What is a key benefit of using Azure App Service?

A. It allows you to run web apps without managing the underlying infrastructure
B. It requires you to rewrite the entire app
C. It provides full control over operating system updates
D. It can only handle small-scale apps

Answer: A

7. What does the Azure App Service Migration Assistant do first?

A. Assesses the app to check if it can be migrated without major changes

B. Migrates the app to Azure immediately
C. Rewrites the app’s code for cloud compatibility
D. Deletes the app from the current server

Answer: A

8. Which of the following best describes the process of refactoring?

A. Complete rewriting of the code for cloud-native development

B. Repackaging the app with minimal changes so it can utilize cloud services
C. Only migrating the database and not the application
D. Moving the entire data center to the cloud without any changes

Answer: B

9. Which scenario is suitable for refactoring?

A. When you need to move apps quickly without modifying the code
B. When you want to add new cloud-specific features like container support
C. When the application is no longer in use
D. When you need to redesign the entire infrastructure for cloud
Answer: B

10. What is the main difference between refactoring and rehosting?

A. Refactoring involves code changes, while rehosting does not

B. Rehosting involves code changes, while refactoring does not
C. Refactoring only applies to databases, while rehosting applies to apps
D. Refactoring is slower and more costly than rehosting

Answer: A

11. When using the Azure App Service Migration Assistant, what must be
provided to begin migration?

A. Source code for the app

B. Access to your Azure account and resource group details
C. A complete redesign of the app’s architecture
D. A new server setup for the app

Answer: B

12. Which of the following features does Azure App Service offer for
managing web apps?

A. Automatic scaling and load balancing

B. Full control over the app’s infrastructure
C. Only basic hosting without scaling options
D. The ability to manage on-premise servers from the cloud

Answer: A

13. What kind of apps can benefit the most from refactoring?

A. Apps that need to be moved quickly without modification

B. Apps that need to take advantage of cloud features like containers and DevOps
C. Apps that are outdated and no longer supported
D. Apps that are already running in the cloud
Answer: B

14. Which tool can help with assessing and migrating apps to Azure App
Service?

A. Azure Data Migration Service

B. Azure App Service Migration Assistant
C. Azure Monitor
D. Azure Cost Management

Answer: B

15. After migrating an app using the Azure App Service Migration
Assistant, what tasks might still need to be done?

A. Full code rewriting for cloud compatibility

B. Setting up hybrid connections and performing post-migration tasks
C. Moving databases manually
D. Redesigning the app’s front-end

Answer: B

Week21

Financial Considerations in Cloud Adoption

Moving to the cloud isn't just about technology—it’s also a financial decision. Here are
key points to consider:

• Financial transformation: Shifting to the cloud changes how businesses think

about costs. Instead of paying large amounts upfront for hardware and software
(CAPEX), they switch to paying only for the cloud services they actually use
(OPEX).
• Cost savings: Companies save money by using only the computing resources
they need and reducing the need for large, expensive data centers.

Cloud Adoption Planning

To successfully adopt the cloud, companies go through different stages or "horizons":

 1. Migration and Modernization: This is where businesses move existing
systems to the cloud with little or no changes.
2. Operation Modernization: Here, companies start optimizing their operations
using cloud tools to increase efficiency.
3. Advanced Modernization: At this stage, businesses explore more advanced
cloud features like artificial intelligence (AI) and big data analytics.
4. Innovation and Growth: Finally, companies use the cloud to drive innovation
and create new business opportunities.

Business Outcomes of Cloud Adoption

Business outcomes refer to the measurable benefits that an organization wants to

achieve by moving to the cloud. These can be financial, operational, or customer-
focused.

1. Financial Outcomes: Moving to the cloud can save money by reducing the
need to buy and maintain expensive physical servers and data centers.
Companies move from capital expenses (CAPEX) to operating expenses
(OPEX), meaning they pay for the cloud services they use, instead of making
big upfront investments.
2. Agility Outcomes: The cloud allows businesses to adapt quickly to changing
market conditions. For example, they can deploy new applications faster or
respond to customer needs more easily.
3. Reach Outcomes: Companies can expand globally by using cloud services that
are available in different countries, ensuring they comply with local regulations
and meet the needs of users worldwide.
4. Customer Engagement Outcomes: The cloud helps companies interact more
effectively with their customers, offering services that meet their needs and
providing better experiences.
5. Performance Outcomes: Businesses expect the cloud to provide reliable
performance, and failing to do so can hurt a company's reputation.
6. Sustainability Outcomes: Many companies are now focused on environmental
goals. Cloud adoption can help reduce a company’s carbon footprint by
optimizing energy use and reducing waste.

Businesses choose to adopt the cloud for various reasons. These motivations can
generally be grouped into two categories: Migration and Innovation.

• Migration: This is when a company moves its existing systems and data to the
cloud. Examples of migration drivers include:
o Closing down a data center to save costs
o Merging with or acquiring another company
o Reducing capital expenses (like buying physical servers)
o Meeting new legal or regulatory requirements
o Improving the stability of IT systems
 o Reducing technical complexity or reliance on certain vendors
• Innovation: Cloud adoption can also help companies develop new capabilities
or expand their operations. For example:
o Scaling up to handle more customers or users
o Introducing new services or products
o Reaching new geographic regions
o Offering better customer experiences and services

These motivations often happen together, meaning a business might move to the cloud
for both migration and innovation reasons.

What are the two main motivations for cloud adoption? A. Migration and
Security
B. Migration and Innovation
C. Innovation and Performance
D. Security and Cost

Answer: B

Which of the following is an example of a business motivation for cloud

adoption? A. Data center exit
B. Improving customer experience
C. Preparing for new technical capabilities
D. All of the above

Answer: D

How does cloud adoption help with financial outcomes? A. By reducing capital
expenses and moving to a pay-as-you-go model
B. By eliminating the need for developers
C. By increasing upfront hardware costs
D. By creating more technical debt

Answer: A

What is the difference between CAPEX and OPEX in cloud adoption? A.

CAPEX is the cost of servers, and OPEX is the ongoing cost of cloud services
B. OPEX is the initial investment in cloud migration, and CAPEX is the monthly billing
C. CAPEX is free, while OPEX is expensive
D. There is no difference between CAPEX and OPEX

Answer: A

What is a technical benefit of using the cloud for scalability? A. You can turn off
workloads when not needed
B. You must always run workloads at full capacity
C. You can only scale during business hours
D. You can't scale resources dynamically

Answer: A