An education company uses Amazon WorkSpaces and stores user profiles on an Amazon FSx for Windows File Server file system. The FSx file system is joined to a self-managed Active Directory and uses a DNS alias. As user adoption grows, logon times have become unacceptably slow. The existing file system was created on HDD storage with 16 MBps throughput. A solutions architect must improve file system performance during a scheduled maintenance window with the least administrative effort. What should the solutions architect do?

The correct option allows in-place modification of the existing FSx for Windows File Server, directly addressing the performance bottleneck. Amazon FSx for Windows File Server supports updating throughput capacity and changing storage type (HDD to SSD) for an existing file system. This minimizes administrative effort as it avoids data migration, DNS alias changes, and the creation/deletion of new resources. Disconnecting users ensures no data corruption during the update. The other options involve creating a new file system and migrating data, which requires more administrative effort, potential downtime for data synchronization, and updating the DNS alias. While these methods are viable for data migration, they are not the least administrative effort for this specific performance improvement.