A solutions architect must migrate mission-critical legacy Microsoft SQL Server databases to AWS and modernize the data architecture with near-zero downtime. Which migration approach satisfies these constraints?

The correct approach leverages SQL Server's native high-availability tools, such as Always On Availability Groups or database mirroring, to replicate data directly to an Amazon RDS for SQL Server instance. This method enables continuous data synchronization with minimal downtime during cutover, which is crucial for mission-critical databases. Incorrect options: AWS Application Migration Service (AWS MGN) is for rehosting entire servers, not for migrating databases while maintaining near-zero downtime and modernizing to Aurora Serverless in a single step. AWS SCT is for schema conversion, but the overall process described is complex and not ideal for near-zero downtime. AWS DMS can rehost, but using Amazon S3 as an intermediate target and then loading into RDS adds complexity and potential downtime, especially for large, mission-critical databases. AWS Application Migration Service (AWS MGN) rehosts the entire server to EC2. Detaching, moving, and reattaching the database to RDS introduces significant downtime and complexity, failing the near-zero downtime requirement.