Answer-first summary for fast verification
Answer: Create an FSx for ONTAP instance in the secondary Region. Use NetApp SnapMirror to replicate data from the primary Region to the secondary Region.
## Explanation **Correct Answer: C** - Create an FSx for ONTAP instance in the secondary Region. Use NetApp SnapMirror to replicate data from the primary Region to the secondary Region. ### Why Option C is Correct: 1. **Native DR Solution**: FSx for ONTAP has built-in disaster recovery capabilities using NetApp SnapMirror technology, which is specifically designed for this purpose. 2. **Same Protocols**: The replicated data in the secondary Region will be accessible using the same CIFS and NFS protocols as the primary Region since it's the same FSx for ONTAP technology. 3. **Least Operational Overhead**: This solution leverages the native capabilities of FSx for ONTAP, requiring minimal manual intervention and management. 4. **Automated Replication**: SnapMirror provides continuous, automated replication with minimal RPO (Recovery Point Objective). ### Why Other Options are Incorrect: **Option A**: Creating a Lambda function to copy data to S3 and then replicating it: - **Protocol Incompatibility**: S3 is object storage and doesn't support CIFS/NFS protocols natively - **High Operational Overhead**: Requires custom Lambda development, monitoring, and management - **Complex Recovery**: Would need additional steps to restore data to a file system in the secondary Region **Option B**: Using AWS Backup and copying volumes: - **Manual Process**: Requires manual copying of volumes between Regions - **Not Real-time**: This is more of a backup/restore approach rather than continuous replication - **Higher RPO**: Data loss window would be larger compared to continuous replication - **More Operational Steps**: Multiple manual steps involved in backup, copy, and restore **Option D**: Migrating to Amazon EFS and replicating: - **Protocol Change**: EFS uses NFSv4.1, not CIFS, so protocol requirements aren't fully met - **Migration Overhead**: Requires migrating all data from FSx for ONTAP to EFS - **Different Technology**: EFS has different performance characteristics and management requirements - **Not Native to FSx for ONTAP**: Doesn't leverage the existing FSx for ONTAP investment ### Key Points: - FSx for ONTAP's SnapMirror provides native, automated cross-region replication - Maintains protocol compatibility (CIFS and NFS) - Minimal operational overhead with automated failover capabilities - Supports both synchronous and asynchronous replication modes - Integrated with AWS services for monitoring and management
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company uses Amazon FSx for NetApp ONTAP in its primary AWS Region for CIFS and NFS file shares. Applications that run on Amazon EC2 instances access the file shares. The company needs a storage disaster recovery (DR) solution in a secondary Region. The data that is replicated in the secondary Region needs to be accessed by using the same protocols as the primary Region.
Which solution will meet these requirements with the LEAST operational overhead?
A
Create an AWS Lambda function to copy the data to an Amazon S3 bucket. Replicate the S3 bucket to the secondary Region.
B
Create a backup of the FSx for ONTAP volumes by using AWS Backup. Copy the volumes to the secondary Region. Create a new FSx for ONTAP instance from the backup.
C
Create an FSx for ONTAP instance in the secondary Region. Use NetApp SnapMirror to replicate data from the primary Region to the secondary Region.
D
Create an Amazon Elastic File System (Amazon EFS) volume. Migrate the current data to the volume. Replicate the volume to the secondary Region.