Amazon AWS Certified Solutions Architect - Professional SAP-C02 Bundle

Although Model future database demand and evaluate appropriate renewal commitment options can be valid when A critical database has one-year reserved capacity that will expire next week, it targets a different technical condition. Renewal should reflect forecasted database utilization rather than blindly copying prior capacity.

This alternative, Use AWS Budgets forecast alerts filtered to the required scope, is appropriate when A product owner wants forecast-based warning before an AWS account exceeds its monthly budget. Forecast alerts flag expected overruns before final charges post.

For the separate situation An organization has steady eligible EC2 and Fargate spend but no capacity commitments, Analyze baseline usage and evaluate an appropriately sized Compute Savings Plan could be useful. Flexible compute commitment discounts can cover stable eligible usage across platforms.

This alternative, Collect stakeholder ownership, classification, residency and recovery requirements during portfolio assessment, is appropriate when An organization must identify application owners and data-classification constraints before deciding target accounts. Governance and data location requirements affect feasible migration destinations.

For the separate situation A regulated application has proprietary hardware dependencies that cannot run on cloud virtualization, Mark it for retain or alternate remediation rather than blindly rehosting the unsupported component could be useful. Technical and licensing constraints can make direct cloud migration infeasible.

Although Group tightly coupled services and databases into a coordinated dependency-aware migration wave can be valid when A critical payment service depends synchronously on five internal databases shared by other applications, it targets a different technical condition. Dependency-aware grouping reduces broken cross-environment application calls during cutover.

Use AWS Transform discovery and migration planning to build a dependency-aware inventory solves the related scenario A new AWS migration program lacks a trusted inventory of 600 on-premises servers and their runtime dependencies; aWS Transform supports new customer discovery and wave planning while Application Discovery Service no longer accepts new customers.

Although Mark it for retain or alternate remediation rather than blindly rehosting the unsupported component can be valid when A regulated application has proprietary hardware dependencies that cannot run on cloud virtualization, it targets a different technical condition. Technical and licensing constraints can make direct cloud migration infeasible.

Group tightly coupled services and databases into a coordinated dependency-aware migration wave would address a different requirement: A critical payment service depends synchronously on five internal databases shared by other applications. Dependency-aware grouping reduces broken cross-environment application calls during cutover.

Use AWS Transform for unified migration portfolio planning and progress visibility solves the related scenario A company launching a new migration program in 2026 needs coordinated assessment and migration-wave progress; aWS Transform is the successor for new customers because Migration Hub stopped accepting new accounts in 2025.

Collect stakeholder ownership, classification, residency and recovery requirements during portfolio assessment would address a different requirement: An organization must identify application owners and data-classification constraints before deciding target accounts. Governance and data location requirements affect feasible migration destinations.

This alternative, Use AWS Transform discovery and migration planning to build a dependency-aware inventory, is appropriate when A new AWS migration program lacks a trusted inventory of 600 on-premises servers and their runtime dependencies. AWS Transform supports new customer discovery and wave planning while Application Discovery Service no longer accepts new customers.

Although Collect stakeholder ownership, classification, residency and recovery requirements during portfolio assessment can be valid when An organization must identify application owners and data-classification constraints before deciding target accounts, it targets a different technical condition. Governance and data location requirements affect feasible migration destinations.

Use AWS Transform discovery and migration planning to build a dependency-aware inventory would address a different requirement: A new AWS migration program lacks a trusted inventory of 600 on-premises servers and their runtime dependencies. AWS Transform supports new customer discovery and wave planning while Application Discovery Service no longer accepts new customers.

This alternative, Mark it for retain or alternate remediation rather than blindly rehosting the unsupported component, is appropriate when A regulated application has proprietary hardware dependencies that cannot run on cloud virtualization. Technical and licensing constraints can make direct cloud migration infeasible.

Use AWS Transform for unified migration portfolio planning and progress visibility would address a different requirement: A company launching a new migration program in 2026 needs coordinated assessment and migration-wave progress. AWS Transform is the successor for new customers because Migration Hub stopped accepting new accounts in 2025.

This alternative, Mark it for retain or alternate remediation rather than blindly rehosting the unsupported component, is appropriate when A regulated application has proprietary hardware dependencies that cannot run on cloud virtualization. Technical and licensing constraints can make direct cloud migration infeasible.

Group tightly coupled services and databases into a coordinated dependency-aware migration wave solves the related scenario A critical payment service depends synchronously on five internal databases shared by other applications; dependency-aware grouping reduces broken cross-environment application calls during cutover.

For the separate situation An application can move from self-managed MySQL to Amazon RDS with only minor connection changes, Choose replatform to a managed database with targeted compatibility changes could be useful. Replatforming reduces operations burden without a full application redesign.

Choose repurchase or replace with the approved SaaS offering solves the related scenario A redundant internal reporting tool has been superseded by an approved third-party SaaS; replacing an application with SaaS avoids migrating its custom software stack.

Choose retire after documented ownership approval and data disposition would address a different requirement: An obsolete internal portal has no active users or regulatory retention need. Retiring unnecessary software removes migration cost and operational liability.

Choose repurchase or replace with the approved SaaS offering solves the related scenario A redundant internal reporting tool has been superseded by an approved third-party SaaS; replacing an application with SaaS avoids migrating its custom software stack.

Choose retire after documented ownership approval and data disposition would address a different requirement: An obsolete internal portal has no active users or regulatory retention need. Retiring unnecessary software removes migration cost and operational liability.

This alternative, Choose refactor or re-architect with staged service extraction, is appropriate when A monolithic application must be decomposed into independent event-driven services to meet new business goals. Refactoring changes the architecture rather than merely the host or runtime.

Although Choose repurchase or replace with the approved SaaS offering can be valid when A redundant internal reporting tool has been superseded by an approved third-party SaaS, it targets a different technical condition. Replacing an application with SaaS avoids migrating its custom software stack.

Choose rehost and use an appropriate server migration mechanism would address a different requirement: A legacy VM can run unchanged on EC2 and must move rapidly with little application change. Rehosting keeps application architecture largely intact while changing infrastructure location.

For the separate situation An application can move from self-managed MySQL to Amazon RDS with only minor connection changes, Choose replatform to a managed database with targeted compatibility changes could be useful. Replatforming reduces operations burden without a full application redesign.

Choose rehost and use an appropriate server migration mechanism would address a different requirement: A legacy VM can run unchanged on EC2 and must move rapidly with little application change. Rehosting keeps application architecture largely intact while changing infrastructure location.

This alternative, Choose replatform to a managed database with targeted compatibility changes, is appropriate when An application can move from self-managed MySQL to Amazon RDS with only minor connection changes. Replatforming reduces operations burden without a full application redesign.

Choose retire after documented ownership approval and data disposition solves the related scenario An obsolete internal portal has no active users or regulatory retention need; retiring unnecessary software removes migration cost and operational liability.

This alternative, Choose refactor or re-architect with staged service extraction, is appropriate when A monolithic application must be decomposed into independent event-driven services to meet new business goals. Refactoring changes the architecture rather than merely the host or runtime.

Choose repurchase or replace with the approved SaaS offering solves the related scenario A redundant internal reporting tool has been superseded by an approved third-party SaaS; replacing an application with SaaS avoids migrating its custom software stack.

Although Choose rehost and use an appropriate server migration mechanism can be valid when A legacy VM can run unchanged on EC2 and must move rapidly with little application change, it targets a different technical condition. Rehosting keeps application architecture largely intact while changing infrastructure location.