A company will migrate a Windows-based, three-tier application (application tier, business tier, and Microsoft SQL Server database tier) from on premises to AWS. The application requires SQL Server features such as native backups and Data Quality Services, and needs file sharing between tiers. How should a solutions architect design this architecture?

The correct solution is to host all three tiers on Amazon EC2 instances and use Amazon FSx for Windows File Server for file sharing. This approach allows the use of SQL Server features like native backups and Data Quality Services, which are not fully supported by Amazon RDS for SQL Server. FSx for Windows File Server provides fully managed, highly available file storage that is natively compatible with Windows applications and SMB protocol, making it ideal for file sharing between Windows-based EC2 instances. Incorrect options: Using Amazon FSx File Gateway is incorrect because it is a hybrid cloud storage service for on-premises access to S3, not a native cloud file share for EC2 instances. Hosting the database tier on Amazon RDS is incorrect because RDS for SQL Server does not support all the advanced features like Data Quality Services and native backups required by the application. Using Amazon EFS is incorrect because EFS is a Linux-native file system (NFS) and is not ideal for Windows-based applications requiring SMB file sharing. Using an Amazon EBS volume for file sharing is incorrect because EBS volumes are block storage attached to a single instance, not a shared file system accessible by multiple instances.