Module 9: Migration and Innovation (Part 1) Flashcards
What are the six core perspectives of the AWS Cloud Adoption Framework (AWS CAF)?
The six core perspectives of the AWS Cloud Adoption Framework are:
Business Perspective: Aligns IT with business needs and prioritizes cloud adoption initiatives.
People Perspective: Supports organizational change management strategy and identifies skill and process requirements.
Governance Perspective: Aligns IT strategy with business strategy, manages cloud investments, and ensures business governance.
Platform Perspective: Provides principles and patterns for implementing new solutions and migrating workloads to the cloud.
Security Perspective: Ensures security objectives are met through the selection and implementation of security controls.
Operations Perspective: Enables the operation and management of IT workloads, aligns with business operations, and defines operating procedures.
What is the focus of the Business, People, and Governance Perspectives in the AWS CAF?
The Business, People, and Governance Perspectives of the AWS CAF focus on business capabilities. The Business Perspective aligns IT with business needs and creates a business case for cloud adoption. The People Perspective supports change management strategy and evaluates organizational structures. The Governance Perspective aligns IT and business strategy, maximizes business value, and manages cloud investments.
What is the focus of the Platform, Security, and Operations Perspectives in the AWS CAF?
The Platform, Security, and Operations Perspectives of the AWS CAF focus on technical capabilities. The Platform Perspective provides architectural principles and patterns for implementing solutions on the cloud. The Security Perspective ensures security objectives are met through the selection and implementation of security controls. The Operations Perspective enables the operation and management of IT workloads and defines operating procedures.
What are some common roles associated with each perspective in the AWS CAF?
Business Perspective: Business managers, finance managers, budget owners, strategy stakeholders.
People Perspective: Human resources, staffing, people managers.
Governance Perspective: Chief Information Officer (CIO), program managers, enterprise architects, business analysts, portfolio managers.
Platform Perspective: Chief Technology Officer (CTO), IT managers, solutions architects.
Security Perspective: Chief Information Security Officer (CISO), IT security managers, IT security analysts.
Operations Perspective: IT operations managers, IT support managers.
What are the six migration strategies commonly used when migrating applications to the cloud?
The six migration strategies are:
Rehosting: Moving applications without changes (also known as “lift-and-shift”).
Replatforming: Making a few cloud optimizations without changing the core architecture of the application.
Refactoring: Reimagining the application’s architecture and development using cloud-native features.
Repurchasing: Moving from a traditional license to a software-as-a-service model.
Retaining: Keeping critical applications in the source environment due to various reasons, such as major refactoring requirements.
Retiring: Removing applications that are no longer needed.
What is the concept of rehosting in migration strategies?
Rehosting, also known as “lift-and-shift,” involves moving applications to the cloud without making any changes to the application itself. It is commonly used in large legacy migrations where the focus is on quickly migrating applications to meet a business case.
What is the purpose of replatforming in migration strategies?
Replatforming, also known as “lift, tinker, and shift,” involves making a few optimizations to the application during the migration process. These optimizations aim to achieve tangible benefits without changing the core architecture of the application.
What is the concept of refactoring/re-architecting in migration strategies?
Refactoring or re-architecting involves reimagining how an application is architected and developed using cloud-native features. This strategy is driven by a strong business need to add new features, improve scalability, or enhance performance that would be challenging to achieve in the application’s existing environment.
What does the repurchasing migration strategy involve?
The repurchasing strategy involves migrating from a traditional software license model to a software-as-a-service (SaaS) model. It typically involves moving from an on-premises or self-hosted solution to a cloud-based service, such as migrating from a CRM system to Salesforce.com.
What is the purpose of the retaining migration strategy?
The retaining strategy involves keeping critical applications in the source environment instead of migrating them to the cloud. This may be due to various reasons, such as the need for major refactoring before migration or postponing migration to a later time.
What does the retiring migration strategy entail?
The retiring strategy involves removing applications that are no longer needed. These applications are deemed unnecessary and can be safely decommissioned from the infrastructure.