What should the solutions architect do to meet these requirements?
Reconfigure the deployment type to Multi-AZ for this Amazon FSx file system.
Create a new Amazon FSx file system with a deployment type of Multi-AZ. Use AWS DataSync to transfer data to the new Amazon FSx file system. Point users to the new location.
Create a second Amazon FSx file system with a deployment type of Single-AZ 2. Use AWS DataSync to keep the data in sync. Switch users to the second Amazon FSx file system in the event of failure.
Use the AWS Management Console to take a backup of the Amazon FSx file system. Create a new Amazon FSx file system with a deployment type of Multi- AZ. Restore the backup to the new Amazon FSx file system. Point users to the new location.
Explanations:
You cannot change the deployment type of an existing Amazon FSx file system from Single-AZ to Multi-AZ. The only way to achieve a Multi-AZ configuration is to create a new file system with the desired deployment type.
This option involves creating a new Amazon FSx file system configured for Multi-AZ and using AWS DataSync to transfer data. This approach minimizes downtime because the original file system remains operational during the data transfer. After the transfer, users can be pointed to the new file system, aligning with the company’s policy for high availability.
This option does not align with the company’s requirement for high availability since it creates another Single-AZ file system. In the event of a failure, users would still experience downtime, and it does not fulfill the policy of Multi-AZ deployments.
While this option creates a new Multi-AZ file system, it requires taking a backup first. This process involves downtime while the backup is being taken, which does not minimize downtime effectively. Additionally, restoring a backup can lead to data loss if changes occurred after the backup was taken.