Cloud Migration Quiz: Lift-and-Shift Or Refactor?

1. Which application characteristic makes it a good candidate for lift-and-shift?

Stable, well-architected app with few dependencies

Highly complex microservices architecture

Requires constant code modifications

Uses only proprietary on-premises databases

2. Which governance concern is critical when migrating to multi-cloud environments?

Consistent security policies, compliance, and cost management across clouds

Matching cloud colors to office décor

Ensuring all staff have the same phone model

Limiting vendor relationships to one provider

3. What is 'application dependency mapping' used for in migration planning?

Identify interconnections between applications and systems

Create office floor plans

Calculate employee salaries

Determine internet bandwidth needs only

4. Which cloud migration phase typically requires the most extensive testing?

Cutover and post-migration validation

Initial planning phase

Budget approval stage

Vendor selection process

5. In cloud migration, what does 'data gravity' refer to?

Tendency of applications to stay near large data repositories

Weight of physical servers

Speed of network connections

Cost of cloud storage per gigabyte

6. What is a 'landing zone' in cloud migration?

Pre-configured cloud environment with security and governance baseline

Physical server location in data center

Final destination after migration ends

Testing area only used once

7. Which factor most influences the choice between lift-and-shift and refactoring?

Business timeline, budget, and application complexity

Cloud provider's color scheme

Number of IT certifications held

Current office location

8. What does 'database heterogeneity' present as a challenge in cloud migration?

Multiple database types require different migration strategies

All databases migrate identically

Cloud doesn't support databases

Databases automatically become compatible

9. During refactoring for cloud migration, which architectural pattern is most cloud-native?

Microservices with containerization and serverless components

Single monolithic application

Tightly coupled legacy modules

Disconnected batch-processing systems

10. What is 'cloud sprawl' in the context of migration?

Uncontrolled proliferation of cloud resources and accounts

Slow internet connection to cloud

Too many cloud providers in one region

Excessive employee cloud training

11. What is the primary advantage of a lift-and-shift cloud migration approach?

Fastest time to cloud with minimal code changes

Optimized cloud-native application performance

Reduced licensing costs immediately

Automatic security compliance across all regions

12. What is the primary purpose of a migration pilot or proof-of-concept phase?

Validate approach, identify risks, and build team confidence

Delay migration indefinitely

Prove the cloud provider is best in market

Reduce IT staff before full migration

13. In lift-and-shift migration, why do organizations often face higher-than-expected cloud costs?

Apps not optimized for cloud resource consumption patterns

Cloud providers intentionally overcharge

Internet connectivity is more expensive

Licensing fees double automatically

14. What does the 'cloud readiness assessment' primarily measure?

Organization's technical and operational capability to migrate

Cloud provider's uptime percentage

Number of IT staff available

Budget allocated for marketing

15. Which cloud migration pattern is 'replatform' most similar to?

Lift-and-shift with minimal optimization

Complete application rewrite

Database-only migration

Hybrid cloud forever

16. During cloud migration assessment, what should be evaluated first?

Application dependencies, compatibility, and cost-benefit analysis

Cloud provider's marketing claims

Vendor discounts available this quarter

Competitor's migration timeline

17. What is a key benefit of refactoring applications before cloud migration?

Shorter overall project timeline

Better utilization of cloud-native services and cost optimization

Elimination of all security vulnerabilities

Guaranteed zero downtime during migration

18. Which risk is most significant when using lift-and-shift migration?

Missing cloud-native optimizations and cost inefficiencies

Complete loss of application functionality

Inability to access cloud services

Automatic compliance violation in all regions

19. In cloud migration planning, what does 'rehost' typically mean?

Move applications to cloud without code modification

Rebuild the entire application architecture

Containerize all legacy applications

Replace on-premises databases with cloud alternatives

20. Which scenario best justifies a refactor-before-migration strategy?

Legacy monolithic app with high cloud costs in current form

Small web app with minimal performance demands

Application already optimized for on-premises

Quick proof-of-concept deadline within one month

Cloud Migration Quiz: Lift-and-Shift or Refactor?