Cloud Migration Strategies Questions and Answers for Viva

Answer-1: Cloud migration is the process of moving data, applications, or other business elements from an on-premises environment to a cloud infrastructure.

Answer-2: To achieve scalability, cost savings, improved performance, flexibility, and access to advanced cloud services.

Answer-3: Rehost, Refactor, Revise, Rebuild, and Replace.

Answer-4: Rehosting, or 'lift and shift', involves moving applications to the cloud with minimal or no changes.

Answer-5: Refactoring means making small optimizations or changes to an application to better suit the cloud environment without rewriting the entire application.

Answer-6: Revising involves modifying or extending the application code significantly to adapt to the cloud.

Answer-7: Rebuilding is rewriting the application from scratch using cloud-native technologies.

Answer-8: Replace means discarding the existing application and moving to a completely new cloud-based solution, often SaaS.

Answer-9: Application complexity, business goals, budget, timeline, and cloud provider capabilities.

Answer-10: Fast migration, minimal upfront cost, and reduced risk as applications remain largely unchanged.

Answer-11: Missed opportunities for cloud optimization and possibly higher operational costs.

Answer-12: Simple or legacy applications that require quick migration without major changes.

Answer-13: Better scalability, performance improvements, and cost optimization.

Answer-14: Requires development effort, testing, and potential downtime.

Answer-15: Using multiple strategies across different applications or phases for a tailored migration.

Answer-16: Crucial for choosing the right strategy and understanding dependencies and risks.

Answer-17: They automate and simplify data transfer, minimize downtime, and help track progress.

Answer-18: AWS Migration Hub, Azure Migrate, Google Cloud Migrate, CloudEndure.

Answer-19: Moving databases and storage to the cloud, often requiring data validation and synchronization.

Answer-20: Data loss, latency, format incompatibilities, and downtime risks.

Answer-21: Updating or rebuilding applications to leverage cloud-native features and architecture.

Answer-22: Cloud-native apps are designed for scalability, resilience, and flexibility using microservices and containers.

Answer-23: Thorough planning, stakeholder involvement, testing, and phased migration.

Answer-24: Mapping dependencies, migrating in correct order, and testing integration points.

Answer-25: Migrating a small, non-critical part of the system to test the migration process.

Answer-26: To restore the previous state quickly if the migration fails or causes issues.

Answer-27: Use live migration tools, phased rollout, and robust rollback mechanisms.

Answer-28: Another name for rehosting strategy focusing on moving applications as-is to the cloud.

Answer-29: It requires updating security policies, configurations, and compliance to protect data and apps.

Answer-30: Designing migration plans, selecting strategies, and ensuring alignment with business goals.

Answer-31: Data integration, feature gaps, and user adoption issues.

Answer-32: Distributing applications or data across multiple cloud providers for redundancy or optimization.

Answer-33: Through functional testing, performance testing, and user acceptance testing.

Answer-34: Helps manage user expectations and adoption of new cloud systems.

Answer-35: Depends on scope and strategy but can range from weeks to months.

Answer-36: Migration costs, ongoing cloud expenses, training, and potential downtime impact.

Answer-37: Automates repetitive tasks, reduces errors, and accelerates the migration process.

Answer-38: Modifying an app to run on a different platform without full redevelopment.

Answer-39: Often rehosting or refactoring depending on complexity and future goals.

Answer-40: By validating data before and after migration and using checksums.

Answer-41: Provides tools, expertise, and best practices to ensure successful migration.

Answer-42: Poor planning, underestimating costs, ignoring security, and lack of testing.

Answer-43: By achieving uptime, performance, cost goals, and minimal disruption.

Answer-44: Moving workloads incrementally rather than all at once to reduce risks.

Answer-45: Using replication, synchronization, and failover techniques.

Answer-46: Ensuring data and applications meet regulatory standards post-migration.

Answer-47: A detailed plan outlining steps, timelines, and responsibilities for migration.

Answer-48: Encourages automation, continuous integration, and delivery aligned with cloud environments.

Answer-49: Evaluating all applications to determine migration strategy and priority.

Answer-50: By decoupling, refactoring, or integrating middleware for smoother migration.